[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: posummit error while merging translations
From:       Park Shinjo <kde () peremen ! name>
Date:       2014-03-23 13:31:23
Message-ID: 10915468.It3KPkG7Sc () arlov
[Download RAW message or body]

Thank you for quick response. I have reviewed each summit PO file's contents after \
updating the script, now all the problematic files were correctly merged. Also I did \
not included line break inside markup tag in previous message (this was quite common \
though) and it is also now fixed. Here is an example:

...
 msgstr ""
-"<strong>쒋은 μ œλͺ©μ˜ μ˜ˆμ‹œ:</strong"
-"><nl />\"Plasma crashed after adding the Notes widget and writing on it"
-"\"<nl />\"Konqueror crashed when accessing the Facebook application 'X'"
...
+"<strong>쒋은 μ œλͺ©μ˜ μ˜ˆμ‹œ:</strong><nl />"
+"\"Plasma crashed after adding the Notes widget and writing on it\"<nl />"
+"\"Konqueror crashed when accessing the Facebook application 'X'\"<nl />"
...

- denotes previous run of merge, + denotes merge run after updating script. As you \
can see at the first line of -/+, now there is no break inside <strong> tag.

If another problem arose or I changed my mind, then I will try to change wrap/split \
option.

Shinjo

2014λ…„ 3μ›” 23일 μΌμš”μΌ μ˜€ν›„ 1:24:28에 Chusslove Illich λ‹˜μ΄ μ“΄ κΈ€:
> > [: Park Shinjo :]
> > While I executed initial gathering step of summit (posummit scripts/
> > messages.summit ko gather --create --force), this step added unneccessary
> > line breaks into resulting summit PO files. As a negative consequence,
> > some escape sequence were invalidated.
> 
> There was an error in the line wrapping algorithm in Pology, I've fixed it
> now. The example msgstr string now looks like this after gathering/merging:
> 
> msgstr ""
> "<p>...ν˜„μž¬ λ©”μ‹œμ§€μ˜ μ’…λ₯˜μ— 따라(일반 ν…μŠ€νŠΈ/HTML/OpenPGP) \
> 색상을\n" " ν‘œμ‹œν•  수 μžˆμŠ΅λ‹ˆλ‹€.</p>"
> "\n"
> "<p>KMail의 μ„œλͺ… μƒνƒœ ν”„λ ˆμž„κ³Ό λΉ„μŠ·ν•œ HTML λ©”μ‹œμ§€λ₯Ό λ³΄λ‚΄μ„œ \
> κ°€μ§œλ‘œ\n" "μ„œλͺ…이 ν™•μΈλœ κ²ƒμ²˜λŸΌ 믿게 ν•˜λŠ” 것을 \
> λ°©μ§€ν•©λ‹ˆλ‹€.</p>" "\n"
> 
> If you wonder why there is now double break (once after </p> and again after
> \n), that is because by default summit is set to break also on particular
> markup sequences (like end-of-paragraph here). The normal way to write this
> message in the source would have been without any \n, and then without
> breaking on markup there would be no break between paragraphs. If you don't
> like this additional breaking, you can add the file
> ko/summit/messages.extras.summit with these lines:
> 
> # Override global summit wrap/split settings.
> S.summit_wrap = True
> S.summit_fine_wrap = False
> 
> There is another reason why you might want to disable wrapping on markup.
> Pology uses a custom text wrapping algorithm, which I've been told is not
> that good for CJK languages, and that the algorithm in Gettext tools is
> better. If wrapping on markup is disabled, Pology will not wrap strings
> itself at all, but leave wrapping to Gettext tools (msgmerge).
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread]