wrong table by importing translation from xml to framemaker

[lowflow]

Hi,

with frammaker 11, after translation we import a ANSI_table back into Framemaker. loding the edd and template over it, the ANSI table still has the layout of a standard TableA. so we have to manualy convert each ANSI_table to its correct ANSI_table layout.

is this a problem of RW-Rules ore something else?

the RW-rules lok like:

ccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc

/* ***************************************************** */

/* **      ANSI Sicherheitshinweis-Elemente                ** */

/* ***************************************************** */

element "Sicherheitshinweis_ANSI" {

is fm element "Sicherheitshinweis_ANSI";

attribute "Cols" is fm property columns;

attribute "Cws" is fm property column widths;

}

element "ANSI_table" {

is fm table element "ANSI_table";

fm property columns value is "3";

fm property column widths value is "2.5cm 10.2cm 2.5cm";

}

element "ANSI_Tabellebody" is fm table body element "ANSI_Tabellebody";

element "ANSI_Tabellereihe" is fm table row element "ANSI_Tabellereihe";

element "ANSI_Tabelle_Inhalt" {

is fm table cell element "ANSI_Tabelle_Inhalt";

}

element "ANSI_2SicherheitsstufenTitel" {

is fm element "ANSI_2SicherheitsstufenTitel";

attribute "ANSI_Sicherheitsstufe" {

is fm attribute "ANSI_Sicherheitsstufe";

value "Gefahr" is fm value "Gefahr";

value "Warnung" is fm value "Warnung";

value "Vorsicht" is fm value "Vorsicht";

value "Hinweis" is fm value "Hinweis";

value "Sicherheitsanweisung" is fm value "Sicherheitsanweisung";

}}

element "ANSI_SicherheitsstufenTitelBalken" {

is fm element "ANSI_SicherheitsstufenTitelBalken";

}

element "ANSI_SicherheitsstufenTitelInhalt" {

is fm element "ANSI_SicherheitsstufenTitelInhalt";

}

element "ANSI_1Gefahrensymbol" {

is fm element "ANSI_1Gefahrensymbol";

attribute "GefahrenArt" {

is fm attribute "GefahrenArt";

value "ANSI_Stromschlag" is fm value "ANSI_Stromschlag";

value "ANSI_Dampf" is fm value "ANSI_Dampf";

value "ANSI_HeisseFluessigkeit" is fm value "ANSI_HeisseFluessigkeit";

value "ANSI_HeisseOberflaeche" is fm value "ANSI_HeisseOberflaeche";

value "ANSI_Quetschen" is fm value "ANSI_Quetschen";

value "ANSI_Giftig" is fm value "ANSI_Giftig";

value "ANSI_ESD" is fm value "ANSI_ESD";

value "ANSI_GefahrAlgemein" is fm value "ANSI_GefahrAlgemein";

}}

element "ANSI_3Sicherheitsbeschreibung" {

is fm element "ANSI_3Sicherheitsbeschreibung";

attribute "Ort" {

is fm attribute "Ort";

value "Im_Kapitel_Allgemeine_Sicherheitshinweise" is fm value "Im_Kapitel_Allgemeine_Sicherheitshinweise";

value "In_anderen_Kapitel" is fm value "In_anderen_Kapitel";

}}

element "ANSI_GefahrenQuelleFolge" {

is fm element "ANSI_GefahrenQuelleFolge";

}

element "ANSI_Massnahme" {

is fm element "ANSI_Massnahme";

}

element "ANSI_4HinweiseSymbol" {

is fm element "ANSI_4HinweiseSymbol";

attribute "HinweiseSymbol" {

is fm attribute "HinweiseSymbol";

value "Handschuhe" is fm value "Handschuhe";

value "Brille" is fm value "Brille";

value "Netztrennung" is fm value "Netztrennung";

value "HaendeWaschen" is fm value "HaendeWaschen";

value "Algemein" is fm value "Algemein";

}}

