Re: [Tm4j-developers] [ tm4j-Bugs-881422 ] TM4Web: display of special chars broken in main display

[Christoph F. <cf...@fo...>]

Hi=20

while thinking about alex' bug report regarding the display of special
chars in TMNav/TM4Web it seems to me, that technically there are three
different issues.

Nevertheless, I'm skating on thin ice, so please correct me if I'm
wrong:


> (1) &auml=20
this is an html-entity. It does not have any meaning outside of html.
But since it is widely used, I would like to add the resolving of
html-entities as an option to the labeling mechanics of panckoucke.


> (2) œ_ &#140 (oe/OE lig)=20
> (3) Œ_&#339 (same)=20
Theese are xml(sgml?)-entities that should be resolved by the
xml-parser. I would be surprised, if the ltm-parser resolves them.  But
maybe it should? In order to make things more convinient for the user?
I tend to the opinion that panckouckes labeling mechanism shouldn't
resolve theese entities, but I would be glad to hear what others think.

> (4) =E4=F6=FC=DF_=C4=D6=DC=20
This enters the field of encodings. In xml this issue should be handled
by the parser. I don't know whether the ltm-parser considers the
encoding attribute of the source file but since alex reported that TMNav
presents theese chars correctly, I assume, that the encoding is already
taken into account by the ltm parser.


does that make sense?

bye=20
c

  =20
> =20
> results:=20
> --------=20
> TMNav:=20
> (4) ok=20
> =20
> TM4Web:=20
>   Main page with all topics: none working=20
>     (4) looks like UTF-8 viewed in ISO-8859-1=20
>   topic.vm: (1), (2), (3) ok=20
> =20
> alex=20
--=20
Christoph Froehlich <cf...@fo...>