translation & untranslated nodes in XML textfield

Author Message

Björn Dieding@xrow.de

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?

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

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 Dieding@xrow.de

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.

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 10:35:12
Script start
Timing: Jan 18 2025 10:35:12
Module start 'layout'
Timing: Jan 18 2025 10:35:12
Module start 'content'
Timing: Jan 18 2025 10:35:12
Module end 'content'
Timing: Jan 18 2025 10:35:12
Script end

Main resources:

Total runtime0.0209 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0097 588.0469152.6406
Module start 'layout' 0.00970.0039 740.687539.4922
Module start 'content' 0.01360.0050 780.179793.3672
Module end 'content' 0.01860.0023 873.546934.3047
Script end 0.0209  907.8516 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.003114.7847140.0002
Check MTime0.00125.5951140.0001
Mysql Total
Database connection0.00209.429310.0020
Mysqli_queries0.004722.519430.0016
Looping result0.00000.086710.0000
Template Total0.00199.110.0019
Template load0.00104.628510.0010
Template processing0.00094.422010.0009
Override
Cache load0.00073.240910.0007
General
dbfile0.00021.047680.0000
String conversion0.00000.051440.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs