I tried again, after having updated the old PC (let's name it "Corsair", this is the network alias it uses) with the latest bells & whistles from Norton and MS Windows 10. This a i7 3500 machine. TM and the whole project are on a NAS. Studio is the current build 14.0.5746.0.

And I got again the same error as above - some files are not recognized.

The other PC (called "Spitfire") is a i7 6700k machine. It accesses the same NAS in my local network.

Both Corsair and Spitfire have a full Internet connection. Both run Windows 10, both are protected with the same version of Norton AV. Studio was installed on both after having uninstalled the previous beta. The only difference is, that Spitfire has had the very latest beta, while on Corsair I had one of the first betas of 2017.

Now Spitfire has finished the analysis and reported 7 errors - all were "Out of memory exceptions". So I think I will run the analysis again in the night, after a PC restart and with only Studio running there. So far we would have a basis for working.

Now the next question:

In customer files we have not only source and target, but also named groups elements. Here's an example:

    <trans-unit id='CAT.ALT.230.1.A' maxwidth='12' resname='ALT.230.1' restype='Category.Abbr' size-unit='x-characters'>

     <source>Overridden</source>

     <target>Overridden</target>

     <context-group name='Item Information'>

      <context context-type='x-info'>Category abbreviation in item [ALT-230-ALERT STATUS] for category title
       "Overridden". Item description: "alert status"</context>

      <context context-type='x-length'>12 characters</context>

     </context-group>

     <note>• INFO: Category abbreviation in item [ALT-230-ALERT STATUS] for category title "Overridden". Item description: "alert status" LENGTH:
      12 characters STRING ID: CAT.ALT.230.1.A</note>

    </trans-unit>

We have to make sure, the translator can see this additional elements, while this elements do not need to be translated. Studio ignores these completely. When I would create a xml file type with only "target" as translatable item, could I declare this tags above as comments? Even if I know how to create a file type I do not yet know how to declare elements to be just comments in Stuido.

Hi Jerzy,

You mentioned that you switched off the validation in the XML filetype, however this should be prepared using the XLIFF filetype, shown here:

Do you not see this filetype in the project settings? If not, it might be located in the Additional installed File Types exist:

If you are using this filetype, I also noticed that these are just warnings, so I would think the files are still processed, just that these entities are not being converted correctly, meaning that &eacute; will be parsed simply as this entity, not as the character it represents: é

Also, if it is necessary to prep this file as XML for some reason, you can turn on/off entity conversion here:

Thank you

Luke

Hi Jerzy,

Maybe a simple stylesheet is the answer here?  Something really simple could be created like this but it might give you what you need:

I created a simple XLIFF file from your sample text and added an XSL file into the preview section of the filetype.  the attached zip contains the sample XLIFF, the filetype settings file and the XSL file.  I'm sure you could do something similar when you how simple such a basic XSL file can be:

epic xlf.zip

You could probably add the comments into the document structure too with some fiddling around but I think the preview is far more accessible.

Regards

Paul