On Sun 05 Mar 2006 15:14, Daniel Swarbrick wrote: > bkml wrote: > > We have specifically settled on plaintext format (and not XML or > > binary) because we wanted the property lists to be human readable and > > editable. Using human readable keywords is an important part of that. > > When did we settle on that? The last I heard, both plist and XML would > be supported transparently by the same library. While plist might be > dominant on your development platform (MacOS), XML is a cross-platform > standard. I reckon XML editors are far more common than plist editors, > not to mention the fact that lots of script languages have good support > for manipulating XML via DOM methods. > > > Multiple languages can also be supported this way. OSX/Darwin does > > this sort of thing all the time via separate sets of plists, one for > > each supported language/locale. > > Gee, that sounds efficient. Easy to maintain too! :P > > > Also, a common user friendly approach for language selection is to > > present each language in its own language, ie. Finish could be "FI- > > Suomi", that's an approach worth considering for a resource intended > > to be human readable/editable. > > Ok, we'd better make the config files written in UTF-8 then, since there > are many languages that will need to be written using non-Latin > characters. Have you thought about how you're going to write > "JP-Nihongo" in native Kanji? Even if you do manage to write Nihongo in > Kanji, what does JP mean to a Japanese person? They don't call their > country Japan, they call it Nihon or Nippon! Even UTF-8 doesn't cover > all the possible characters from every single language in the world.
Yep. You would have to use UTF-16 ... -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
pgpXsLleYicuX.pgp
Description: PGP signature
_______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
