About ${DYNAMIC_CONTENT} variable is some msgids

[Vincent Fretin]

Hi,

I didn't test it. When you have  ${DYNAMIC_CONTENT} in a msgid, should
we keep it in the msgstr?
I see that plone-sv.po has removed it for the following msgid:

+# ${DYNAMIC_CONTENT} rendreras ordagrant utan substitution!
 #. Default: "(${location}${DYNAMIC_CONTENT}from ${start} to ${end})"
 #: CMFPlone/skins/plone_content/folder_listing.pt:102
 msgid "label_event_byline"
-msgstr "(${location}${DYNAMIC_CONTENT}från ${start} till ${end})"
+msgstr "(${location}, från ${start} till ${end})"

 I don't understand your comment here Karl Johan Kleist, I don't speak
Svenska. :-)

Regards
--
Vincent Fretin

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Hanno Schlichting-3]

Vincent Fretin wrote:
> I didn't test it. When you have  ${DYNAMIC_CONTENT} in a msgid, should
> we keep it in the msgstr?

No, you should fix the page template. If ${DYNAMIC_CONTENT} shows up in
a message, there's something wrong in the page template.

> I see that plone-sv.po has removed it for the following msgid:
>
> +# ${DYNAMIC_CONTENT} rendreras ordagrant utan substitution!
>  #. Default: "(${location}${DYNAMIC_CONTENT}from ${start} to ${end})"
>  #: CMFPlone/skins/plone_content/folder_listing.pt:102
>  msgid "label_event_byline"
> -msgstr "(${location}${DYNAMIC_CONTENT}från ${start} till ${end})"
> +msgstr "(${location}, från ${start} till ${end})"

Looking at the template is has a very weird 'tal:replace="string:, "' on
a tag with an tal:content and i18n:name statement. That's simply invalid
TAL markup. From a short glance I'd just remove the tal:replace and
everything should be fine.

Hanno


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Vincent Fretin]

There is one other
#. Default: "${action} by ${actor_with_home} ${actor_without_home} on
${time} (x: ${DYNAMIC_CONTENT})"
#: plone.app.layout/plone/app/layout/viewlets/content_history.pt:54
msgid "history_action"
msgstr ""

Can you take care of it? Tell me when you have commited the fix, then
I'll resync po files.
--
Vincent Fretin

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Vincent Fretin]

On Sun, Mar 22, 2009 at 7:25 PM, Hanno Schlichting <[hidden email]> wrote:
>> +# ${DYNAMIC_CONTENT} rendreras ordagrant utan substitution!
>>  #. Default: "(${location}${DYNAMIC_CONTENT}from ${start} to ${end})"
>>  #: CMFPlone/skins/plone_content/folder_listing.pt:102
>>  msgid "label_event_byline"
>> -msgstr "(${location}${DYNAMIC_CONTENT}från ${start} till ${end})"
>> +msgstr "(${location}, från ${start} till ${end})"

About this string.
If you don't specify a location in the event, in the folder view you
will see for example:
(${location},  från 2009-03-22 till 2009-03-25)"
There should be two i18n strings in the template. One with location,
and one without I think.
--
Vincent Fretin

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Vincent Fretin]

There is one in cmfeditions as well:
#. Default: "${DYNAMIC_CONTENT} (${date})"
#: CMFEditions/browser/diff.pt:56
msgid "label_history_version"
msgstr "${DYNAMIC_CONTENT} (${date})"

Translators, don't put ${DYNAMIC_CONTENT} in your msgstr, it will
appear as is in Plone.
When the templates will be fixed, I will resync po files and you will
have to unfuzzy those 3 messages.
--
Vincent Fretin

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Karl Johan Kleist]

Vincent,

in English, my comment was "${DYNAMIC_CONTENT} is rendered verbatim without substitution".

So, as a temp. solution to avoid uglyness in the gui I removed it from the translation string and filed https://dev.plone.org/plone/ticket/9042 .

Vincent Fretin wrote:

 When you have  ${DYNAMIC_CONTENT} in a msgid, should
we keep it in the msgstr?
I see that plone-sv.po has removed it for the following msgid:

+# ${DYNAMIC_CONTENT} rendreras ordagrant utan substitution!
 #. Default: "(${location}${DYNAMIC_CONTENT}from ${start} to ${end})"
 #: CMFPlone/skins/plone_content/folder_listing.pt:102
 msgid "label_event_byline"
-msgstr "(${location}${DYNAMIC_CONTENT}från ${start} till ${end})"
+msgstr "(${location}, från ${start} till ${end})"

 I don't understand your comment here Karl Johan Kleist, I don't speak
Svenska. :-)

[Vincent Fretin]

Hi,

I fixed all three templates (https://dev.plone.org/plone/ticket/9042)
and synched plone and cmfeditions po files.
Please remove any DYNAMIC_CONTENT of your translation.

Regards
--
Vincent Fretin

------------------------------------------------------------------------------
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Vincent Fretin]

Hi,

There are ${DYNAMIC_CONTENT} left in
cmfeditions-cs.po
cmfeditions-es.po
cmfeditions-ja.po
plone-cs.po
plone-cs.po
plone-es.po
plone-es.po
plone-it.po
plone-ja.po
plone-ja.po
plone-sl.po
plone-sv.po
plone-uk.po

label_event_byline msgid was splitted in two.
label_event_byline has the ${location} variable and
label_event_byline_without_location don't have the ${location} variable.
Here is the french translation for example:

#. Default: "(${location}, from ${start} to ${end})"
#: CMFPlone/skins/plone_content/folder_listing.pt:99
msgid "label_event_byline"
msgstr "(${location}, du ${start} au ${end})"

#. Default: "(from ${start} to ${end})"
#: CMFPlone/skins/plone_content/folder_listing.pt:111
msgid "label_event_byline_without_location"
msgstr "(du ${start} au ${end})"

Regards
--
Vincent Fretin

------------------------------------------------------------------------------
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n