This page is part of the web mail archives of SRFI 52 from before July 7th, 2015. The new archives for SRFI 52 are here. Eventually, the entire history will be moved there, including any new messages.
(continued) as opposed tab, which is commonly presumed to be advance to the next natural vertical character position representing at least one equivalent space, as defined by either the application and or platform default. (over all, it's interesting that possibly in lieu of worrying about any specific character-sets, it may be more productive to define the presumed display semantics of a more abstract language/platform dependant character-set, which may express itself differently based on the target language and platform conventions of the text it composes, rather than trying to worry about how to deal with N potentially different representations of a particular character may exist in different language texts; for example although Chinese is displayed vertically, tab for example is always presumed to have the same relative semantics, or if the letter z is typically displayed differently in Slavic languages, it is presumed to do so based on whatever that languages conventions are (although I confess to not being familiar with it's implied complexities, it feels more productive than placing the responsibility for the idiosyncrasies of an arbitrary language/platform on the programmer). -paul- > From: Paul Schlie <schlie@xxxxxxxxxxx> > Date: Sun, 15 Feb 2004 17:23:37 -0500 > To: <srfi-52@xxxxxxxxxxxxxxxxx> > Subject: Re: char-whitespace? > Resent-From: srfi-52@xxxxxxxxxxxxxxxxx > Resent-Date: Sun, 15 Feb 2004 23:23:48 +0100 (NFT) > > Actually surprised to here that, as with the exception of tab, I perceive > the remaining control characters to have no common semantics, other than > being used by various platforms as being being semantically equivalent to > newline; and correspondingly perceive newline not to be literal character, > but an abstraction for the end-of-line sequence as presumed by various > different platforms, which is how it's historically been treated. > >> From: bear <bear@xxxxxxxxx> >> Date: Sun, 15 Feb 2004 13:40:17 -0800 (PST) >> To: Ken Dickey <Ken.Dickey@xxxxxxxxxxxxxx> >> Cc: srfi-52@xxxxxxxxxxxxxxxxx >> Subject: Re: char-whitespace? >> Resent-From: srfi-52@xxxxxxxxxxxxxxxxx >> Resent-Date: Sun, 15 Feb 2004 22:40:28 +0100 (NFT) >> >> On Sat, 14 Feb 2004, Ken Dickey wrote: >> >>> I just noted that Tab, Form Feed, Line Feed, and Carriage Return have >>> Unicode >>> class Cc [Control Code] and are not in Zs (Separator, space) or Zl >>> (Separator, line). >>> >>> I suspect the char-whitespace? definition should include them. >> >> agreed. >> >> Bear >> >