garfieldius
Issues with opening and import of xlf files
Hi
thanks for this tool!
Currently I have some troubles to use it under Ubuntu 23.04.
The tool shuts down immediately, leaving the google chrome window open, without any language files loaded. In rare cases the xlf files are loading and I can edit and save them. I did not figure out, when it works or when it fails. There is also no exception message or anything else in the logs.
What can I do to get an exception message to find the cause?
TIA
Tested versions 0.6.6 and 0.6.5 ... The files load and can be edited.
Both variants of the import fail here also. Checked it with a minimal fresh exported file with minor changes.
I asked a colleague using the current MacOS 13.4.1c to test it. The xlf files open as expected. The import of an csv results also in closing the app without any comment or exception.
Hint:
If you are in the same situation like me: There is a TYPO3 extension undefined/translate-locallang, that does exactly the same thing in the TYPO3 backend. It is compatible up to TYPO3 V11.
composer req --dev undefined/translate-locallang
@garfieldius : No pun indented with this comment ... It should be just a hint, if somebody has the same issue and needs to edit / import many labels.
Big advantage of your solution is, that no fully installed TYPO3 is necessary. :-)
I'll test on Fedora 38 with chromium tomorrow again. But last time it worked flawlessly.
Not sure if this could be remotely related, but maybe it helps to cleanup some caches of *chrome. ~/.config/chromium/Default/*Cache/*
@mschwemer I found some issues with the CSV handling. The browser navigates away, which causes the server to "loose contact" and closes. Will look into that. However, this is only during exporting or importing CSV files. During "standard" operations I cannot reproduce this. Calling t3ll locllang.xlf loads the file and editing and saving it works on several systems. Including Ubuntu jammy.
@mschwemer There were several issues with the sent HTTP headers and internal state handling. Please upgrade to 0.7.2 and check if it works now.
@garfieldius I have the same problem on Windows 11, if I try to open locallang files via WSL2 - the command executes but no Chrome window appears (problem even with the new 0.7.2 release). Is it possible to start the program with debugging output to check where it hangs?
Hi, unfortunately I cannot reproduce this on Fedora or Windows 11.
In Version 0.7.4 there is now a debug flag. Please try this version like this: t3ll -d path/to/locallang.xlf and check if it says something about a chrome error.