Daniel Weck

@naglis @ThanatosDi you are now team "translators" :) Welcome and thank you

@nvdaes @izorba @jonaslil you are now team "translators" :) Welcome and thank you @milliet first you need to log into GitLocalize :)

interesting ... there are new commits in the develop branch, and GitLocalize synchronizes its state with GitHub so maybe that's the cause of the refresh. I'll see if anything was...

To those of you who submitted your translation as "Review Request", I am horrified and mortified to discover that your work seems to have vanished from GitLocalize!! I am posting...

> Even with frequent updates to your project, GitLocalize keeps localization stress-free. https://docs.gitlocalize.com/about.html

@nvdaes your Spanish data was still in GitLocalize as a pending / open Review Request, so I quickly created a Pull Request here in GitHub https://github.com/edrlab/thorium-reader/pull/2231

@nvdaes your Spanish translation is indeed at 78%, in fact I see empty strings in the GitLocalize user interface. I hope this is not too hard with your screen reader:...

So, I went back to all the notification emails I received from GitLocalize (because their website admin panel doesn't show this) and I found the following: * @ThanatosDi I am...

I posted my feedback in the GitLocalize GitHub issue tracker: https://github.com/gitlocalize/feedback/issues/138

Looking at Thorium's JSON locales changelog timeline (timestamps), I am now fairly certain that the reason why @nvdaes Spanish data survived is because she posted her work after we pushed...