Knut Atle Klausen

What have you done to try and narrow this down?  That process of thinking about what could cause this may help you find the solution to the problem.  So for example:

• have you checked that the project template you are using when you create a project is set up to handle txlf files?
• if it is, then when you add your files in the project wizard is the file shown as recognised or not at that point?
• if it's not recognised what do you see when you then click in the settings from the project wizard to check the filetype is correctly configured?

Hi Paul,

I do have some thinking process going on when facing a problem like this, but it is pretty simple, I must admit. I am very focused on a big and compliacted project and I just want the tools to work. The thing about the template did not cross my mind at all, but your are right, I changed it to default, and then they became acceptet and translatable. That is great, but when I tried open the files, I get a popup about the wrong source language, but I think it is the correct one. I probably should have some idea about narrowing it down, but for now it is just "What on earth do the project expect?"

When I open a single file, it has by default American English as source and I have to choose the target language. So I specify the languages in the project according to that. The files are American English and my target is Norwegian bokmål, it always is, so there should be no problems there.

Knut Atle Klausen

Knut Atle Klausen said:

I know what language pair the files has; the same as the project. I am still not able to open the files

Perhaps you can share the language codes used in the TXLF and also confirm the languages being used in your Studio project?

Knut Atle Klausen said:

When I open a single file, it has by default American English as source and I have to choose the target language.

ok.  So this tells me that the TXLF files have no target language specified and Studio is going to complete the segmentation and add the languages.  Perhaps you can take the header of the TXLF, delete all the trans units apart from one or two and edit the content so it can be shared.  Then paste it into here so we can test and see if we can find where the problem is coming from?

OK, I will save this one for later. Problem is, there is almost 100 files. I am just checking them, and would have liked to send them through QA Checker, but Xbecnh works well, so that has to be it. 

Knut Atle Klausen

Knut Atle Klausen said:

Problem is, there is almost 100 files.

So the problem could also be that just one of these files doesn't have the same languages as the rest.  If you are inclined to try and figure it out you could try taking just one of the files you know you can open as a single file project and see if you can create a project with just that one file.

I just did, but it was not that. I open the file as single file and than made a project of it, but the same message came. First I thought this was it, as I could see both a xml and html among the billinguals, so first I deleted those and tried, but did not work.

Knut Atle Klausen can you share one of these files?

No, not for this project. I did check another project for the same customer from May just now, and the same happens. I include it here. But I just realized some bits of information I did not share: These files comes actually from wordfast packages, which I change to zip and open. I do not have wordfast desktop versions and work in wordfast online, but check stuff in SDL, Xbench etc. Maybe this fact has something to do with it? This file seems to have no other extension other then the txlf, but the others I work on today are html, or at least there is html i the names (like this: Fourth Arm Control 1.html-Source_TXLF-no-NO#PR_BHYWSH#). 
U_NO_.zip

Knut Atle Klausen

Thanks for the file, this helped and now I can reproduce exactly what you are seeing and I know how to solve it.

First thing is that the TXLF uses no-NO for Norwegian Bokmål while Studio will use nb-NO since this is what Microsoft uses as well.  So the reason you get no target language code is because Studio doesn't know what it is.

Next thing is that when you create a Project, if you use the drag and drop (which I would highly recommend you don't), the files will be checked against the default languages in your template and as a result if your default template source happens to be something other what's in the file you will get the message you have shown.  If however you create your project using the create a new project icon in the Projects View or by using Ctrl+N you will be able to correct the languages that are in the default before you add your files.  This way you won't get that error on creation.  You will however still get it when you try to open the file.

So this leads me onto the only way to fix this which is to use a text editor to correct the language codes in the TXLF files.  So this:

target-language="no-NO"

Needs to be changed to this:

target-language="nb-NO"

Then you won't have any of the problems you have mentioned so far.  I think that if we had a TXLF filetype specifically for Trads Studio we could map the languages Wordfast uses and avoid these issues.  But seeing as you are doing what I would do and have probably added *.txlf to the fiemask for the XLIFF filetype you are caught up with using a very specific XLIFF filetype that validates the languages.

Some good news is that we are buildig a new multilingualXML filetype for the AppStore at the monent and this filetype would allow you to handle these files easily and without any worries over language codes because it doesn't care what codes are used.  You just tell it where the source is and where the target is, and then what languages they should be.  That's it.  So once we release it you'll find these problems are a thing of the past.

Thanks a lot, Paul, much appriciated. I will for sure use Ctrol+N in the future and very good to know that there was a difference in language codes (nb-NO is the only correct one, as we have two written languages, the other having "nn" as code. For this job it would be too much work, but often it is only three huge documents and then it will certainly help. I look very much forward to the multilingualXML! 

Thanks for all your help and sorry for being moody.

Best regards,

Knut

Knut Atle Klausen

Replacing codes in 100's of files shouldn't be a problem.  Easy way if you have Notepad++ is like this:

https://darrenoneill.eu/?p=1250

Knut Atle Klausen

Replacing codes in 100's of files shouldn't be a problem.  Easy way if you have Notepad++ is like this:

https://darrenoneill.eu/?p=1250