<div class="gmail_quote">2009/9/4 Ceki Gulcu <span dir="ltr"><<a href="mailto:ceki@qos.ch">ceki@qos.ch</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<snipped><br>
<br>
Can you think of a more elegant approach which still allows the user<br>
to designate the charset for a given locale?<font color="#888888"><a href="http://qos.ch/mailman/listinfo/cal10n-dev" target="_blank"></a><br>
</font></blockquote></div><br><br clear="all">Hmm - it has become rather messy. Can I suggest an alternative tack: require the properties files to be always UTF-8 (or UTF-16 with a BOM). Then the original simple syntax is viable. KISS principle.<br>
<br>As far as producing UTF-8 files is concerned, I imagine a spreadsheet 'compiler' that will take a CSV, ODS or XLS file and extract the necessary separate properties files bundle. The spreadsheet would be a simple single sheet containing the keys in the first column and any number of translation strings in the following columns, each of which has the locale name as its header (e.g. "en_UK ").<br>
<br>Rick<br>-- <br>Big Bee Consultants Limited : Registered in England & Wales No. 6397941<br>Registered Office: 71 The Hundred, Romsey, Hampshire, SO51 8BZ<br>