Tim Young [Elevate Software] wrote:

> .. This feature is
> still "hidden" for release as part of 2.04, but here's the new
> syntax that you can use to "unhide" it:
>

Brilliant, it even imports without breaking my cludge (but cludge now
removed).  Tested with UTF-16 files with and without BOMs - it just
'works', all by istself.

I have not tried importing from UTF-8 files with BOMs but if that
works I guess the file *will* need a BOM.

The icing on the cake would be an option to export in any of the
supported encodings instead of just Ansi and UTF-16.

Malcolm

--

Malcolm,

<< Brilliant, it even imports without breaking my cludge (but cludge now
removed).  Tested with UTF-16 files with and without BOMs - it just 'works',
all by istself. >>

There is one bug that Frank found - if you specify the ENCODING UNICODE
clause under EDB Unicode versions, it doesn't skip the BOMs properly and
barfs on the import.  So, the key is to only use the ENCODING UNICODE when
there aren't any BOMs, at least until that is fixed.

<< I have not tried importing from UTF-8 files with BOMs but if that works I
guess the file *will* need a BOM. >>

It probably won't handle UTF-8 properly at all.

<< The icing on the cake would be an option to export in any of the
supported encodings instead of just Ansi and UTF-16. >>

Baby-steps, baby-steps....  We've had a request for XML for some time,
so that is next, and I'll look at other encodings also at that time.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

>
> There is one bug that Frank found - if you specify the ENCODING
> UNICODE clause under EDB Unicode versions, it doesn't skip the BOMs
> properly and barfs on the import.  So, the key is to only use the
> ENCODING UNICODE when there aren't any BOMs, at least until that is
> fixed.
>

Hmm, I thought it worked both with and without a BOM in my little
test.  But I did not use the ENCODING clause, I let it default.  I
will test again tomorrow some time - maybe I didn't have a BOM when I
thought I did!

Malcolm
--

Malcolm,

<< Hmm, I thought it worked both with and without a BOM in my little test.
But I did not use the ENCODING clause, I let it default. >>

Yeah, if you don't use the ENCODING clause on the IMPORT, then you'll be
fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Malcolm,
>
> << Hmm, I thought it worked both with and without a BOM in my
> little test. But I did not use the ENCODING clause, I let it
> default. >>
>
> Yeah, if you don't use the ENCODING clause on the IMPORT, then
> you'll be fine.

Good, and that probably means it is a simple fix for you.  

It was most considerate of you to introduce a bug that does not
affect me .. though Frank may wonder why you picked on him.  I must
remember not to push too hard for new features before their time.
<vbg>

--

Malcolm,

<< Good, and that probably means it is a simple fix for you.   >>

Actually, yes - skip a couple of bytes in a file stream.

<< It was most considerate of you to introduce a bug that does not affect me
... though Frank may wonder why you picked on him.  I must remember not to
push too hard for new features before their time. >>

Yes, let that be a lesson to everyone here..... (evil grin)....

--
Tim Young
Elevate Software
www.elevatesoft.com

> Malcolm,

> It was most considerate of you to introduce a bug that does not
> affect me .. though Frank may wonder why you picked on him.  I must
> remember not to push too hard for new features before their time.

Sometimes you have to take one for the team

Frank wrote:

>
> Sometimes you have to take one for the team

Very true.  Been there, got the T-shirt.

--