[opensuse-translation] Bug report against webyast files
Hi all, I am translating webyast files and I have noted that they contain incomplete phrases, so I am going to open bug reports against them, as Karl suggested. Should I open a report for each file containing incomplete phrases? or is it sufficient to open a single report against all files? Is there some page that I can link to remark that incomplete phrases are not allowed? Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
On Friday 16 April 2010 08:42:28 Andrea Turrini wrote:
Hi all, I am translating webyast files and I have noted that they contain incomplete phrases, so I am going to open bug reports against them, as Karl suggested.
Should I open a report for each file containing incomplete phrases? or is it sufficient to open a single report against all files?
Is there some page that I can link to remark that incomplete phrases are not allowed?
Martin, could you help here? Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-16 11:16, Andreas Jaeger wrote:
On Friday 16 April 2010 08:42:28 Andrea Turrini wrote:
Hi all, I am translating webyast files and I have noted that they contain incomplete phrases, so I am going to open bug reports against them, as Karl suggested.
Should I open a report for each file containing incomplete phrases? or is it sufficient to open a single report against all files?
Is there some page that I can link to remark that incomplete phrases are not allowed?
Martin, could you help here?
I was going to comment that as well, but I forgot. In fact, some sentences got "improved" to incompleteness a few days ago: #: app/views/repositories/index.html.erb:208 #, fuzzy #| msgid "Repository will be %s." msgid "Repository is currently" msgstr "El repositorio será %s." In this case, there is another problem: not knowing what word will be following means that I don't know what verb to use for the translation of "to be" to Spanish, as we have two different verbs with different meaning (it is one of the difficulties English speakers have when learning Spanish): msgstr "El repositorio será %s." or msgstr "El repositorio estará %s." I need to see an example of the complete sentence. My guess is it would be enabled/disabled, but I do not know. In fact, we would also need to see the related set of words that would fill the "%s" connected somehow, so that we could translate the group of sentences/words in a consistent manner. But this is something the gettext format does not support, as far as I know. Therefore, possibly the best solution is not to have incomplete sentences, but neither "%s to be filled" sentences. We would need 2, 4, or 20 different and distinct msgids, one for each combination that the programmer is going to use. :-( - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkvIuEoACgkQja8UbcUWM1zOjgD+KvJtsnqADgYqsekjKLXcwpDl MfJZWQHvalNpn1FGdMgBAIX9eMCpw/+Ylimtpq070/aGt8gvI9bjeGi+U9jh4mPI =x3eO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
In this case, there is another problem: not knowing what word will be following means that I don't know what verb to use for the translation of "to be" to Spanish, as we have two different verbs with different meaning (it is one of the difficulties English speakers have when learning Spanish):
msgstr "El repositorio será %s."
or
msgstr "El repositorio estará %s."
I need to see an example of the complete sentence. My guess is it would be enabled/disabled, but I do not know. In fact, we would also need to see the related set of words that would fill the "%s" connected somehow, so that we could translate the group of sentences/words in a consistent manner. But this is something the gettext format does not support, as far as I know.
Therefore, possibly the best solution is not to have incomplete sentences, but neither "%s to be filled" sentences. We would need 2, 4, or 20 different and distinct msgids, one for each combination that the programmer is going to use. :-( That's exactly the sentences that made me to start the discussion about i18n rules for developers. Cause it is impossible to translate
2010/4/16 Carlos E. R. <carlos.e.r@opensuse.org>: those lines in russian, since the form of the word standing for %s depends on a gender of forthcoming noun: repository is male, autorefresh is of middle gender, option is female (or male or middle depending on context)? that gives three different forms for enabled\disabled word in russian. We definitely need to formalize some of the rules so we can point developers on it. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-04-16 21:59, Александр Мелентьев wrote:
2010/4/16 Carlos E. R. <>:
...
That's exactly the sentences that made me to start the discussion about i18n rules for developers. Cause it is impossible to translate those lines in russian, since the form of the word standing for %s depends on a gender of forthcoming noun: repository is male, autorefresh is of middle gender, option is female (or male or middle depending on context)? that gives three different forms for enabled\disabled word in russian. We definitely need to formalize some of the rules so we can point developers on it.
But we also need an improved gettext system and po format that makes this easier. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkvIwykACgkQU92UU+smfQXDwQCfS75cRdvTkPLxG5dzAqu09xN7 kOQAnj29VrE+ez7EZTfCAuk6cSSKPoEb =UTpK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
On Fri, Apr 16, 2010 at 10:06 PM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2010-04-16 21:59, Александр Мелентьев wrote:
2010/4/16 Carlos E. R. <>:
...
That's exactly the sentences that made me to start the discussion about i18n rules for developers. Cause it is impossible to translate those lines in russian, since the form of the word standing for %s depends on a gender of forthcoming noun: repository is male, autorefresh is of middle gender, option is female (or male or middle depending on context)? that gives three different forms for enabled\disabled word in russian. We definitely need to formalize some of the rules so we can point developers on it.
But we also need an improved gettext system and po format that makes this easier.
With use of good comments it should be easier. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (5)
-
Andrea Turrini -
Andreas Jaeger -
Carlos E. R. -
Leandro Regueiro -
Александр Мелентьев