[yast-devel] YaST in Ruby and string to be translated
Hi all, I send this mail to both os-translation and yast-devel ML since it addresses both yast development and translation, so take care of these two ML when you reply. I have just noted that the POT files for YaST have been updated, probably as the result of the conversion of YaST in Ruby. As a result, the msgid strings now contain "\\n" instead of "\n" to denote the new line inside the same msgid. For instance, in printer.pot, the current string is msgid "Started the CUPS daemon.\\nWaiting half a minute for the CUPS daemon to get ready to operate...\\n" while before it was msgid "" "Started the CUPS daemon.\n" "Waiting half a minute for the CUPS daemon to get ready to operate...\n" Now, the question is: is this change expected and wanted? Note that now we have around 3310 fuzzy and 40 untranslated strings so I think it is better to be sure that all these fuzzy strings are correct before starting fixing their translations. Best, Andrea -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2013-08-01 at 18:59 +0200, Andrea Turrini wrote:
Hi all,
I send this mail to both os-translation and yast-devel ML since it addresses both yast development and translation, so take care of these two ML when you reply.
I'm only subscribed here; if I post to yast-devel-ml I don't know if it will be rejected.
msgid "" "Started the CUPS daemon.\n" "Waiting half a minute for the CUPS daemon to get ready to operate...\n"
Now, the question is: is this change expected and wanted?
What I know is that the translation tools will not detect the double slash, and will not flag as an error if a single slash is used. What will happen if we (translators) fail to use them? Can our tools be modified so that those errors be flagged? Why has that double slash got to be used? :-? - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEUEARECAAYFAlH7BfEACgkQtTMYHG2NR9XNoACWIyiohQnlYMstQYFk9y7DCGzY zACeNJ5SN1EiT38bdkSaDAOFZp7REFw= =Uhnw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 1.8.2013 18:59, Andrea Turrini napsal(a):
As a result, the msgid strings now contain "\\n" instead of "\n" to denote the new line inside the same msgid.
For instance, in printer.pot, the current string is
msgid "Started the CUPS daemon.\\nWaiting half a minute for the CUPS daemon to get ready to operate...\\n"
Yeah, I haven't noticed that, thanks for reporting this!
Now, the question is: is this change expected and wanted?
This was caused by switching from YCP to Ruby which needs using Ruby gettext (rxgettext) instead of GNU gettext (xgettext). For me it looks like a bug, I'll investigate further. Moreover many comments are missing, this is another incompatibility in rxgettext and needs to be solved. For now ignore the new translations, and I think the last changes could be even reverted to not cause confusions for translators... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Ladislav Slezak <lslezak@suse.cz> writes:
This was caused by switching from YCP to Ruby which needs using Ruby gettext (rxgettext) instead of GNU gettext (xgettext).
For me it looks like a bug, I'll investigate further.
Moreover many comments are missing, this is another incompatibility in rxgettext and needs to be solved.
Any idea how long it may take? ;) BTW, please talk to the GNU gettext maintainers and ask them to add Ruby support. Private (x)gettext implementations are often somehow problematic... -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 1.8.2013 18:59, Andrea Turrini napsal(a):
I have just noted that the POT files for YaST have been updated, probably as the result of the conversion of YaST in Ruby.
As a result, the msgid strings now contain "\\n" instead of "\n" to denote the new line inside the same msgid.
For instance, in printer.pot, the current string is
msgid "Started the CUPS daemon.\\nWaiting half a minute for the CUPS daemon to get ready to operate...\\n"
while before it was
msgid "" "Started the CUPS daemon.\n" "Waiting half a minute for the CUPS daemon to get ready to operate...\n"
Now, the question is: is this change expected and wanted?
On the first sight it looks like a bug of a string extraction tool for Ruby (rxgettext). Ladislav (in CC) is looking at the problem now more deeply. We'll send an update once we know more. -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (5)
-
Andrea Turrini -
Carlos E. R. -
David Majda -
Karl Eichwalder -
Ladislav Slezak