On Thu, 6 Jan 2005, Joel wrote:
> > > For example, I would that UTF-{16,32} are effectively binary files, in
> > > many ways.
> > > They can't be diffed, unless you teach the diff program what a lineend
> > > is in the new format, and they can't be displayed on most terminals,
> > > nor easily shown in email.
> > > They require special editors/viewers, just like MSWord docs require
> > > special editors.
> >
> > Unicode is the new ASCII. The editors are already here. I.e. if
> > Notepad.exe can handle it you have to set the bar pretty low :)
>
> All of the systems I work with on a regular basis (Mac, Linux, fBSD,
> MSWxxx) handle Unicode Japanese, and include a default GUI text editor
> that is usable for many of the large character set languages. Many of
> the terminal programs can handle Unicode Japanese if you set them up to
> do so. (Install the fonts and export LANG=ja_JP.UTF-8 or something like
> that.) You can get VIM and emacs set up to handle Unicode, as well, if
> you look/ask around. I've used Netbeans with Japanese, so I know that
> works, and I understand that Eclipse does well, also.
>
Please don't confuse Unicode and UTF16. Unicode is a character repertoire.
UTF16 is a way to serialize a stream of characters from that Repertoire.
Subversion supports Unicode, but it doesn't handle UTF16 very well yet.
So, there is no problem using Unicode with subversion, just use UTF8.
That being said, I agree that we should support the other transformation
forms as well.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 6 13:39:12 2005