Forum: CAT Tools Technical Help
Topic: TMLookup
Poster: FarkasAndras
Post title: Creative tag formatting
[quote]Michael Joseph Wdowiak Beijer wrote:
The TMX was created by Déjà Vu X3. Just sent it to you.
Thanks for the new version!
Michael [/quote]
As expected, this is due to creative tag formatting. The tmx has the <tuv xml:lang="nl"> tag split between two lines and TMLookup expects it to be on one line. Again, like a previous issue, this is because TMLookup doesn't have a proper xml parser because I can't be bothered to learn how to implement one. So instead of wrangling with a horrible coding problem I'm left wrangling with somewhat less horrible troubleshooting problems every now and then. So it goes. I could just look for xml:lang= without the tuv, but in principle some tmx files could have other elements where the language is specified with xml:lang=, not just the text itself. So then it could break on those. This can be solved in multiple ways of course, but none of them are trivial or appetizing to me. Implementing a proper parser is the least appetizing of all. So maybe I'll fix this... maybe not. Adding the language codes to the filename should work.
In the meantime, the new version of sqlite that will allow for somewhat fancier/faster text searches is trickling down the pipeline. It went through two stages and it is now one step away from where I can start fiddling with it. We'll see.
Topic: TMLookup
Poster: FarkasAndras
Post title: Creative tag formatting
[quote]Michael Joseph Wdowiak Beijer wrote:
The TMX was created by Déjà Vu X3. Just sent it to you.
Thanks for the new version!
Michael [/quote]
As expected, this is due to creative tag formatting. The tmx has the <tuv xml:lang="nl"> tag split between two lines and TMLookup expects it to be on one line. Again, like a previous issue, this is because TMLookup doesn't have a proper xml parser because I can't be bothered to learn how to implement one. So instead of wrangling with a horrible coding problem I'm left wrangling with somewhat less horrible troubleshooting problems every now and then. So it goes. I could just look for xml:lang= without the tuv, but in principle some tmx files could have other elements where the language is specified with xml:lang=, not just the text itself. So then it could break on those. This can be solved in multiple ways of course, but none of them are trivial or appetizing to me. Implementing a proper parser is the least appetizing of all. So maybe I'll fix this... maybe not. Adding the language codes to the filename should work.
In the meantime, the new version of sqlite that will allow for somewhat fancier/faster text searches is trickling down the pipeline. It went through two stages and it is now one step away from where I can start fiddling with it. We'll see.