1 Followers
65 Following
24 Posts
@nextcloud Works fine in PC, but fails in Android.
@grote @fdroidorg Thanks, had been looking to find this kind of page. And design is fine - everything does not have to look like a nightclub.
@Tutanota IYPS as one of the apps, where everyone can experiment and check password strength in offline mode. Android version: https://f-droid.org/en/packages/com.iyps/
IYPS | F-Droid - Free and Open Source Android App Repository

Evaluate passwords, predict crack times, and get tips for stronger passwords.

@nixCraft With @matrix one wouldn't have these problems. And you choose client and server of your preference.

@weblate @nijel Other translators probably have different comments on this, but some or all this can be added to the Weblate document you linked to (Educating developers for proper internationalization). Could be helpful.

I'm pretty sure, that devs see a lot of things that translators mess up. It would be very useful to see that list as well.

Thanks for reading this thread.
7/7

@weblate @nijel • forgetting that well-functioning automation is available in Weblate (like automatic source code commits, either time-triggered or by some other metrics); as a translator I would like to see my translations commited to source code in a regular and trackable way (Weblate is able to add translation percentage to commit message and this helps a lot to keep eye on status and other translation systems do not have this feature)
6.5/7
@weblate @nijel • when project is closing down, then from translators point of view the good sequence of events is: close translation → commit latest changes → do last release (if possible) → close down (often it is vice versa)
• if project is in still life phase (not closed, but nothing happens), then translation is kept open without notice of status (I know projects where no commits have happened for 5 years, but translation is still open)
6/7
@weblate @nijel • forgetting that for small languages it is impossible to use schemes that involve many people (translate, review, ...) - there simply are not enough translators and people for this
• assuming that all translators have GitHub account and will report issues there
• not having alternate communication methods (or having one that is not bridged to other systems)
5/7
@weblate @nijel • adding source strings without context, key and location (description and screenshot are rare and those projects that have, are a lot easier to translate; probably that is too much overhead for devs)
• using different source strings for plural (instead of using language-based built-in logic in Weblate); some languages have very complex scenarions of grammatical number
• changing policy and not communicating this to translators
4/7
@weblate @nijel • not adding context to ambiguous source strings (typically you will need to ask "verb or noun" questions)
• forgetting that languages are very different from English (e.g. languages may have different needs for word order and use different language constructs like grammatic cases)
• joining different souce stings in code (does not work for many languages)
• using identical variables in the source string (you can't change word order then)
3/7