Some of my segments aren't recognized by the Translation Providers. Usually they include some tags liike shown here:
Here is another example of a segment which is "ignored" by the Translation Providers:
These are my Translation Providers, working fine on other segments:
Is this a bug or can I do something about it?
Many thanks!
You can provide a sample file and the settings to achieve what you have shown. I spent time trying to mimic what you shave shown but probably could not get what you have:
Everything seems ok for me. So to investigate this further you need to supply something to test with.
Thank you for testing, Paul.
I explored a bit further, and checked whether if the beghavioru is consistent. So I went back to that segment, deleted the translation and waited for the response of the Translation Providers. In my initial posting above in screenshot 2 it stuck at "Searching ...". When revisiting the segment (cursor in empty segment translation) and checking or unchekcing oine of my 4 providers, I get this error: "The end tag </1> does not have a matching tag":
When I leave the segment and reenter it again, it says: "4 matches found" (but doesn't show any):
Only when I play with the combnination of activated providers, I get results. It seems that any combination without DeepL does work. Chanhig the position of DeepL in the list of providers doesn't solve it.
So I guess that the problem lies within the DeepL addon.
Maybe that helps. I can of course send you a stripped down source (HTML that is) file as well, but thought that kind of digging might be helpful as well.
Can you make sure you have the latest DeepL plugin installed? There was an update recently (will check if it was released) and I do recall that message being part of the problem that needed solving. It stems from DeepL and not the plugin specifically, but I know the developers tied to workaround it as it may be faster than waiting for a fix from DeepL.
ok - it's not released, but we do have a fix and it's in QA. All being well it'll be released soon.
Alright, thanks for letting me know! I will work without DeepL for now.
I checked today with the latest version 6.1.3.2 from 2024-02-16 - still the same problem.
Please provide an sdlxliff, and the underlying html file it was based on, that exhibits this behaviour.
Thanks
Paul.
Paul
I have project-specific parser settings for HTML as well, do you need a settings file (.sdlproj probably?)? Or some other information?
Can I send the files you asked for by mail?
Can I send the files you asked for by mail?
I only want a very small file that just contains these problematic sentences. You should be able to do that easily enough, then zip them and attach to here.
Translate
