[yast-devel] Incomplete phrases in several WebYaST po files
Hi all, I am translating some WebYast po files and I have found several incomplete phrases in them. This makes difficult for translators to provide good translations since in languages like Italian we distinguish genre and plural also for verbs and adjectives. As Karl Eichwalder said in translation-ml [1], incomplete phrases are not allowed and in [2] I asked if I should open a different bug report for each file containing incomplete phrases. The answer is to open a report for each po file. Before opening such reports, I would like to know your opinion about incomplete phrases since removing them affects the work of both YaST developers and translators. For instance, if you replace incomplete phrases with complete sentences in a short time such that new translation could be included into openSUSE 11.3, then translating current po files is useless. Best regards, Andrea [1] http://lists.opensuse.org/opensuse-translation/2010-03/msg00015.html [2] http://lists.opensuse.org/opensuse-translation/2010-04/msg00053.html -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Andrea Turrini
Hi all, I am translating some WebYast po files and I have found several incomplete phrases in them.
This makes difficult for translators to provide good translations since in languages like Italian we distinguish genre and plural also for verbs and adjectives.
As Karl Eichwalder said in translation-ml [1], incomplete phrases are not allowed and in [2] I asked if I should open a different bug report for each file containing incomplete phrases. The answer is to open a report for each po file.
Thanks for bringing this topic up. The current work on WebYaST is for the enterprise product, which is already in the late RC phase. Touching translations now seems kind of risky. But if Karl agrees, I'm fine with fixing texts. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf
The current work on WebYaST is for the enterprise product, which is already in the late RC phase. Touching translations now seems kind of risky.
Yes, you are right. In the SLE branch we'd better keep it now as-is. Maybe, we can prepare an online update (WebYaST plus its translations) right after the release. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 04/19/2010 10:28 AM, Karl Eichwalder wrote:
Klaus Kaempf
writes: The current work on WebYaST is for the enterprise product, which is already in the late RC phase. Touching translations now seems kind of risky.
Yes, you are right. In the SLE branch we'd better keep it now as-is. Maybe, we can prepare an online update (WebYaST plus its translations) right after the release.
It seems reasonable... about translations in openSUSE, do you think it is better to complete translation of current po files (accepting possibly poor translations) and then to provide updated packages? And for bug reports, I think it is better to open them anyway, isn't it? In this way they can play as a recall for the online update... Andrea -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Andrea Turrini
It seems reasonable... about translations in openSUSE, do you think it is better to complete translation of current po files (accepting possibly poor translations) and then to provide updated packages?
This probably depends on the language and the targeted audience (and personal preference). Sometimes a poor translation is better than none--sometimes it is the opposite.
And for bug reports, I think it is better to open them anyway, isn't it? In this way they can play as a recall for the online update...
Yes, opening a bug report straight away is useful. Thanks for your feedback! -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 04/19/2010 02:09 PM, Karl Eichwalder wrote:
Andrea Turrini
writes: And for bug reports, I think it is better to open them anyway, isn't it? In this way they can play as a recall for the online update...
Yes, opening a bug report straight away is useful. Thanks for your feedback!
Done. These are the bug numbers: bnc#597749, bcn#597753, bcn#597755 and bnc#597760. Other webyast po files seem to me to be ok. Andrea -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Andrea Turrini
-
Karl Eichwalder
-
Klaus Kaempf