nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Localization

oduiubo

Hello,
I am straggling again with template localization English and French.
I am using

substitution

method to do on fly language localization.
Almost everything works fine. Only one problem I cannot resolve which is label localization under item nodes. All others elements are working fine.

This is a snapshot of the code:

[PHP]

G&eacute;n&eacute;rique

&eacute;l&eacute;ments
&eacute;l&eacute;ments

[/PHP]

Even, when I am changing problematic part to unescaping solution and entered entity to DOCTYPE TeamSite returns error SAX Parse:The entity "eacute" was referenced, but not declared.

This is a sample:
[PHP]
.
.
.

G&eacute;n&eacute;rique

éléments
&eacute;l&eacute;ments

[/PHP]

It is looks for me TeamSite 6.7.2 and 6.7.1 as well have some problem with FormAPI.

If you have some solution or idea, please provide it. I would like to try.

Find more posts tagged with

Comments

ISCBorisB

You are trying to use HTML's named Entities ( like é ) in the distinctly XML context.

HTML (eg, Browser) may *know* what these Entities are, XML (eg, XML Parser) certainly does not.
What you can do is use XML Numeric Entities directly or define your own Internal / External / Parameter
Entities. Like this:[php]

Éléments - Numeric XML Entities
<br />

Éléments - Internal XML Entities
<br />

[/php]

oduiubo

Entities declaration does works in static template (hardcoded template). When I am doing

inline substitution

entire

root-container

it's just doesn't work. This is kind of frustration.

oduiubo

Thank you Boris,
It's working with

substitution

only when I remap entities to hex numbers. It might works even with decimal type but, I didn't try.

ISCBorisB

Thank you Boris,
It's working with substitution only when I remap entities to hex numbers. It might works even with decimal type but, I didn't try.

Not sure what you mean by "substitution" - an inline XML output?

If so, remember that both substitution Fragment and ultimate DCT must be well-formed XMLs
with declared Entities, etc. It's actually not that hard to use named Entities in inlines, just
keep in mind double-parsing. Ampersand is one of the five predefined XML Entities. So, something
like &Eacute; is a perfectly good XML. It *should* render as É on the DCT level
and as long as Eacute is a defined Entity there (Internal or perhaps Parameter) it'll probably work.
(note that I have not tested that)

Btw, you can certainly use either Hex or Dec numeric entities, matter of personal preferences

oduiubo

Yes Boris, I am talking about

inline

element.
XML is definitely well formatted. I did simple test when I got error at first time by coping XML from

substitution

(which is I pushed also to a log file) and replaced

inline

node. Result was successful, no errors, everything worked fine in hardcoded version.
Unfortunately, entities declaration doesn't work under

substitution

dynamic XML parts.

ISCBorisB

Unfortunately, entities declaration doesn't work under Substitution dynamic XML parts...

Oh, please... The following worked perfectly, I just tried.

If you need this stuff within multiple inline's abstract out Declarations of diacritical
character Entities into single Parameter Entity and use it everywhere instead of Internal
Entities

[php]*** This is DCT ***

Éléments - Numeric XML Entities
<br />

*** This is get_fragment.ipl ***

print q(

Éléments - Internal XML Entities
<br />
);[/php]