"Carlos Santander B." <carlos8294@msn.com> wrote in message news:bhccj1$2emj$1@digitaldaemon.com...
> Bug:
>
> void main() { char x='á'; }
>
> invalid UTF-8 sequence

It is an invalid utf-8 sequence. Code pages with values 0x80-0xFF won't work with UTF-8.

> I must admit I don't know about encoding and such, but that just doesn't
> make sense to me.
> (I think it doesn't work for anything not 7 bit ascii, but I don't know.
It
> doesn't work with dchar either)

The source text needs to be UTF-8, UTF-16 or UCS-4. Does your text editor have a setting for that? (Notepad does.)

What I apparently need to write is a translator from the usual code pages to UTF-8. Anyone have a guide to the mappings?

"Walter" <walter@digitalmars.com> wrote in message
news:bhe1u2$12n1$1@digitaldaemon.com...
|
| It is an invalid utf-8 sequence. Code pages with values 0x80-0xFF won't
work
| with UTF-8.

So, what should I use instead?

|
| The source text needs to be UTF-8, UTF-16 or UCS-4. Does your text editor
| have a setting for that? (Notepad does.)
|

I use SciTE, and if I save in UTF-8 encoding, I get:

test.d(1): unsupported char 0xef
test.d(1): unsupported char 0xbb
test.d(1): unsupported char 0xbf

————————————————————————— Carlos Santander


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.509 / Virus Database: 306 - Release Date: 2003-08-12

"Carlos Santander B." <carlos8294@msn.com> wrote in message news:bhe3r9$14jq$1@digitaldaemon.com...
> "Walter" <walter@digitalmars.com> wrote in message
> news:bhe1u2$12n1$1@digitaldaemon.com...
> |
> | It is an invalid utf-8 sequence. Code pages with values 0x80-0xFF won't
> work
> | with UTF-8.
>
> So, what should I use instead?
>
> |
> | The source text needs to be UTF-8, UTF-16 or UCS-4. Does your text
editor
> | have a setting for that? (Notepad does.)
> |
>
> I use SciTE, and if I save in UTF-8 encoding, I get:
>
> test.d(1): unsupported char 0xef
> test.d(1): unsupported char 0xbb
> test.d(1): unsupported char 0xbf

Email me the source file, and I'll have a look.

I found & fixed the problem. In the meantime, you can work around it by either lopping the first 3 bytes off of the file or try writing it out as UTF-16 instead.