2009/5/13 Christian Weisgerber :
>
> Being able to use it with a Unix-style filesystem is one of UTF-8's
> design principles.
>
> All ASCII characters (0-127) represent themselves; all characters
>>127 are represented by sequences of bytes with the top bit set.
I recently looked into this. Apologi
Toni Mueller wrote:
> > OpenBSD does not restrict or interpret filenames in any way, apart
> > from the obvious: / and NUL are not allowed in filenames.
>
> I guess, but don't know, that NUL is not part of any UTF-8 character...
Being able to use it with a Unix-style filesystem is one of UTF-8'
Hi,
On Wed, 13.05.2009 at 19:26:59 +0900, Jordi Beltran Creix
wrote:
> print '?' or an octal escape sequence on nonprint chars. With a hacked
> libc and a utf-8 version of multibyte functions as well as a few fixes
> on apps solve most of these problems, gtk apps and scim will be happy
> with ju
On Wed, May 13, 2009 at 12:55:05PM +0200, Toni Mueller wrote:
> Hi,
>
> On Wed, 13.05.2009 at 12:12:31 +0200, Otto Moerbeek wrote:
> > show me what filename you constructed (and how you did that) and the
> > contents of ls-output.txt. I prefer hexdump -C, btw.
>
> I can't send you a recipe for co
Hi,
On Wed, 13.05.2009 at 12:12:31 +0200, Otto Moerbeek wrote:
> show me what filename you constructed (and how you did that) and the
> contents of ls-output.txt. I prefer hexdump -C, btw.
I can't send you a recipe for constructing these filenames because I
didn't do it, and I also don't have th
utf-8 is ignored as regular valid ASCII in most utilities. This is
what makes utf-8 so nice.
The main problem(1) is for utilities like for example ls and ed that
use isprint to determine if they are allowed to print a character and
print '?' or an octal escape sequence on nonprint chars. With a ha
On Wed, May 13, 2009 at 11:59:04AM +0200, Toni Mueller wrote:
> Hi Otto,
>
> thanks for the quick answer.
>
> On Wed, 13.05.2009 at 10:50:37 +0200, Otto Moerbeek wrote:
> > On Wed, May 13, 2009 at 10:35:25AM +0200, Toni Mueller wrote:
> > > fd = open(filename_with_utf8_characters);
> > >
> > >
Hi Otto,
thanks for the quick answer.
On Wed, 13.05.2009 at 10:50:37 +0200, Otto Moerbeek wrote:
> On Wed, May 13, 2009 at 10:35:25AM +0200, Toni Mueller wrote:
> > fd = open(filename_with_utf8_characters);
> >
> > succeed on a standard OpenBSD disk (FFS, if I'm not mistaken), using
> > open(2)
On Wed, May 13, 2009 at 10:35:25AM +0200, Toni Mueller wrote:
> Hi,
>
> from a discussion around early November last year, I gather that
> OpenBSD has not much UTF-8 support right now. I am a bit unsure about
> whether having file names with UTF-8 characters are supported, though.
> I don't need
Hi,
from a discussion around early November last year, I gather that
OpenBSD has not much UTF-8 support right now. I am a bit unsure about
whether having file names with UTF-8 characters are supported, though.
I don't need to type the characters, nor see or print them, but only
have a program like
10 matches
Mail list logo
