118
edits
Bugzilla:L10n:Maketext: Difference between revisions
Jump to navigation
Jump to search
→Drawbacks and concerns: more readability issues added
(→Work Breakdown: bug numbers added) |
(→Drawbacks and concerns: more readability issues added) |
||
| Line 121: | Line 121: | ||
== Drawbacks and concerns == | == Drawbacks and concerns == | ||
Real-life examples can be seen in {{bug|412161}} attachments. | |||
=== Default template look and feel === | === Default template look and feel === | ||
| Line 140: | Line 142: | ||
And then in '''en.po''': | And then in '''en.po''': | ||
msgid "0 bug(s) were found in 0 product(s). | msgid "0 bug(s) were found in 0 product(s)." | ||
msgstr "Zarro boogs found." | msgstr "Zarro boogs found." | ||
| Line 147: | Line 149: | ||
Note exact match for a special case. | Note exact match for a special case. | ||
=== Template security === | |||
Real situation is even worse because most variable pieces are unsafe and require <tt>FILTER html</tt>. | |||
[% nbugs FILTER html %] $terms.bugs were found in [% nproducts FILTER html%] products. | |||
and after | |||
[% bugs = BLOCK; nbugs FILTER html; END; | |||
products = BLOCK; nproducts FILTER html; END; | |||
l("[_1] bug(s) were found in [_2] products.", bugs, products) %] | |||
Perhaps we should add function helpers to more filters. | |||
=== Large keys === | |||
Long texts as <tt>%Lexicon</tt> keys are not so handy, with their multiple explicit newlines, leading spaces, etc. Other projects using Maketext and Template Toolkit also confront this: | |||
''Act!'' ended up with keys cut at first newline: | |||
msgid "This is your personal page." | |||
msgstr "" | |||
"This is your personal page.\n" | |||
"From here you can manage everything regarding your participation\n" | |||
''Request Tracker'' indeed uses long keys, up to 400 characters on a single line. Not a problem with special PO editing tools, but their template files [http://svn.bestpractical.com/cgi-bin/index.cgi/bps/view/rt/3.8/trunk/share/html/Install/DatabaseDetails.html look accordingly], i.e. do not wrap paragraphs at all. | |||
=== Site maintainers' skills === | === Site maintainers' skills === | ||