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

Re: svn commit: r37733 - in trunk/subversion: include libsvn_wc

From: Hyrum K. Wright <hyrum_at_hyrumwright.org>
Date: Fri, 15 May 2009 09:41:34 -0500

On May 15, 2009, at 6:27 AM, Stefan Sperling wrote:

> On Thu, May 14, 2009 at 10:19:14PM -0700, Hyrum K. Wright wrote:
>> Author: hwright
>> Date: Thu May 14 22:19:14 2009
>> New Revision: 37733
>> Log:
>> Create a new public data structure for interacting with wc-ng. The
>> working copy context will take the place of the adm_access baton in
>> our
>> APIs, while being much cleaner to use.
>> + can just destory the state pool. Voilà! Everything is
>> closed and
> Do we expect everyone of us to always use editors that understand
> the particular charset that contains the à character and that run in
> terminals that can display the à character?
> Even though I've recently quit using OpenBSD I still remember the
> pains
> of not having UTF-8 capable terminal applications and pretty much
> everyone
> else out there assuming the opposite.
> Is there precedent to using non-ASCII chars in our code or can we just
> agree on ASCII? I mean for code only, not documentation that is not
> generated from the code, some files in www/, etc which obviously need
> to be encoded in UTF-8.

COMMITTERS contains several non-ASCII characters, iirc.

However, I was just trying to be technically correct with the above
spelling. If it causes problems, we can change it.


Received on 2009-05-15 16:41:54 CEST

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