[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[TSVN] TMerge's (poor) Unicode handling

From: Norbert Unterberg <nepo_at_gmx.net>
Date: 2005-04-14 23:05:24 CEST

I lost some of my work recently when using TMerge to resolve a confilct.
So I managed to build TSVN myself and did some debugging.

Is it by design that there is no unicode build of TMerge, and that
TMerge uses ANSI CStrings to store the user's text data? Or did you
simply "forget" to enable UNICODE in TMerge?
Using UTF-8 text files, the code that loads the user's file converts the
data from UTF-8 to UTF-16 and then to ANSI, which destroys all
characters in the file that do not map to the current user's code page.
I am talking about the CUnicodeUtils::GetUnicode() function which
returns a standard CString object (storing TCHAR which maps to ANSI
characters in non-Unicode builds).

Is that a bug or a feature? Maybe someone should put some work into
TMerge to create a Unicode build?


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 14 23:05:55 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.