Migrating Docs to new Transifex server

[Dimitris Glezos]

Hey all.

As many of you already heard, we are migrating our Transifex server to
fedora.transifex.net. For more info, please refer to the logistics and
translation lists.

We have already manually migrated the core Fedora apps (ones we are
upstream and are affected by the string freeze). The Docs projects
will need to migrate its projects as well.

Compared to our old setup, we have changed the way project maintainers
interact with Transifex. We now have a command-line client to push
source files (POT) & pull translations (PO). Here are the instructions
on how to manage your docs project.

Create your project
===================

As an example, I already migrated the release notes:

http://www.transifex.net/projects/p/fedora-release-notes/

To create your project and setup your client, run the following. This
only needs to be run once:

- Login or Create account on Transifex.net
- Create project:
  Transifex → Projects → Create → MyProjectName
- Share teams with Fedora Project:
  Transifex → MyProjectName → Access Control → Outsource → "Fedora Project"
- Push existing translations to the server:

$ git clone http://git.fedorahosted.org/git/anaconda.git
    $ cd anaconda
    $ tx init
    $ tx set --auto-local -r anaconda.master 'po/<lang>.po' \
      --source-lang en --source-file po/anaconda.pot

Especially for docs, which have a bunch of POT files, we'll need
multiple "tx set" commands like this, which we get by running the
following:

for POTFILE in `ls pot`; do
    FILE=$(basename "$POTFILE" .pot)
    tx set --auto-local -r fedora-docs-relnotes.$FILE --source-language=en \
    --source-file pot/$FILE.pot "<lang>/$FILE.po" --execute
  done

These commands will create a file called '.tx/config', which tells the
client what translations to pull from the server and in which local
files to put them. This will be needed by other Docs people to test,
so you should commit this file in your repo. Feel free to open it,
modify and check whether things look correct.

Pushing source languages & pulling translations
===============================================

Now we can simply push our source files to the server:

$ tx push --source
  Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
  Pushing source file (pot/Amateur_Radio.pot)
  ...

Since we want to pre-populate our translations too from our existing
ones, we do this.

$ tx push --translations
  Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
  Pushing 'da-DK' translations (file: da-DK/Amateur_Radio.po)
  ...

Because Publican generates a bunch of unneeded (mostly empty) translation
files, your push will take a million years and make our server hate you
forever.

When you are ready to publish a document, you'll need to pull fresh
translations. To do this, simply run 'tx pull'.

More info:
http://help.transifex.net/user-guide/client/client-0.4.html#for-developers

Your project in the Fedora 15 release
=====================================

We track the Fedora 15 release here:

http://www.transifex.net/projects/p/fedora/r/fedora-15/

To include your project in the Fedora 15 release (or a separate Fedora Docs),
a Fedora L10n admin needs to do the following. If you're not a member of the
Fedora L10n Admin team, just ping us and we'll include your project in the
release.

Transifex → Fedora Project → Release 15 → Edit → Resources → MyProject

Downloading translations of a whole release
===========================================

We encourage translators to translate using the online editor, since
it offers many additional features than the offline one. However, we
sometimes prefer to download translation files, either for offline
translation or for backup. Translators can pull only the translation
files they want for a whole release, without worrying about source
code or other languages (including English). Here's how:

