9:09 p.m.
Hi
Some translators seems starting translation via DL.
I am afraid of recent repository move for IG.
Could you please advise if any of documents listed on DL should be
stopped working?
thanks
noriko
10:26 p.m.
On Fri, Sep 26, 2008 at 12:09 PM, Noriko Mizumoto <noriko(a)redhat.com> wrote:
Hi
Some translators seems starting translation via DL.
I am afraid of recent repository move for IG.
Could you please advise if any of documents listed on DL should be
stopped working?
thanks
noriko
Hi Noriko,
I think the installation guide was moved to a new repository in git:
<https://www.redhat.com/archives/fedora-docs-list/2008-September/msg00073....
It looks like that message was also sent to this list.
Cheers.
10:31 p.m.
Noriko Mizumoto pisze:
Some translators seems starting translation via DL.
I am afraid of recent repository move for IG.
Could you please advise if any of documents listed on DL should be
stopped working?
I have just disabled documentation modules for Fedora 10. Starting from
this release docs are stored and developed in git. Unfortunately, we
can't switch DL to use these repos, because it doesn't support publican
documents.
--
Piotr Drąg
http://raven.pmail.pl
11:17 p.m.
Piotr Drąg さんは書きました:
Noriko Mizumoto pisze:
> Some translators seems starting translation via DL.
> I am afraid of recent repository move for IG.
>
> Could you please advise if any of documents listed on DL should be
> stopped working?
>
I have just disabled documentation modules for Fedora 10. Starting from
this release docs are stored and developed in git. Unfortunately, we
can't switch DL to use these repos, because it doesn't support publican
documents.
Ok, thanks!
Then may be separate instruction will be needed to follow, how to get
the docs-file and where to commit. Could someone give me any pointer?
noriko
4:08 a.m.
2008/9/26 Piotr Drąg <piotrdrag(a)gmail.com>:
Noriko Mizumoto pisze:
>
> Some translators seems starting translation via DL.
> I am afraid of recent repository move for IG.
>
> Could you please advise if any of documents listed on DL should be
> stopped working?
>
I have just disabled documentation modules for Fedora 10. Starting from this
release docs are stored and developed in git. Unfortunately, we can't switch
DL to use these repos, because it doesn't support publican documents.
Thanks Piotr.
We'll need the usual steps followed to add these modules to transifex:
http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
The most important ones are having 'transif' added to the respective
account system groups and notifying us with which <VCS root, module,
branch> to use. One bug report for all moved Docs would be sufficient,
and we can re-open it when a new module has been moved.
-d
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
6:59 a.m.
On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos wrote:
2008/9/26 Piotr Drąg <piotrdrag(a)gmail.com>:
> Noriko Mizumoto pisze:
>>
>> Some translators seems starting translation via DL.
>> I am afraid of recent repository move for IG.
>>
>> Could you please advise if any of documents listed on DL should be
>> stopped working?
>>
>
> I have just disabled documentation modules for Fedora 10. Starting from this
> release docs are stored and developed in git. Unfortunately, we can't switch
> DL to use these repos, because it doesn't support publican documents.
Thanks Piotr.
We'll need the usual steps followed to add these modules to transifex:
http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
The most important ones are having 'transif' added to the respective
account system groups and notifying us with which <VCS root, module,
branch> to use. One bug report for all moved Docs would be sufficient,
and we can re-open it when a new module has been moved.
I've added the transif user to all the following groups:
* gitinstall-guide
* gitrelease-notes
* gitabout-fedora
* gitreadme
* gitreadme-burning-isos
* gitreadme-live-image
* githomepage
The repos are located here, respectively, with branches:
* git://git.fedorahosted.org/git/docs/install-guide (f8, f9, devel)
* git://git.fedorahosted.org/git/docs/release-notes (f8, f9, devel)
I still need to properly branch the following repos:
* git://git.fedorahosted.org/git/docs/about-fedora
* git://git.fedorahosted.org/git/docs/readme
* git://git.fedorahosted.org/git/docs/readme-burning-isos
* git://git.fedorahosted.org/git/docs/readme-live-image
* git://git.fedorahosted.org/git/docs/homepage
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
11:36 a.m.
2008/9/26 Paul W. Frields <stickster(a)gmail.com>:
On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos wrote:
> We'll need the usual steps followed to add these modules to transifex:
>
> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
>
> The most important ones are having 'transif' added to the respective
> account system groups and notifying us with which <VCS root, module,
> branch> to use. One bug report for all moved Docs would be sufficient,
> and we can re-open it when a new module has been moved.
I've added the transif user to all the following groups:
* gitinstall-guide
* gitrelease-notes
* gitabout-fedora
* gitreadme
* gitreadme-burning-isos
* gitreadme-live-image
* githomepage
The repos are located here, respectively, with branches:
* git://git.fedorahosted.org/git/docs/install-guide (f8, f9, devel)
* git://git.fedorahosted.org/git/docs/release-notes (f8, f9, devel)
I still need to properly branch the following repos:
* git://git.fedorahosted.org/git/docs/about-fedora
* git://git.fedorahosted.org/git/docs/readme
* git://git.fedorahosted.org/git/docs/readme-burning-isos
* git://git.fedorahosted.org/git/docs/readme-live-image
* git://git.fedorahosted.org/git/docs/homepage
All 7 docs projects have been registered and enabled [1] in Transifex.
https://translate.fedoraproject.org/submit/module/
The branch in use is 'master'. We support >1 branches per module,
please let me know if we really need to have more branches active for
submissions.
A successful commit has been made to release-notes:master:
http://git.fedorahosted.org/git/docs/release-notes?p=docs/release-notes.g...
Patches that make DL (and, even better, Translate Toolkit) read
Publican documents are welcome.
-d
[1]: http://dpaste.com/80730/
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
6:49 a.m.
Dimitris Glezos wrote:
2008/9/26 Paul W. Frields <stickster(a)gmail.com>:
> On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos wrote:
>
>> We'll need the usual steps followed to add these modules to transifex:
>>
>> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
>>
>> The most important ones are having 'transif' added to the respective
>> account system groups and notifying us with which <VCS root, module,
>> branch> to use. One bug report for all moved Docs would be sufficient,
>> and we can re-open it when a new module has been moved.
>>
> I've added the transif user to all the following groups:
> * gitinstall-guide
> * gitrelease-notes
> * gitabout-fedora
> * gitreadme
> * gitreadme-burning-isos
> * gitreadme-live-image
> * githomepage
>
> The repos are located here, respectively, with branches:
>
> * git://git.fedorahosted.org/git/docs/install-guide (f8, f9, devel)
> * git://git.fedorahosted.org/git/docs/release-notes (f8, f9, devel)
>
> I still need to properly branch the following repos:
>
> * git://git.fedorahosted.org/git/docs/about-fedora
> * git://git.fedorahosted.org/git/docs/readme
> * git://git.fedorahosted.org/git/docs/readme-burning-isos
> * git://git.fedorahosted.org/git/docs/readme-live-image
> * git://git.fedorahosted.org/git/docs/homepage
>
All 7 docs projects have been registered and enabled [1] in Transifex.
https://translate.fedoraproject.org/submit/module/
Can we get all 7 docs projects enabled in DL as well?
Thanks!
The branch in use is 'master'. We support >1 branches per
module,
please let me know if we really need to have more branches active for
submissions.
A successful commit has been made to release-notes:master:
http://git.fedorahosted.org/git/docs/release-notes?p=docs/release-notes.g...
Patches that make DL (and, even better, Translate Toolkit) read
Publican documents are welcome.
-d
[1]: http://dpaste.com/80730/
--
Regards,
Ankit Patel
http://www.indianoss.org/
7:13 a.m.
On Mon, Sep 29, 2008 at 05:19:14PM +0530, Ankitkumar Rameshchandra Patel wrote:
Dimitris Glezos wrote:
> 2008/9/26 Paul W. Frields <stickster(a)gmail.com>:
>
>> On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos wrote:
>>
>>> We'll need the usual steps followed to add these modules to transifex:
>>>
>>> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
>>>
>>> The most important ones are having 'transif' added to the respective
>>> account system groups and notifying us with which <VCS root, module,
>>> branch> to use. One bug report for all moved Docs would be sufficient,
>>> and we can re-open it when a new module has been moved.
>>>
>> I've added the transif user to all the following groups:
>> * gitinstall-guide
>> * gitrelease-notes
>> * gitabout-fedora
>> * gitreadme
>> * gitreadme-burning-isos
>> * gitreadme-live-image
>> * githomepage
>>
>> The repos are located here, respectively, with branches:
>>
>> * git://git.fedorahosted.org/git/docs/install-guide (f8, f9, devel)
>> * git://git.fedorahosted.org/git/docs/release-notes (f8, f9, devel)
>>
>> I still need to properly branch the following repos:
>>
>> * git://git.fedorahosted.org/git/docs/about-fedora
>> * git://git.fedorahosted.org/git/docs/readme
>> * git://git.fedorahosted.org/git/docs/readme-burning-isos
>> * git://git.fedorahosted.org/git/docs/readme-live-image
>> * git://git.fedorahosted.org/git/docs/homepage
>>
>
> All 7 docs projects have been registered and enabled [1] in Transifex.
>
> https://translate.fedoraproject.org/submit/module/
>
Can we get all 7 docs projects enabled in DL as well?
I think Dimitris mentioned earlier that Damned Lies won't support
Publican's multiple POT files. It would be great if Red Hat I18n/L10n
would collaborate with the community to help pave the way for
statistics reporting for these repos. I don't know whether that means
fixing part of DL, or simply accelerating the rate at which
statistical support in Tx is written. I know Dimitris, Asgeir, and
any of the other Tx developers would be thrilled to have some
assistance with this.
In the meantime, Dimitris also suggested a workaround using some sort
of simple Python script. I doubt that's been written yet, maybe
someone can help there?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
12:13 p.m.
2008/9/29 Paul W. Frields <stickster(a)gmail.com>:
On Mon, Sep 29, 2008 at 05:19:14PM +0530, Ankitkumar Rameshchandra
Patel wrote:
> Dimitris Glezos wrote:
>> 2008/9/26 Paul W. Frields <stickster(a)gmail.com>:
>>
>>> On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos wrote:
>>>
>>>> We'll need the usual steps followed to add these modules to
transifex:
>>>>
>>>> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
>>>>
>>>> The most important ones are having 'transif' added to the
respective
>>>> account system groups and notifying us with which <VCS root, module,
>>>> branch> to use. One bug report for all moved Docs would be
sufficient,
>>>> and we can re-open it when a new module has been moved.
>>>>
>> All 7 docs projects have been registered and enabled [1] in Transifex.
>>
>> https://translate.fedoraproject.org/submit/module/
>>
>
> Can we get all 7 docs projects enabled in DL as well?
I think Dimitris mentioned earlier that Damned Lies won't support
Publican's multiple POT files. It would be great if Red Hat I18n/L10n
would collaborate with the community to help pave the way for
statistics reporting for these repos. I don't know whether that means
fixing part of DL, or simply accelerating the rate at which
statistical support in Tx is written. I know Dimitris, Asgeir, and
any of the other Tx developers would be thrilled to have some
assistance with this.
Patches are welcome with champagnes and fireworks, as always. :D
In the meantime, Dimitris also suggested a workaround using some
sort
of simple Python script. I doubt that's been written yet, maybe
someone can help there?
Here's a sample skeleton for such a script/scenario, for anyone who'd
like to actually code it.
-----------------------
== Get the source ==
First time:
$ project-list = ['about', 'release-notes']
$ for p in project-list:
git clone git://git.fedoraproject.org/git/{p}.git
Later, to pull new changes:
$ for p in project-list:
git fetch && ...
== Calculate statistics ==
$ wget http://.../fedora-docs-l10n-script.py
$ python fedora-docs-l10n-script.py pt_BR
pt_BR statistics:
about: 80% (115T, 40F, 10U)
release-notes: 80% (115T, 40F, 10U)
-----------------------
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
4:38 p.m.
On Tue, Sep 30, 2008 at 3:13 AM, Dimitris Glezos <dimitris(a)glezos.com> wrote:
2008/9/29 Paul W. Frields <stickster(a)gmail.com>:
> On Mon, Sep 29, 2008 at 05:19:14PM +0530, Ankitkumar Rameshchandra Patel wrote:
>> Dimitris Glezos wrote:
>>> 2008/9/26 Paul W. Frields <stickster(a)gmail.com>:
>>>
>>>> On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos wrote:
>>>>
>>>>> We'll need the usual steps followed to add these modules to
transifex:
>>>>>
>>>>> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex
>>>>>
>>>>> The most important ones are having 'transif' added to the
respective
>>>>> account system groups and notifying us with which <VCS root,
module,
>>>>> branch> to use. One bug report for all moved Docs would be
sufficient,
>>>>> and we can re-open it when a new module has been moved.
>>>>>
>>> All 7 docs projects have been registered and enabled [1] in Transifex.
>>>
>>> https://translate.fedoraproject.org/submit/module/
>>>
>>
>> Can we get all 7 docs projects enabled in DL as well?
>
> I think Dimitris mentioned earlier that Damned Lies won't support
> Publican's multiple POT files. It would be great if Red Hat I18n/L10n
> would collaborate with the community to help pave the way for
> statistics reporting for these repos. I don't know whether that means
> fixing part of DL, or simply accelerating the rate at which
> statistical support in Tx is written. I know Dimitris, Asgeir, and
> any of the other Tx developers would be thrilled to have some
> assistance with this.
Patches are welcome with champagnes and fireworks, as always. :D
> In the meantime, Dimitris also suggested a workaround using some sort
> of simple Python script. I doubt that's been written yet, maybe
> someone can help there?
Here's a sample skeleton for such a script/scenario, for anyone who'd
like to actually code it.
-----------------------
== Get the source ==
First time:
$ project-list = ['about', 'release-notes']
$ for p in project-list:
git clone git://git.fedoraproject.org/git/{p}.git
Later, to pull new changes:
$ for p in project-list:
git fetch && ...
== Calculate statistics ==
$ wget http://.../fedora-docs-l10n-script.py
$ python fedora-docs-l10n-script.py pt_BR
pt_BR statistics:
about: 80% (115T, 40F, 10U)
release-notes: 80% (115T, 40F, 10U)
-----------------------
If I remember correctly, publican actually has a 'genearate
translation statistics' make target that can even generate HTML.
Would it be ok If I set up a cron job that:
1) Puts translation statistics on a public web page (to make it
simple, e.g. my fedorapeople web space)
2) Sends updated statistics to fedora-trans-list daily, or even after
each 'submission' depending on how much we want to spam that list...
In addition, we could add a link to this stats through the front page
of translate.fedoraproject.org
Comments on this workflow is welcome, but I'll try to make sure we at
least have some statistics for our documentation SOON.
I guess the fedora infrastructure is in 'freeze' mode, so I'm not sure
how easy it would be to make the script run inside the
infrastructure... But the main concern now is giving translators some
statistics :)
But first for some breakfast...
cheers,
asgeir
5:33 p.m.
2008/9/30 Asgeir Frimannsson <asgeirf(a)gmail.com>:
If I remember correctly, publican actually has a 'genearate
translation statistics' make target that can even generate HTML.
What would a translator need to do to get one of ours Docs and
generate statistics himself? Could we have this documented somewhere
(eg. the TQSG or FAQ)? Necessary git commands would also help a lot.
Would it be ok If I set up a cron job that:
1) Puts translation statistics on a public web page (to make it
simple, e.g. my fedorapeople web space)
A page updated daily with docs stats could do the trick until Publican
support can be added inside DL and the Toolkit.
Since it's just 7 modules I guess we could start simple and avoid
Fedora-hosted crons and Infra (they already have a lot on their
minds). Someone of us could cron on his workstation and rsync the
HTMLs on his fedorapeople page.
2) Sends updated statistics to fedora-trans-list daily, or even
after
each 'submission' depending on how much we want to spam that list...
Ideally no spamming at all. :-) The information will be in one place
for anyone who'd like to see it.
In addition, we could add a link to this stats through the front
page
of translate.fedoraproject.org
Comments on this workflow is welcome, but I'll try to make sure we at
least have some statistics for our documentation SOON.
Thanks for looking into this Asgeir.
-d
I guess the fedora infrastructure is in 'freeze' mode, so
I'm not sure
how easy it would be to make the script run inside the
infrastructure... But the main concern now is giving translators some
statistics :)
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
7:03 p.m.
On Tue, Sep 30, 2008 at 01:33:24AM +0300, Dimitris Glezos wrote:
2008/9/30 Asgeir Frimannsson <asgeirf(a)gmail.com>:
> If I remember correctly, publican actually has a 'genearate
> translation statistics' make target that can even generate HTML.
What would a translator need to do to get one of ours Docs and
generate statistics himself? Could we have this documented somewhere
(eg. the TQSG or FAQ)? Necessary git commands would also help a lot.
Start here and let me or Karsten know what's missing or erroneous:
https://fedoraproject.org/wiki/Docs_Project_work_using_git
> Would it be ok If I set up a cron job that:
> 1) Puts translation statistics on a public web page (to make it
> simple, e.g. my fedorapeople web space)
A page updated daily with docs stats could do the trick until Publican
support can be added inside DL and the Toolkit.
Since it's just 7 modules I guess we could start simple and avoid
Fedora-hosted crons and Infra (they already have a lot on their
minds). Someone of us could cron on his workstation and rsync the
HTMLs on his fedorapeople page.
I used to do this (more or less) using the wiki and the Fedora Docs
toolchain. Enough would be different now (new wiki, different SCM,
etc.) that the script I used is entirely worthless.
> 2) Sends updated statistics to fedora-trans-list daily, or even
after
> each 'submission' depending on how much we want to spam that list...
Ideally no spamming at all. :-) The information will be in one place
for anyone who'd like to see it.
> In addition, we could add a link to this stats through the front page
> of translate.fedoraproject.org
>
> Comments on this workflow is welcome, but I'll try to make sure we at
> least have some statistics for our documentation SOON.
Thanks for looking into this Asgeir.
+1.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
8:46 p.m.
Paul W. Frields さんは書きました:
On Tue, Sep 30, 2008 at 01:33:24AM +0300, Dimitris Glezos wrote:
> 2008/9/30 Asgeir Frimannsson <asgeirf(a)gmail.com>:
>> If I remember correctly, publican actually has a 'genearate
>> translation statistics' make target that can even generate HTML.
> What would a translator need to do to get one of ours Docs and
> generate statistics himself? Could we have this documented somewhere
> (eg. the TQSG or FAQ)? Necessary git commands would also help a lot.
Start here and let me or Karsten know what's missing or erroneous:
https://fedoraproject.org/wiki/Docs_Project_work_using_git
Let me see what I can do.
>> Would it be ok If I set up a cron job that:
>> 1) Puts translation statistics on a public web page (to make it
>> simple, e.g. my fedorapeople web space)
> A page updated daily with docs stats could do the trick until Publican
> support can be added inside DL and the Toolkit.
>
> Since it's just 7 modules I guess we could start simple and avoid
> Fedora-hosted crons and Infra (they already have a lot on their
> minds). Someone of us could cron on his workstation and rsync the
> HTMLs on his fedorapeople page.
I used to do this (more or less) using the wiki and the Fedora Docs
toolchain. Enough would be different now (new wiki, different SCM,
etc.) that the script I used is entirely worthless.
>> 2) Sends updated statistics to fedora-trans-list daily, or even after
>> each 'submission' depending on how much we want to spam that list...
> Ideally no spamming at all. :-) The information will be in one place
> for anyone who'd like to see it.
>
>> In addition, we could add a link to this stats through the front page
>> of translate.fedoraproject.org
Do you mean here (where old doc translation was placed)?
http://translate.fedoraproject.org/languages/ja/fedora-10
If so very nice :-)
>>
>> Comments on this workflow is welcome, but I'll try to make sure we at
>> least have some statistics for our documentation SOON.
> Thanks for looking into this Asgeir.
+1.
+1
noriko
------------------------------------------------------------------------
--
Fedora-trans-list mailing list
Fedora-trans-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-trans-list
5687
days inactive
5691
days old
13 comments
7 participants
participants (7)
-
Ankit Patel -
Asgeir Frimannsson -
Dimitris Glezos -
Murray McAllister -
Noriko Mizumoto -
Paul W. Frields -
Piotr Drąg