On Tue, 8 Jul 2003, Bill Janssen wrote:
> It depends on the multibyte encoding. However, in Plucker, we really
> can't have them, since we use NUL to introduce function codes in the
> text stream.
The present code will work fine with NUL in the middle of a multi-byte
character. Only a NUL at th
> Is there anywhere one can ask to get an "official" answer to such a
> question, as my question whether middle or final bytes can be zero?
Again, it depends on the character set encoding. You can't answer
that without restricting the usage to some set of character set
encodings. Currently, the
It depends on the multibyte encoding. However, in Plucker, we really
can't have them, since we use NUL to introduce function codes in the
text stream. I think you can count on this for text records in a
Plucker DB.
Bill
> > > 2. Can multi-byte encoded texts have nulls that do not signal the end
Is there anywhere one can ask to get an "official" answer to such a
question, as my question whether middle or final bytes can be zero?
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: w
> > 2. Can multi-byte encoded texts have nulls that do not signal the end of
> > the string, i.e., nulls in the middle of multi-byte characters? (I
assume
> > there can't be nulls at the start of them--if there can, our code is in
> > trouble.)
>
> Uhmm.. although this isn't my area of expertise,
On Tue, Jul 08, 2003 at 11:00:26AM -0400, Alexander R. Pruss wrote:
> 1. There is no guarantee that every bit of text in a record is followed
> eventually by a null, right? (There is, e.g., no guarantee that there is
> a function at the end of a record, or a terminating null?)
I don't think so. I
I am trying to optimize the rendering code. Things could, indeed, be made
more efficient if one didn't care about multi-byte encodings. Of course,
we should care about them. ANyway, while optimizing, I had some
questions:
1. There is no guarantee that every bit of text in a record is followed
e