$ cd my-translations
  $ tx set --auto-remote http://www.transifex.net/projects/p/fedora/r/fedora-15/
  $ tx pull --language el
  $ ll translations/*/el.po
  translations/anaconda.master/el.po
  translations/usermode.master/el.po

More info:
http://help.transifex.net/user-guide/client/client-0.4.html#auto-remote
http://help.transifex.net/user-guide/client/client-0.4.html#for-translators

Hope this helps!

-d

[Nick Bebout]

I'm working on adding our docs to transifex.net which will also involve
branching them for f15.  If for some reason you don't want me to branch
your guide, let me know.  Also, if you have a transifex.net account, let
me know and I'll make you a maintainer so you can push updates to your
pot's to transifex.net

Nick
> Hey all.
>
> As many of you already heard, we are migrating our Transifex server to
> fedora.transifex.net. For more info, please refer to the logistics and
> translation lists.
>
> We have already manually migrated the core Fedora apps (ones we are
> upstream and are affected by the string freeze). The Docs projects
> will need to migrate its projects as well.
>
> Compared to our old setup, we have changed the way project maintainers
> interact with Transifex. We now have a command-line client to push
> source files (POT) & pull translations (PO). Here are the instructions
> on how to manage your docs project.
> Create your project
>
> As an example, I already migrated the release notes:
>
> http://www.transifex.net/projects/p/fedora-release-notes/
>
> To create your project and setup your client, run the following. This
> only needs to be run once:
> Login or Create account on Transifex.net
> Create project:
> Transifex → Projects → Create → MyProjectName
> Share teams with Fedora Project:
> Transifex → MyProjectName → Access Control → Outsource → "Fedora
>
> Project"
>
> Push existing translations to the server:
>
> $ git clone http://git.fedorahosted.org/git/anaconda.git
>   $ cd anaconda
>   $ tx init
>   $ tx set --auto-local -r anaconda.master 'po/<lang>.po' \
>     --source-lang en --source-file po/anaconda.pot
>
> Especially for docs, which have a bunch of POT files, we'll need
> multiple "tx set" commands like this, which we get by running the
> following:
>
> for POTFILE in `ls pot`; do
>     FILE=$(basename "$POTFILE" .pot)
>     tx set --auto-local -r fedora-docs-relnotes.$FILE --source-language=en
> \
>     --source-file pot/$FILE.pot "<lang>/$FILE.po" --execute
>   done
>
> These commands will create a file called '.tx/config', which tells the
> client what translations to pull from the server and in which local
> files to put them. This will be needed by other Docs people to test,
> so you should commit this file in your repo. Feel free to open it,
> modify and check whether things look correct.
> Pushing source languages & pulling translations
>
> Now we can simply push our source files to the server:
>
> $ tx push --source
>   Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
>   Pushing source file (pot/Amateur_Radio.pot)
>   ...
>
> Since we want to pre-populate our translations too from our existing
> ones, we do this.
>
> $ tx push --translations
>   Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
>   Pushing 'da-DK' translations (file: da-DK/Amateur_Radio.po)
>   ...
>
> Because Publican generates a bunch of unneeded (mostly empty) translation
> files, your push will take a million years and make our server hate you
> forever.
>
> When you are ready to publish a document, you'll need to pull fresh
> translations. To do this, simply run 'tx pull'.
>
> More info:
> http://help.transifex.net/user-guide/client/client-0.4.html#for-developers
> Your project in the Fedora 15 release
>
> We track the Fedora 15 release here:
>
> http://www.transifex.net/projects/p/fedora/r/fedora-15/
>
> To include your project in the Fedora 15 release (or a separate Fedora
> Docs),
> a Fedora L10n admin needs to do the following. If you're not a member of
> the
> Fedora L10n Admin team, just ping us and we'll include your project in the
> release.
>
> Transifex → Fedora Project → Release 15 → Edit → Resources →
> MyProject
> Downloading translations of a whole release
>
> We encourage translators to translate using the online editor, since
> it offers many additional features than the offline one. However, we
> sometimes prefer to download translation files, either for offline
> translation or for backup. Translators can pull only the translation
> files they want for a whole release, without worrying about source
> code or other languages (including English). Here's how:
>
> $ cd my-translations
>   $ tx set --auto-remote
> http://www.transifex.net/projects/p/fedora/r/fedora-15/
>   $ tx pull --language el
>   $ ll translations/*/el.po
>   translations/anaconda.master/el.po
>   translations/usermode.master/el.po
>
> More info:
> http://help.transifex.net/user-guide/client/client-0.4.html#auto-remote
> http://help.transifex.net/user-guide/client/client-0.4.html#for-translators
>
> Hope this helps!
>
> -d
>
> --
> Dimitris Glezos
>
> Transifex: The Multilingual Publishing Revolution
> http://www.transifex.net/ -- http://www.indifex.com/
> --
> docs mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs

[Nick Bebout]

The following link will show you the status of moving docs translations to
transifex.net

If you'd like maintainer access to any of them on transifex.net, let me
know.  maintainer access is necessary for you to be able to push new pot's
to the server.  Translator access is managed through the "fedora" project,
not through each's doc's teams.

