Ian,

 

IMO "Not enough lines in translation (expected 4, found 3)" is not a critical error. I'm not sure if it's useful during review or not -- I'm imagining if there was ever a "expected 7 found 1" error that would suggest a translation problem.

 

However, if you edit this string to correct it you may create a more serious problem with line endings. The PO compile process is very opinionated about ending newlines and will fail to compile if there is a mismatch between the msgid and msgstr. During the compile this error is similar to " 'msgid' and 'msgstr' entries do not both end with '\n'" I'm not sure how it looks in Zanata. This kind of error will prevent any translations from being imported into the projects.

 

I'd suggest waiting to do any clean up like this until after Liberty is complete, and maybe this specific warning message isn't a problem and could be hidden.

Doug Fish

----- Original message -----
From: "Ian Y. Choi" <ianyrchoi@gmail.com>
To: Openstack-i18n Openstack-i18n <openstack-i18n@lists.openstack.org>
Cc:
Subject: [Openstack-i18n] "Warning: none, Errors: 1" from the difference of number of lines
Date: Mon, Oct 5, 2015 11:55 AM
 

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_in_zh-CN.png?dl=0 
)

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

_______________________________________________
Openstack-i18n mailing list
Openstack-i18n@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n