• State Suggested Answer
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 436 subscribers
  • Views 4773 views
  • Users 0 members are here
Options

Analysing/editing of Wordpress xml files (online shop)

Corinna Ortmann

Hi to all you experts,

I'm desperately looking for a Studio 2019 filetype that allows me to analyze and work on XML files generated from a Wordpress site (online shop).

The standard XML filetype is working quite properly for the static web pages, but the shop data aren't read/analyzed/recognized at all.

I tried to define a custom XML filetype (e.g. according to the - very valuable - instruction on https://multifarious.filkin.com/), but failed - probably because I don't know too much about the XML file format - and I need to submit a quotation for both parts of the website (and naturally also have to work on those), not only for the pages.

Can someone help?

Thanks a lot for your assistance! 

Corinna
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Can you share a sample file so we can give you a hint?

    Paul Filkin | RWS Group

    ________________________
    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

    Hello Paul,

    Thanks for your reply and willingness to help - please find a sample file attached (hope this will do ...)

    Fullscreen sample-file.xml Download

    Thank you and kind regards, Corinna
  • 0 in reply to Corinna Ortmann

    Thanks for the sample file.  The first thing you need to do is identify what should actually be translated in this file.  Quickly reviewing this there is actually very little that looks as though it would be translatable... maybe just this part:

    <content:encoded><![CDATA[Keramische tegels worden al sinds de 16e eeuw gemaakt in Delft en omstreken. xxx eert deze traditie en creëert miniatuurverhalen op tegels. Alle tegels worden in Nederland ambachtelijk gebakken op hoge temperatuur. De kunstwerkjes zijn dus hitte- en waterbestendig waardoor het bijzondere design levenslang mee gaat. Elk ontwerp is met de hand gebakken en daarmee uniek.

    De tegels worden geleverd met een ophangsysteem en zijn beschikbaar in volgende maten: Small: 10×10 cm Medium: 13×13 cm* Large 20x20cm

    *De medium tegel is gelijk aan het formaat van het beroemde Oud Hollandse Witje    ]]></content:encoded>

    There are also some statuses and post types that may or may not be required for translation... I think you'd need to check with your client, so things like these:

    <wp:comment_status><![CDATA[closed]]></wp:comment_status>

    <wp:status><![CDATA[draft]]></wp:status>

    <wp:post_type><![CDATA[product]]></wp:post_type>

    The out of the box XML filetype will open this file and it extracts all of this along with a lot of other stuff I'm pretty sure you don't want.  So the first step is to determine what needs to be translated.

    Once you have this information it should be fairly sraightforward.  For example, I created a filetype using just two rules like this.  One to prevent anything from being extracted and then anoter to extract only the content of the content:encoded element above:

    Trados Studio error message indicating 'Please load sample.xml using XML filetype' with a red arrow pointing to the error.

    See if any of this helps you.

    Also, you mentioned that this file is not being handled at all and it should be.  Can you tell us more about what happens when you try to open it?

    Paul Filkin | RWS Group

    ________________________
    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:47 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Paul

    Hello Paul,

    Thanks for your reply. I just tried your a.m. solution, but I'm ending up with the same result.

    If I create a new project with one of the xml files in question, I receive an error message "The process can't access this xml file as it's used by another process". I confirm the error message and can then see the file in the project's initial screen with the created xml filetype assigned to it, but there's no way to continue creating the project:

    Trados Studio error message stating 'The process can't access this xml file as it's used by another process' with an 'OK' button.

    If I press "Next", I receive the next error message: "The project must contain at least one file to be translated", and I have no option but to abort creating the project.

    When I first received all xml files from the customer, I tried to analyse all 5 files in one project. Three files were analysed (static web pages), but these two xml files weren't analysed at all. I was able to see them in the project's file list, but without any content (both no word count and no content upon opening them in the Studio editor). 

    That's why I tried to create a custom xml file type for these two files. 

    Thanks & kind regards,

    Corinna
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:47 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Corinna Ortmann

    Corinna Ortmann said:
    "The process can't access this xml file as it's used by another process"

    This has nothing to do with the filetype settings.  I reckon if you open this as a single file for translation and not as part of your project it will probaby work.  If it doesn't then maybe you have this file open in another application somewhere?  Worth checking your processes to see what may be hanging onto it.

    If this is not the problem then it "might" be due to a known bug in Studo related to validation.  Try turning off all of these checks in your filetype validation before creating your project:

    Trados Studio screenshot showing the Validation options under File Types settings with a red arrow pointing to the 'Use only for XML documents' checkbox.

    Paul Filkin | RWS Group

    ________________________
    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:47 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Paul

    Hello Paul,

    the validation settings don't seem to be the root cause for this problem; they are identical to those shown in your screenshot.

    I had already tried to open the file as single file for translation - it actually does open, but there's no content:

    Trados Studio screenshot showing an empty Editor workspace with no content displayed, despite the file being opened for translation.

    To overcome the error message, I have also tried to copy this "problem file" (supposed to be open in another aplication) to another location and use that copied file instead, but still the message is the same. I have also rebooted my PC several times to make sure there's no process/application left using this file (I had indeed opened it in the text editor to check for the translateable lines, but also had closed the text editor before trying to create the project).

    Regards,

    Corinna
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:47 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Corinna Ortmann

    Corinna Ortmann said:
    the validation settings don't seem to be the root cause for this problem; they are identical to those shown in your screenshot.

    I didn't say copy my settings... I just showed you where they are.  Try turning them all off.

    Corinna Ortmann said:
    I had already tried to open the file as single file for translation - it actually does open, but there's no content:

    In this case you are either opening a file that has no content for translation, or you are not using the correct filetype.  If you switch to TagID mode then orange tab at the top of the file in the editor will display the name of the filetype being used and you can verify it.

    Trados Studio screenshot showing the Tag Id option highlighted in the editor toolbar.

    For me, because I created a custom xml filetype it says this:

    Trados Studio editor displaying 'wordpress.xml Translation en-US>de-DE' at the top with Dutch text content below.

    This is because I set it here:

    Trados Studio File Type Information dialog with 'wordpress_xml' entered as the File type definition.

    So whatever it says you should be able to make sure you are using the filtype you think you are.

    Paul Filkin | RWS Group

    ________________________
    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:48 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Paul
    Paul said:
    I didn't say copy my settings... I just showed you where they are.  Try turning them all off.

    Sorry for expressing this unclearly - they are all turned off, that's what I meant.

    Paul said:
    So whatever it says you should be able to make sure you are using the filtype you think you are.

    Actually, the filetype created before (I named it "wordpress-test") has been used. 

    BUT ... I just tried the same not using the "real" xml file, but using the sample file instead I created to provide it here. And unbelievably, this file works perfectly fine and delivers the same result as on your side. So, I assume that the problem is not the custom filetype creation, but maybe an error in the source files.

    I'll get in touch with the customer to double-check - maybe I'm not that stupid after all. 

    Thank you very much, Paul, for your great support on this! I'll update this post as soon as they'll provide me with new source files to let you know whether it's solved.

    Best wishes,

    Corinna
  • 0 in reply to Corinna Ortmann

    Hello Paul, 

    Just to round this topic off - the customer has decided to not provide a new file exported from WP, but to copy the translateable text manually and have a Word document translated ... 

    Therefore, I have no possibility to further check whether a new file would do fine. 

    However, as the sample file worked perfectly also with my Studio version, I assume that the corrupted/damaged file was the only reason for my problems with this custom xml file type creation.

    If I face such task again, I'll certainly rely on your approach. Thanks again for your great support and patience! Relaxed

    Best wishes,

    Corinna