![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Hi all,
This is the list of issues I've collected from your feedback. Let me
know if I've missed something, I'll try to ping developers on irc on
Monday (currently it seems everybody is on vacations).
Liste of bugs reported on the lists (I already forwarded the first one
to Dwayne):
- Only external TM suggestions are shown and they are very outdated
(after some checking, I would say they come from the beginning of the
4.x series) - and they can be more misleading than helpful.
- inconsistent output of surrounding strings:
https://translations.documentfoundation.org/id/libo_ui/translate/svx/#filter=incomplete&unit=117710482&offset=0
- inconsistent stats displayed whether you are logged or not
Translation statistics are unreliable. Also, it's not the same numbers
depending on the page you display
For example:
https://translations.documentfoundation.org/projects/libo_online/ shows 760
words incomplete for Slovak, while
https://translations.documentfoundation.org/sk/libo_online/ shows that
Slovak is 100% translated.
- detailed translation statistics are missing (current version only
shows the last 30 days). "The stats also gave us an option to zoom in to
specific translations and check on the quality"
- problems with page scrolling:
" I get so far down the page and then the edit box, rather than being
visible, starts dropping off the bottom of the screen. I scroll down,
commit and boom, it's back down at the bottom off the screen. Very
annoying. The only workaround I've found is to translate till I hit the
bottom of the screen, then reload the page which removes the translated
strings from the UI. "
- login with umlauts get a server error:
"I can't log in with my user name ("Kü"), and always get a server error.
I think it's a problem with german umlauts as I have had another problem
for the last great upgrade of Pootle server with this.
The shown of server error is permanent and could only be solved by
deleting the session cookie."
Cheers
Sophie