Hi,
I am editing the translation-quick-start-guide to solve the bug #198725
published in Bugzilla.
I have made a list of steps needed to participate as a translator in the
documentation project. Can anybody tell me if I am leaving something
out?. At the moment I have:
* Create ssh key
* Create gpg key
* Suscribe to fedora-docs-list (and post a self introduction)
* apply for a fedora account
(https://admin.fedora.redhat.com/accounts => Create account)
* edit your account to apply for cvsdocs' write access
(https://admin.fedora.redhat.com/accounts => Edit your account)
* Create wiki account
(http://fedoraproject.org/wiki/UserPreferences)
* Complete the Contributor License Agreement
* Contact a person with edit access to ask for edit access
Cheers,
Manuel
Hi all.
Are there any plans to move the FAQs from the wiki to the Docs?
I'm not sure if it is really worth it, because a) FAQs are not the best
way to write documentation and b) probably every answer is/will be
included in or linked to the Guides (installation, desktop, etc).
Nevertheless, FAQs *are* popular among users and so are websites like
fedorafaq.org. Very linkable from outside, handy.
Do you guys think we should migrate the FAQs to a Doc, probably
maintained with the moinmoin export? This way we'll get them translated
more too.
-dim
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, PGP: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
Hello everyone,
Fedora usability was born but it's not official yet;-) :
http://fedoraproject.org/wiki/DamienDurand/Usability
What's fedora Usability?
The Fedora Usability project aims to provide coherence, accessibility and
intuivity for all people using Fedora Core and its associated resources.
Fedora must be easy and making things simple and coherent for a pleasant use
is my objectif with this project.
I need feedback, if you're interested to contribute feel free to add your
name in the usability group :
http://fedoraproject.org/wiki/DamienDurand/Usability/UsabilityGroup
Once this project completed and approved by you, I'll move the wiki pages
and will send an official announce ;-)
Thanks in advance
Damien Durand
It's been about six months (and one release!) since we did any major
surgery on our build tools, and we're past the test2 stage, which for
some reason seems to be our "jump into action" time here in Docs. Tommy
and I have decided that the rpm-info.xml file ought to be in our
per-language directories, which simplifies the translation process,
since it makes at least one less "extra" Docs-only rule for translators.
THIS CHANGE WILL BREAK BUILDING FOR EXISTING DOCUMENTS. But only
*temporarily*, assuming one does the following:
1. Move the rpm-info.xml file into the ${PRI_LANG} directory, usually
en_US/
2. Change the DTD reference to be one more parent up from the new
location (e.g. "../../docs-common..." becomes "../../../docs-common...")
3. Right now, the rpm-info.xml file contains <translation> subnodes in
the <titles> element, which is where translators currently put their
translations. The DTD will be changed to remove the <translation>
element entirely in favor of a single <title> and a single <desc>
element, which will be translated via the document's unified PO/POT
along with the other textual content. So any <translation> nodes other
than the ${PRI_LANG} (original) language SHOULD BE REMOVED, and the
${PRI_LANG} version should simply inhabit the parent element which will
now be <title> instead of <titles>. IOW, instead of this:
...
<titles>
<translation lang="en_US">
<title>Foo Tutorial</title>
<desc>A tutorial about Foo</desc>
</translation>
<translation lang="xx">
<title>Foofen Tutorialste</title>
<desc>Er tutorialste vio Foofen</desc>
</translation>
</title>
...
...we will now have this:
...
<title>Foo Tutorial</title>
<desc>A tutorial about Foo</desc>
...
All extra translated <changelog/revision/details> will also be removed
for the same reason. Sorry to cause a little bit more work for the
translators initially, but at wdorst you guys should be able to pull the
old translators out of CVS from a time before the commit if needed.
Until we get everything settled, stuff may not build correctly. I will
try and fix all the existing modules "in play," since there's not that
many to worry about. If I miss one and you find it, let me know. Give
me a couple days to get everything sussed out; the first modules to be
treated will be:
* release-notes
* example-tutorial
* translation-quick-start-guide
* install-guide
I should be able to get all the others done as well, but I promise those
four will be done soonest. Questions can go to this list per usual.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project Board: http://fedoraproject.org/wiki/Board
Fedora Docs Project: http://fedoraproject.org/wiki/DocsProject
Can i ask where we are on the FC6 Install GUide. I did not hear anything
back from the list about this, and want to know if this is still going
ahead, and if an editor/writer is still neded. If i am still required, can i
have some ideas where i need to start, and whom else is working on the
project.
Many Thanks,
Mr Adam L Moreland (MAniX) | Registered Linux User: #417406
BA (Hons) Media Studies, 2nd Year, UoN
WEB: http://www.manix-place.co.uk
BLOG:http://www.2welshmen-and-a-sheep.co.uk
****
System: Pentium 4 SKT478 2.8GHz Precott, AMD Athlon XP-M 2800+ | GPG Key:
AC230C32
****
pub 1024D/AC230C32 2006-05-21
Key fingerprint = 14F4 50F5 806C 25A5 B33C C2BF 982C 87B7 AC23 0C32
uid Adam Moreland (MAniX)
sub 2048g/A471FCE7 2006-05-21
****
_________________________________________________________________
The new Windows Live Toolbar helps you guard against viruses
http://toolbar.live.com/?mkt=en-gb