Re: some issues in docs.fedoraproject.org
by Ruediger Landmann
On 10/06/2009 10:22 PM, Domingo Becker wrote:
> 2009/10/6 Ruediger Landmann<r.landmann(a)redhat.com>:
>
>> No books were actually changed; only the main index page. Therefore, any
>> errors in any books were already there. In the case of the Installation
>> Guide, since 19 June [1]; and in the case of the Installation Quick Start
>> Guide, since 6 August [2].
>>
> I remember that. I remember I have asked that before.
> If it's possible to correct it, please do so.
> If you need some more extra work from us, just let us know.
>
The only way I can see to correct this will be:
* I identify the PO files in Publican that still contain fuzzy and
untranslated strings even after the big Transifex PO file has been split
across them
* I email these PO files out to translators
* Translators work on these files and mail them back to me
* I check these files into the repo manually
* I rebuild and republish the books with the updated PO files in place
* We all pray that the next time that we split a big PO file from
Transifex across the Publican PO files, that it does not break what we
did in the above steps :)
Basically, we side-step Transifex with a manual process.
If any language team would like to attempt this with the Installation
Guide and Installation Quick Start Guide, I'm prepared to work with you
to do this. But I admit that I'm not very eager to "work around" our own
systems and processes this way :(
As you say later in your email, this is time and effort that we could
probably all spend in better ways, especially because when we get
Transifex 0.7, this problem will go away by itself! :) Please make sure
to file that bug, though.
>>> and the common content.
>>>
>> As far as I can tell. the only part of the Common Content that ever appeared
>> in English was the Legal Notice, which always appears in English, for legal
>> reasons. Was there something else wrong?
>>
> No. It seems it's in English for the new books.
> Take a look at [1]
> If there are legal issues about this, then leave it like this.
> Otherwise, it would be better to have that localised.
> I know a wrong translation here would be a problem. But if a
> translator has doubts, then it's better to leave it untranslated.
>
> [1] http://docs.fedoraproject.org/release-notes/f10/es/sn-legalnotice.html
>
>
The Fedora 10 Release Notes were an anomaly; they are the only place
I've found the Legal Notice ever translated -- it certainly wasn't that
way in the Release Notes in earlier versions.
I have confirmed with Red Hat's legal department today that this notice
should not be translated. The reason is simple: in legal matters, the
/exact/ wording of the notice has consequences. Therefore, if we
translate the legal notice, the legal department would need to check and
approve the wording in every language. Unfortunately, the legal
department simply does not have the resources to do this.
Maybe this should be added to an L10N FAQ somewhere?
Cheers, and thanks for your kind words :)
Ruediger
14 years, 5 months
some issues in docs.fedoraproject.org
by Domingo Becker
oops, I forgotten to include fedora-docs-list
---------- Forwarded message ----------
From: Domingo Becker <domingobecker(a)gmail.com>
Date: 2009/10/6
Subject: Re: some issues in docs.fedoraproject.org
To: Fedora Translation Project List <fedora-trans-list(a)redhat.com>
2009/10/6 Ruediger Landmann <r.landmann(a)redhat.com>:
>
> No books were actually changed; only the main index page. Therefore, any
> errors in any books were already there. In the case of the Installation
> Guide, since 19 June [1]; and in the case of the Installation Quick Start
> Guide, since 6 August [2].
>
I remember that. I remember I have asked that before.
If it's possible to correct it, please do so.
If you need some more extra work from us, just let us know.
>
> Please file a bug against the Fedora 11 Installation Guide so that we have a
> record that this happened.
>
Ok, I'll file a bug report.
> If anyone knows of a more reliable method or tool to merge the many small PO
> files into a single, big PO file, please say so!
>
> I also seem to recall seeing problems in the other direction; some strings
> that were translated in the big PO files were sometimes lost while splitting
> them into many small PO files -- I can't think of an example right now, but
> someone else might remember?
>
>> and the common content.
>
> As far as I can tell. the only part of the Common Content that ever appeared
> in English was the Legal Notice, which always appears in English, for legal
> reasons. Was there something else wrong?
>
No. It seems it's in English for the new books.
Take a look at [1]
If there are legal issues about this, then leave it like this.
Otherwise, it would be better to have that localised.
I know a wrong translation here would be a problem. But if a
translator has doubts, then it's better to leave it untranslated.
[1] http://docs.fedoraproject.org/release-notes/f10/es/sn-legalnotice.html
>
> Of course, the degree of localisation depends on the degree of localisation
> in anaconda.
So, the problem is in anaconda. I'll take a closer look today, I have
to install Fedora on a desktop computer for production. I will file a
bug report against anaconda so they include those strings too in the
pot file.
> Of course, with so many screenshots and so many languages, it's quite
> possible I made some mistakes here and there.
That's why I say that you probably will need our help.
We (translators) are more interested than anyone else in its accuracy.
So let us know, we'll be glad to help you.
The big pot file issue is solved in the next Transifex, that is not
still in use in Fedora Infrastructure.
If necessary, let's wait until then. Anyway, we still have work to do
with Installation Guide, Virtualization Guide and SELinux Managing
Confined Services Guide. We can be busy until that upgrade.
Thank you Ruediger, specially for your interest to improve Fedora's
documentation quality.
And thank you all the docs team, for all the great books you gave us
since Fedora 11. They cover almost every aspect ! There's no need to
go and read elsewhere. It makes me happy. :-)
kind regards
Domingo Becker (es)
14 years, 5 months
Docs preparing to convert to Creative Commons BY-SA 3.0 Unported license
by Ian Weller
Today, the Docs team finalized the conversion of the licensing of our
documentation and project content from the Open Publication License
(OPL) to a Creative Commons Attribution-Share Alike 3.0 Unported License
(CC-BY-SA). Docs originally reached a consensus to change the license in
June 2009, and after answering questions raised by the community, the
Docs team decided to go ahead with the transition.
While OPL is a free and open documentation license, moving to a more
widely known and adopted license and the one used by the likes of
Wikipedia and GNOME Project helps us share our content more easily with
the rest of the Free software community.
Additional information can be found at:
https://fedoraproject.org/wiki/Relicensing_OPL_to_CC_BY_SA
We'd like to thank Tom 'spot' Callaway, Fedora's legal ninja, and
Richard Fontana of Red Hat Legal for their help with the conversion. We
look forward to continue working with the community and share our
documentation freely.
--
Ian Weller <ian(a)ianweller.org>
"Why, a four-year-old could understand this report.
Find me a four-year-old child.
I can't make head or tail out of it." -- Groucho Marx, "Duck Soup"
14 years, 5 months
Fedora 12 install-guide screenshots
by Domingo Becker
The new option "autostep --autoscreenshot" in the kickstart file would
probably make it ease to get the localized screenshots included in the
Install Guide.
Don't hesitate to ask translators to get those screenshots.
For Fedora 11 Install Guide they are all in English. We can improve that. :-)
kind regards
Domingo Becker
Spanish Translation Team
14 years, 5 months
ready to send out license changeover email on monday
by Ian Weller
Thanks to Karsten filling in the appropriate wiki page, I'm ready to
send out this email:
http://fedoraproject.org/wiki/User:Ianweller/Creative_Commons_press_relea...
on Monday. It will go to the following lists:
fedora-announce-list
fedora-devel-announce
fedora-advisory-board
fedora-docs-list
(It should probably go to a translator's list as well but I don't know
which one, and I'd need it approved when I send it since I'm not
subscribed to one.)
Let me know what modifications you would make to either the email or the
recipients before about 19:00 UTC Monday. Happy weekend :)
--
Ian Weller <ian(a)ianweller.org>
"Why, a four-year-old could understand this report.
Find me a four-year-old child.
I can't make head or tail out of it." -- Groucho Marx, "Duck Soup"
14 years, 5 months
2nd Draft Ready for Review: Ch. 1: Yum
by Douglas Silas
2nd try on 2nd draft for Ch. 1: *YUM* (not PackageKit ;-)) Ah well...
I have expanded the Yum chapter significantly since the 1st draft,
and it should now be more-or-less complete. This is the last draft
before I finalize the text for translation, so please send your
comments/ suggestions! Especially if you think the Yum chapter
should cover something important that it does not.
Note: Yum and its "ecosphere" (yum-utils, plugins, etc.) provide
many more capabilities than can be described in the Deployment
Guide. That said, I am very interested in Yum use cases and
procedures that system administrators find indispensable. One
example would be: documenting orphan and unneeded package removal
with the package-cleanup command. Or merging config files with
yum-plugin-merge-conf. Initial text for supplementary sections would
be much appreciated.
Without further ado:
http://dsilas.fedorapeople.org/Deployment_Guide/en-US/html-single/#ch-yum
I have incorporated many suggestions from Rahul Sundaram and others
into this draft. Thanks Rahul!
The (partial) list of changes:
* Yum plugins in general documented; specific ones (presto,
fastestmirror, refresh-packagekit) now described
* chapter's 2nd paragraph is now a large admonition concerning GPG
package verification and security, with links
* removing packages and groups now explained in detail, along with
discussion of dependencies
* [main] and [repository] sections beefed up; new options explained
* improved command for creating Yum repos
* Additional Resources added (only one thus far)
Regards,
--
Douglas Silas
Technical Writer | Red Hat, Inc.
_______________________________________________
deployment-guide-list
https://fedorahosted.org/deploymentguide/
Unsubscribe:
https://www.redhat.com/mailman/options/deployment-guide-list
--
Douglas Silas
Technical Writer | Red Hat, Inc.
14 years, 5 months
2nd Draft Ready for Review: Ch. 1: PackageKit
by Douglas Silas
I have expanded the Yum chapter significantly since the 1st draft,
and it should now be more-or-less complete. This is the last draft
before I finalize the text for translation, so please send your
comments/ suggestions! Especially if you think the Yum chapter
should cover something important that it does not.
Note: Yum and its "ecosphere" (yum-utils, plugins, etc.) provide
many more capabilities than can be described in the Deployment
Guide. That said, I am very interested in Yum use cases and
procedures that system administrators find indispensable. One
example would be: documenting orphan and unneeded package removal
with the package-cleanup command. Or merging config files with
yum-plugin-merge-conf. Initial text for supplementary sections would
be much appreciated.
Without further ado:
http://dsilas.fedorapeople.org/Deployment_Guide/en-US/html-single/#ch-yum
I have incorporated many suggestions from Rahul Sundaram and others
into this draft. Thanks Rahul!
The (partial) list of changes:
* Yum plugins in general documented; specific ones (presto,
fastestmirror, refresh-packagekit) now described
* chapter's 2nd paragraph is now a large admonition concerning GPG
package verification and security, with links
* removing packages and groups now explained in detail, along with
discussion of dependencies
* [main] and [repository] sections beefed up; new options explained
* improved command for creating Yum repos
* Additional Resources added (only one thus far)
Regards,
--
Douglas Silas
Technical Writer | Red Hat, Inc.
14 years, 5 months