Re: lynx-dev chrtrans .tbl format (was: ... (em dash = --)

[dickey]

> 16-Mar-99 20:28 Klaus Weide wrote: 
> >> >    U+2001: 
> >> >    U+2003: 
> >> 
> >> > (there are two significant spaces at the end of both lines) 
> >> > should probably become 
> >> >    U+2001 "  " 
> >> >    U+2003 "  " 
> >> 
> >> there is no universal solution, yours will restrict " char from the 
> >> string. 
>  
> > I think you miss that this syntax is already implemented - and you 
> > can use stuff like "...\"..." for embedded " chars.  But I was just 
> > suggesting to use this for the few strings with significant trailing 
> > spaces, not to change all lines. 
>  
> >    Klaus 
>  
> Yes, I have overlooked it. I thought it was for octal codes etc. 
> and miss its obvious usage for 7bit replacement strings: 
> It was not written explicitely in chrtrans/README.format 
> Apparently, dev.20 happens to have "-- " for mdash instead of "--" 
> (I guess Tom was misguided from our discussion in a rush hour 
> and made incorrect interpretation of a patch sent by e-mail as open text). 

not exactly - I missed the trailing blank because I've been generally
refraining from trimming trailing blanks in *.tbl (you told me not to
do that early last year).  As a matter of practice, I have been
trimming all of the other files (patches sent in email always come
to me with trailing blanks, unless they're uuencoded).

>  
> I think we should tweak README.format 
> so *every* string with trailing spaces 
> should be enclosed as U+1234 "..." string (add example) 
> with (or without?) support for trailing spaces in U+2345:normal 

yes.
  
> >From the current chrtrans/README.format: 
>  
>  
> d) string replacement definitions: 
>  
>   They look like 
>  
>   U+00cd:I' 
>  
>   which would mean "Replace Unicode U+00cd (LATIN CAPITAL LETTER I WITH 
>   ACUTE" with the string (consisting of two character) I' (if no other 
>   translation is available)."  Please note that replacement definitions 
>   in certain charset table will override ones from the Default table. 
>  
>   Note that everything after the ':' is currently taken VERBATIM, so 
>   careful with trailing blanks etc. 
>  
>  * Syntax accepted: 
>  *      <unicode>       :<replace> 
>  *      <unicode range> :<replace> 
>  *      <unicode>       "<C replace>" 
>  *      <unicode range> "<C replace>" 
>  * 
>  * where <unicode range> ::= <unicode>-<unicode> 
>  * and <unicode> ::= U+<h><h><h><h> 
>  * and <h> ::= <hexadecimal digit> 
>  * and <replace> any string not containing '\n' or '\0', taken verbatim 
>  * and <C replace> any string, with backslash having the usual C meaning. 
>  
>  


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey