On Tue, 2008-07-08 at 23:37 +0200, Alexandre Prokoudine wrote:
> I was reminded by a RU user recently that Audacity still uses a
> transliterated list of languages on startup and in preferences dialog.
> Are we unicode enough :) to move over and provide names of languages
> without these artificial ASCII limitations?
I'm not sure our toolchains are. I'm not quite sure how I'd go about
creating a file with unicode strings in it, and I'm under the impression
that it won't compile on all platforms if we do.
I know GCC will will accept UTF-8 source files, but I suspect that
Visual Studio chokes on them. I'm not sure whether there is a reverse
case.
We are also still building ASCII for legacy windows system, which may be
a problem.
Richard
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at
http://www.sourceforge.net/community/cca08_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
