-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tue, Jan 21, 2020 at 08:45:19PM +0100, Tobias Killer wrote:
> Hi,
>
> Am 21.01.20 um 06:02 schrieb Marek Marczykowski:
> > Hi,
> >
> > On Sat, Dec 28, 2019 at 10:29:12AM +0100, Maya wrote:
> >> good morning ...! :)
> >
> >> name of test branch is translation-wf-test
> >
> > After embarrassingly long delay, I've finally finished review of this
> > and made some modifications. The most important is adding
> > qubes-translated as a collection to _config.yml, which allowed to get
> > rid of all the symlinks!
>
> Nice!
>
> > Also, I've squashed the whole history of that branch to just few
> > commits. BTW, Maya, please tell me what author (name + email) should I set
> > there, you seems to use different ones for different commits.
> >
> > I've pushed the result here:
> >
https://github.com/marmarek/qubesos.github.io/tree/translation
>
> Some translation-related files seem to be in `_util/` but not in
> `_util/_translation_utils/`. These files should be moved.
I've done that on purpose, with intention of removing _translation_utils
subdir completely (currently only some test scripts remains there).
There aren't that much scripts there (3) to create overly long path for
them.
> >
> > Then I've executed all the translation steps from the README (including
> > push + pull to transifex), built the site and uploaded it here:
> >
> >
https://wwwtest.qubes-os.org/
>
> Great for testing, thank you!
>
> >
> > Generated changes in sources pushed to the translation-output branch in
> >
qubesos.github.io, qubes-doc, qubes-translated.
> >
> > I've downloaded only some languages (de, fr, es), we have way more
> > of them enabled (most with minimal or no translations). Bulgarian is not
> > one of them...
> > Also, while downloading from Transifex, I've used --minimum-perc=5 option, but
> > I don't think it really worked. I was expecting to download only files
> > with at least 5% content translated.
>
> Maybe we shouldn't take care of the fraction of translation? IMHO it
> could be easier to provide always *all* links to *all* supported
> languages for *every* page. A button "Translate this page" could be
> added to the sidebar, for example.
Yes, such button is a good idea. And even for fully translated pages it
makes sense, for improving/updating the translation.
> > Menu and other main website parts are setup only for English
> > (obviously), German, and Bulgarian, so on other languages things are
> > missing.
> >
> > I've tried to run html-proofer locally, but ran out of memory :/
> > Will get travis into shape for that (now it is confused with different
> > branches).
> >
> > There are various issues to be solved:
> > - sometimes 'layout' in frontmatter gets translated, breaking
> > pages (example:
https://wwwtest.qubes-os.org/de/donate/)
>
> That's one reason why IMHO the frontmatter should be stripped off before
> uploading to Transifex. It's just too critical.
On the other hand, some attributes should be translated - for example
title.
I think the post-processing script can easily access both source and
translated frontmatter and combine the final one from them (for example
take title from translated and the rest from source).
> > - on some (most?) pages, translation disclaimer is included twice
>
> Not critical but should be avoided.
>
> > - some not translated pages (those where transifex didn't returned
> > anything, maybe because of --minimum-perc=5) are returning 404
> > - I think in such cases there should be a different disclaimer for not
> > translated page (maybe inviting to help with translation?) and the
> > original page should be included (or redirected to?)
>
> Untranslated parts should always be visible since those could make the
> difference. Maybe, we could highlight those parts in screaming red and
> add a disclaimer saying that red means untranslated or not up-to-date?
I have no idea how to do that.
I was rather expecting that the whole file would be skipped if it isn't
translated in at least X percents. The we could fill such missing files
with some placeholders or such.
But apparently it isn't how it works.
> > - documentation index will fairly easy get out of sync - generated
> > one that Andrew done for version-specific documentation would be very
> > useful here
>
> Yes, indeed!
>
> > - translation of base site elements (top menu, footer menu etc) isn't
> > integrated with transifex - it's about files in _data/
>
> No spontaneous idea, sorry. :(
>
> > - language selection IMO should be a drop-down instead of a flat list
> > (especially when it'll get longer) - does anybody know how to do
> > that?
>
> Do you mean something like this?:
>
https://www.w3schools.com/Css/css_dropdowns.asp
Yes!
> > Next steps:
> > - solve critical issues (first: define which are critical)
> > - remove all resources from transifex
> > - decide what languages should we enable and generally cleanup
> > transifex
> > - upload fresh content (I believe "translation memory" will remain
> > there, so some content will automatically get translated)
>
> Yes, I guess, too. Otherwise, maybe the translations will just be
> proposed and the top proposal can be pulled in via a keyboard shortcut.
>
> > - enable automated translation in transifex for initial draft (google
> > translate)
>
> Could help but also make things more difficult. Let's try and see what
> happens!
>
> > - enable calling "the script" (I give up waiting for having proper "github
> > integration" enabled) - this can be done by the same script downloads
> > other submodules
>
> What do you mean? I don't understand.
The steps mentioned in README. I've executed them manually by copy&paste
into terminal. This needs to be called automatically on some schedule
(or detected change).
> > - open transifex for translators
> >
> > Anything missing?
> >
> >
>
> What about fragments in URLs (the part beyond `#`)? They are used to
> link to the sections of a page.
That's a good point. When section title gets translated, such URL
fragments will change too. Do we have any plan what to do about that?
> Thank you for your work!
>
> Cheers,
> Tobias
>
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl4nYegACgkQ24/THMrX
1yzuswf/esfWnIDiexhSCVWt4uo5VDJRWDCx5KLOOhb0GdRv4dSZavfS2FxhAO5U
4+vKf/MC7xPLJMupoNCzuKsirr0ErdtFjJydKS2aJrMFgjOgjG0xTikeIeYeVoPH
e2ZqLJ/PIrv0RdLSJzCxa/qiRdGvh9fPRTF/SVDsbRYSjm1qGuhX8E9Yl5+D4J7+
KwvE7g4rmDa0VzHfh+I7PBb0AxoEHN46f3hTWLvcUszgwPJCD8mEFTBiTTptasYa
iwEIBdGEpfoHgixaXCQRD4eT/9zbCMvV5pENBaGHh3QOfcZ8Tw4/OX2xezxPw2xY
X75wtU/YXS9UZqeqA9+0Ub0ZR/OSaA==
=VplX
-----END PGP SIGNATURE-----