Forums / Suggestions / translation & untranslated nodes in XML textfield

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

translation & untranslated nodes in XML textfield

Author Message

Björn X

Friday 11 July 2003 2:13:03 am

I somehow figured out the the translation option for xml text fields is uneasy to handle.

We should archive something like the following.

for example if you do a technical translation you always have text/code that never change and parts that need translation

<h1>MY php code</h1>
<literal>
echo "asdasd";
exit;
<literal>

I love to see that we would have some kind for translation namespaces/attribute in the main language contentobject.

e.g.
image the following we have a obj with a xmk attrrib for main language eng-GB that looks like that

<h1 translation=head>MY php code</h1>
<literal translation=sourcecodel>
echo "asdasd";
exit;
<literal>

in the obj of ger-DE we would use now

<h1>Mein PHP Quellcode</h1>
<translation name=sourcecode />

in this example the object of ger-DE would reference to eng-GB and get the proper value of &translation name=sourcecode /&

What do you think?

Bård Farstad

Saturday 12 July 2003 10:30:24 am

This sounds like a problem we should address. But the implementation should not give overhead or be hard to use.

This should also be handled generally by all datatypes.

--bård

Documentation: http://ez.no/doc

Björn X

Wednesday 16 July 2003 2:07:37 am

Yes I bet you find a much easier way in doing this back referencing to the main translation.