element "ListInANSI_Table" {

is fm element "ListInANSI_Table";

attribute "Ort" {

is fm attribute "Ort";

value "Im_Kapitel_Allgemeine_Sicherheitshinweise" is fm value "Im_Kapitel_Allgemeine_Sicherheitshinweise";

value "In_anderen_Kapitel" is fm value "In_anderen_Kapitel";

}}

element "ListInANSITablePunkt" is fm element "ListInANSITablePunkt";

cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc

best regards

beat

[Lynne A. Price]

Beat,

   You can specify the table format for an imported table in three ways:

1) With an InitialTableFormat subelement of the Table element in the EDD

2) With an XML attribute, identified with an fm property table format value is "xxx";

3) If different ANSI_table tables use different formats, with an XML attribute. Use the attribute "attname" is fm property table format;

         --Lynne

[lowflow]

Dear Lynne

thanks for your answer.

I asume the first one is genaraly spocken the best way to go?

so i would have to add it in the edd's element catalog below the section (1) "inhaltstruktur tabelle" = "contentstructure table"

and not within the section (2) "ANSI_table"?

see picture below

Best regards

beat

[Lynne A. Price]

Beat,

   All the methods I listed have their place, depending on the circumstances. If I understand your original message, you want to use table format ANSI_table for every ANSI_table element. You can specify the table format in either the EDD or the r/w rules. In the EDD, you would modify the existing definition of ANSI_table. In an English EDD, you'd enter something like:

Element (Table): ANSI_table

    General rule:  ...

    Initial table format

         1.   In all contexts.

                    Table format: ANSI_table

   The initial table format is the format that FM applies when you create the table, either interactively when editing or by opening an XML document. Importing element definitions from the EDD does not change the format of existing tables (the designers of FM's structured tables recognized that formatting a table can depend highly on the particular table and therefore decided to preserve any table format that a user applied manually).

   This definition would apply the table format when you open an XML document. When you create a new table, FM will still bring up the Insert Table dialog box, and you will be able to select any defined table format, but the table format will be initialized to ANSI_table.

    The other approach would be to add one more read/write rule, changing:

element "ANSI_table" {

is fm table element "ANSI_table";

fm property columns value is "3";

fm property column widths value is "2.5cm 10.2cm 2.5cm";

}

to

element "ANSI_table" {

is fm table element "ANSI_table";

fm property table format value is "ANSI_table";

fm property columns value is "3";

fm property column widths value is "2.5cm 10.2cm 2.5cm";

}

Note that the read/write rule will affect only tables read from XML, not tables created during editing.

--Lynne

[lowflow]

Dear Lynne,

thanks a lot this helped me very much, we are testing it and i will get back to you asap.

best regards

beat

[Lynne A. Price]

You are quite welcome!

    --Lynne

[Stefan-Gentz]

Beat,

as you mention that something goes wrong "after translation" I assume, that opening the source language XML file works as expected? Because then it sounds more like something went wrong in the translation process. Any translation tool should not mess up the XML code and expose only the text itself to the translator and any attributes should get properly set up in the file format filter of the CAT tool if their values are extracted for translation or not. Maybe the CAT tool's custom file format XML filter was not set up that way?

Example:

You have a table element. This table has an attribute style with value "Sicherheitshinweis". Based on this attribute value you let FM apply a certain formatting (table style "Sicherheitshinweis" from the template).

Like this:

<table style="Sicherheitshinweis">
     (...)
</table>

Now, if you send this to translation, and the CAT is configured to read and expose all attributes, the translator will get a segment "Sicherheitshinweis" (he/she might not even able to see that this is an attribute value!) and will translate it e.g. for English into "Security advice". That is, you will get back from translation this XML:

<table style="Security advice">
     (...)
</table>

Now, when you open this XML in FM, FM will look into the EDD and template and will try to apply the table style "Security advice". However, if there is no table style "Security advice" in the template, this will fail, and FM will fall back to "TableA" style as the default table style.

Have you compared if the XML elements and attributes in the translated file are exactly the same as in the source file that you sent to translation and where it worked?

*Stefan.

[lowflow]

Dear Stefan,

thanks for your answer, this is a good input but the translaters have done a got job and did not make this mistake.

best regards

beat