public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: gerrit.scholl@philips.com
Cc: kronos@kronoz.cjb.net, linux-kernel@vger.kernel.org,
	linux_udf@hpesjro.fc.hp.com
Subject: Re: Unable to read UDF fs on a DVD
Date: 27 Apr 2004 10:11:26 -0600	[thread overview]
Message-ID: <1083082286.6562.55.camel@patibmrh9> (raw)
In-Reply-To: <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phil i ps.com>

Three points:

1)

> > I remember separately I saw the ... guess that the
> > unamerican chars were at issue: maybe the truthful or slanderous
> > rumours of UDF in 2004 tripping over unamerican chars as often as
> > other software does have substance.
> 
> I do not know what 'unamerican chars' problem there could be in:
>  
> > http://web.tiscali.it/kronoz/ucf_test.log

Same as you, I do not yet understand, but:

The rumour of unamerican char troubles in UDF implementations reached
this thread without coming from me.  From others we have, in the
subscriber-only linux_udf@h... archives:

-----
Cc: linux_udf@h...
Subject: Re: Unable to read UDF fs on a DVD
Date: 23 Apr 2004 14:15:10 -0600

On Fri, Apr 23, 2004 at 09:50:04PM +0200, ... wrote:
> 
> I used udfct utility (from Philips). The output is quite long, I put it
> here:
> 
> http://web.tiscali.it/kronoz/ucf_test.log

Ok, that confirmed my guess as to what the problem is (it's a problem
with 16 bit characters vs 8 bit characters)

I'll work up a patch this weekend.
...
-----

2)

My local records tell me no patch has reached `cvs co udf` or `cvs co
udftools` at sourceforge.net/linux-udf/ since 2004-03-22.

3)

I say "unamerican chars" to mean the printable chars that do not appear
on a US keyboard, even when lowercased.  Do you prefer some other term?

I can't be sure how literally the authority quoted above meant 16 vs. 8
bit.  For example, I fear together all of:

$'\x23' # "octothorpe"
$'\xA3' £ "pound sterling, ... Italian lira, ... etc."
$'\xA5' ¥ "YEN SIGN"
$'\xE2\x82\xAC' x20AC € "EURO SIGN"

Yet only the x20AC of these four chars is unequivocally not "8 bit".

The char names I quote I took from http://www.unicode.org/charts/

The arcane $'\xXX\xXX\xXX' UTF-8 notation is from `man bash` re \xHH.

Pat LaVarre


       reply	other threads:[~2004-04-27 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phili ps.com>
     [not found] ` <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phil i ps.com>
2004-04-27 16:11   ` Pat LaVarre [this message]
2004-04-27 19:48     ` Unable to read UDF fs on a DVD Pat LaVarre
     [not found] <OF7EE48D71.4DD148E6-ONC1256E82.003678FE-C1256E82.0038D7EE@phili ps.com>
     [not found] ` <OF7EE48D71.4DD148E6-ONC1256E82.003678FE-C1256E82.0038D7EE@phil i ps.com>
2004-04-26 21:24   ` Pat LaVarre
2004-04-23 16:28 Kronos
2004-04-23 17:56 ` Pat LaVarre
2004-04-23 19:50   ` Kronos
2004-04-23 20:21     ` Pat LaVarre
2004-04-24 19:47       ` Kronos
2004-04-26 15:52         ` Bill Davidsen
2004-04-26 21:48         ` Pat LaVarre

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=1083082286.6562.55.camel@patibmrh9 \
    --to=p.lavarre@ieee.org \
    --cc=gerrit.scholl@philips.com \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_udf@hpesjro.fc.hp.com \
    /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