I haven't noticed much projects migrating from Pootle at Weblate, most of projects which come to Weblate didn't use anything before.
hi, just furthering what @unho said above - i have also moved on to other things. I tried for a while to figure out a model to support pootle development etc, but it wasnt working out. If anyone wants to take the baton and continue with dev - i will happily facilitate any required access
Hi! at https://bugs.debian.org/916745 / translate/translate#3254 , encoding problems with Python 3 and web2py are discussed. I'm a bit nervous that the patches change the bytes/unicode handling and that there might be further problems that this creates. I'd love some review before applying these patches to the Debian packages.
Any thoughts on https://bugs.debian.org/916745 / translate/translate#3838 ? I really don't want to diverge in Debian without this being reviewed and preferably merged.
@nijel (simply because you seem most active at the moment....) any thoughts on the above?
Got to a point when I can read a file and send it to Google Cloud to have translated with a specific custom-trained model and output into a separate file
but the file is plain text file and I need to do a bunch of custom model testing by getting XLIFFs translated with it retaining the format
found this guy's repo https://github.com/translate/pyliff
anyone knows if a similar solution exists?
It might already work now, but I'm still busy, so expect it go up and down for a little while longer.
(translate/virtaal@77c43a9 on its own cannot be cherry-picked; it needs some of the preceding patches too, which makes me nervous)
Virtaal isn't packaged for some distros anymore (just recently saw it is not on fedora, for example)
I guess a flatpak would solve parts of the distribution problem
there are already several nice improvements in git since the last release
It is unfortunate that backwards compatibility was not important enough for the toolkit
However, Python 2 and gtk2 will both be going away in Debian and Ubuntu reasonably soon, I think, and that will force other action.
we struggle with providing long-term platforms in our world, it seems.
(And it's better than Qt, which seems determined to kill off all Qt-using software with incompatible upgrades)
Mixing these 3 big transitions up is certainly a nasty challenge though. I've never done any gtk programming at all to know how difficult that might be. ttkit and friends are probably amongst the hardest things to do the py2→3 transition too :(
but it requires time
@friedelwolff Regarding backwards compatibility there is a point when we should stop supporting everything. I sincerely hope this is another kick to get another Virtaal release out, this time including fixed requirements to avoid new TTK releases breaking compatibility for already rolled out Virtaal installs.
BTW, I have plans for removing support for Python 2 in any TTK release after Python 2.7 support goes away, which basically is 1st January 2020, which is in less than 6 months from now: https://pythonclock.org/
fixed requirements won't help in the case of distros that want to upgrade the toolkit
I'd like to do a million things on virtaal, but my life went through multiple very disruptive changes in the last few years
Let's hope I can look into it more
Hi,
I have huge text files - raw text. I want to convert them to a different language. Google/Microsoft/Yandex is best for online conversions. However we need to copy and paste and moreover it has size limitation as well.
Is there is any tool which i can use for bulk conversion at one shot which can give the output in multiple files.
Thanks in advance.
