Have found multiple untranslated strings in Zebra.
The strings for repo import and drop tables are not localized.
Screenshots:
iPhone 11 Pro
Zebra 1.0 (Sandboxed)
iOS 13.1.1
worldlydev
All 12 comments
How about “Installing Zebra” !!
eve0415
on 2 Jan 2020
Hmm, "Downloading" and "Done" are properly localized, I'm not sure why they're not showing up.
wstyres
on 2 Jan 2020
I added the missing strings in e7ec4de7f5b5b31bafa233635810f10c00c78ecd they should be on CrowdIn shortly and will be included in 1.0.1.
wstyres
on 2 Jan 2020
I added the missing strings in e7ec4de they should be on CrowdIn shortly and will be included in 1.0.1.
What about "Release files need to be updated" and "Package files need to be updated"?
worldlydev
on 2 Jan 2020
I went ahead and removed those strings, they were going to be removed later on anyway so I just went ahead and removed them now while I was there.
wstyres
on 2 Jan 2020
They should all be there, check to make sure that I didn't miss any before the issue is closed.
wstyres
on 2 Jan 2020
Somewhat fixed on 1.0.1
Drop Tables
"Downloading", "Done", and "Parsing" are not localized. "Done" at the end is localized.
Repo import screen
"Yes" is not localized. Also, would it be possible to rearrange or add some spacing up top (highlighted in green)?
Repo import console
"Downloading", "Done", and "Parsing" are not localized. "Done" at the end is localized.
worldlydev
on 2 Jan 2020
Removing Zebra is not localized still
eve0415
on 4 Jan 2020
So there was an issue when I added the new strings when I used a # to mark the comment instead of // so CrowdIn didn't like that very much. I've updated the strings as of 3a0d73a15198ff8912df2f6b8fc4e58e49ab94d0 and removed the problem causing comment markers. Hopefully that fixes all of the problems (but you might have to retranslate the strings... :/)
wstyres
on 5 Jan 2020
Tested on 1.0.3 non-jailbroken.
"Downloading", "Done", and "Parsing" are localized for both repo importing and drop tables.
"Yes" is still not localized on the repo import screen.
worldlydev
on 6 Jan 2020
Turns out "Yes" does not actually exist in Localizable.strings so that would explain why it is not translated.
wstyres
on 6 Jan 2020
Can confirm that all the strings are now localized as of 1.0.5.
worldlydev
on 10 Jan 2020
Related issues
unclehumble
·
4Comments
worldlydev
·
7Comments
eve0415
·
3Comments
Jailbreaker92
·
5Comments
aRvedk
·
5Comments
Most helpful comment
I added the missing strings in e7ec4de7f5b5b31bafa233635810f10c00c78ecd they should be on CrowdIn shortly and will be included in 1.0.1.