Apart from the known slowdowns during this operation, weblate doesn't
run on the final hardware yet, we'll have a dedicated machine to run
the translation services on, so performance overall should be a bit
better - but if you experience overall slowdown, please let us know
for what operations exactly.
- translation memory and terminology are not included (should we add
No, don't add it yourself, I added translation memory from pootle, but
he way weblate makes use of it doesn't scale for large projects like
It is again more suited for many little projects. In other words:
Translation memory view is slow and also matches way too loosely to be
Translation memory will be handled by a separate translation memory
server that we'll hook up to weblate.
What is in weblate is the translation history/cross-referencing of
other same/very similar translated strings.
- instructions for translating refer to old Pootle, e.g. .
Is addressing of these issues planned? In other words, is it worth to
wait with translation, or should we live with what we have now?
No, don't wait with translation - 6.4 translation is already in
weblate, there won't be another way to translate for 6.4.
6.3 translations are so far still on pootle, but will eventually also
copied over to weblate instance.