When marking source files. There should take into account to try taking apart HTML code when possible: eample) original code: msg = "<em><strong>Don't change the option here.</strong>Use the main options page instead.</em>" marked code: msg = "<em><strong>" + _("Don't change the option here.") + "</strong>" + _(Use the main options page instead." + "</em>" Greetings -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------# # Solo se que cada vez se menos :-| # #----------------------------------------------#
On Mon, 13 Nov 2000, Juan Carlos Rey Anaya wrote:
When marking source files. There should take into account to try taking apart HTML code when possible: eample) original code: msg = "<em><strong>Don't change the option here.</strong>Use the main options page instead.</em>" marked code: msg = "<em><strong>" + _("Don't change the option here.") + "</strong>" + _(Use the main options page instead." + "</em>"
This limits the positioning of the bold text for translations (ie. it must always go before). I don't know if that is a problem in this case. This is similar to the reasons why printf style output is easier to internationalise than c++ streams. James.
James Henstridge wrote:
This limits the positioning of the bold text for translations (ie. it must always go before). I don't know if that is a problem in this case.
At first sight I see one inconvenient: If we let all to be in one string to translate, we also give a chance translators to mispell at translation time. example) msgid "<strong>Hello Word</strong>" msgstr "<strong>Hola Mundo>/strong>" When we later look for this message in catalog, this error can make the browser not to display the proper page. Time will say :-) Cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------# # Solo se que cada vez se menos :-| # #----------------------------------------------#
On Mon, 13 Nov 2000, Juan Carlos Rey Anaya wrote:
James Henstridge wrote:
This limits the positioning of the bold text for translations (ie. it must always go before). I don't know if that is a problem in this case.
At first sight I see one inconvenient: If we let all to be in one string to translate, we also give a chance translators to mispell at translation time.
example) msgid "<strong>Hello Word</strong>" msgstr "<strong>Hola Mundo>/strong>"
This is not the only occasion when the translated string has some requirements on it. The most obvious is format strings (I suppose with named substitutions like %(name)s, mistyping may be more common). Also, the translator should probably be escaping entities in these strings (unless mailman does that), so pretending the string is not an HTML fragment may not be the best idea.
When we later look for this message in catalog, this error can make the browser not to display the proper page.
invalid translations can cause all sorts of problems. This is not the only case. James.
James Henstridge wrote:
This is not the only occasion when the translated string has some requirements on it. The most obvious is format strings (I suppose with named substitutions like %(name)s, mistyping may be more common).
Well, I am agree that stuff like %(name)s is unavoided. But to the other side, I think we should to abstract as much as we can, so error can be minor.
Also, the translator should probably be escaping entities in these strings (unless mailman does that), so pretending the string is not an HTML fragment may not be the best idea.
I can not find a convincing reason to leave "<strong>Hello</strong>". - 'strong>' and '</strong' are not translatable and only may induce to errors. - Al last catalog can be fully of untranslatable text and can make translation heavier than it really is. Writing 20 or 30 string with this stuff can be normal but translating almost all the catalog is a daunting task. Cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------# # Solo se que cada vez se menos :-| # #----------------------------------------------#
"JCRA" == Juan Carlos Rey Anaya <jcrey@uma.es> writes:
JCRA> I can not find a convincing reason to leave JCRA> "<strong>Hello</strong>". - 'strong>' and '</strong' are JCRA> not translatable and only may induce to errors. - Al last JCRA> catalog can be fully of untranslatable text and can make JCRA> translation heavier than it really is. Writing 20 or 30 JCRA> string with this stuff can be normal but translating almost JCRA> all the catalog is a daunting task. I'd like to eventually fix all that, but let's not worry about it in the first go 'round. Let's worry about getting markups for what's there now and try to fix the templating problems in subsequent revisions. Otherwise I fear it'll delay getting something out too long (waiting for the Quixotic <wink> "perfect solution"). -Barry
participants (3)
-
barry＠digicool.com -
James Henstridge -
Juan Carlos Rey Anaya