> Yes, this is rather unavoidable, and to fix it in any non-hackish > way would need a redesign of the rendering pipeline.
Mhh ok, I've been guessing this already... > Please put in the correct ISO-8859-1 code instead of the HTML > entity. You can also use the native2ascii utility, if needed. Just to be sure, because this collides with the current instructions in the German language files: > # Please, do not forget to use proper HTML entities, so > # " = " > # ' = ' Note that ' is NOT HTML, and does not necessarily work in > all browsers. "Die Straßenangabe 'Straußenweg 10' ist ungültig!" becomes "Die Stra\u00DFenangabe 'Strau\u00DFenweg 10' ist ung\u00FCltig!" then? In particular, the '' and "" don't have to be escaped via \u0022 and \u0027 ? I'm asking because native2Ascii doesn't do that. If so, I'll change these instructions, too. > It's clearer, saves space, makes editing of the localization easier, > and is in general a lot less hassle. Well that's true, once the rules are clear :-) Regards, Florian
