On Thu, 2009-07-02 at 15:47 -0300, Raul Fragoso wrote:
On Fri, 2009-07-03 at 01:29 +0800, Steve Underwood wrote:
Michael Collins wrote:
On Thu, Jul 2, 2009 at 3:01 AM, Igor Neves <igor@3gnt.net <mailto:igor@3gnt.net>> wrote:
Hi,
Michael Collins wrote:
Hello all!
There's been some discussion lately on how to handle multiple languages, specifically with the *say* application. We would like some input from the community on how to handle multiple languages and sound files. Anthony notes that the say application needs to build the path to the sound files by using the ${sound_prefix} and ${lang} variables. Some have asked about countries or language variants, like European Portugese vs. Brazilian Portugese. These are good questions.
What it's the problem about Portuguese VS Brazilian?
Can't we just use "PT_pt" and "PT_br" in ${lang}, just like a lot of others softwares do?
What about ${sound_prefix} = ${lang}, since ${lang} should always be unique, and you make the path's automatically language organized?
This is reasonable to me, but it would be nice to have a consensus, just to be sure.
The <lang>-<dialect> thing would appear to be the obvious choice; what's slightly less obvious is what to do about fallback. Three choices: - None - i.e. I say en-gb, I either get en-gb or nothing; - Best guess - I want en-gb, but I'm quite happy with en-us or en-au. I could specify en-gb and, if en-gb's not available but en-something else is, whatever's available gets chosen for me; - Preference list - I specify a (possibly) wildcarded list of what I want - e.g. en-gb,en-us,en* - and whichever match comes first is what I get. --Dave -- David Knell, Director, 3C Limited T: +44 20 3298 2000 E: dave@3c.co.uk W: http://www.3c.co.uk