https://spreadsheets.google.com/a/bebout.net/pub?hl=en&hl=en&key=0Au...
> I'm working on adding our docs to transifex.net which will also involve
> branching them for f15.  If for some reason you don't want me to branch
> your guide, let me know.  Also, if you have a transifex.net account, let
> me know and I'll make you a maintainer so you can push updates to your
> pot's to transifex.net
>
> Nick
> > Hey all.
> >
> > As many of you already heard, we are migrating our Transifex server to
> > fedora.transifex.net. For more info, please refer to the logistics and
> > translation lists.
> >
> > We have already manually migrated the core Fedora apps (ones we are
> > upstream and are affected by the string freeze). The Docs projects
> > will need to migrate its projects as well.
> >
> > Compared to our old setup, we have changed the way project maintainers
> > interact with Transifex. We now have a command-line client to push
> > source files (POT) & pull translations (PO). Here are the instructions
> > on how to manage your docs project.
> > Create your project
> >
> > As an example, I already migrated the release notes:
> >
> > http://www.transifex.net/projects/p/fedora-release-notes/
> >
> > To create your project and setup your client, run the following. This
> > only needs to be run once:
> > Login or Create account on Transifex.net
> > Create project:
> > Transifex → Projects → Create → MyProjectName
> > Share teams with Fedora Project:
> > Transifex → MyProjectName → Access Control → Outsource →
> >
> > "Fedora
> > Project"
> >
> > Push existing translations to the server:
> >
> > $ git clone http://git.fedorahosted.org/git/anaconda.git
> >   $ cd anaconda
> >   $ tx init
> >   $ tx set --auto-local -r anaconda.master 'po/<lang>.po' \
> >     --source-lang en --source-file po/anaconda.pot
> >
> > Especially for docs, which have a bunch of POT files, we'll need
> > multiple "tx set" commands like this, which we get by running the
> > following:
> >
> > for POTFILE in `ls pot`; do
> >     FILE=$(basename "$POTFILE" .pot)
> >     tx set --auto-local -r fedora-docs-relnotes.$FILE
> > --source-language=en
> > \
> >     --source-file pot/$FILE.pot "<lang>/$FILE.po" --execute
> >   done
> >
> > These commands will create a file called '.tx/config', which tells the
> > client what translations to pull from the server and in which local
> > files to put them. This will be needed by other Docs people to test,
> > so you should commit this file in your repo. Feel free to open it,
> > modify and check whether things look correct.
> > Pushing source languages & pulling translations
> >
> > Now we can simply push our source files to the server:
> >
> > $ tx push --source
> >   Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
> >   Pushing source file (pot/Amateur_Radio.pot)
> >   ...
> >
> > Since we want to pre-populate our translations too from our existing
> > ones, we do this.
> >
> > $ tx push --translations
> >   Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
> >   Pushing 'da-DK' translations (file: da-DK/Amateur_Radio.po)
> >   ...
> >
> > Because Publican generates a bunch of unneeded (mostly empty)
> > translation
> > files, your push will take a million years and make our server hate you
> > forever.
> >
> > When you are ready to publish a document, you'll need to pull fresh
> > translations. To do this, simply run 'tx pull'.
> >
> > More info:
> > http://help.transifex.net/user-guide/client/client-0.4.html#for-developers
> > Your project in the Fedora 15 release
> >
> > We track the Fedora 15 release here:
> >
> > http://www.transifex.net/projects/p/fedora/r/fedora-15/
> >
> > To include your project in the Fedora 15 release (or a separate Fedora
> > Docs),
> > a Fedora L10n admin needs to do the following. If you're not a member of
> > the
> > Fedora L10n Admin team, just ping us and we'll include your project in
> > the
> > release.
> >
> > Transifex → Fedora Project → Release 15 → Edit → Resources →
> > MyProject
> > Downloading translations of a whole release
> >
> > We encourage translators to translate using the online editor, since
> > it offers many additional features than the offline one. However, we
> > sometimes prefer to download translation files, either for offline
> > translation or for backup. Translators can pull only the translation
> > files they want for a whole release, without worrying about source
> > code or other languages (including English). Here's how:
> >
> > $ cd my-translations
> >   $ tx set --auto-remote
> > http://www.transifex.net/projects/p/fedora/r/fedora-15/
> >   $ tx pull --language el
> >   $ ll translations/*/el.po
> >   translations/anaconda.master/el.po
> >   translations/usermode.master/el.po
> >
> > More info:
> > http://help.transifex.net/user-guide/client/client-0.4.html#auto-remote
> > http://help.transifex.net/user-guide/client/client-0.4.html#for-translators
> >
> > Hope this helps!
> >
> > -d
> >
> > --
> > Dimitris Glezos
> >
> > Transifex: The Multilingual Publishing Revolution
> > http://www.transifex.net/ -- http://www.indifex.com/
> > --
> > docs mailing list
> > [e-mail]
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/docs
>
> --
> docs mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs

[Nick Bebout]

Apparently that link won't work.

You can use http://nb.fedorapeople.org/docs.html  although it will not be
totally up to date, I'll try to update it frequently.

Nick
> The following link will show you the status of moving docs translations to
> transifex.net
>
> If you'd like maintainer access to any of them on transifex.net, let me
> know.  maintainer access is necessary for you to be able to push new pot's
> to the server.  Translator access is managed through the "fedora" project,
> not through each's doc's teams.
>
> https://spreadsheets.google.com/a/bebout.net/pub?hl=en&hl=en&key=0Au...
> > I'm working on adding our docs to transifex.net which will also involve
> > branching them for f15.  If for some reason you don't want me to branch
> > your guide, let me know.  Also, if you have a transifex.net account, let
> > me know and I'll make you a maintainer so you can push updates to your
> > pot's to transifex.net
> >
> > Nick
> > > Hey all.
> > >
> > > As many of you already heard, we are migrating our Transifex server to
> > > fedora.transifex.net. For more info, please refer to the logistics and
> > > translation lists.
> > >
> > > We have already manually migrated the core Fedora apps (ones we are
> > > upstream and are affected by the string freeze). The Docs projects
> > > will need to migrate its projects as well.
> > >
> > > Compared to our old setup, we have changed the way project maintainers
> > > interact with Transifex. We now have a command-line client to push
> > > source files (POT) & pull translations (PO). Here are the instructions
> > > on how to manage your docs project.
> > > Create your project
> > >
> > > As an example, I already migrated the release notes:
> > >
> > > http://www.transifex.net/projects/p/fedora-release-notes/
> > >
> > > To create your project and setup your client, run the following. This
> > > only needs to be run once:
> > > Login or Create account on Transifex.net
> > > Create project:
> > > Transifex → Projects → Create → MyProjectName
> > > Share teams with Fedora Project:
> > > Transifex → MyProjectName → Access Control → Outsource →
> > >
> > > "Fedora
> > > Project"
> > >
> > > Push existing translations to the server:
> > >
> > > $ git clone http://git.fedorahosted.org/git/anaconda.git
> > >   $ cd anaconda
> > >   $ tx init
> > >   $ tx set --auto-local -r anaconda.master 'po/<lang>.po' \
> > >     --source-lang en --source-file po/anaconda.pot
> > >
> > > Especially for docs, which have a bunch of POT files, we'll need
> > > multiple "tx set" commands like this, which we get by running the
> > > following:
> > >
> > > for POTFILE in `ls pot`; do
> > >     FILE=$(basename "$POTFILE" .pot)
> > >     tx set --auto-local -r fedora-docs-relnotes.$FILE
> > > --source-language=en
> > > \
> > >     --source-file pot/$FILE.pot "<lang>/$FILE.po" --execute
> > >   done
> > >
> > > These commands will create a file called '.tx/config', which tells the
> > > client what translations to pull from the server and in which local
> > > files to put them. This will be needed by other Docs people to test,
> > > so you should commit this file in your repo. Feel free to open it,
> > > modify and check whether things look correct.
> > > Pushing source languages & pulling translations
> > >
> > > Now we can simply push our source files to the server:
> > >
> > > $ tx push --source
> > >   Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
> > >   Pushing source file (pot/Amateur_Radio.pot)
> > >   ...
> > >
> > > Since we want to pre-populate our translations too from our existing
> > > ones, we do this.
> > >
> > > $ tx push --translations
> > >   Pushing translations for resource fedora-docs-relnotes.Amateur_Radio:
> > >   Pushing 'da-DK' translations (file: da-DK/Amateur_Radio.po)
> > >   ...
> > >
> > > Because Publican generates a bunch of unneeded (mostly empty)
> > > translation
> > > files, your push will take a million years and make our server hate you
> > > forever.
> > >
> > > When you are ready to publish a document, you'll need to pull fresh
> > > translations. To do this, simply run 'tx pull'.
> > >
> > > More info:
> > > http://help.transifex.net/user-guide/client/client-0.4.html#for-developers
> > > Your project in the Fedora 15 release
> > >
> > > We track the Fedora 15 release here:
> > >
> > > http://www.transifex.net/projects/p/fedora/r/fedora-15/
> > >
> > > To include your project in the Fedora 15 release (or a separate Fedora
> > > Docs),
> > > a Fedora L10n admin needs to do the following. If you're not a member
> > > of
> > > the
> > > Fedora L10n Admin team, just ping us and we'll include your project in
> > > the
> > > release.
> > >
> > > Transifex → Fedora Project → Release 15 → Edit → Resources
> > > →
> > > MyProject
> > > Downloading translations of a whole release
> > >
> > > We encourage translators to translate using the online editor, since
> > > it offers many additional features than the offline one. However, we
> > > sometimes prefer to download translation files, either for offline
> > > translation or for backup. Translators can pull only the translation
> > > files they want for a whole release, without worrying about source
> > > code or other languages (including English). Here's how:
> > >
> > > $ cd my-translations
> > >   $ tx set --auto-remote
> > > http://www.transifex.net/projects/p/fedora/r/fedora-15/
> > >   $ tx pull --language el
> > >   $ ll translations/*/el.po
> > >   translations/anaconda.master/el.po
> > >   translations/usermode.master/el.po
> > >
> > > More info:
> > > http://help.transifex.net/user-guide/client/client-0.4.html#auto-remote
> > > http://help.transifex.net/user-guide/client/client-0.4.html#for-translators
> > >
> > > Hope this helps!
> > >
> > > -d
> > >
> > > --
> > > Dimitris Glezos
> > >
> > > Transifex: The Multilingual Publishing Revolution
> > > http://www.transifex.net/ -- http://www.indifex.com/
> > > --
> > > docs mailing list
> > > [e-mail]
> > > To unsubscribe:
> > > https://admin.fedoraproject.org/mailman/listinfo/docs
> >
> > --
> > docs mailing list
> > [e-mail]
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/docs
>
> --
> docs mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs

