pushing translated guides to docs.fedoraproject.org

[Pete Travis]

On Jan 8, 2014 11:25 AM, "Christopher Antila" <crantila at fedoraproject.org>
wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 8 January 2014 09:22:14 Gianluca Sforna wrote:
> > It seems I wrongly assumed completed translations would be pushed
> > automatically from transifex to the docs site. In particular, I was
> > looking for the burning ISO guide which I recently brought to 100%
> >
> > Maybe the IT team could help with the process by pushing ours once
> > completed?
>
> Gianluca:
>
> As far as I know, the Docs Project only publishes documentation in the
source
> language, unless a localization team specifically requests our assistance.
>
> By leaving publication to localization teams, we allow translators to
decide
> when to publish (40% may be sufficient in some cases). Furthermore, we
avoid
> accidentally publishing content that was planned for revision (when 100%
of
> strings are translated, but with minimal confidence).
>
> So please feel free to publish your team's translations as you wish. We
would,
> however, be happy to help!
>
>
> Christopher
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBCgAGBQJSzZgZAAoJEAWCcTQ3FNFM7AYP/REfb6QgTV+9U3ipnpAsxNcA
> MTAyoX/iXQCHbhlrnYQr9LpJgA30nRV5MlC0pRYh8WdWlpNCwi1eAWsnUCHRAMmZ
> 19xuTBNMRIclr7GJTfjxCJEjZ89mx8gOcySVFhTyHMwQzENRQifFT+YkLTBEgG5k
> /0dAj3852LAWVJg83eAv62Q0C6n0lZpr04ny4ywA7NllFpZfvo+1RcgMrjyom3F1
> RJHcAGlR+87f8fV52sCtZLqtg7gDDuC7mPkVhfx39k2SLer0SGTAF5SJvDdR/aA8
> ouSUsigYrjJExLFwbiaZvsxi0ik4jR5K5EjEKz64sCCcD+4ERvhlZCjNUaIkuYaz
> VBVokDsrO+ze8NepPPGBvpSq0rYgIuYTGkAN3RNBMY7H1DF3XqHSVPewF2Sw3qcb
> 04QJxbNW7sJnTUShLwyiP6vnbjrmbEAFwi8rPS3bx4/KFxiV8LJb/oZfCqEbVgNT
> kFtrKqO+G/c0cd/SFnraC71bSz+AZFXUuyDeZp3ppzifDi69zLKIDFmZbnrXS7FT
> V52mHlQuIUlkVFN7tVNFY/+MIs/LT19RD+QZzv8PJ4bXClOHatA7L/dkPfYo4eC/
> rHTPBVl7QXT7IMcjM1QR5G+l7pUj3YGpPtYkQos5yKTYIrjwSYyhzFLwXrzwEsf2
> a81+xnLMsNuDBOuyG/lZ
> =w7RR
> -----END PGP SIGNATURE-----
>
> --
>

There are publishing instructions in the Documentation Guide, but it occurs
to me now that a few bits of the SOP that are missing :

- publishing needs membership in the docs-writers and docs-publishers
groups. Many translation team leads have been sponsored into these groups
to allow publishing, and we are happy to sponsor more.

- publish from the release branch, ie f20, not master. Commit your POs to
make life easy if we need to republish.

- after publishing, open your local copy of web.git and look it over before
committing to that repo. In particular, check the menu structure. Strange
things can happen.

- As Chris said, there is currently no notification for when translations
reach 100%, and you might want to publish sooner. It isn't uncommon to see
code snippets or command output as untranslated strings, for example, since
there's little reason to translate those.  I might be able to get such
notifications going, but it would require some consensus among the l10n
group on what is considered "ready for publishing".

Also, I like having translation team leads do the publishing because it
gives them the opportunity to do a final review and build test.  I can and
do correct obvious markup issues, but I can only push changed strings back
to projects I manage. I can't assess the language I'm correcting, just the
markup structure.

--Pete
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/docs/attachments/20140108/ed7d2fdc/attachment.html>