John Machin wrote:
There may possibly different interpretations of a codepage out there
somewhere, but they are all *intended* to be the same, and I advise
you to cross the different-cp437s bridge *if* it exists and you ever
come to it.
Have you got access to files with LDID not in (0, 1) that y
On Oct 28, 2:51 am, Ethan Furman wrote:
> John Machin wrote:
> > On Oct 27, 7:15 am, Ethan Furman wrote:
>
> >>Let me rephrase -- say I get a dbf file with an LDID of \x0f that maps
> >>to a cp437, and the file came from a german oem machine... could that
> >>file have upper-ascii codes that will
John Machin wrote:
On Oct 27, 7:15 am, Ethan Furman wrote:
>
Let me rephrase -- say I get a dbf file with an LDID of \x0f that maps
to a cp437, and the file came from a german oem machine... could that
file have upper-ascii codes that will not map to anything reasonable on
my \x01 cp437 machin
On Oct 27, 7:15 am, Ethan Furman wrote:
> John Machin wrote:
> > On Oct 27, 3:22 am, Ethan Furman wrote:
>
> >>John Machin wrote:
>
> >>>Try this:
> >>>http://webhelp.esri.com/arcpad/8.0/referenceguide/
>
> >>Wow. Question, though: all those codepages mapping to 437 and 850 --
> >>are they real
John Machin wrote:
On Oct 27, 3:22 am, Ethan Furman wrote:
John Machin wrote:
Try this:
http://webhelp.esri.com/arcpad/8.0/referenceguide/
Wow. Question, though: all those codepages mapping to 437 and 850 --
are they really all the same?
437 and 850 *are* codepages. You mean "all those
On Oct 27, 3:22 am, Ethan Furman wrote:
> John Machin wrote:
> > On Oct 24, 4:14 am, Ethan Furman wrote:
>
> >>John Machin wrote:
>
> >>>On Oct 23, 3:03 pm, Ethan Furman wrote:
>
> John Machin wrote:
>
> >On Oct 23, 7:28 am, Ethan Furman wrote:
>
> > Try this:
> >http://webhelp.esri.com
John Machin wrote:
On Oct 24, 4:14 am, Ethan Furman wrote:
John Machin wrote:
On Oct 23, 3:03 pm, Ethan Furman wrote:
John Machin wrote:
On Oct 23, 7:28 am, Ethan Furman wrote:
Greetings, all!
I would like to add unicode support to my dbf project. The dbf header
has a one-byte
On Oct 24, 4:14 am, Ethan Furman wrote:
> John Machin wrote:
> > On Oct 23, 3:03 pm, Ethan Furman wrote:
>
> >>John Machin wrote:
>
> >>>On Oct 23, 7:28 am, Ethan Furman wrote:
>
> Greetings, all!
>
> I would like to add unicode support to my dbf project. The dbf header
> has a one-
John Machin wrote:
On Oct 23, 3:03 pm, Ethan Furman wrote:
John Machin wrote:
On Oct 23, 7:28 am, Ethan Furman wrote:
Greetings, all!
I would like to add unicode support to my dbf project. The dbf header
has a one-byte field to hold the encoding of the file. For example,
\x03 is cod
On Oct 23, 3:03 pm, Ethan Furman wrote:
> John Machin wrote:
> > On Oct 23, 7:28 am, Ethan Furman wrote:
>
> >>Greetings, all!
>
> >>I would like to add unicode support to my dbf project. The dbf header
> >>has a one-byte field to hold the encoding of the file. For example,
> >>\x03 is code-pag
John Machin wrote:
On Oct 23, 7:28 am, Ethan Furman wrote:
Greetings, all!
I would like to add unicode support to my dbf project. The dbf header
has a one-byte field to hold the encoding of the file. For example,
\x03 is code-page 437 MS-DOS.
My google-fu is apparently not up to the task o
On Oct 23, 7:28 am, Ethan Furman wrote:
> Greetings, all!
>
> I would like to add unicode support to my dbf project. The dbf header
> has a one-byte field to hold the encoding of the file. For example,
> \x03 is code-page 437 MS-DOS.
>
> My google-fu is apparently not up to the task of locating
12 matches
Mail list logo
