Subject | Re: [firebird-support] UTF8 database and extended characters |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2008-11-14T10:04:37Z |
Helen Borrie escreveu:
Then it pad strings with spaces based on byte lengths. If you see the
output on a UTF8 editor/screen, everything is in wrong place.
to not work.
Adriano
> Adriano,No. It's because ISQL doesn't know length in characters but only bytes.
>
> At 12:03 AM 14/11/2008, Adriano dos Santos Fernandes wrote:
>
>> Another know problem you will see is the wrong formatting in utf8.txt.
>> The others things should be equal.
>
> Is the "formatting problem" you refer to the habit, of Notepad, OO.o and other text editors, of auto-inserting a BOM sequence at the beginning of the file?
>
Then it pad strings with spaces based on byte lengths. If you see the
output on a UTF8 editor/screen, everything is in wrong place.
> UTF8 doesn't need a BOM (unlike other Unicode formats, it is byte-order-neutral). For my UTF8 scripts I have been using a free, open source editor called Notepad-Plus-Plus (Notepad++) which allows you to save unicode files without the BOM. (You can convert existing textfiles in-line with this editor as well; *and* it is SQL-aware! -- very worthwhile for developers of GUI third-party tools to consider building into their products.)Yes. Notepad++ do the right thing. In fact, notepad BOM make "isql -i"
>
to not work.
> For Linux you *can* run NP++ in Wine but I don't like that idea...so I'm still looking for a kill-BOM (preferably CLI) editor to use on Linux...in the meantime, I make my scripts on Windows and take the option to save them in Linux format. Thanks to formatting my decommissioned laptop HDD as FAT32 and putting it into service as an external USB drive, it's not a showstopper for me...Maybe pico/nano or gedit?
>
Adriano