docs August 2006

docs@lists.fedoraproject.org

30 participants
36 discussions

Self-Introduction: Magnus Larsson
by Magnus Larsson 29 Sep '06

29 Sep '06

Magnus Larsson Philadelphia, USA Work as a software engineer. I want to translate the Fedora tools into Swedish. Then write some of the guides if time permits. I have good computer skills but not really a technical writer. I know how the software works. pub 1024D/D86B89C9 2006-08-24 Key fingerprint = 70BE 9E32 0AEE 5216 B988 32C4 E2EC 3019 D86B 89C9 uid Magnus Larsson <fedoratrans(a)gmail.com > sub 2048g/246F9AF8 2006-08-24

2 1

Wiki freeze for DUG today
by Karsten Wade 30 Aug '06

30 Aug '06

We are going into a Wiki freeze for the DUG, in order to convert it to XML: http://fedoraproject.org/wiki/DocsProject/Schedule#guides-schedule I've left it open for a few days to catch any last minute help, and I'm going to do some work on the Wiki today before conversion. Freeze will be at 23:59 UTC today, but I reserve the right as editor to continue to do fixes in the Wiki before conversion. Once converted to XML, we are keeping the FC6 branch in XML in CVS forevermore. This is because Wiki -> XML is decompressing; once we further edit the XML, returning it to the Wiki is lossy and time consuming. Finally, we still consider XML the preferred format for working on full-length guides. - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

2 1

Overview bloat? (was [Fedora Project Wiki] Update of "Docs/Beats/Desktop" by RahulSundaram)
by Karsten Wade 30 Aug '06

30 Aug '06

> The following page has been changed by RahulSundaram: > http://fedoraproject.org/wiki/Docs/Beats/Desktop > + > + > + = Comment = > + > + Since the overview section covers the destkop already, do we need this section for FC6? > + Good question. My thoughts are like this ... 1. What does a user/reader do when coming to a massive release notes like this, with a comprehensive Tables of Contents? a. Look through the ToC for relevant items and go read them? b. Read the introduction/overview, and consider going deeper? Our current setup actually supports both, except that from the OverView, the reader is not directed to the relevant content areas. Instead, they get a comprehensive overview right there. Perhaps the OverView should say something brief, then link to more content? We faced this with FC5, where the OverView grew to be so big that it was repeating information stated elsewhere, which means it now had to be maintained twice. The OverView is starting to remind me of the old Fedora/RHEL release notes. One, long page with all the information in brief. Is it useful to have both styles supported? - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

3 3

man/XML
by SigmaX asdf 30 Aug '06

30 Aug '06

I discovered the following project availability on http://fedoraproject.org/wiki/FedoraBounties (I'm not expecting an official "bounty," just for the record): > Publication of all man and info pages for each release > We would like to have every man and info page for each release of Fedora Core and Extras to be available via a simple Web interface, > > One option would be a directory full of formatted ASCII files. Another would be a simple search interface or contents listing, with the directory on the back-end. > > One objective is to be able to browse manual pages of various releases. > > Another goal is to have permanent URIs for documentation and reference. > > Having a simple Web-based diff tool to see what was added/subtracted across versions would be cool too. > > This could be a relative or a tie-in to DocsRawhide. The man and info pages for Fedora rawhide could be made available through this method. > > In the future, I'd like to see this format extended to allow a Wiki-like ability to edit the man pages directly. > > See bug #179524: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179524 > > Contact: KarstenWade > Upon contacting Karsten Wade I was told: > Community members have been asking for "all the system documentation" > available online, outside of the actual install itself. > > I don't know of the man and info pages are translated, but by converting > them to XML, we can make them available for the community to translate. > > There has been a project proposed to the Linux Doc Project for a while > to convert man pages to XML, so this could be part of that idea, if we > wanted to carry it that far. > > ...We'd be looking for something > clever and automated; someone from the release team or docs team would > "press a button" (run a script), a tree of RPM packages would be > checked, and all the documentation extracted and converted into XML. > Anyway, that's just a first pass at an idea. So. Here I am. I admit a degree of ignorance, but claim spirit to learn and take a shot at a solution. First off: Is there already an XML template, or something related (ex. used in the translation project), which I should refer to in order to be sure things are done in Fedora style? Besides that I'm ready to start tinkering with it, in between my full class load and 23 work hours a week :-S. Cheerio, SigmaX

2 2

Self-Introduction: Eric Scott
by SigmaX asdf 30 Aug '06

30 Aug '06

