Thanks, it works great.
I made a new PR with some updates. No need to merge it now, it can
stay open for a few days. I'll use it to add any fixes that I notice.
Regarding the package description translation workflow - it works, but
it clearly wasn't designed for translation. Here's what a translator
must do before he can translate:
1) click on package
2) click on "View localizations bundled in this package" and copy the
English strings from there (it's slightly easier than copying them
from the previous screen)
3) go back to package description page
4) click on "Edit fallback localizations"
(Slovak now appears in the list, but before I translated the
interface, I had to select it from the drop-down and click add)
5) click on Slovak (I often forget this and edit the empty English
fallback localization)
6) paste the English original
Ideally, these should be reduced to just 2 steps:
1) click on package
2) click on "Edit fallback localizations" (or just "Translate")
Then the localization page would be displayed, with:
* your language pre-selected
* original strings visible on the same page (in English or in a
fallback language according to your preferences)
Regards,
~~helix84
On Wed, Jan 11, 2017 at 11:36 AM, Andrew Lindesay <apl@xxxxxxxxxxxxxx> wrote:
Hello Ivan; I've got that deployed now so you should be able to see that
in production.
Regards;
--
Andrew Lindesay
On Wed, 11 Jan 2017, at 13:29, helix84 wrote:
On Wed, Jan 11, 2017 at 1:16 AM, Andrew Lindesay <apl@xxxxxxxxxxxxxx>
wrote:
Great stuff thanks. I will take a look at the pull-request soon, but in
