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

Re: converting unconvertible UTF-8 data

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-22 17:14:21 CEST

Ulrich Drepper <drepper@redhat.com> writes:
> When it comes to these things it really a quality of implementation
> thing. You don't want to drag down to quality on one system just
> because there are some others which don't have implementations of the
> needed functionality.
> Also, consistency in the output of information which is meant for the
> user (e.g., log files, changelogs etc) is not that important. A human
> reader is able to figure out a lot despite noise on the channel.

Hmm, yeah, that seems reasonable to me.

> All you need is a configure test and a bit of #ifdef'ed code to append
> "//TRANSLIT" to the codeset name.


Okay, Ulrich, it's time for me to make the Big Request:

You need to be able to build Subversion, so you can contribute code as
well as ideas. This *should* be simply a matter of

   1) Download the latest tarball from

   2) Build it, then use it to check out the sources
      "svn co http://svn.collab.net/repos/svn"

   3) Then build your new working copy. First run autogen.sh, it will
      tell you exactly what dependencies you need and where to get

This is a slightly more complex recipe than users need, since they
aren't trying to get a working tree for development, but it's not
really _that_ hard -- dozens of people here have done it.

Can you write this configuration patch? Sure, someone else could do
it, but probably you are the most qualified to get it done quickly, so
why settle for less? :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 17:27:16 2002

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

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