Ardo van Rangelrooij <[EMAIL PROTECTED]> writes: > Further, I've identified all character strings currently not properly > translated. I've already added them to the respective i18n data files, > but they lack a proper translation, except for English and Dutch. To > make the i18n data files provide completely proper translations, I need > a translation of the following strings: > > Section, Subsection, Subsubsection, Paragraph, Subparagraph, > previous, page, The Detailed Node Listing > > for the following languages: > > Czech, Danish, German, Spanish, Finnish, French, Croatian, Italian, > Japanese, Russian (both encodings)
I also think this 1:1 translation is not a good i18n idea. It's much worse than gettext. Besides the gender problems in some languages... In Japanese or in Korean, the order of words in `Chapter 2' should be `2 <chapter>'. (Bug #34146) -- Changwoo Ryu
