Translation XLIFF format

Thanks Christine (for both!)

Good morning Christine!

I did get Cleo's reply/suggested fix but have had to stay on a project with a closer deadline... I'll let you know how the project shakes out.

Thanks for keeping tabs on it!

Mike

Hi again

 I can now import the file but the problem is not solved please that text will not change in storyline

The tags was wrong

i replaced > with >

Furthermore the degree celsius sign is exported wrong in the xliff file

so now i import the file again but the changes i make in the exported file does not appear when i import the file back again...

what can i do? switch to .doc? i prefer xliff because it much smarter when working with translations...

kr

Robert

Hi Robert,

I took a quick look this morning and I see that we've received a support case for this problem (#00309516). Someone will be contacting you soon regarding the issue and will work with you to resolve it.

Thanks, Robert. Have a great Friday!

Christine

In readiness for a series of translations and realising that I have not done this before I thought I'd test it. I have a rather large Story file that takes a few minutes to export. I have simply changed a few words and saved it with a new file name.  Importing from Word works fine, but when I import the xliff file it states Import successful almost immediately and no changes made. 

Translating seems so straightforward that it surely cannot be operator error.  So do I have a similar issue to Robert?

Hi Bryan,

The first thing I would check is the location of the file. Make sure all the files you're working with are local. If you try to export, edit, or publish from project files on an external source, you may run into issues. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate). Avoid using special characters, accents or symbols in your file names.

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

If you've confirmed all the files are local, we'd be happy to take a closer look at what's happening. 

Thanks!

Thanks, Christine, for covering all the bases. But the filenames and structure are pretty standard. As the file is:

1. 137Mb
2. Commercially sensitive

Hi Bryan

To double-check the process you're using to import the xliff file, please take a look at this tutorial and the below Screencast:

You may also want to check to make sure there are no characters in the translated text that may be causing issues. Are you able to import any other xliff files? 

I have only seen a handful of reports regarding xliff files, most seem to be file or system specific, so it may be best to have our technical department test the files, if the suggestions above don't resolve the problem.

Thanks Bryan,

Christine

Christine, I'm sure I'll get there eventually! 

When I export and select file type as xliff.  I would expect the default of .doc to change, but it doesn't.

So, I should leave this as .doc, do I (and not manually change the file extension)? My thought is that the translation company are expecting .xliff files and sending a doc file would lead to confusion (as indeed I have!)

Bryan

Good morning Bryan,

I think I see at least a little something that's causing a problem there. The file name when you're saving shouldn't be ".doc", you're right. Do you have the correct option set for "Save as type", though. The name doesn't need to have an extension on it. If you do that, it may cause some confusion (as you can see ) and some issues. Try either removing the ".doc" from the file name, or add ".xliff" in its place. 

So, it would look something like this:

Try that out and let me know if it makes a difference.

Thanks!