�ݺ�ߣ

Editor's Notes

• #3: XML is a software- and hardware-independent tool for storing and transporting data. It doesn’t do anything… it just stores data that’s used somewhere else, often in multiple places. Why is it called “XML”, my guess is that "XML" looked a lot cooler than "EML.“ The important part in here is actually the eXtensible bit… So XML has rules… but the developer has complete freedom to extend these and use them as he sees fit. So there are no predefined tags as there are in HTML for example
• #4: All the translatable text is in elements and all the elements are translatable
• #5: Studio, memoQ, Café Tran
• #6: When only the title is in an element and all the lines have been moved into attributes
• #7: When only the title is in an element and all the lines have been moved into attributes
• #8: So Studio would allow you to create a custom XML filetype, you import the file and it extracts the elements and attributes for you to easily select with a dropdown box. Déjà Vu lists all the elements and attributes so you go through each one and tell it how to handle them. But not all tools allow you to handle this at all… so in my example Café Tran does not let customise XML requirements at all… so you would not be able to handle these files with Café Tran for example.
• #9: In this example we have valid XML but it starts to get a little trickier… CDATA sections… and has the same text element but may not be an element you want to translate alternative translations that might be helpful as a preview Also the text elements are nested in verse# elements, so multiple rules could be required if you needed to be specific Max/min text lengths, maybe to suit some fixed window translate=“n” attribute
• #10: In this example we have valid XML but it starts to get a little trickier… CDATA sections… and has the same text element but may not be an element you want to translate alternative translations that might be helpful as a preview Also the text elements are nested in verse# elements, so multiple rules could be required if you needed to be specific Max/min text lengths, maybe to suit some fixed window translate=“n” attribute
• #11: In this example we have valid XML but it starts to get a little trickier… CDATA sections… and has the same text element but may not be an element you want to translate alternative translations that might be helpful as a preview Also the text elements are nested in verse# elements, so multiple rules could be required if you needed to be specific Max/min text lengths, maybe to suit some fixed window translate=“n” attribute
• #12: In this example we have valid XML but it starts to get a little trickier… CDATA sections… and has the same text element but may not be an element you want to translate alternative translations that might be helpful as a preview Also the text elements are nested in verse# elements, so multiple rules could be required if you needed to be specific Max/min text lengths, maybe to suit some fixed window translate=“n” attribute
• #13: So this is nothing specific to Studio or memoQ for example… this is a World Wide Web Consortium (w3c) recommendation as a web standard. So it’s easy to find information on how to learn this. We’re going to look at some basics to get you started.
• #14: What all that means is just this…
• #15: There isn’t a lot a theory around this, but it does take a little digesting and plenty of time to get your head around it all. It’s also all worth learning.
• #16: But if at this point you’re starting to feel like he does… then don’t worry… we only have an hour!! Of course it’s important to know all this stuff if you want to be completely comfortable with XPath, but for our normal day to day needs I don’t think you do. So let’s try and cut to the chase
• #17: Here we see two of a possible seven kinds of XPath nodes. An element and an attribute. “text” was the element simply referred to by name, and “line” was the attribute also referred to by name, but recognised as an attribute by using the @ symbol.
• #18: Here we see two of a possible seven kinds of XPath nodes. An element and an attribute. “text” was the element simply referred to by name, and “line” was the attribute also referred to by name, but recognised as an attribute by using the @ symbol.
• #19: It’s a little like a file path. We all know how these work and the path takes you straight to the file. Now add the XPath expression we just saw on the end… The // just means select from the text node no matter where in the path it is.
• #20: It’s a little like a file path. We all know how these work and the path takes you straight to the file. Now add the XPath expression we just saw on the end… The // just means select from the text node no matter where in the path it is.
• #23: Worth mentioning… but not free. Small built in helper tool available when using the memoQ multilingual XML filetype.
• #30: Let’s consider this simple sentence and break it down into a few simple components.
• #31: Let’s consider this simple sentence and break it down into a few simple components.
• #32: Let’s consider this simple sentence and break it down into a few simple components.
• #33: Let’s consider this simple sentence and break it down into a few simple components.
• #34: Now let’s take the same sentence and mark it up like this. This is basically how an XPath expression works using predicates. The node test would be the complete subject, and the predicate is always enclosed in square brackets.
• #35: Now let’s take the same sentence and mark it up like this. This is basically how an XPath expression works using predicates. The node test would be the complete subject, and the predicate is always enclosed in square brackets.
• #36: Now let’s take the same sentence and mark it up like this. This is basically how an XPath expression works using predicates. The node test would be the complete subject, and the predicate is always enclosed in square brackets.
• #37: Now let’s take the same sentence and mark it up like this. This is basically how an XPath expression works using predicates. The node test would be the complete subject, and the predicate is always enclosed in square brackets.
• #40: This is all about conflict resolution. Namespaces provide a way to avoid element name conflicts, but sometimes these cause complexity for the simple task of extracting all the text for translation.
• #45: XSLT is used to transform an XML document into another XML document, or another type of document that is recognized by a browser, like HTML and XHTML. With XSLT you can add/remove elements and attributes to or from the output file. You can also rearrange and sort elements, perform tests and make decisions about which elements to hide and display, and a lot more.
• #50: memoQ can’t handle images unless they are referred to from a URL (confirmed by Gábor Ugray) but the style and flow of the document is there.
• #51: memoQ can’t handle images unless they are referred to from a URL (confirmed by Gábor Ugray) but the style and flow of the document is there.