[asterisk-dev] [policy] Language specific prompts

[Tzafrir Cohen]

On Sat, Feb 07, 2009 at 10:27:20PM +0100, Philipp Kempgen wrote:
> Tzafrir Cohen schrieb:
> > On Fri, Feb 06, 2009 at 09:26:25PM +0100, Philipp Kempgen wrote:
> 
> >> What about CSV/TSV?
> > 
> > If we have a long text, I'm not really sure it needs to fit in a single
> > line.
> > 
> > BTW, one thing I forgot was that in case the respective script is an RTL
> > one (Hebrew, Arabic, etc.), most naive displays of the text would render
> > the paragraph as LTR (as it ebgins with English text) and thus the 
> > original script part may not be displayed properly. Specifically if it
> > has an English letter or two in it.
> 
> GNU gettext .po files could be an option because many standard
> tools are already available.
> But I'm just making suggestions. If you decide to go with ODS,

ODF is not handled well by SVN (well, there's
http://odfsvn.sourceforge.net/ . But we can't also depend on it)

> fine.
> 
> msgid ""
> msgstr ""
> "Project-Id-Version: Asterisk, file $Revision$\n"
> "Report-Msgid-Bugs-To: \n"
> "PO-Revision-Date: 2009-01-07 12:00+0200\n"
> "Last-Translator: John Doe <john.doe at example.com>\n"
> "Language-Team: German <>\n"
> "MIME-Version: 1.0\n"
> "Content-Type: text/plain; charset=UTF-8\n"
> "Content-Transfer-Encoding: 8bit\n"
> 
> msgid "digits/1"
> msgstr "ein"

It solves a different problem. Using gettext here would require brute
force and wouldn't buy you much.

Oh, and digits/1 is digits/1 (only under a de/ )

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir