from that page:
While UTF-8 does not have byte order issues, a BOM encoded in UTF-8
may be used to mark text as UTF-8. It only identifies a file as UTF-8
and does not state anything about byte order.[1] Quite a lot of
Windows software (including Windows Notepad) adds one to UTF-8 files.
and according to the unicode consortium:
A: Yes, UTF-8 can contain a BOM. However, it makes no difference as
to the endianness of the byte stream. UTF-8 always has the same
byte order. An initial BOM is only used as a signature -- an
indication that an otherwise unmarked text
On 9/8/07, Elf [EMAIL PROTECTED] wrote:
and does not state anything about byte order.[1] Quite a lot of
Windows software (including Windows Notepad) adds one to UTF-8 files.
However in Unix-like systems (which make heavy use of text files for
configuration) this practice is not
CarlosPita ([EMAIL PROTECTED])
has invited you as a friend on Quechup...
...the social networking platform sweeping the globe
Go to: http://quechup.com/join.php/aT0wMDAwMDAwMDA5OTgyMTgwJmM9MTAyMjE0 to
accept Carlos's invite
You can use Quechup to meet new people, catch up with old
On Sep 8, 2007, at 2:49 PM, Terrence Brannon wrote:
(require-extension array-lib)
(require-extension array-lib-hof)
(define (quikary shape)
(let ([element-count (apply * shape)])
(apply array shape (iota element-count
(define h (quikary '(2 3)))
Quibble - 'shape' above isn't a
On 9/9/07, Kon Lovett [EMAIL PROTECTED] wrote:
On Sep 8, 2007, at 2:49 PM, Terrence Brannon wrote:
(require-extension array-lib)
(require-extension array-lib-hof)
(define (quikary shape)
(let ([element-count (apply * shape)])
(apply array shape (iota element-count
When I attempt to use pos.scm I get this error -
#;9 ; loading /usr/local/lib/chicken/1/pos.scm ...
Error: (define-syntax) during expansion of (define-syntax ...) -
highlevel macros are not supported
Call history:
syntax(require-extension pos)
syntax
everything ive seen on the unicode site itself seems to discourage the use of
a BOM outside of protocol ambiguous cases since its not a necessary object.
its not an easy thing to be tolerant of in code text, although it is
relatively easy to be tolerant of it in plain text. possibilties: is it
Shawn Rutledge scripsit:
Instead, you think Scite should assume that when it sees any bytes
with the MSB set, the file is UTF-8? Or there is a better way to
detect it?
There is no *guaranteed correct* way to detect UTF-8, because a Latin-1
(or various other 8859-x encodings) file can contain
BOM breaks the UNIX shebang mechanism. To me, this is good enough
reason to avoid prepending a BOM to scripts, and to detect encoding
via heuristic, user directive or current locale.
On 9/9/07, John Cowan [EMAIL PROTECTED] wrote:
Shawn Rutledge scripsit:
It would be nice if Chicken was
it does not seem to work:
(require-extension protobj)
(define a (%))
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On 9/10/07, John Cowan [EMAIL PROTECTED] wrote:
Pierpaolo Bernardi scripsit:
which says that you can put a bom in a utf8 file (of course, you can
put whatever character you want in a file), but it is a character
like every other character, it has no particular meaning wrt the encoding.
12 matches
Mail list logo
