Mark Phippard wrote:
> The way we are handling it in the EBCDIC port is to do exactly what brane
> suggested. We defne character constants that escape the literal to UTF-8
> and then modified the code to use the constants.
How extensive is this? Did you just need to do this for a few odd characters
here and there, or does this involve replacing hundreds of literal strings and
characters all over the code base? Bear in mind that I don't know whether
EBCDIC has any overlap with ASCII, or what your other options are (such as
controls to make certain parts be compiled with ASCII as the execution
character set).
Could you show us a patch for this, or is it all mixed up with lots of other
changes? Could you show us an example of exactly what you did? I'm interested
to see whether it is something that we could reasonably maintain in the
Subversion code base, or far too disruptive for that. It would also be
interesting to see what macro names you use, what header files, and so on, so
that we don't needlessly conflict with you.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 10 15:31:43 2005