[Zach Oglesby]

On Tue, Feb 22, 2011 at 3:27 AM, Nick Bebout  wrote:
> If you'd like maintainer access to any of them on transifex.net, let me
> know.  maintainer access is necessary for you to be able to push new pot's
> to the server.  Translator access is managed through the "fedora" project,
> not through each's doc's teams.

I would just like to point out that this really is not optional for
guide owners, you really need to have a tx.net account so that you can
push your changes up.

[Eric Christensen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/22/2011 12:37 AM, Zach Oglesby wrote:
> On Tue, Feb 22, 2011 at 3:27 AM, Nick Bebout  wrote:
> > If you'd like maintainer access to any of them on transifex.net, let me
> > know.  maintainer access is necessary for you to be able to push new pot's
> > to the server.  Translator access is managed through the "fedora" project,
> > not through each's doc's teams.
>
> I would just like to point out that this really is not optional for
> guide owners, you really need to have a tx.net account so that you can
> push your changes up.

And why can't tx.net pull from our repos like the current one does?

- --Eric
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iF4EAREIAAYFAk1jyTcACgkQU03aaJDMNEXYwQD/WhUN0qrKzSsVkajO0+A9wu0p
> 2zXbbmt/eZ0l5X9UySoA+wUnRXOyvMzvJ8zxEJMPiFtIxBgUbEiYY6A9xgGt3MLJ
> =jdCm
> -----END PGP SIGNATURE-----

[Zach Oglesby]

On Tuesday, February 22, 2011 at 3:33 PM, Eric "Sparks" Christensen wrote:
> And why can't tx.net pull from our repos like the current one does?

It is no longer a feature of tx. However it was mentioned that it can monitor git repos over http for new pot files.

--
Zach Oglesby
GPG Key: F20C4707
zoglesby on irc.freenode.net
https://fedoraproject.org/wiki/User:Zoglesby

[Eric Christensen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/22/2011 09:36 AM, Zach Oglesby wrote:
> On Tuesday, February 22, 2011 at 3:33 PM, Eric "Sparks" Christensen wrote:
> > And why can't tx.net http://tx.net pull from our repos like the
> > current one does?
>
> It is no longer a feature of tx. However it was mentioned that it can
> monitor git repos over http for new pot files.

That's going to be a problem...  It was seamless before.  Things just
happened without a lot of user interaction which is good because people
just don't have time for a lot of extra steps.  I know John scripted
many steps to keep his sanity dealing with the Release Notes.  Is there
a way to script this on the backend?

- --Eric
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iF4EAREIAAYFAk1jzCgACgkQU03aaJDMNEUjswD+KLmlxOfVjXNDkulpCvZyLHaP
> vnGBm7dqD8tI4PocqeEA/3uDiJ5KBYRgU+LarW9fqXBTljppL8/HpaPbiAEeMjsD
> =x8OM
> -----END PGP SIGNATURE-----

[John J. McDonough]

On Tue, 2011-02-22 at 09:46 -0500, Eric "Sparks" Christensen wrote:
> That's going to be a problem...  It was seamless before.  Things just
> happened without a lot of user interaction which is good because people
> just don't have time for a lot of extra steps.  I know John scripted
> many steps to keep his sanity dealing with the Release Notes.  Is there
> a way to script this on the backend?

We can script *SOME* of it.  It appears that some has to be manual, tho.
Worse, the manual steps aren't all the time, but only once in a while,
so the odds of someone remembering how to do them, or even remembering
TO do them, are vanishingly small.

Well, I suspect we might be able to script all of it, but some of the
bits are going to be really tricky, and since I don't know what the new
tx API looks like, not guaranteed possible.

--McD

[Ricky Zhou]

On 2011-02-22 09:46:06 AM, Eric "Sparks" Christensen wrote:
> That's going to be a problem...  It was seamless before.  Things just
> happened without a lot of user interaction which is good because people
> just don't have time for a lot of extra steps.  I know John scripted
> many steps to keep his sanity dealing with the Release Notes.  Is there
> a way to script this on the backend?

If you want seamless transifex pushing/pulling, we can look at
integrating the transifex steps into the docs build process, or if
desired, a git hook.

Thanks,
Ricky

[Paul W. Frields]

On Tue, Feb 22, 2011 at 10:19:12AM -0500, Ricky Zhou wrote:
> On 2011-02-22 09:46:06 AM, Eric "Sparks" Christensen wrote:
> > That's going to be a problem...  It was seamless before.  Things just
> > happened without a lot of user interaction which is good because people
> > just don't have time for a lot of extra steps.  I know John scripted
> > many steps to keep his sanity dealing with the Release Notes.  Is there
> > a way to script this on the backend?
>
> If you want seamless transifex pushing/pulling, we can look at
> integrating the transifex steps into the docs build process, or if
> desired, a git hook.

Ricky et al.,

Dimitris and I were talking about language mappings earlier, which I
think will need to figure into the tooling to achieve something like
seamlessness.

The point being that, AFAICT, Docs is going to need some help with the
tooling so they can continue doing their actual documentation work for
F15.

* * *
<stickster> glezos: How are languages mapped between Publican <--> Tx?
<glezos> stickster: Tx has a large list of canonical languages:
     http://www.transifex.net/languages/
     stickster: languages are mapped to *local files* using the client
<stickster> glezos: So in the case of a Publican doc, let's take for
        example a translation into Greek -- the translations are stored in a
        "el-GR" directory as multiple PO files.
        glezos: Do we need to add some sort of config information in
        .tx/config since that's not el_GR but rather el-GR?
        http://git.fedorahosted.org/git/?p=docs/release-notes.git;a=tree
<glezos> stickster: Tx does its best when you push a file to it, to
     map it to a canonical language name (in this case, el_GR). But when
     you PULL the file, it can't know where you want to put it, really.
<stickster> glezos: So it would pull that content into something like
        'el/'
         or maybe 'el_GR/'
<glezos> stickster: You'll need to add this support to
     transifex-client.. ie. in .tx/config have some kind of mapping between
     canonical language names (el_GR) and your custom ones (el_-_**_-_GR or
     sth)
     stickster: correct.
<stickster> glezos: So let me make sure I understand correctly
        We have a couple options:
        1. Don't bother storing the PO locally at all, and grab it on demand
        from Tx when we need to build or publish
        "locally" == "in the git repo"  (sorry)
<glezos> stickster: correct.
<stickster> 2. If we have to store the PO in the git repo for some
        reason, we have to get someone who can add code to the
        transifex-client package to make the mapping possible
        In the case of 1, someone's got to write a set of e.g. Makefile rules
        to wrap around publican commands for building and publishing.
        In the case of 2, someone's got to write some Python code in
        transifex-client to do language mapping.
<glezos> stickster: 3. Instead of pushing this customization upstream
     to transifex-client like you mentioned, you can also just create your
     own scripts to mass-move codes (el_GR → el-GR) to make publican happy.
<stickster> Yes, good point
<glezos> stickster: I think that also in the case of 1, Publican won't
     be happy with underscores.
* * *

[Paul W. Frields]

On Tue, Feb 22, 2011 at 01:51:09PM -0500, Paul W. Frields wrote:
> On Tue, Feb 22, 2011 at 10:19:12AM -0500, Ricky Zhou wrote:
> > On 2011-02-22 09:46:06 AM, Eric "Sparks" Christensen wrote:
> > > That's going to be a problem...  It was seamless before.  Things just
> > > happened without a lot of user interaction which is good because people
> > > just don't have time for a lot of extra steps.  I know John scripted
> > > many steps to keep his sanity dealing with the Release Notes.  Is there
> > > a way to script this on the backend?
> >
> > If you want seamless transifex pushing/pulling, we can look at
> > integrating the transifex steps into the docs build process, or if
> > desired, a git hook.
>
> Ricky et al.,
>
> Dimitris and I were talking about language mappings earlier, which I
> think will need to figure into the tooling to achieve something like
> seamlessness.
>
> The point being that, AFAICT, Docs is going to need some help with the
> tooling so they can continue doing their actual documentation work for
> F15.

[...snip...]

I haven't seen more discussion about this here -- has anyone made a
request for help from either Infrastructure, or has Ricky talked to
someone elsewhere about rigging up the steps above?  Just speaking as
a guy who's trying to gear back up to being a team member, it's
unclear to me whether anyone's handling this problem.  I think
everyone agrees we don't want it to gather moss until a crucial point
in the release cycle.

So, who's got the ball?

[Nathan Thomas]

On Mon, 2011-02-21 at 15:36 -0600, Nick Bebout wrote:
> I'm working on adding our docs to transifex.net which will also involve
> branching them for f15.  If for some reason you don't want me to branch
> your guide, let me know.  Also, if you have a transifex.net account, let
> me know and I'll make you a maintainer so you can push updates to your
> pot's to transifex.net
>
> Nick

Hi Nick,

Thanks for doing this! I was wondering, how does this affect the working
process for maintaining a guide? Previously it went something like the
following:

- I'd commit changes to the git repo
- Translators would update their translations and commit to the git repo
- I'd use publican to build the guide from the git repo in various
formats for the languages that were sufficiently translated
- The built guides would be pushed to docs.fedoraproject.org, either as
a draft version or a full release

Will the above procedure change any following the move to Transifex.net?

Thanks,
Nathan
Live Image Guide maintainer

[Nick Bebout]

Basically now it will be

Commit changes to git repo
run publican update_pot
run tx push --source
translators translate on tx.net
run tx pull --all to download translations
use publican to publish to the website.
> On Mon, 2011-02-21 at 15:36 -0600, Nick Bebout wrote:
> > I'm working on adding our docs to transifex.net which will also involve
> > branching them for f15.  If for some reason you don't want me to branch
> > your guide, let me know.  Also, if you have a transifex.net account, let
> > me know and I'll make you a maintainer so you can push updates to your
> > pot's to transifex.net
> >
> > Nick
>
> Hi Nick,
>
> Thanks for doing this! I was wondering, how does this affect the working
> process for maintaining a guide? Previously it went something like the
> following:
> I'd commit changes to the git repo
> Translators would update their translations and commit to the git repo
> I'd use publican to build the guide from the git repo in various
>
> formats for the languages that were sufficiently translated
> The built guides would be pushed to docs.fedoraproject.org, either as
>
> a draft version or a full release
>
> Will the above procedure change any following the move to Transifex.net?
>
> Thanks,
> Nathan
> Live Image Guide maintainer
>
> --
> docs mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs

[Nathan Thomas]

Thanks Nick, that sounds simple enough!

Nathan

On Wed, 2011-02-23 at 18:00 -0600, Nick Bebout wrote:
> Basically now it will be
>
> Commit changes to git repo
> run publican update_pot
> run tx push --source
> translators translate on tx.net
> run tx pull --all to download translations
> use publican to publish to the website.
> > On Mon, 2011-02-21 at 15:36 -0600, Nick Bebout wrote:
> > > I'm working on adding our docs to transifex.net which will also involve
> > > branching them for f15.  If for some reason you don't want me to branch
> > > your guide, let me know.  Also, if you have a transifex.net account, let
> > > me know and I'll make you a maintainer so you can push updates to your
> > > pot's to transifex.net
> > >
> > > Nick
> >
> > Hi Nick,
> >
> > Thanks for doing this! I was wondering, how does this affect the working
> > process for maintaining a guide? Previously it went something like the
> > following:
> > I'd commit changes to the git repo
> > Translators would update their translations and commit to the git repo
> > I'd use publican to build the guide from the git repo in various
> >
> > formats for the languages that were sufficiently translated
> > The built guides would be pushed to docs.fedoraproject.org, either as
> >
> > a draft version or a full release
> >
> > Will the above procedure change any following the move to Transifex.net?
> >
> > Thanks,
> > Nathan
> > Live Image Guide maintainer
> >
> > --
> > docs mailing list
> > [e-mail]
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/docs

[Nathan Thomas]

Hi Nick, I now have a Transifex.net account (username: nathant). Please
could you make me a maintainer for the Live Image Guide
(readme-live-image).

Thanks
Nathan

On Wed, 2011-02-23 at 18:00 -0600, Nick Bebout wrote:
> Basically now it will be
>
> Commit changes to git repo
> run publican update_pot
> run tx push --source
> translators translate on tx.net
> run tx pull --all to download translations
> use publican to publish to the website.
> > On Mon, 2011-02-21 at 15:36 -0600, Nick Bebout wrote:
> > > I'm working on adding our docs to transifex.net which will also involve
> > > branching them for f15.  If for some reason you don't want me to branch
> > > your guide, let me know.  Also, if you have a transifex.net account, let
> > > me know and I'll make you a maintainer so you can push updates to your
> > > pot's to transifex.net
> > >
> > > Nick
> >
> > Hi Nick,
> >
> > Thanks for doing this! I was wondering, how does this affect the working
> > process for maintaining a guide? Previously it went something like the
> > following:
> > I'd commit changes to the git repo
> > Translators would update their translations and commit to the git repo
> > I'd use publican to build the guide from the git repo in various
> >
> > formats for the languages that were sufficiently translated
> > The built guides would be pushed to docs.fedoraproject.org, either as
> >
> > a draft version or a full release
> >
> > Will the above procedure change any following the move to Transifex.net?
> >
> > Thanks,
> > Nathan
> > Live Image Guide maintainer
> >
> > --
> > docs mailing list
> > [e-mail]
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/docs

[Nick Bebout]

Done.
> Hi Nick, I now have a Transifex.net account (username: nathant). Please
> could you make me a maintainer for the Live Image Guide
> (readme-live-image).
>
> Thanks
> Nathan
>
> On Wed, 2011-02-23 at 18:00 -0600, Nick Bebout wrote:
> > Basically now it will be
> >
> > Commit changes to git repo
> > run publican update_pot
> > run tx push --source
> > translators translate on tx.net
> > run tx pull --all to download translations
> > use publican to publish to the website.
> > > On Mon, 2011-02-21 at 15:36 -0600, Nick Bebout wrote:
> > > > I'm working on adding our docs to transifex.net which will also
> >
> > involve
> > > > branching them for f15.  If for some reason you don't want me to
> >
> > branch
> > > > your guide, let me know.  Also, if you have a transifex.net account,
> >
> > let
> > > > me know and I'll make you a maintainer so you can push updates to
> >
> > your
> > > > pot's to transifex.net
> > > >
> > > > Nick
> > >
> > > Hi Nick,
> > >
> > > Thanks for doing this! I was wondering, how does this affect the
> >
> > working
> > > process for maintaining a guide? Previously it went something like the
> > > following:
> > > I'd commit changes to the git repo
> > > Translators would update their translations and commit to the git
> >
> > repo
> > > I'd use publican to build the guide from the git repo in various
> > >
> > > formats for the languages that were sufficiently translated
> > > The built guides would be pushed to docs.fedoraproject.org, either
> >
> > as
> > > a draft version or a full release
> > >
> > > Will the above procedure change any following the move to
> >
> > Transifex.net?
> > > Thanks,
> > > Nathan
> > > Live Image Guide maintainer
> > >
> > > --
> > > docs mailing list
> > > [e-mail]
> > > To unsubscribe:
> > > https://admin.fedoraproject.org/mailman/listinfo/docs
>
> --
>
> <h3 style="color: #3d4d55"><i>Thinking, Feeling, Doing: Three
> Imaginative Dance Works</i></h3><br />
> Featuring Hagit Yakira, Maaikor Dance and Katia Lom<br />
> Thursday 3rd March 2011, Gulbenkian Theatre Canterbury<br />
> More info <a
> href="http://www.kent.ac.uk/gulbenkian/theatre/shows/2011/march/2011-03-03-thinking-feeling-doing.html">here</a><br
> />
> --
> docs mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs

[Nick Bebout]

Basically now it will be

Commit changes to git repo
run publican update_pot
run tx push --source
translators translate on tx.net
run tx pull --all to download translations
use publican to publish to the website.
> On Mon, 2011-02-21 at 15:36 -0600, Nick Bebout wrote:
> > I'm working on adding our docs to transifex.net which will also involve
> > branching them for f15.  If for some reason you don't want me to branch
> > your guide, let me know.  Also, if you have a transifex.net account, let
> > me know and I'll make you a maintainer so you can push updates to your
> > pot's to transifex.net
> >
> > Nick
>
> Hi Nick,
>
> Thanks for doing this! I was wondering, how does this affect the working
> process for maintaining a guide? Previously it went something like the
> following:
> I'd commit changes to the git repo
> Translators would update their translations and commit to the git repo
> I'd use publican to build the guide from the git repo in various
>
> formats for the languages that were sufficiently translated
> The built guides would be pushed to docs.fedoraproject.org, either as
>
> a draft version or a full release
>
> Will the above procedure change any following the move to Transifex.net?
>
> Thanks,
> Nathan
> Live Image Guide maintainer
>
> --
> docs mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs