[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: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 15 May 2009 12:27:59 +0100

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.

Received on 2009-05-15 13:28:31 CEST

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