[wp-polyglots] Re: [wp-testers] i18n strings disambiguation

[Pandem]

Ryan Boren escribió:
> Pandem wrote:
>> Ryan Boren escribió:
>>>
>>> http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html#Q-:CAPS
>>>
>>> "|" is fine.  Do we want a separate Q_() like function for those 
>>> situations that require context?
>>>
>>>
>> I've been adding i18n to some themes and plugins for their use in 
>> multilingual sites. At this moment, I can't seem to recall anyone 
>> using "|" as a separator in the middle of a string, but  there are 
>> chances that some use it... How will we avoid conflict?
>
> In glib, only Q_() attempts to strip context, and it strips it only if 
> the original string is not translated.  This means translators should 
> never translate the context.  They must discard everything before the 
> "|".
>>
>> http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html#Q-:CAPS
>>
>> "|" is fine.  Do we want a separate Q_() like function for those 
>> situations that require context?
Ok, then I think we do need a separate Q_() like function, just in 
case... Otherwise, strings using "|" could get stripped in English.

Maira