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

[Stefan Sperling <st...@elego.de>]

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.

Stefan

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

[Stefan Sperling <st...@elego.de>]

On Fri, May 15, 2009 at 09:41:34AM -0500, Hyrum K. Wright wrote:
>
> On May 15, 2009, at 6:27 AM, Stefan Sperling wrote:
>> 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.

And it would clearly fall under the category of files where UTF-8
is necessary.

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

Yeah.

Well, actually it is not causing problems for me right now.
It would have caused problems for me 2 weeks ago when I didn't have
a UTF-8 capable terminal, had I wanted to hack that file. There are
workarounds of course, mine was to use gvim instead of running vim
in a terminal.

So I guess my complaint is moot...
I was just thinking of future contributers who are in similar
situations as I was. But maybe OpenBSD is just the odd one out.
Most other systems in use today seem to have UTF-8 support all the way.
Let's just wait until it really becomes a problem for someone else.
Sorry about the noise.

And I agree that correctly spelt comments are more esthetically
pleasing.

OT: I have to admit that one of the first silly things I did after switching
to Linux again was to install all sorts of font packages, to enjoy all
the spam using non-latin characters I get in its full glory, in mutt.
No more question marks where non-latin chars should be! The only problem
(or blessing?) is that I still can't read it :)

Stefan

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

["Hyrum K. Wright" <hy...@hyrumwright.org>]

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.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2271607