The Defensive and coding guide sports an interesting and forgotten feature
in its file organization: directories.
Beyond directories, it also happens to show files having the same name
(such as Language.xml, found in Python/, Java/, CXX/, C/, etc. or
You tell me, that is what directories are for. Fair enough.
The real issue here is that pushing .po resulting from those XML files to
Transifex which only handles uniquely named resources in a flat hierarchy
leads to a mess, where there is no predictibility in having the Language
resource always the same on Transifex, depending how those are pushed.
Could it be possible to rename all those files to unique names, ideally
with the subdir as a prefix (such as CXX-Language.xml or C-schema.xml) so
that we have unique resource names in Transifex?
Furthermore, could we add a requirement to documentation authors in order
to ensure that all XML files in their document hierarchy show unique names?
--- Comment #17 from Eric Christensen <sparks(a)redhat.com> ---
I only know of one other project that had its base (source) language that
wasn't EN. The "problem" was solved by translating it to English and then to
Unfortunately that is how our model is setup. Our expectation is that the
translators will translate text from English to another language. This should
limit someone's ability to write in their native language, though. There's
just another hop involved.
You are receiving this mail because:
You are the assignee for the bug.
Some Docbook XML files I've seen do not contain line breaks within
paragraphs. These long lines are a bit unwieldy in line-based editors
and also show up badly in line-based diffs.
Is this XML source layout the preferred style, or would it be considered
okay to wrap long lines as a separate change before making actual
Florian Weimer / Red Hat Product Security Team
Well, I can't say I've done much writing in the past, or worked on any big
name free-software projects, but I do have a bit of code up on the
I have fairly advanced computer skills, no degree, but otherwise I do have
programming and administrative skills.
I have moderate people skills, and can speak well, having a firm grasp of
the English language.
I feel I am an excellent match for this project because I have an
understanding of the English language and of the technical concepts
required for it.
Hi Fedora translators and writers :)
My name is Isaac Rooskov. I am the new Product Manager for the Zanata
translation tool, and I also supervise the localization and translation
efforts for JBoss, Red Hat Enterprise Virtualization and Cloud business
units at Red Hat.
If you have any questions or feedback concerning Zanata I would love to
I'm based in Brisbane, Australia, so if there is a slight delay in my
responses that may be why ;)
Thanks and I look forward to being apart of the Fedora community with
Supervisor, Localization Services
Product Manager, Zanata
-----BEGIN PGP SIGNED MESSAGE-----
I just realized the reason I couldn't publish an update to the Defensive Coding Guide was because I've upgraded to Fedora 19 which has Publican 3 as its offering. This causes several errors to occur when trying to install a book onto the web repo. I guess I have two questions:
1) Is there a workaround for this so we can publish things to the web using the latest version of Publican?
2) When will we be able to publish documents using koji?
- -- Eric
Eric "Sparks" Christensen
sparks(a)fedoraproject.org - sparks(a)redhat.com
097C 82C3 52DF C64A 50C2 E3A3 8076 ABDE 024B B3D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
-----END PGP SIGNATURE-----
Okay, let's go down the bullet list from the wiki:
Hi, my name is Benjamin Thompson and I go by Ben, my handle on FAS is
I'm in the US Eastern time zone, in northern Indiana, USA.
My experience is in technical support, Python development including
web2py, Linux administration, and I have a Bachelor of Arts degree in
English. I am Linux+/LPIC-1 certified. In time, I plan to go up to
LPIC-3 and RHCE. I've been using Linux as a desktop OS since about 2003.
I'm looking to join the Fedora Project in order to hone my technical
writing skills, and perhaps flex my coding or sysadmin muscles
eventually as well. My aim is to make myself a more proficient,
knowledgeable user/administrator of Linux operating systems.
To start I would like to contribute documentation, no matter how small
or seemingly inconsequential. The parts of the OS I am most interested
in helping with are cryptographic and networking tools, although my
knowledge level is not terribly deep yet on those subjects. My other
passion is user-friendliness. Applications geared toward making the OS
as a whole more approachable are of great interest to me. If
documentation on any of these is lacking I would be quite happy to try
and fill in the gaps.
After finding some training and/or a sponsor, I look forward to
contributing about 4 hours per week. I work full time sometimes up to 50
hours a week, but there is often enough time on the nights and weekends
to put several hours in.
I have lurked for quite some time. I've recently decided that I need to
stop WISHING I was contributing and start making that a reality. I look
forward to listening in on meetings in the coming weeks. Perhaps I can
even contribute some documentation work for the Fedora 20 release.
We're throwing a meeting in #fedora-meeting on freenode, 26 Aug 2013 at
1400 UTC. I hope everyone can attend.
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode