Re: treatment of SDATA (was Re: (dsssl) Jade keeps translating...)

Subject: Re: treatment of SDATA (was Re: (dsssl) Jade keeps translating...)
From: Holger Klawitter <lists@xxxxxxxxxxxx>
Date: Mon, 31 Mar 2003 21:33:36 +0200
>  If I may ask an ignorant question: what's SDATA? 

SDATA means "system specific data". "&auml;", for example, might be a 
differenct character depending on the character set you are using. You can 
mark Entities to be other types as well, like NDATA and CDATA, which I am too 
tired to explain now ;-)

> What are the
> implications of "blocking all SDATA entity refs from being
> translated"?  If, as I guess, it means preserving all "&nbsp;",
> "&#160;"


> , and "Æ" types of characters from being changed,

This is not an entity-ref.

> I don't see
> why you'd ever *not* want it.

I almost never want SDATA to be translated as my output should stay device 

> Seriously, my problem occurs in two places.  I mentioned the code
> problem, that things like
>     (literal "abc&nbsp;def")
> result in "abc def" (with a normal space). 

Text exists in three states:
1.) node-list data [input],
2.) strings [variables, dsssl code, constants, ...] and
3.) sosofo [output]

Inside strings there is no such thing as entityrefs.
preserve-sdata helps you only directly from 1.) to 3.)

You should try to avoid the other state changes! If you can't, I can place 
some other code online on request ...

With kind regards / mit freundlichem Gruß
	Holger Klawitter
Holger Klawitter                

 DSSSList info and archive:

Current Thread