D.gnu - invalid UTF-8 sequence compiler error
- Cesar Rabak (11/11) Apr 01 2007 Doing some tests on the gdc-0.22-1 for Linux (result of uname -a: Linux
- Carlos Santander (5/20) Apr 01 2007 This is a D feature, not a GDC problem. Save your file as UTF-8, -16, or...
- Cesar Rabak (6/10) Apr 01 2007 It will take time to convince my folks it is a feature but I'll try :-)
- Cesar Rabak (7/16) Apr 06 2007 In a chat with the stake holders I learned the source I can use the code...
- Thomas Kuehne (12/26) Apr 07 2007 -----BEGIN PGP SIGNED MESSAGE-----
- Cesar Rabak (10/32) Apr 07 2007 Thanks Thomas.
- Lars Ivar Igesund (9/44) Apr 07 2007 If you should find yourself in need of such conversion routines, conside...
- Cesar Rabak (3/23) Apr 08 2007 Thank you, Lars.
- 0xFFFFFFFF (3/23) Jun 30 2018 Even tho I didn't ask the question, it does solve my problem too.
Doing some tests on the gdc-0.22-1 for Linux (result of uname -a: Linux Pentium(R) 4 CPU 3.00GHz GNU/Linux), I got the error "invalid UTF-8 sequence" even if the 'offending' character is in comments. Since the gcc counterpart does not complain on similar code with locale specific characters (mainly accented chars), I ponder: Is there a way to have a gdc that can work with accented characters in strings and comments? Regards, -- Cesar Rabak
Apr 01 2007
Cesar Rabak escribió:Doing some tests on the gdc-0.22-1 for Linux (result of uname -a: Linux Pentium(R) 4 CPU 3.00GHz GNU/Linux), I got the error "invalid UTF-8 sequence" even if the 'offending' character is in comments. Since the gcc counterpart does not complain on similar code with locale specific characters (mainly accented chars), I ponder: Is there a way to have a gdc that can work with accented characters in strings and comments? Regards, -- Cesar RabakThis is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work. -- Carlos Santander Bernal
Apr 01 2007
Carlos Santander escreveu: [snipped]This is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work.It will take time to convince my folks it is a feature but I'll try :-) Thanks, -- Cesar Rabak
Apr 01 2007
Cesar Rabak escreveu:Carlos Santander escreveu: [snipped]In a chat with the stake holders I learned the source I can use the code I want, but for the message strings I'll need to abide the sysadmin's decisions which may be not UTF-. How it is this solved with the D compiler? -- Cesar RabakThis is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work.It will take time to convince my folks it is a feature but I'll try :-)
Apr 06 2007
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cesar Rabak schrieb am 2007-04-06:Cesar Rabak escreveu:If you simply store and print message you could use "ubyte[]". For everyting else like searching, concating etc. more information about the encoding(s) is required. Thomas -----BEGIN PGP SIGNATURE----- iD8DBQFGF4+YLK5blCcjpWoRArCeAJ9rHeF6lxdnM84SbB0u+yn8v9q+igCdHakA 7Wzc3v3elbwKzB7y+wAwudQ= =Lzag -----END PGP SIGNATURE-----Carlos Santander escreveu: [snipped]In a chat with the stake holders I learned the source I can use the code I want, but for the message strings I'll need to abide the sysadmin's decisions which may be not UTF-. How it is this solved with the D compiler?This is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work.It will take time to convince my folks it is a feature but I'll try :-)
Apr 07 2007
Thomas Kuehne escreveu:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cesar Rabak schrieb am 2007-04-06:Thanks Thomas. For going further in the tests for the consideration of D for programming in new projects storing and printing messages is all I need by now. If too much text data starts to appear to be processed I might have to consider an input method that makes the appropriate conversion to an internal representation (and an output one, too). -- Cesar RabakCesar Rabak escreveu:If you simply store and print message you could use "ubyte[]". For everyting else like searching, concating etc. more information about the encoding(s) is required.Carlos Santander escreveu: [snipped]In a chat with the stake holders I learned the source I can use the code I want, but for the message strings I'll need to abide the sysadmin's decisions which may be not UTF-. How it is this solved with the D compiler?This is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work.It will take time to convince my folks it is a feature but I'll try :-)
Apr 07 2007
Cesar Rabak wrote:Thomas Kuehne escreveu:If you should find yourself in need of such conversion routines, consider using the ICU (IBM package for such things) bindings in the Mango library, see http://www.dsource.org/projects/mango -- Lars Ivar Igesund blog at http://larsivi.net DSource, #d.tango & #D: larsivi Dancing the Tango-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cesar Rabak schrieb am 2007-04-06:Thanks Thomas. For going further in the tests for the consideration of D for programming in new projects storing and printing messages is all I need by now. If too much text data starts to appear to be processed I might have to consider an input method that makes the appropriate conversion to an internal representation (and an output one, too). -- Cesar RabakCesar Rabak escreveu:If you simply store and print message you could use "ubyte[]". For everyting else like searching, concating etc. more information about the encoding(s) is required.Carlos Santander escreveu: [snipped]In a chat with the stake holders I learned the source I can use the code I want, but for the message strings I'll need to abide the sysadmin's decisions which may be not UTF-. How it is this solved with the D compiler?This is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work.It will take time to convince my folks it is a feature but I'll try :-)
Apr 07 2007
Cesar Rabak <crabak acm.org> Lars Ivar Igesund escreveu:Cesar Rabak wrote:[snipped]Thomas Kuehne escreveu:Thank you, Lars.Thanks Thomas. For going further in the tests for the consideration of D for programming in new projects storing and printing messages is all I need by now. If too much text data starts to appear to be processed I might have to consider an input method that makes the appropriate conversion to an internal representation (and an output one, too). -- Cesar RabakIf you should find yourself in need of such conversion routines, consider using the ICU (IBM package for such things) bindings in the Mango library, see http://www.dsource.org/projects/mango
Apr 08 2007
On Monday, 2 April 2007 at 01:37:27 UTC, Carlos Santander wrote:Cesar Rabak escribió:Even tho I didn't ask the question, it does solve my problem too. ThanksDoing some tests on the gdc-0.22-1 for Linux (result of uname 2005 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GNU/Linux), I got the error "invalid UTF-8 sequence" even if the 'offending' character is in comments. Since the gcc counterpart does not complain on similar code with locale specific characters (mainly accented chars), I ponder: Is there a way to have a gdc that can work with accented characters in strings and comments? Regards, -- Cesar RabakThis is a D feature, not a GDC problem. Save your file as UTF-8, -16, or -32, and it'll work.
Jun 30 2018