You are currently working on UAT 

  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 430 subscribers
  • Views 1948 views
  • Users 0 members are here
Options
Related

Context information in bilingual Excel file from XML will not be imported in Studio 2019

Daniel Hug

Hi,

when I open an XML file with Excel and save it as an Excel Workbook, Studio 2019 won't read the context information.

I moved the Bilingual file format up and deactivated all other Excel file formats in the project settings. In the File view, Studio says "Bilingual Excel v.1.0.0.0" in the column "File Type Identifier". But when I process the file, no context information is displayed in the document structure column.

If I copy the entire spreadsheet and past only the VALUES into a new workbook, then add the workbook to the same Studio project, it will read everything correctly: Source text, target text, context information - everything wonderful.

Why does Studio not manage to read context information in the "original" Excel file with XML information?

Daniel
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Here I am, answering my own question...maybe somebody else can profit from this:

    The XML map that Excel saves in the file seems to cause the problem. After deleting the XML map in the Excel file, Studio manages to read the file correctly. (Excel can re-import the map from the original XML file and after mapping the columns onto the map fields, the whole thing exports sweetly as XML which can be imported into a CMS for example.)

    For the future, I wonder whether SDL could refine the bilingual Excel file format definition to tolerate an XML map in an Excel file.
    Ceterum censeo... a bilingual XML file format would be very desirable as the whole Excel detour is a workaround and has all the little problems that workarounds do have in this world.

    Daniel
  • 0 in reply to Daniel Hug

    Daniel Hug said:
    a bilingual XML file format would be very desirable as the whole Excel detour is a workaround and has all the little problems that workarounds do have in this world.

    I've seen a few people develop their own, but nobody has ever put one on the appstore... well there was one once but they removed it because they didn't want to share.

    Creating one isn't that difficult for a developer because there is a good starting point in the SDK with an example filetype.  Maybe the appstore team will pick this up one day if nobody else is ever going to share what they have done.

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul Filkin

    Hi Paul,

    I would surely appreciate this. At the moment I need to run Excel macros to get all the German umlauts from HTML code into normal characters and back on the return trip. ­ I mark as tag. It works, but it's a few extra steps.

    The most grievious loss is the document structure display in the navigation pane. That is sad.

    A while ago a user asked how to deal with bilingual Excel files here in the forum (can't find the post now) and considered the Excel route to be not an option because she would have to re-import the xml file into a CMS (Sitecore if I remember correctly). I want to point out that re-importing such XML files into a CMS does work. Excel seems to be very stable here.

    Daniel
Reply
  • 0 in reply to Paul Filkin

    Hi Paul,

    I would surely appreciate this. At the moment I need to run Excel macros to get all the German umlauts from HTML code into normal characters and back on the return trip. ­ I mark as tag. It works, but it's a few extra steps.

    The most grievious loss is the document structure display in the navigation pane. That is sad.

    A while ago a user asked how to deal with bilingual Excel files here in the forum (can't find the post now) and considered the Excel route to be not an option because she would have to re-import the xml file into a CMS (Sitecore if I remember correctly). I want to point out that re-importing such XML files into a CMS does work. Excel seems to be very stable here.

    Daniel
Children
No Data