"Warning: none, Errors: 1" from the difference of number of lines
Hello, Sorry if I am asking an already discussed issue. I am now reviewing horizon > stable-liberty > Documents (ko-KR)
openstack_dashboard/locale/django before our freezing deadline, as Daisy mentioned.
But I have found that some Korean strings still have an error with the following message like: "Not enough lines in translation (expected 4, found 3)". The main reason I think is that in our previous translation platform Transifex, truncating the last empty line was recommended as far as I remember. (If not, Transifex generated an error.) My question is: should we fix those error translated strings with same number of lines and same spaces? I think it would be ignored because when I see Chinese translation, there were the same type of error message for almost translated strings. (Screenshot: https://www.dropbox.com/s/bvd098wsakpi192/Zanata_horizon_translation_example... ) And if this error would be negligible to us, are there some ways not to see this type of errors? I would like to copy an example sentence string in Zanata from Korean for my better explanation. <in English>(Translated from) === First, select which type of job that you want to run. This choice will determine which other steps are required === <in Korean>(Translated to) === 먼저, 실행하고자 하는 job 유형 을 선택합니다. 이 선택을 통해 필요로 하는 다른 과정들을 결정할 것입니다. === With many thanks, /Ian
On 10/05/2015 06:54 PM, Ian Y. Choi wrote:
Hello,
Sorry if I am asking an already discussed issue.
I am now reviewing horizon > stable-liberty > Documents (ko-KR)
openstack_dashboard/locale/django before our freezing deadline, as Daisy mentioned.
But I have found that some Korean strings still have an error with the following message like: "Not enough lines in translation (expected 4, found 3)".
Akihiro, is this something you could look at in Horizon? Does horizon really need these as separate lines - or is that formatted automatically? Can we do something in horizon here to avoid these problems? Ian, I think this is fine, I don't see errors in the downloaded po files for Korean. The only error that msgfmt produces is if the original text has after the last line some white space - and you do not copy that.
The main reason I think is that in our previous translation platform Transifex, truncating the last empty line was recommended as far as I remember. (If not, Transifex generated an error.)
My question is: should we fix those error translated strings with same number of lines and same spaces? I think it would be ignored because when I see Chinese translation, there were the same type of error message for almost translated strings. (Screenshot: https://www.dropbox.com/s/bvd098wsakpi192/Zanata_horizon_translation_example... )
And if this error would be negligible to us, are there some ways not to see this type of errors?
Zanata allows to disable/enable some checks, but I think this error is nothing we can enable/disable. so, might be worth a feature request to the Zanata team.
I would like to copy an example sentence string in Zanata from Korean for my better explanation.
<in English>(Translated from) === First, select which type of job that you want to run. This choice will determine which other steps are required
===
<in Korean>(Translated to) === 먼저, 실행하고자 하는 job 유형 을 선택합니다. 이 선택을 통해 필요로 하는 다른 과정들을 결정할 것입니다. ===
Thanks, this is a good point to bring up! Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hi, I would like to comment before going to bed :-) Japanese team discussed the same thing during Horizon translation review this weekend. See my comment inline. 2015-10-06 2:01 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 10/05/2015 06:54 PM, Ian Y. Choi wrote:
Hello,
Sorry if I am asking an already discussed issue.
I am now reviewing horizon > stable-liberty > Documents (ko-KR)
openstack_dashboard/locale/django before our freezing deadline, as Daisy mentioned.
But I have found that some Korean strings still have an error with the following message like: "Not enough lines in translation (expected 4, found 3)".
Akihiro, is this something you could look at in Horizon? Does horizon really need these as separate lines - or is that formatted automatically? Can we do something in horizon here to avoid these problems?
I don't see any problems in this situation. They are formatted automatically according to a regular HTML rendering rules. What I can say is that this is a limitation of Django or underlying string extraction tool. Django manage.py makemessage subcommand (which extracts translatable strings from sources codes and templates) preserves newlines and spaces even though they have no meaning after rendering templates. Hopefully Django tool deals with these strings into a single line (though it may be a hard thing) from the point of view of translators :-)
Ian, I think this is fine, I don't see errors in the downloaded po files for Korean.
The only error that msgfmt produces is if the original text has after the last line some white space - and you do not copy that.
On the other hand, it is not productive to insert newlines just to avoid error warning from Zanata. Zanata prevents reviewers from approving translations when there is such error, and we cannot complete reviews :-( # Japanese team insert meaningless newlines to avoid warnings for Liberty translations # but would not like to do that in the future.
The main reason I think is that in our previous translation platform
Transifex, truncating the last empty line was recommended as far as I remember. (If not, Transifex generated an error.)
My question is: should we fix those error translated strings with same number of lines and same spaces? I think it would be ignored because when I see Chinese translation, there were the same type of error message for almost translated strings. (Screenshot:
https://www.dropbox.com/s/bvd098wsakpi192/Zanata_horizon_translation_example... )
And if this error would be negligible to us, are there some ways not to see this type of errors?
Zanata allows to disable/enable some checks, but I think this error is nothing we can enable/disable. so, might be worth a feature request to the Zanata team.
This kind of check is sometimes useful and sometimes not. At the current configuration of Zanata, it seems a global configuration and translators cannot control the option. Thanks, Akihiro
I would like to copy an example sentence string in Zanata from Korean
for my better explanation.
<in English>(Translated from) === First, select which type of job that you want to run. This choice will determine which other steps are required
===
<in Korean>(Translated to) === 먼저, 실행하고자 하는 job 유형 을 선택합니다. 이 선택을 통해 필요로 하는 다른 과정들을 결정할 것입니다. ===
Thanks, this is a good point to bring up!
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Thanks for your comments and have a good night!
# Japanese team insert meaningless newlines to avoid warnings for Liberty translations # but would not like to do that in the future.
Please file a feature request with the Zanata team, I have not found an option to disable this myself ;( Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hi Andreas, The reason translations can't be save when newline character doesn't match with source is due to the settings in project horizon. For some reason, it was set to "Error", and this will prevent saving of translation whenever this validation failed. You can change the setting via: https://translate.openstack.org/project/view/horizon/settings/translation (need to be project maintainer for admin), set the "Leading/trailing newline (\n)" to warning. --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Tue, Oct 6, 2015 at 4:59 AM, Andreas Jaeger <aj@suse.com> wrote:
Thanks for your comments and have a good night!
# Japanese team insert meaningless newlines to avoid warnings for
Liberty translations # but would not like to do that in the future.
Please file a feature request with the Zanata team, I have not found an option to disable this myself ;(
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
I want to say we did that because the linters for the various projects do msgfmt checks that fail when newlines don't match. This means that any of those translations sneaking into the git repo proposals prevent any translations for that project from merging. I believe we do want this to be an error in Zanata as long as the projects are going to check and fail on that when linting. Clark On Mon, Oct 5, 2015, at 12:51 PM, Alex Eng wrote:
Hi Andreas,
The reason translations can't be save when newline character doesn't match with source is due to the settings in project horizon. For some reason, it was set to "Error", and this will prevent saving of translation whenever this validation failed.
You can change the setting via: https://translate.openstack.org/project/view/horizon/settings/translation (need to be project maintainer for admin), set the "Leading/trailing newline (\n)" to warning.
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
On Tue, Oct 6, 2015 at 4:59 AM, Andreas Jaeger <aj@suse.com> wrote:
Thanks for your comments and have a good night!
# Japanese team insert meaningless newlines to avoid warnings for
Liberty translations # but would not like to do that in the future.
Please file a feature request with the Zanata team, I have not found an option to disable this myself ;(
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Thanks for the explanation. I think its good to allow translators for Horizon project aware of this special requirement of formatting. --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Tue, Oct 6, 2015 at 6:43 AM, Douglas Fish <drfish@us.ibm.com> wrote:
+1 on keeping the newline mismatch an error
For Horizon, it's not just a linter that fails - it's the actual compilation of the PO files, which means the translations (all of them!) become unmergeable.
Doug Fish
----- Original message ----- From: Clark Boylan <cboylan@sapwetik.org> To: openstack-i18n@lists.openstack.org Cc: Subject: Re: [Openstack-i18n] "Warning: none, Errors: 1" from the difference of number of lines Date: Mon, Oct 5, 2015 3:20 PM
I want to say we did that because the linters for the various projects do msgfmt checks that fail when newlines don't match. This means that any of those translations sneaking into the git repo proposals prevent any translations for that project from merging. I believe we do want this to be an error in Zanata as long as the projects are going to check and fail on that when linting.
Clark
On Mon, Oct 5, 2015, at 12:51 PM, Alex Eng wrote:
Hi Andreas,
The reason translations can't be save when newline character doesn't match with source is due to the settings in project horizon. For some reason, it was set to "Error", and this will prevent saving of translation whenever this validation failed.
You can change the setting via:
https://translate.openstack.org/project/view/horizon/settings/translation
(need to be project maintainer for admin), set the "Leading/trailing newline (\n)" to warning.
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
On Tue, Oct 6, 2015 at 4:59 AM, Andreas Jaeger <aj@suse.com> wrote:
Thanks for your comments and have a good night!
# Japanese team insert meaningless newlines to avoid warnings for
Liberty translations # but would not like to do that in the future.
Please file a feature request with the Zanata team, I have not found an option to disable this myself ;(
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2015-10-05 22:50, Alex Eng wrote:
Thanks for the explanation.
I think its good to allow translators for Horizon project aware of this special requirement of formatting.
Readded it. Alex, we have two issues. Please check the examples again. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2015-10-05 21:51, Alex Eng wrote:
Hi Andreas,
The reason translations can't be save when newline character doesn't match with source is due to the settings in project horizon. For some reason, it was set to "Error", and this will prevent saving of translation whenever this validation failed.
You can change the setting via: https://translate.openstack.org/project/view/horizon/settings/translation (need to be project maintainer for admin), set the "Leading/trailing newline (\n)" to warning.
Alex, that's a different behaviour according to the description: Source \n hello world with lead new line Target missing \n hello world with lead new line Nevertheless I changed the setting, Andreas
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID:+61 3514 8262 <callto:+61+3514+8262> Mobile:+614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office:+61 7 3514 8100 <callto:+61+7+3514+8100> Fax:+61 7 3514 8199 <callto:+61+7+3514+8199> Website:www.redhat.com <http://www.redhat.com/>
On Tue, Oct 6, 2015 at 4:59 AM, Andreas Jaeger <aj@suse.com <mailto:aj@suse.com>> wrote:
Thanks for your comments and have a good night!
# Japanese team insert meaningless newlines to avoid warnings for Liberty translations # but would not like to do that in the future.
Please file a feature request with the Zanata team, I have not found an option to disable this myself ;(
Andreas -- Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org <http://opensuse.org>} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto:Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hi, According to clarkb and doug-fish's input, "msgfmt --check-format" will check the heading newlines and trailing newlines in the source string and translation string. If they are not same, it will cause a failure in the gate testing of Gerrit. So we do want Zanata to enable these validations. The complains from translators are about errors of different line numbers, for example: "Not enough lines in translation (expected 2, found 1)". After reading the source pot files, I noticed there were some meaningless newlines in the source pot files. These newlines come from HTML files. For example: http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/loc... So I don't think it's useful to keep the line numbers exactly same. @ Alex, in the web UI of Zanata, the validation of "leading/trailing newline (\n)" is described as "check for consistent leading and trailing newline (\n)". But actually, the validation will also check for the same line numbers of source string and translation string. Do you agree it is a bug ? I think we don't need the check of same line numbers. If you agree it is bug, I will report it. Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 10/06/2015 02:42:00 PM:
From: Andreas Jaeger <aj@suse.com> To: Alex Eng <aeng@redhat.com> Cc: Openstack-i18n Openstack-i18n <openstack-i18n@lists.openstack.org> Date: 10/06/2015 03:13 PM Subject: Re: [Openstack-i18n] "Warning: none, Errors: 1" from the difference of number of lines
On 2015-10-05 21:51, Alex Eng wrote:
Hi Andreas,
The reason translations can't be save when newline character doesn't match with source is due to the settings in project horizon. For some reason, it was set to "Error", and this will prevent saving of translation whenever this validation failed.
You can change the setting via:
https://translate.openstack.org/project/view/horizon/settings/translation (need
to be project maintainer for admin), set the "Leading/trailing newline (\n)" to warning.
Alex, that's a different behaviour according to the description:
Source
\n hello world with lead new line
Target
missing \n hello world with lead new line
Nevertheless I changed the setting, Andreas
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID:+61 3514 8262 <callto:+61+3514+8262> Mobile:+614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office:+61 7 3514 8100 <callto:+61+7+3514+8100> Fax:+61 7 3514 8199 <callto:+61+7+3514+8199> Website:www.redhat.com <http://www.redhat.com/>
On Tue, Oct 6, 2015 at 4:59 AM, Andreas Jaeger <aj@suse.com <mailto:aj@suse.com>> wrote:
Thanks for your comments and have a good night!
# Japanese team insert meaningless newlines to avoid warnings
for
Liberty translations # but would not like to do that in the future.
Please file a feature request with the Zanata team, I have not
found
an option to disable this myself ;(
Andreas -- Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org <http://opensuse.org>} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C
C272
A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto:Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On Wed, Oct 7, 2015 at 1:33 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
heck for consistent leading and trailing newline (\n)". But actually, the validation will also check for the same line numbers of source string and translation string. Do you agree it is a bug ? I think we don't need the check o
Daisy, I agree its a bug. Please file a report for it. --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
Hello, It is so fine that there are no errors in current Korean po files. I think for Korean we need to keep the current translation status now and we will remove meaningless newlines for the future. Thank you so much Akihiro, Andreas, Douglas, and Zanata team members for discussing this issue. With many thanks, /Ian Akihiro Motoki wrote on 10/6/2015 2:23 AM:
Hi,
I would like to comment before going to bed :-)
Japanese team discussed the same thing during Horizon translation review this weekend. See my comment inline.
2015-10-06 2:01 GMT+09:00 Andreas Jaeger <aj@suse.com <mailto:aj@suse.com>>:
On 10/05/2015 06:54 PM, Ian Y. Choi wrote:
Hello,
Sorry if I am asking an already discussed issue.
I am now reviewing horizon > stable-liberty > Documents (ko-KR) > openstack_dashboard/locale/django before our freezing deadline, as Daisy mentioned.
But I have found that some Korean strings still have an error with the following message like: "Not enough lines in translation (expected 4, found 3)".
Akihiro, is this something you could look at in Horizon? Does horizon really need these as separate lines - or is that formatted automatically? Can we do something in horizon here to avoid these problems?
I don't see any problems in this situation. They are formatted automatically according to a regular HTML rendering rules.
What I can say is that this is a limitation of Django or underlying string extraction tool. Django manage.py makemessage subcommand (which extracts translatable strings from sources codes and templates) preserves newlines and spaces even though they have no meaning after rendering templates. Hopefully Django tool deals with these strings into a single line (though it may be a hard thing) from the point of view of translators :-)
Ian, I think this is fine, I don't see errors in the downloaded po files for Korean.
The only error that msgfmt produces is if the original text has after the last line some white space - and you do not copy that.
On the other hand, it is not productive to insert newlines just to avoid error warning from Zanata. Zanata prevents reviewers from approving translations when there is such error, and we cannot complete reviews :-(
# Japanese team insert meaningless newlines to avoid warnings for Liberty translations # but would not like to do that in the future.
The main reason I think is that in our previous translation platform Transifex, truncating the last empty line was recommended as far as I remember. (If not, Transifex generated an error.)
My question is: should we fix those error translated strings with same number of lines and same spaces? I think it would be ignored because when I see Chinese translation, there were the same type of error message for almost translated strings. (Screenshot: https://www.dropbox.com/s/bvd098wsakpi192/Zanata_horizon_translation_example... )
And if this error would be negligible to us, are there some ways not to see this type of errors?
Zanata allows to disable/enable some checks, but I think this error is nothing we can enable/disable. so, might be worth a feature request to the Zanata team.
This kind of check is sometimes useful and sometimes not. At the current configuration of Zanata, it seems a global configuration and translators cannot control the option.
Thanks, Akihiro
I would like to copy an example sentence string in Zanata from Korean for my better explanation.
<in English>(Translated from) === First, select which type of job that you want to run. This choice will determine which other steps are required
===
<in Korean>(Translated to) === 먼저, 실행하고자 하는 job 유형 을 선택합니다. 이 선택을 통해 필요로 하는 다른 과정들을 결정할 것입니다. ===
Thanks, this is a good point to bring up!
Andreas -- Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org <http://opensuse.org>} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto:Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (7)
-
Akihiro Motoki
-
Alex Eng
-
Andreas Jaeger
-
Clark Boylan
-
Douglas Fish
-
Ian Y. Choi
-
Ying Chun Guo