Name: Eric O'Neal Scott (a.k.a. SigmaX) Location: Berrien Springs, Michigan, USA Profession: Student School: Andrews University Goals: I have the intent to work on the "Publication of all man and info pages for each release" announced at http://fedoraproject.org/wiki/FedoraBounties for the sake of gaining general experience. I'm a computer science major and see myself going into a related career, so any project I can find for education's sake will enhance that goal. Qualifications: I am a student. And as such I expect to learn more then I can give. That said, I have sufficient web design skills (See SigmaX.org), including some PHP and SQL knowledge. Three years or so of Linux/UNIX experience has yielded a reasonable level of proficiency. As far as programming, the most noteworthy project laboured at can be found at http://sigmax.no-ip.org/programming_cdurry.php I enjoy writing documentation, believe it or not. My website has a series of articles from the last few weeks, and I'm as easily entertained commenting my code as I am writing it. I journal and blog regularly to keep up the practice of conveying complicated ideas in relatively simple-to-fathom terms. SigmaX

1 0

test3 relnotes translation location
by Karsten Wade 29 Aug '06

29 Aug '06

We have had the release note's POT file put into the i18n.redhat.com CVS and translation system. This email is in support of A S Alam's. As we discussed last time, all translation for the release notes is now happening through that CVS. When it is done, we are going to *copy* the files from one CVS back to the other. If you are translating release notes, you need to: i. Merge any changes in your PO files from the cvs.fedoraproject.org/docs/cvs/release-notes/devel/po into the PO files on i18n.redhat.com. ii. Do all translation in i18n.redhat.com There have been very few changes; only four of the original XML files were updated between test2 and test3. This is good, because we are a few days late in making the PO files available, and we still need to respect the 02 September due date for translations: http://fedoraproject.org/wiki/DocsProject/Schedule Thanks again to Paul W. Frields and A S Alam. We're still doing too much manually, but we are improving incrementally with each test and release. - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

1 0

[translation]Release-notes FC6test3 POT available in CVS
by A S Alam 29 Aug '06

29 Aug '06

hi Teams Latest Release-notes POT available at i18n Server, please update your translate folder goto your translate folder $cd release-notes $cvs up and Merge your language with latest POT by following: $ msgmerge -o <NEW_NAME>.po <OLD_PO>.po RELEASE-NOTES.pot $mv <NEW_NAME>.po <OLD_PO>.po and commit your file to cvs for More details, please check at https://www.redhat.com/archives/fedora-trans-list/2006-July/msg00056.html Date for submission: 02 Sep 23:59 UTC more detail at http://fedoraproject.org/wiki/DocsProject/Schedule if have any question, please ask on mailing list or IRC channel thanks -- A S Alam timezone: GMT+5:30 join us at #fedora-l10n, #fedora-docs (freenode) "Either find a way or make one"

1 0

Salutations.
by Gain Paolo Mureddu 28 Aug '06

28 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Fedora Documentation list members. The purpose of this e-mail is only to introduce myself to the list. My name is Gian Paolo Mureddu, and I'm an avid Fedora user who would like to contribute in some way to our great community. I figured that doing so by documenting, reviewing, discussing and proposing to the documentation project would be one way to do it. I reckon that we in the Fedora community are missing a centralized source of Fedora-specific, Linux-in-general documentation, especially since a lot of users seem to be oblivious of the existence of www.fedoraproject.org/wiki I'll now run through the archives and read all there is to read to get started... So I guess that for now I have my hands full. Anyway, hello to all the Fedora Documentation Project members! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE8iigXM+XOp70dwoRAo2DAKCXFky7ewfaPXN1aBKF1OfGdpk0HwCgjLv4 0fEXBsJETxmIxXcAXirnkzw= =wflA -----END PGP SIGNATURE-----

3 2

Wiki editing refresher
by Karsten Wade 27 Aug '06

27 Aug '06

For all who are editing the DUG or Docs/Beats/, a quick reminder pointer: http://fedoraproject.org/wiki/WikiEditing#Marking_Technical_Terms http://fedoraproject.org/wiki/WikiEditing#Quick_Tips Especially note the first, Marking Technical Terms. There is a table there that is useful. The entire Quick Tips section is good to be familiar with. When it comes time to convert to XML, it is important to have standard usage from the Wiki. It also helps the final Wiki edit in preparation for the XML conversion. Thanks - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

3 2

ISO file burning how-to
by David Fletcher 26 Aug '06

26 Aug '06

When I wrote this:- http://fedoraproject.org/wiki/Docs/Drafts/BurningDiscs?highlight=%28burning… I thought the general agreement was to place a plain text version of it in the ISO files download folder. For FC5 it never happened, even though it was supposed to. See comment 25 of bug 178847. It would of course not be practical to put a read-me file in the same folder as the ISO files in all languages, but if only an English version was placed there as intended, it would be an enormous help. We still get messages posted by would-be Fedora users who have difficulties with the procedure I documented. I posted the above link into the wiki onto the Fedora list again this morning because its presence is anything but obvious. Also see comment 13 of the same bug. Will FC6 suck again? Dave Fletcher -- Registered Linux user number 393408

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs August 2006