emericg
commented
4 years ago Can't see the beta, maybe it takes a while.
Yes indeed every text and software posted on Google or Apple store is subject to validation, and it can take from a couple of minutes to a couple of days :/
I changed espanol and frisk. Auto means automatic selection, it's pretty standard (haha) in this case, while standard language doesn't mean much.
Some strings can change language automatically while other needs either a reboot the app (so it's really an acceptable trade off) or an action (a sensor refresh will change most text and so update their translations) to act on the language change. This can't be fixed without reworking stuff, and reworking stuff means new bugs, etc...
This version was only supposed to have couples of bugfixes onto the last release done last month, then got new languages, then now has a whole lot of new code, so that's why I really want it out and new code in another release.
I can't thank you enough for your work on the new translations. Doing the translations on a mobile device really tells a lot about your motivation, and I believe we've been doing some real improvements on English too. Doing them manually has proven to be a lot of extra work though, especially simultaneously changing source (English) strings and doing incremental changes on many translations files. Every changes on source strings means updating translations for every languages, with the possibility to swap latest translation with older version of the (more or less) same string, especially when I don't speak the target language. Coupled with the many manual fixes on files, this has become really tricky.
So this release will be published like this, and then take your time while using the application to note where changes should be made. If you want to discuss the source strings and meaning of the different text let's do it separately. It should probably come first. Things like untranslated units (like uS/cm) means adding them to the translated strings list, and so will have repercussions for every translation files. These files also need to be up to date with latest changes to the code or you risk translating already deprecated strings. If you want to improve translations, let's do it all at once. This is probably best done before the next release, to take into account every changes that will be made between now and then. Like before, delete your fork, recreate it with last version of the source code, update every translations and push the changes.
FYr76
Maybe you could do something with the contrast of the text (themes)
Hi there,
Your app is growing more and more and starting to flower. Love it! I'd like to contribute with a Dutch translation. I'm compactly new to contributing on GitHub, so I hope you can help me a bit with the necessary steps.
Kind regards, FYr76