• State Suggested Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 434 subscribers
  • Views 2953 views
  • Users 0 members are here
Options

Fixing errors from XML Validator

Naoko Jones

Hello Community,

 

I am an engineer and don't speak translator, and that's why I am here to ask the community if anyone is interested in recording their brilliant tips and tricks on how to fix errors reported by XML Validator. If you already have some handy, can you kindly point them to me?

If you translate DITA content, you are or should be familiar with XML Validation and error messages from it. I believe there is no other way around it.

For one reason or another, translators complain and ask DITA system to be changed. We have provided trainings regularly but there is always someone new to DITA. We just want to be able to point them to recordings of fellow translator’s showing how to go about it. I hope that’s not too much to ask.

If someone is willing but doesn’t have DITA files handy, I could potentially craft something so that there will be no client data exposed in the recording. Thanks for listening.

 

Thanks,

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

    Seems an interesting question... I'd be interested too. perhaps you can clarifiy a few things:

    1. Which XML Validator are you referring to?
    2. Can you give a few examples of the sort of errors you are referring to?

    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
    Hi Paul,

    I really need to learn how to use the Community. My apologies for the delay here.

    1. The common file format that requires XML Validation is DITA and,
    2. here are a few example messages and Studio behaviors when the messages are double-clicked on

    o The errors message says “The element ‘systemoutput’ has invalid child element ‘systemoutput’, and double-clicking the error message took you to a segment with no tags. Then you go back a few segments up where you can find a segment with “systemoutput” tags. You can see that “systemoutput” tags are nested (one inside the another pair), which needs to be fixed.


    o The element ‘uicontrol’ has invalid child element ‘b’. List of possible elements expected: ‘keyword, options…
    It is usually hard to tell where errors are coming from and we need to refer to the English source segments closely for an entire file with errors in it.

    o The element ‘menucascade’ cannot contain text. List of possible elements expected: ‘uicontrol’.
    The same as above. Double-clicking the error message does not take you to the segment that needs fixing.

    The issues of linguists not being able to fix XML validation errors, pop up so often that we just thought documenting this type of information is not attractive enough for linguists to spend time on reading. We need short videos that linguists can consume without feeling too difficult to deal with.

    PS. I love your picture from SKO/GSD.

    Thanks,
    Naoko
  • 0 in reply to Naoko Jones

    Hi  

    Unknown said:
    I really need to learn how to use the Community. My apologies for the delay here.

    No worries :-)

    Unknown said:
    1. The common file format that requires XML Validation is DITA

    Ah, I see.  I wondered if you were using some other tool called "XML Validator".  My bad... understand now.

    Unknown said:
    The issues of linguists not being able to fix XML validation errors, pop up so often that we just thought documenting this type of information is not attractive enough for linguists to spend time on reading.

    It sounds as though it might be a good idea to document as many of these problems as possible and see whether the development team can improve the error referrals so they make it easier for the linguist to find the problem in the file and fix it.

    Unknown said:
    PS. I love your picture from SKO/GSD

    hehe... it was a fun event and great to catch up with representatives from your neck of the woods.

    I hope you do get some feedback from others here.  I'd like to see how other people deal with these issues too.

    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