From: Paul Steckler <steck@stecksoft.com>
To: caml-list@yquem.inria.fr
Subject: Windows filenames and Unicode
Date: Wed, 29 Sep 2010 15:05:39 +1000 [thread overview]
Message-ID: <AANLkTikXYCdGHBzQ0G4mRbrWcA245K5oOp1CZay-OYoT@mail.gmail.com> (raw)
In Windows, NTFS filenames are specified in Unicode (UTF-16). Am I
right in thinking that
OCaml file primitives, like open_in, readdir, etc. cannot handle NTFS
filenames containing
characters with codepoints greater than 255?
I'm aware of the Camomile library, which gives the ability to
manipulate UTF-16 strings inside
of OCaml. But it looks like crucial points of OCaml's I/O, like
Sys.argv and file primitives are
strictly limited to 8-bit characters.
Is there a way around this limitation, other than rewriting the file
I/O primitives?
-- Paul
next reply other threads:[~2010-09-29 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 5:05 Paul Steckler [this message]
2010-09-29 6:23 ` [Caml-list] " David Allsopp
2010-09-29 7:26 ` Paul Steckler
2010-09-29 7:56 ` Michael Ekstrand
2010-09-29 7:58 ` David Allsopp
2010-09-29 8:14 ` Jerome Vouillon
2010-09-30 19:27 ` ygrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikXYCdGHBzQ0G4mRbrWcA245K5oOp1CZay-OYoT@mail.gmail.com \
--to=steck@stecksoft.com \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox