From brent at fprimex.com Tue Nov 4 23:32:23 2003 From: brent at fprimex.com (fprimex) Date: Tue, 4 Nov 2003 18:32:23 -0500 Subject: Interested in volunteering Message-ID: <24188D08-0F1F-11D8-974D-000A958EFC64@fprimex.com> Hello, I'm interested in writing some documentation for Fedora. I'm not a professional technical writer, but I have written some employee manuals for the technical support at my university. I have also spent a considerable amount of time helping Linux users on IRC, which has lead me to write some guides in the past. At the present, there isn't a particular topic I would like to cover. I would simply like to help the project in some way. My time is too limited while I'm in graduate school to undertake any serious coding or bug fixing, but I want to contribute to the project and do what is needed. I've not used many of the tools listed on the project page, as most of my writing is done in LaTeX for my work. I can, however, learn quickly and am willing to do so. Please reply directly to me or include my address as a Cc, as I haven't subscribed to the fedora-docs-list yet. Thanks! Brent W. From Bruce.Martin at asp-networks.co.uk Thu Nov 6 12:52:53 2003 From: Bruce.Martin at asp-networks.co.uk (Bruce Martin) Date: Thu, 6 Nov 2003 12:52:53 -0000 Subject: Fedora Documentation Message-ID: Hi, I would like to volunteer my services as either an editor, or as a writer. I have been following the project with keen interest, and are very impressed with the outcome so far. If I can be of any assistance, please contact me. Kind regards, Bruce Bruce Martin Director ASP Network Solutions Limited http://www.asp-networks.co.uk From tfox at redhat.com Thu Nov 6 16:34:24 2003 From: tfox at redhat.com (Tammy Fox) Date: Thu, 6 Nov 2003 11:34:24 -0500 Subject: Loving Fedora In-Reply-To: <3F91704A.7050107@diazcalvo.com> References: <3F91704A.7050107@diazcalvo.com> Message-ID: <20031106163424.GD13868@redhat.com> On Sat, Oct 18, 2003 at 05:54:34PM +0100, hector wrote: > Hi there, > > just installed fedora looking for ACPI support to power off my computer. > Got it with little work but also really surprised with the core system. > It's run much faster in my machine than rh9 and feel the graphics look > better. > Well, i'm a newbie buy i'm here to learn. I'm gonna start with the > documentation guide and try emacs. I'd like to help with the documentation. > I need some time but hope soon can help with translations (to spanish). > Great. If you need any help with getting your environment setup, let us know. Also, if you can think of anything that needs to be added to the documentation guide, let me know. > The redhat-config-package can't read the cdrom, does someone knows about it? > Are you seeing the same problem as discussed in: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=105767 I was seeing this before as well. I haven't tested it with the latest version of redhat-config-packages yet. According to the bug report, version 1.2.6 of redhat-config-packages fixes the problem. > Enjoy fedora > > hector > > Cheers, Tammy From tfox at redhat.com Thu Nov 6 16:39:27 2003 From: tfox at redhat.com (Tammy Fox) Date: Thu, 6 Nov 2003 11:39:27 -0500 Subject: Interested in volunteering In-Reply-To: <24188D08-0F1F-11D8-974D-000A958EFC64@fprimex.com> References: <24188D08-0F1F-11D8-974D-000A958EFC64@fprimex.com> Message-ID: <20031106163926.GE13868@redhat.com> Hi Brent, We would love for you to participate in the docs project. Most people's time is limited, especially those who are writing on a volunteer basis. That is one of the reasons I chose tutorials as the format. The term implies small or medium documents on specific topics. I tell everyone to draw on their experiences and knowledge. It is usually easier to write about a topic you are familiar. Are there any tasks that you recently figured out that you would like to share in a tutorial? Tammy On Tue, Nov 04, 2003 at 06:32:23PM -0500, fprimex wrote: > Hello, > > I'm interested in writing some documentation for Fedora. I'm not a > professional technical writer, but I have written some employee manuals > for the technical support at my university. I have also spent a > considerable amount of time helping Linux users on IRC, which has lead > me to write some guides in the past. > > At the present, there isn't a particular topic I would like to cover. > I would simply like to help the project in some way. My time is too > limited while I'm in graduate school to undertake any serious coding or > bug fixing, but I want to contribute to the project and do what is > needed. > > I've not used many of the tools listed on the project page, as most of > my writing is done in LaTeX for my work. I can, however, learn quickly > and am willing to do so. > > Please reply directly to me or include my address as a Cc, as I haven't > subscribed to the fedora-docs-list yet. > > Thanks! > > Brent W. > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From tfox at redhat.com Thu Nov 6 16:40:10 2003 From: tfox at redhat.com (Tammy Fox) Date: Thu, 6 Nov 2003 11:40:10 -0500 Subject: Fedora Documentation In-Reply-To: References: Message-ID: <20031106164009.GF13868@redhat.com> Great. We need writers right now more than editors because we need something to editor first. ;-) Do you have any topics in mind? Tammy On Thu, Nov 06, 2003 at 12:52:53PM -0000, Bruce Martin wrote: > Hi, > > I would like to volunteer my services as either an editor, or as a > writer. > > I have been following the project with keen interest, and are very > impressed with the outcome so far. > > If I can be of any assistance, please contact me. > > > > Kind regards, > > > Bruce > > > > Bruce Martin > Director > > ASP Network Solutions Limited > http://www.asp-networks.co.uk > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From christian.huegel at redhatforum.net Thu Nov 6 15:28:26 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Thu, 6 Nov 2003 16:28:26 +0100 Subject: Logo Font Message-ID: <200311061528.hA6FSQFX000449@webmailer.hosteurope.de> Is there a possibility to provide the modified Myriad bold italic font. I\'m askin because i set up a forum for the german community and i want to re-design the layout for the page so it fits into the fedora project design. The forum can be reached under http://www.redhatforum.net or http://www.fedoraforum.de Thx in advance From dpawson at nildram.co.uk Thu Nov 6 17:00:06 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Thu, 06 Nov 2003 17:00:06 +0000 Subject: Fedora Documentation In-Reply-To: <20031106164009.GF13868@redhat.com> References: <20031106164009.GF13868@redhat.com> Message-ID: <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> At 16:40 06/11/2003, Tammy Fox wrote: >Great. We need writers right now more than editors Hi Tammy. I subscribed to the (rather hi volume) fedora list, as well as this one. Getting irked by the esotericism's I volunteered to start (asking) then scraping some of the jargon together. I'll feed it here /to you when its worthwhile? I think docbook is preferred? Article as wrapper OK? If/when I get it installed, I'll start to add comments to existent documentation / volunteer for new, perhaps with help. I'm no guru, but I've been around for a while. regards DaveP www.dpawson.co.uk/docbook From tfox at redhat.com Thu Nov 6 17:31:48 2003 From: tfox at redhat.com (Tammy Fox) Date: Thu, 6 Nov 2003 12:31:48 -0500 Subject: Fedora Documentation In-Reply-To: <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> References: <20031106164009.GF13868@redhat.com> <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> Message-ID: <20031106173147.GG13868@redhat.com> On Thu, Nov 06, 2003 at 05:00:06PM +0000, Dave Pawson wrote: > At 16:40 06/11/2003, Tammy Fox wrote: > >Great. We need writers right now more than editors > > Hi Tammy. > I subscribed to the (rather hi volume) fedora list, > as well as this one. > > Getting irked by the esotericism's I volunteered to start > (asking) then scraping some of the jargon together. > > I'll feed it here /to you when its worthwhile? > Yes. That sounds fine. > I think docbook is preferred? > Article as wrapper OK? > In the fedora-docs module, there is a directory called example-tutorial with a basic example file to get you started. It is in DocBook article format. > If/when I get it installed, I'll start to add comments > to existent documentation / volunteer for new, perhaps with help. > > I'm no guru, but I've been around for a while. > > regards DaveP > www.dpawson.co.uk/docbook > > Thanks, Tammy From gtroberts at gtroberts.org Thu Nov 6 18:09:03 2003 From: gtroberts at gtroberts.org (Gary Travis Roberts) Date: Thu, 6 Nov 2003 11:09:03 -0700 Subject: Interested in volunteering In-Reply-To: <20031106163926.GE13868@redhat.com> Message-ID: <200311061809.hA6I95809000@gtroberts.org> I would be interested in volunteering to write some documentation. I could do a tutorial on setting up a firewall and also on setting up networking both with a network card and through an ISP. I am proficient at emacs and have been using Redhat since the 0.9x series kernels. I work as a network admin (for over 8 years) over many different styles of Unix. Redhat, though, is by far most used in-house. Let me know where I can get templates and I will starting running. -Gary Roberts From kwade at redhat.com Thu Nov 6 19:16:24 2003 From: kwade at redhat.com (Karsten Wade) Date: 06 Nov 2003 11:16:24 -0800 Subject: Interested in volunteering In-Reply-To: <200311061809.hA6I95809000@gtroberts.org> References: <200311061809.hA6I95809000@gtroberts.org> Message-ID: <1068146184.5785.197.camel@erato.phig.org> On Thu, 2003-11-06 at 10:09, Gary Travis Roberts wrote: > I would be interested in volunteering to write some documentation. I could > do a tutorial on setting up a firewall and also on setting up networking > both with a network card and through an ISP. > > I am proficient at emacs and have been using Redhat since the 0.9x series > kernels. I work as a network admin (for over 8 years) over many different > styles of Unix. Redhat, though, is by far most used in-house. > > Let me know where I can get templates and I will starting running. Hi Gary, welcome. http://fedora.redhat.com/projects/docs/ has details about getting the Doc Guide via anonymous CVS. The checkout includes a tutorial template, example-tutorial/. It's all very pretty. There are a few bugs with the documentation as it stands (e.g. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104983). hth - Karsten > > -Gary Roberts > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From gsorian at kapax.com.mx Thu Nov 6 22:04:04 2003 From: gsorian at kapax.com.mx ([KAPAX] Guillermo Soria) Date: Thu, 6 Nov 2003 16:04:04 -0600 Subject: Fedora Documentation In-Reply-To: <20031106173147.GG13868@redhat.com> References: <20031106164009.GF13868@redhat.com> <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> <20031106173147.GG13868@redhat.com> Message-ID: <20031106215429.M18012@kapax.com.mx> I'm newbie in this kind of projects, but I'm interested in translate to spanish the fedora docs -ready signed translator-. So, what's the steps to start with it... ----------------------------- Soria-Ni?o, Guillermo KAPAX Information Solutions http://www.kapax.com.mx ----------------------------- From tfox at redhat.com Thu Nov 6 22:21:34 2003 From: tfox at redhat.com (Tammy Fox) Date: Thu, 6 Nov 2003 17:21:34 -0500 Subject: Fedora Documentation In-Reply-To: <20031106215429.M18012@kapax.com.mx> References: <20031106164009.GF13868@redhat.com> <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> <20031106173147.GG13868@redhat.com> <20031106215429.M18012@kapax.com.mx> Message-ID: <20031106222134.GL13868@redhat.com> We are waiting for the translation project leads to setup the XML to PO and PO to XML conversion scripts. Cheers, Tammy On Thu, Nov 06, 2003 at 04:04:04PM -0600, [KAPAX] Guillermo Soria wrote: > I'm newbie in this kind of projects, but I'm interested in translate to > spanish the fedora docs -ready signed translator-. > > So, what's the steps to start with it... > > ----------------------------- > Soria-Ni?o, Guillermo > KAPAX Information Solutions > http://www.kapax.com.mx > ----------------------------- > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list From christian.huegel at redhatforum.net Fri Nov 7 12:23:06 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Fri, 7 Nov 2003 13:23:06 +0100 Subject: Volunteer Message-ID: <200311071223.hA7CN6r7021432@webmailer.hosteurope.de> I would like to volunteer as a translator or as a editor/writer. If you have any questions please contact me. I would start writing a tutorial regarding the installation of a ssh Server with public/private key authentification. If this is ok please drop me a note. Best regards Christian From tfox at redhat.com Fri Nov 7 17:59:46 2003 From: tfox at redhat.com (Tammy Fox) Date: Fri, 7 Nov 2003 12:59:46 -0500 Subject: Volunteer In-Reply-To: <200311071223.hA7CN6r7021432@webmailer.hosteurope.de> References: <200311071223.hA7CN6r7021432@webmailer.hosteurope.de> Message-ID: <20031107175946.GG19248@redhat.com> The priority is for writers right now since we need content for the editors to edit and the translators to translate. Of course, if you could translate your own tutorials, that would be great. What languages can you translated into? Your idea for a tutorial on the installation of an SSH server with public/private key authentication is fine. Instructions for checking out the DocBook XML templates are in the Documentation Guide. Let me know if you have any questions, Tammy On Fri, Nov 07, 2003 at 01:23:06PM +0100, christian.huegel wrote: > I would like to volunteer as a translator or as a editor/writer. If you have any questions please contact me. I would start writing a tutorial regarding the installation of a ssh Server with public/private key authentification. If this is ok please drop me a note. > Best regards Christian From jike at allyes.com Fri Nov 7 03:59:53 2003 From: jike at allyes.com (jike) Date: Fri, 7 Nov 2003 11:59:53 +0800 Subject: Fedora Documentation Message-ID: <200311070356.hA73un722958@adf141.allyes.com> hi,all I am interested in translating the docs to Chinese, How can i do it. Best regards Jike Zhou (RHCE) >I'm newbie in this kind of projects, but I'm interested in translate to >spanish the fedora docs -ready signed translator-. > >So, what's the steps to start with it... > >----------------------------- >Soria-Ni?o, Guillermo >KAPAX Information Solutions >http://www.kapax.com.mx >----------------------------- > > >-- >fedora-docs-list mailing list >fedora-docs-list at redhat.com >http://www.redhat.com/mailman/listinfo/fedora-docs-list = = = = = = = = = = = = = = = = = = = = ?????????????????? ???? ????????????????jike ????????????????jike at allyes.com ????????????????????2003-11-07 From christian.huegel at redhatforum.net Fri Nov 7 08:12:16 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Fri, 7 Nov 2003 09:12:16 +0100 Subject: Volunteer Message-ID: <200311070812.hA78CGHn010045@webmailer.hosteurope.de> I would like to volunteer as a translator or as a editor/writer. If you have any questions please contact me. I would start writing a tutorial regarding the installation of a ssh Server with public/private key authentification. If this is ok please drop me a note. Best regards Christian From bhankins at micahtek.com Fri Nov 7 21:03:29 2003 From: bhankins at micahtek.com (Brian Hankins) Date: Fri, 07 Nov 2003 15:03:29 -0600 Subject: Volunteer In-Reply-To: <20031107175946.GG19248@redhat.com> References: <200311071223.hA7CN6r7021432@webmailer.hosteurope.de> <20031107175946.GG19248@redhat.com> Message-ID: <1068239009.28940.34.camel@bhankins> On Fri, 2003-11-07 at 11:59, Tammy Fox wrote: > The priority is for writers right now since we need content for the > editors to edit and the translators to translate. Of course, if you > could translate your own tutorials, that would be great. What > languages can you translated into? > > Your idea for a tutorial on the installation of an SSH server with > public/private key authentication is fine. Instructions for checking > out the DocBook XML templates are in the Documentation Guide. > > Let me know if you have any questions, > Tammy > > On Fri, Nov 07, 2003 at 01:23:06PM +0100, christian.huegel wrote: > > I would like to volunteer as a translator or as a editor/writer. If you have any questions please contact me. I would start writing a tutorial regarding the installation of a ssh Server with public/private key authentification. If this is ok please drop me a note. > > Best regards Christian > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list I will go ahead and try my hand at writing tutorials also. I have two or three previously written tutorials, that would be nice to try and adapt to be Fedora specific. This would give me a chance to look into learning the document tools from the guide as well. I might try to tackle the "Configuring and using digital cameras" tutorial also, however I only have one camera, so the first revision might be more or less pretty specific. Well I look forward to helping out. -- Brian H. From chinoh81 at hotmail.com Sat Nov 8 08:45:16 2003 From: chinoh81 at hotmail.com (Jorge Hirahoka) Date: Sat, 08 Nov 2003 08:45:16 +0000 Subject: What's next? Message-ID: Hi everybody: I would like to make translations to spanish. I already signed up as a translator, I received the autoreply e-mail. But now I'm stuck. What do I have to do next? I'm a newbie at this so I'm kinda lost. Jorge Luis Hirahoka (ChinoH81) _________________________________________________________________ Charla con tus amigos en l?nea mediante MSN Messenger: http://messenger.yupimsn.com/ From christian.huegel at redhatforum.net Sat Nov 8 11:47:43 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Sat, 8 Nov 2003 12:47:43 +0100 Subject: Volunteer Message-ID: <200311081147.hA8BlhsM014887@webmailer.hosteurope.de> Hi Tammy, I can translate it into german or romanian. About the DocBook XML Templates: i have the same problem described in previous threads with the printable format..HTML-one-file. However, i will start writing ... Cheers Christian From dpawson at nildram.co.uk Sat Nov 8 17:03:17 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Sat, 08 Nov 2003 17:03:17 +0000 Subject: Fedora Documentation In-Reply-To: <20031106222134.GL13868@redhat.com> References: <20031106164009.GF13868@redhat.com> <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> <20031106173147.GG13868@redhat.com> <20031106215429.M18012@kapax.com.mx> <20031106222134.GL13868@redhat.com> Message-ID: <6.0.0.22.2.20031108170247.025d13c8@pop3.Nildram.co.uk> At 22:21 06/11/2003, Tammy Fox wrote: >We are waiting for the translation project leads to setup the XML to >PO and PO to XML conversion scripts. More Jargon Tammy? PO please? regards DaveP From dpawson at nildram.co.uk Sat Nov 8 17:08:05 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Sat, 08 Nov 2003 17:08:05 +0000 Subject: Volunteer In-Reply-To: <1068239009.28940.34.camel@bhankins> References: <200311071223.hA7CN6r7021432@webmailer.hosteurope.de> <20031107175946.GG19248@redhat.com> <1068239009.28940.34.camel@bhankins> Message-ID: <6.0.0.22.2.20031108170641.02582558@pop3.Nildram.co.uk> At 21:03 07/11/2003, Brian Hankins wrote: >to be Fedora specific. This would give me a chance to look into learning >the document tools from the guide as well. I might try to tackle the >"Configuring and using digital cameras" tutorial also, however I only >have one camera, so the first revision might be more or less pretty >specific. I might be able to help out there, I'm a Canon user, OK with docbook and authoring. Perhaps we could work out something between us? regards DaveP From gsorian at kapax.com.mx Sat Nov 8 17:31:05 2003 From: gsorian at kapax.com.mx ([KAPAX] Guillermo Soria) Date: Sat, 8 Nov 2003 11:31:05 -0600 Subject: Fedora Documentation In-Reply-To: <6.0.0.22.2.20031108170247.025d13c8@pop3.Nildram.co.uk> References: <20031106164009.GF13868@redhat.com> <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> <20031106173147.GG13868@redhat.com> <20031106215429.M18012@kapax.com.mx> <20031106222134.GL13868@redhat.com> <6.0.0.22.2.20031108170247.025d13c8@pop3.Nildram.co.uk> Message-ID: <20031108172705.M80033@kapax.com.mx> I found some info -link- on Gnome list, about a PO discuss, and a documentation in spanish talking about the use of translate techs... El articulo que viene adjunto a la liga, puede ayudar a aclarar el uso de archivos .PO, para quienes esten interesados http://lists.gnome.org/archives/gnome-i18n/2003-September/msg00292.html ...saludos -greets-. ----------------------------- Soria-Ni?o, Guillermo KAPAX Information Solutions http://www.kapax.com.mx ----------------------------- > At 22:21 06/11/2003, Tammy Fox wrote: > >We are waiting for the translation project leads to setup the XML to > >PO and PO to XML conversion scripts. > > More Jargon Tammy? > > PO please? > > regards DaveP > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list ------- End of Original Message ------- From luis.licon at cimav.edu.mx Mon Nov 10 17:00:22 2003 From: luis.licon at cimav.edu.mx (luis.licon at cimav.edu.mx) Date: Mon, 10 Nov 2003 10:00:22 -0700 (MST) Subject: Translation Message-ID: <49649.148.223.46.10.1068483622.squirrel@www3.cimav.edu.mx> Hi, I would like to participate on this with you guys, I can contribute translating documents to spanish, hope my help is needed. Luis From tfox at redhat.com Mon Nov 10 20:43:54 2003 From: tfox at redhat.com (Tammy Fox) Date: Mon, 10 Nov 2003 15:43:54 -0500 Subject: What's next? In-Reply-To: References: Message-ID: <20031110204353.GN2385@redhat.com> Where did you sign up? Did you sign up for software translations? That is the only type of translations we have a process in place for right now. Are you familiar with the PO translation format? That is what we use for all translations, software and documentation. Sorry there aren't any docs on the translations process yet. The RH translation team is always overbooked. Tammy On Sat, Nov 08, 2003 at 08:45:16AM +0000, Jorge Hirahoka wrote: > Hi everybody: > > I would like to make translations to spanish. I already signed up as a > translator, I received the autoreply e-mail. But now I'm stuck. What do I > have to do next? I'm a newbie at this so I'm kinda lost. > > Jorge Luis Hirahoka (ChinoH81) > > _________________________________________________________________ > Charla con tus amigos en l?nea mediante MSN Messenger: > http://messenger.yupimsn.com/ > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list From tfox at redhat.com Mon Nov 10 20:51:56 2003 From: tfox at redhat.com (Tammy Fox) Date: Mon, 10 Nov 2003 15:51:56 -0500 Subject: Fedora Documentation In-Reply-To: <6.0.0.22.2.20031108170247.025d13c8@pop3.Nildram.co.uk> References: <20031106164009.GF13868@redhat.com> <6.0.0.22.2.20031106165601.025f6208@pop3.Nildram.co.uk> <20031106173147.GG13868@redhat.com> <20031106215429.M18012@kapax.com.mx> <20031106222134.GL13868@redhat.com> <6.0.0.22.2.20031108170247.025d13c8@pop3.Nildram.co.uk> Message-ID: <20031110205156.GP2385@redhat.com> On Sat, Nov 08, 2003 at 05:03:17PM +0000, Dave Pawson wrote: > At 22:21 06/11/2003, Tammy Fox wrote: > >We are waiting for the translation project leads to setup the XML to > >PO and PO to XML conversion scripts. > > More Jargon Tammy? > > PO please? > ;-) I'll add it to your jargon doc and get it posted on the website by the end of the week. Tammy > regards DaveP > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list From christian.huegel at redhatforum.net Wed Nov 12 12:19:53 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Wed, 12 Nov 2003 13:19:53 +0100 Subject: Further toughts Message-ID: <200311121219.hACCJrws004325@webmailer.hosteurope.de> In the future i suggest to create teams for each country they make translation for. I think this way the things are better coordinated. What you mean? An example what i mean is here: http://i18n.kde.org/teams/ Does this make sense? Greetz Christian From thorsten at mandrakeuser.de Wed Nov 12 19:33:54 2003 From: thorsten at mandrakeuser.de (Thorsten von Plotho-Kettner) Date: Wed, 12 Nov 2003 20:33:54 +0100 Subject: German users in this list? Message-ID: <200311122033.54186.thorsten@mandrakeuser.de> Hi, any german users here interested in german translations or guides? Regards, Thorsten From georg at georgs.org Wed Nov 12 18:41:14 2003 From: georg at georgs.org (Georg E Schneider) Date: Wed, 12 Nov 2003 19:41:14 +0100 Subject: German users in this list? In-Reply-To: <200311122033.54186.thorsten@mandrakeuser.de> References: <200311122033.54186.thorsten@mandrakeuser.de> Message-ID: <3FB27ECA.9030700@georgs.org> Thorsten von Plotho-Kettner schrieb: >Hi, > >any german users here interested in german translations or guides? > >Regards, >Thorsten > > >-- >fedora-docs-list mailing list >fedora-docs-list at redhat.com >http://www.redhat.com/mailman/listinfo/fedora-docs-list > > > > I'm not german I'm austrian german-speaking/writing = yes > ...Interested in german translations or guides? = yes germann/at ! From christian.huegel at redhatforum.net Wed Nov 12 20:50:21 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Wed, 12 Nov 2003 21:50:21 +0100 Subject: German users in this list? Message-ID: <200311122050.hACKoLMs026918@webmailer.hosteurope.de> I am one and started to translate some docs. For infos and questions please contact me. You can view the status of the translations at: http://www.stonebyte.de/dokus.php Greetz Christian From kwade at redhat.com Wed Nov 12 21:44:18 2003 From: kwade at redhat.com (Karsten Wade) Date: 12 Nov 2003 13:44:18 -0800 Subject: Fedora Docs FAQ - proposal, draft Message-ID: <1068673457.2866.967.camel@erato.phig.org> All: It looks like we have some regular questions on this list. If we can gather together some questions and answers, perhaps Tammy can post a FAQ on fedora.redhat.com, and/or we can include the FAQ in the Mailman "Welcome" email. I'm happy to maintain it for now. Below is what I've thought of so far. Let's use this thread to gather the questions and answers. These are my proposed answers, please feel free to "fix" them: ## begin FAQ (draft) ## Does Fedora Project need writers/editors? Yes! Writers are needed right now more then editors, until we have something to edit. What documents does FP need? FP documents are going to be of the tutorial/HOWTO variety. This is the most useful information we can gather at this time, and it works well with the distributed project. In the future, if small teams want to work on larger works similar to the manuals for Red Hat products, we can work on adding that in. How is the docs project organized? Rather loosely right now. Tammy Fox (tfox at redhat.com) is the project leader. It has been proposed that translators can work in teams by languages. We may want to organize so that every writer has two-editors, and contributors can work in either or both roles. This makes for a more cumbersome process, but the quality control is higher. What is the process/procedure for translating documents? There is currently no defined process. We are waiting for the participation of the ever-busy Red Hat docs translation team. What are PO files? PO files are textual, editable files used in translation. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC7 What are some of the tutorial/HOWTOs currently proposed? From the mailing list: * Installing an SSH server with public/private key authentication * Configuring and using digital cameras Can I translate the legal notice? The legal notice page can be translated, but a statement that the translation is provided for convenience only and that the English language version takes precedence must be on the top of the page. What are the tools for writing documents? http://fedora.redhat.com/projects/docs details how to get the Documentation Guide source and tools. The toolchain is explained on that page, with the exception of PO files (see What are PO files?). Currently, there is a problem with PDF production (refer to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104983). If you have TeX experience and can help us resolve that one, please dive in! I have a tutorial in HTML, how do I convert it to DocBook? Grab html2db from http://www.cise.ufl.edu/~ppadala/tidy/ . What are some resources for learning DocBook? The definitive DocBook reference written and maintained by Norm Walsh is available at http://docbook.org/tdg/en/html/docbook.html . A combination tutorial and reference book is available at http://www.sagehill.net/docbookxsl/index.html Can I have CVS write access? Eventually, we intend for full contributors to have write access to CVS, as well as access to other build environments. This is being worked out across the entire Fedora Project. In the meantime, you can contact the docs project leader Tammy Fox (tfox at redhat.com) with your changes. What else is can I do to help? Have ideas for admonition graphics? ## 30 ## -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From christian.huegel at redhatforum.net Wed Nov 12 18:45:55 2003 From: christian.huegel at redhatforum.net (Christian Huegel) Date: Wed, 12 Nov 2003 19:45:55 +0100 Subject: German users in this list? In-Reply-To: <200311122033.54186.thorsten@mandrakeuser.de> References: <200311122033.54186.thorsten@mandrakeuser.de> Message-ID: <1068662755.21934.1.camel@mini001.webpack.hosteurope.de> On Wed, 2003-11-12 at 20:33, Thorsten von Plotho-Kettner wrote: > Hi, > > any german users here interested in german translations or guides? > > Regards, > Thorsten > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list > Hi Thorsten, i have allready started stranslations. You can check this at www.stonebyte.de out Greetz Christian From thorsten at mandrakeuser.de Wed Nov 12 18:56:12 2003 From: thorsten at mandrakeuser.de (Thorsten von Plotho-Kettner) Date: Wed, 12 Nov 2003 19:56:12 +0100 Subject: German users in this list? In-Reply-To: <3FB27ECA.9030700@georgs.org> References: <200311122033.54186.thorsten@mandrakeuser.de> <3FB27ECA.9030700@georgs.org> Message-ID: <200311121956.12189.thorsten@mandrakeuser.de> Hi, Am Mittwoch, 12. November 2003 19:41 schrieb Georg E Schneider: > Thorsten von Plotho-Kettner schrieb: > >any german users here interested in german translations or guides? > I'm not german I'm austrian > german-speaking/writing = yes > > ...Interested in german translations or guides? = yes > > germann/at ! I am sorry for that fault ;) Thorsten From christian.huegel at redhatforum.net Thu Nov 13 08:51:58 2003 From: christian.huegel at redhatforum.net (christian.huegel) Date: Thu, 13 Nov 2003 09:51:58 +0100 Subject: Sorry Message-ID: <200311130851.hAD8pwC1024485@webmailer.hosteurope.de> All: Sorry for my double postings. I had recently problems with my mailserver and i hope this doesn`t occur anymore. Best regards Christian From thorsten at mandrakeuser.de Thu Nov 13 13:48:46 2003 From: thorsten at mandrakeuser.de (Thorsten von Plotho-Kettner) Date: Thu, 13 Nov 2003 14:48:46 +0100 Subject: German users in this list? In-Reply-To: <200311122050.hACKoLMs026918@webmailer.hosteurope.de> References: <200311122050.hACKoLMs026918@webmailer.hosteurope.de> Message-ID: <200311131448.46557.thorsten@mandrakeuser.de> Hi, Am Mittwoch, 12. November 2003 21:50 schrieb christian.huegel: > I am one and started to translate some docs. > For infos and questions please contact me. > You can view the status of the translations at: > http://www.stonebyte.de/dokus.php there should be a central point to coordinate translations, maybe a forum or a wiki. A place, in short, to meet translators, find people for translation-projects and to reach no double-work. Thorsten From kwade at redhat.com Thu Nov 13 18:34:51 2003 From: kwade at redhat.com (Karsten Wade) Date: 13 Nov 2003 10:34:51 -0800 Subject: German users in this list? In-Reply-To: <200311131448.46557.thorsten@mandrakeuser.de> References: <200311122050.hACKoLMs026918@webmailer.hosteurope.de> <200311131448.46557.thorsten@mandrakeuser.de> Message-ID: <1068748490.17465.16.camel@erato.phig.org> On Thu, 2003-11-13 at 05:48, Thorsten von Plotho-Kettner wrote: > Hi, > > Am Mittwoch, 12. November 2003 21:50 schrieb christian.huegel: > > I am one and started to translate some docs. > > For infos and questions please contact me. > > You can view the status of the translations at: > > http://www.stonebyte.de/dokus.php > > there should be a central point to coordinate translations, maybe > a forum or a wiki. A place, in short, to meet translators, find people for > translation-projects and to reach no double-work. In general, that's what this mailing list is for. If we recreate that function outside of here, we risk splitting our knowledge and having double-work occur. However, it's true we are without a repository that contributors can share (CVS). While that's being worked on -- and it _is_ being worked on :) -- perhaps translators can follow a plan like this, with as much of the conversation happening on-list for the benefit of all: 1. Meet on this list, organize by language 2. Pick what to translate, divide the work 3. Coordinate using personal resources such as Christian has at stonebyte.de, with discussions happening on-list as much as possible. 4. If possible, keep work in CVS for possible later integration into Fedora Project CVS Does this sound reasonable? - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From tfox at redhat.com Thu Nov 13 19:06:59 2003 From: tfox at redhat.com (Tammy Fox) Date: Thu, 13 Nov 2003 14:06:59 -0500 Subject: Fedora Docs FAQ - proposal, draft In-Reply-To: <1068673457.2866.967.camel@erato.phig.org> References: <1068673457.2866.967.camel@erato.phig.org> Message-ID: <20031113190658.GH18027@redhat.com> Thanks for starting this FAQ. On Wed, Nov 12, 2003 at 01:44:18PM -0800, Karsten Wade wrote: > All: > > It looks like we have some regular questions on this list. If we can > gather together some questions and answers, perhaps Tammy can post a FAQ > on fedora.redhat.com, and/or we can include the FAQ in the Mailman > "Welcome" email. I'm happy to maintain it for now. > > Below is what I've thought of so far. Let's use this thread to gather > the questions and answers. These are my proposed answers, please feel > free to "fix" them: > > ## begin FAQ (draft) ## > > Does Fedora Project need writers/editors? > > Yes! Writers are needed right now more then editors, until we have > something to edit. > > > What documents does FP need? > > FP documents are going to be of the tutorial/HOWTO variety. This is > the most useful information we can gather at this time, and it works > well with the distributed project. > > In the future, if small teams want to work on larger works similar > to the manuals for Red Hat products, we can work on adding that in. > > I would rather stick to tutorials with the exception of the Installation Guide for now. > How is the docs project organized? > > Rather loosely right now. Tammy Fox (tfox at redhat.com) is the > project leader. It has been proposed that translators can work in > teams by languages. > > We may want to organize so that every writer has two-editors, and > contributors can work in either or both roles. This makes for a > more cumbersome process, but the quality control is higher. > > > What is the process/procedure for translating documents? > > There is currently no defined process. We are waiting for the > participation of the ever-busy Red Hat docs translation team. > > > What are PO files? > > PO files are textual, editable files used in translation. > http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC7 > > > What are some of the tutorial/HOWTOs currently proposed? > > From the mailing list: > > * Installing an SSH server with public/private key authentication > * Configuring and using digital cameras > > I have a bigger list I will send out shortly. > Can I translate the legal notice? > > The legal notice page can be translated, but a statement that the > translation is provided for convenience only and that the English > language version takes precedence must be on the top of the page. > > > What are the tools for writing documents? > > http://fedora.redhat.com/projects/docs details how to get the > Documentation Guide source and tools. The toolchain is explained on > that page, with the exception of PO files (see What are PO files?). > > Currently, there is a problem with PDF production (refer to > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104983). If > you have TeX experience and can help us resolve that one, please > dive in! > > > I have a tutorial in HTML, how do I convert it to DocBook? > > Grab html2db from http://www.cise.ufl.edu/~ppadala/tidy/ . > > > What are some resources for learning DocBook? > > The definitive DocBook reference written and maintained by Norm > Walsh is available at http://docbook.org/tdg/en/html/docbook.html . > > A combination tutorial and reference book is available at > http://www.sagehill.net/docbookxsl/index.html > > > Can I have CVS write access? > > Eventually, we intend for full contributors to have write access to > CVS, as well as access to other build environments. This is being > worked out across the entire Fedora Project. In the meantime, you > can contact the docs project leader Tammy Fox (tfox at redhat.com) with > your changes. > > > What else is can I do to help? > > Have ideas for admonition graphics? > > ## 30 ## > -- > Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 > kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 > Red Hat Enterprise Applications : WAF, CMS, Portal Server > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list From thorsten at mandrakeuser.de Thu Nov 13 20:11:26 2003 From: thorsten at mandrakeuser.de (Thorsten von Plotho-Kettner) Date: Thu, 13 Nov 2003 21:11:26 +0100 Subject: German users in this list? In-Reply-To: <1068748490.17465.16.camel@erato.phig.org> References: <200311122050.hACKoLMs026918@webmailer.hosteurope.de> <200311131448.46557.thorsten@mandrakeuser.de> <1068748490.17465.16.camel@erato.phig.org> Message-ID: <200311132111.26584.thorsten@mandrakeuser.de> Hi Karsten. Am Donnerstag, 13. November 2003 19:34 schrieb Karsten Wade: > On Thu, 2003-11-13 at 05:48, Thorsten von Plotho-Kettner wrote: > > Am Mittwoch, 12. November 2003 21:50 schrieb christian.huegel: > > > I am one and started to translate some docs. > > > For infos and questions please contact me. > > > You can view the status of the translations at: > > > http://www.stonebyte.de/dokus.php > > there should be a central point to coordinate translations, maybe > > a forum or a wiki. A place, in short, to meet translators, find people > > for translation-projects and to reach no double-work. > In general, that's what this mailing list is for. If we recreate that > function outside of here, we risk splitting our knowledge and having > double-work occur. But for some german translators a general meeting-point is a good idea, I think. Or they should write, if this would be no problem, in their language here in Any the opion of the listusers? Maybe also a wiki for fixing ideas out of the list is a possible idea. Lists are fluid. > However, it's true we are without a repository that contributors can > share (CVS). While that's being worked on -- and it _is_ being worked > on :) -- perhaps translators can follow a plan like this, with as much > of the conversation happening on-list for the benefit of all: > 1. Meet on this list, organize by language Okay. Ans then? Private lists or CC:? > 2. Pick what to translate, divide the work And mark it "in progress" for the list. > 3. Coordinate using personal resources such as Christian has at > stonebyte.de, with discussions happening on-list as much as possible. Okay. > 4. If possible, keep work in CVS for possible later integration into > Fedora Project CVS Fine. > Does this sound reasonable? Sounds okay for me, but only the thing with the language is tumbeling around my head. Regards, Thorsten From deryck at devurandom.org Thu Nov 13 20:48:08 2003 From: deryck at devurandom.org (Deryck Hodge) Date: Thu, 13 Nov 2003 14:48:08 -0600 Subject: Newbie Participation In-Reply-To: <1068748490.17465.16.camel@erato.phig.org> References: <200311122050.hACKoLMs026918@webmailer.hosteurope.de> <200311131448.46557.thorsten@mandrakeuser.de> <1068748490.17465.16.camel@erato.phig.org> Message-ID: <3FB3EE08.5060804@devurandom.org> Hi, all. I'm new to the list. Just upgraded my Red Hat 9 to Fedora a couple days ago. I'm new to linux as well -- I only loaded Red Hat just over two months ago. I would like to get involved if possible. I'm a writer, not a developer. My education is liberal arts--a few courses in tech/professional editing, as well as some small experience--but I have this thing for technology. (Don't we all?) My strengths would definitely be editing, proofreading, etc. since my knowledge about linux only goes so deep. Is there a way for me to get involved? Or does the list require more technical expertise to participate? --Deryck Hodge ---------------------------------- "Inside my head's a box of stars I never dared to open" --Sting http://www.devurandom.org From hugo at devin.com.br Thu Nov 13 22:14:07 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Thu, 13 Nov 2003 19:14:07 -0300 Subject: Translations in this list? Message-ID: <3FB4022F.7090100@devin.com.br> Hi, I subscribed to this list after reading a message in fedora-devel list telling that here is the place for people willing to contribute to Fedora translating software and docs to some language. Is this right? I ask because I see this in the page: - http://fedora.redhat.com/projects/translations/ Mailing Lists The place to discuss the translation of software is fedora-devel-list. - I just want a place to start, so if anyone can point me something... Oh yeah, and my language is Brazilian Portuguese. []'s Hugo From kwade at redhat.com Thu Nov 13 22:34:01 2003 From: kwade at redhat.com (Karsten Wade) Date: 13 Nov 2003 14:34:01 -0800 Subject: Translations in this list? In-Reply-To: <3FB4022F.7090100@devin.com.br> References: <3FB4022F.7090100@devin.com.br> Message-ID: <1068762841.17465.44.camel@erato.phig.org> On Thu, 2003-11-13 at 14:14, Hugo Cisneiros wrote: > Hi, > > I subscribed to this list after reading a message in fedora-devel list > telling that here is the place for people willing to contribute to > Fedora translating software and docs to some language. Is this right? I > ask because I see this in the page: > > - > http://fedora.redhat.com/projects/translations/ > > Mailing Lists > The place to discuss the translation of software is fedora-devel-list. > - > > I just want a place to start, so if anyone can point me something... Oh > yeah, and my language is Brazilian Portuguese. Welcome. This list is mainly for Fedora Project documentation, and translation of that documentation. A recent FAQ in the draft stage can be viewed in the archives: http://www.redhat.com/archives/fedora-docs-list/2003-November/msg00029.html The translation process for software and documentation have some similarities. I would expect that some of the translation process for Fedora Project will happen on this list, so it's good to be subscribed to both. - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From sarahs at redhat.com Thu Nov 13 23:51:06 2003 From: sarahs at redhat.com (Sarah Wang) Date: Fri, 14 Nov 2003 09:51:06 +1000 Subject: Issues related to translation Message-ID: <3FB418EA.4090308@redhat.com> Hi all, Apologies to all those people who have showed interests in Fedora Translation Project for responding so late. We have been quite busy trying to clear out the last release. To become a translator, you first need to sign up an account on http://rhlinux.redhat.com/cgi-bin/i18n-signup/ The steps to generate ssh key pair need by the sign up process are: * open a terminal window * [username at host homedirectory]$ cd .ssh * [username at host .ssh]$ ls * If you see "id_dsa" and "id_dsa.pub", you can skip the following steps. However, you must remember the password you have used to generate the keys. * If you do not see the above two files, do the following: * [username at host .ssh]$ssh-keygen -t dsa * You will be requested to enter your password twice to generate the key pair. * Once the keys are generated, copy the "id_dsa.pub" content and paste it into the account sign up page. (you can use "cat id_dsa.pub" to display the key content.) Once you have submitted account request, and got it approved, you can start to check out the modules. The CVSROOT for the software translation module is ":ext:username at i18n.redhat.com:/usr/local/CVS". You can add aliases in your ~/.bashrc file to make life easier. The alias name can be changed using your own preference. And don't forget to substitute the "username" with your user name. eg: alias cvs-software='export CVSROOT=:ext:username at i18n.redhat.com:/usr/local/CVS' Now, you are ready to check out modules. The module name for software po files is "translate". e.g. [username at host homedirectory]$ cvs-software [username at host homedirectory]$ cvs -z9 co translate You should be able to find all software package names under ~/translate/ directory. Under each package, there are a number of po files such as "de.po" or "zh_CN.po". The name represents the language code. It's strongly advised that you coordinate with other translators in your language group to avoid possible file conflicts or overwriting each other's work. This is just a rough outline. We will post more detailed information on the website as soon as we can. Thanks for your contribution! Sarah From ml at elf.no-ip.org Fri Nov 14 03:18:57 2003 From: ml at elf.no-ip.org (Tadashi Jokagi) Date: Fri, 14 Nov 2003 12:18:57 +0900 Subject: Issues related to translation In-Reply-To: <3FB418EA.4090308@redhat.com> References: <3FB418EA.4090308@redhat.com> Message-ID: <3fb449a1.4479%ml@elf.no-ip.org> Hi, I applied for account on December 11. There was the following information in mail of an answer. >------------------------------------------------------------------------- >Request details are: > name:Tadashi Jokagi > login:elf > email:fedora at elf.no-ip.org > group:external > status:pending My present condition seems to be pending. It seems that therefore, I cannot do the checkout work of CVS etc. Next, I should just do what. ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ From hugo at devin.com.br Fri Nov 14 03:28:33 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Fri, 14 Nov 2003 00:28:33 -0300 Subject: Issues related to translation In-Reply-To: <3fb449a1.4479%ml@elf.no-ip.org> References: <3FB418EA.4090308@redhat.com> <3fb449a1.4479%ml@elf.no-ip.org> Message-ID: <3FB44BE1.5080905@devin.com.br> Tadashi Jokagi wrote: > Hi, > > I applied for account on December 11. > There was the following information in mail of an answer. > > >>------------------------------------------------------------------------- >>Request details are: >> name:Tadashi Jokagi >> login:elf >> email:fedora at elf.no-ip.org >> group:external >> status:pending > > > My present condition seems to be pending. > It seems that therefore, I cannot do the checkout work of CVS etc. > Next, I should just do what. Same for me, but I applied on November 6. > ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 > Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org > Yokukitana http://elf.no-ip.org/ > Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ []'s Hugo From jaap at haitsma.org Sat Nov 15 11:05:13 2003 From: jaap at haitsma.org (Jaap A. Haitsma) Date: Sat, 15 Nov 2003 12:05:13 +0100 Subject: Font on Fedora website Message-ID: <1068894312.2321.8.camel@PC67148135> Hi, I really like the design of the fedora webpage. Just a minor remark, when I read the page with a browser or on the other OS that does not support anti aliased fonts the font looks quite bad. www.mozilla.org uses a very similar font (maybe it's even the same :-) ) but the font looks OK on the other OS. So maybe it's quite easy to fix this. Jaap From twaugh at redhat.com Mon Nov 17 15:29:59 2003 From: twaugh at redhat.com (Tim Waugh) Date: Mon, 17 Nov 2003 15:29:59 +0000 Subject: nxml-mode for Emacs Message-ID: <20031117152959.GH5686@redhat.com> Emacs users might find this interesting: http://www.xmlhack.com/read.php?item=2061 Packages are here: ftp://people.redhat.com/twaugh/docbook/nxml-mode Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From tfox at redhat.com Mon Nov 17 16:39:51 2003 From: tfox at redhat.com (Tammy Fox) Date: Mon, 17 Nov 2003 11:39:51 -0500 Subject: Font on Fedora website In-Reply-To: <1068894312.2321.8.camel@PC67148135> References: <1068894312.2321.8.camel@PC67148135> Message-ID: <20031117163950.GJ19956@redhat.com> Thanks for letting us know. I'll look into it with Garrett and try to figure out what is going on. Tammy On Sat, Nov 15, 2003 at 12:05:13PM +0100, Jaap A. Haitsma wrote: > Hi, > > I really like the design of the fedora webpage. Just a minor remark, > when I read the page with a browser or on the other OS that does not > support anti aliased fonts the font looks quite bad. www.mozilla.org > uses a very similar font (maybe it's even the same :-) ) but the font > looks OK on the other OS. So maybe it's quite easy to fix this. > > Jaap > > > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From dpawson at nildram.co.uk Mon Nov 17 18:00:56 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 17 Nov 2003 18:00:56 +0000 Subject: nxml-mode for Emacs In-Reply-To: <20031117152959.GH5686@redhat.com> References: <20031117152959.GH5686@redhat.com> Message-ID: <6.0.0.22.2.20031117175923.0263c0a0@pop3.Nildram.co.uk> At 15:29 17/11/2003, you wrote: >Emacs users might find this interesting: > >http://www.xmlhack.com/read.php?item=2061 > >Packages are here: > >ftp://people.redhat.com/twaugh/docbook/nxml-mode http://www.thaiopensource.com/download/ is the 'horses mouth'? Delightful IMHO. regards DaveP From twaugh at redhat.com Mon Nov 17 18:15:16 2003 From: twaugh at redhat.com (Tim Waugh) Date: Mon, 17 Nov 2003 18:15:16 +0000 Subject: nxml-mode for Emacs In-Reply-To: <6.0.0.22.2.20031117175923.0263c0a0@pop3.Nildram.co.uk> References: <20031117152959.GH5686@redhat.com> <6.0.0.22.2.20031117175923.0263c0a0@pop3.Nildram.co.uk> Message-ID: <20031117181514.GE540@redhat.com> On Mon, Nov 17, 2003 at 06:00:56PM +0000, Dave Pawson wrote: > http://www.thaiopensource.com/download/ is the 'horses mouth'? Yes, that's the upstream site. Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gavin.henry at magicfx.co.uk Mon Nov 17 18:15:44 2003 From: gavin.henry at magicfx.co.uk (G Henry) Date: Mon, 17 Nov 2003 18:15:44 +0000 Subject: nxml-mode with Emacs Message-ID: <200311171815.14128.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I've been trying this all today, and I really like it. I was chatting to Tim Waugh on our #fedora-devel irc channel today and has been using for ages and also has rpms for it. I think we should update the docs guide to include this as an alternative to psgml mode. Thoughts? Gav. - -- Regards Trying to be a RHCE... http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/uRBQgNqd7Kng8UoRAkpoAKDLhoYKDQAgFMEL0P+WDiKCwUTdjwCfSw0S B61Sgmf1+ewMIiPhodaLQ1w= =lvaZ -----END PGP SIGNATURE----- From gavin.henry at magicfx.co.uk Mon Nov 17 18:30:16 2003 From: gavin.henry at magicfx.co.uk (G Henry) Date: Mon, 17 Nov 2003 18:30:16 +0000 Subject: nxml-mode for Emacs In-Reply-To: <6.0.0.22.2.20031117175923.0263c0a0@pop3.Nildram.co.uk> References: <20031117152959.GH5686@redhat.com> <6.0.0.22.2.20031117175923.0263c0a0@pop3.Nildram.co.uk> Message-ID: <200311171830.18863.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 17 Nov 2003 6:00 pm, Dave Pawson wrote: > At 15:29 17/11/2003, you wrote: > >Emacs users might find this interesting: > > > >http://www.xmlhack.com/read.php?item=2061 > > > >Packages are here: > > > >ftp://people.redhat.com/twaugh/docbook/nxml-mode > > http://www.thaiopensource.com/download/ is the 'horses mouth'? > > Delightful IMHO. > > regards DaveP Sorry Dave and original mailer, didn't see that someone else had been spreading the news :-) - -- Regards Trying to be a RHCE... http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/uRO4gNqd7Kng8UoRApzbAKCzxNmUcu53km9kxCb39I7u01uXswCePClz kIPVcM9YTd13qsmwIzPu5QQ= =8ROl -----END PGP SIGNATURE----- From dpawson at nildram.co.uk Mon Nov 17 19:10:34 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 17 Nov 2003 19:10:34 +0000 Subject: nxml-mode with Emacs In-Reply-To: <200311171815.14128.gavin.henry@magicfx.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> Message-ID: <6.0.0.22.2.20031117190741.02590de8@pop3.Nildram.co.uk> At 18:15 17/11/2003, you wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Hi all, > >I've been trying this all today, and I really like it. I was chatting to Tim >Waugh on our #fedora-devel irc channel today and has been using for ages and >also has rpms for it. > >I think we should update the docs guide to include this as an alternative to >psgml mode. Benefits? Better error reporting. Allows odd character entry (Unicode code points) slick association with schema. Flexible, DTD, XSD (if you have no taste :-) or relax-NG schema. I'm sure it will improve more... and its only a few weeks old. Concerns? No tag this highlight region with X tag. No Move to next entry with CDATA. Generally, better than psgml.... if namespaces wanted. I'm working with it after 6 years with psgml. regards DaveP From gavin.henry at magicfx.co.uk Mon Nov 17 19:59:26 2003 From: gavin.henry at magicfx.co.uk (G Henry) Date: Mon, 17 Nov 2003 19:59:26 +0000 Subject: nxml-mode with Emacs In-Reply-To: <6.0.0.22.2.20031117190741.02590de8@pop3.Nildram.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <6.0.0.22.2.20031117190741.02590de8@pop3.Nildram.co.uk> Message-ID: <200311171959.28595.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 17 Nov 2003 7:10 pm, Dave Pawson wrote: > At 18:15 17/11/2003, you wrote: > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > >Hi all, > > > >I've been trying this all today, and I really like it. I was chatting to > > Tim Waugh on our #fedora-devel irc channel today and has been using for > > ages and also has rpms for it. > > > >I think we should update the docs guide to include this as an alternative > > to psgml mode. > > Benefits? > Better error reporting. > Allows odd character entry (Unicode code points) > slick association with schema. > Flexible, DTD, XSD (if you have no taste :-) or relax-NG schema. > I'm sure it will improve more... and its only a few weeks old. > Concerns? > No tag this highlight region with X tag. > No Move to next entry with CDATA. > > Generally, better than psgml.... if namespaces wanted. > > I'm working with it after 6 years with psgml. > > regards DaveP > I do like the error reporting. I saw all your posts on the nxml yahoo list. One, thing though, I am having difficulty using tag completion with the fedora xml docs, but on nxml-mode.xml they work fine. Any idea? - -- Regards Trying to be a RHCE... http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/uSiegNqd7Kng8UoRAgYEAKCBat4zYouiHMzQxXqS3m7CCDbKhgCg2k47 ZzD/UK4/VG4Xc3GL0du6oCw= =NvRO -----END PGP SIGNATURE----- From ml at elf.no-ip.org Tue Nov 18 05:52:53 2003 From: ml at elf.no-ip.org (Tadashi Jokagi) Date: Tue, 18 Nov 2003 14:52:53 +0900 Subject: Issues related to translation In-Reply-To: <3fb449a1.4479%ml@elf.no-ip.org> References: <3FB418EA.4090308@redhat.com> <3fb449a1.4479%ml@elf.no-ip.org> Message-ID: <3fb9b3b5.4514%ml@elf.no-ip.org> Hi, Is there any person who solved? I took out mail to i18n at redhat.com. Please give advice. Regards. Tadashi Jokagi's "Re: Issues related to translation" wrote: >Hi, > >I applied for account on December 11. >There was the following information in mail of an answer. > >>------------------------------------------------------------------------- >>Request details are: >> name:Tadashi Jokagi >> login:elf >> email:fedora at elf.no-ip.org >> group:external >> status:pending > >My present condition seems to be pending. >It seems that therefore, I cannot do the checkout work of CVS etc. >Next, I should just do what. > >----.----1----.----2----.----3----.----4----.----5----.----6----.----7 >Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org >Yokukitana http://elf.no-ip.org/ >Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ > > >-- >fedora-docs-list mailing list >fedora-docs-list at redhat.com >http://www.redhat.com/mailman/listinfo/fedora-docs-list ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ From dpawson at nildram.co.uk Tue Nov 18 17:53:13 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Tue, 18 Nov 2003 17:53:13 +0000 Subject: nxml-mode with Emacs In-Reply-To: <200311171959.28595.gavin.henry@magicfx.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <6.0.0.22.2.20031117190741.02590de8@pop3.Nildram.co.uk> <200311171959.28595.gavin.henry@magicfx.co.uk> Message-ID: <6.0.0.22.2.20031118175210.025e5a38@pop3.Nildram.co.uk> At 19:59 17/11/2003, you wrote: >I do like the error reporting. > >I saw all your posts on the nxml yahoo list. One, thing though, I am having >difficulty using tag completion with the fedora xml docs, but on >nxml-mode.xml they work fine. > >Any idea? Are you using nxml-mode for fedora documents? If so, tag completion, C-RET should work for both elements and attributes. HTH DaveP From gavin.henry at magicfx.co.uk Wed Nov 19 08:55:00 2003 From: gavin.henry at magicfx.co.uk (Gavin Henry) Date: Wed, 19 Nov 2003 08:55:00 +0000 Subject: nxml-mode with Emacs In-Reply-To: <6.0.0.22.2.20031118175210.025e5a38@pop3.Nildram.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311171959.28595.gavin.henry@magicfx.co.uk> <6.0.0.22.2.20031118175210.025e5a38@pop3.Nildram.co.uk> Message-ID: <200311190855.03727.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 18 November 2003 5:53 pm, Dave Pawson wrote: > At 19:59 17/11/2003, you wrote: > >I do like the error reporting. > > > >I saw all your posts on the nxml yahoo list. One, thing though, I am > > having difficulty using tag completion with the fedora xml docs, but on > >nxml-mode.xml they work fine. > > > >Any idea? > > Are you using nxml-mode for fedora documents? > If so, tag completion, C-RET should work for both elements > and attributes. > Yes, at home when I open any of the fedora-docs C-RET doesn't work. - -- Regards, Gavin Henry http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/uy/mgNqd7Kng8UoRAoF/AJ9+Z5TPWqan+T7Yx16YfMox42V70gCfX4vI 27ZAz2xhG4xVCawC0N1asyE= =dX1U -----END PGP SIGNATURE----- From twaugh at redhat.com Wed Nov 19 09:59:32 2003 From: twaugh at redhat.com (Tim Waugh) Date: Wed, 19 Nov 2003 09:59:32 +0000 Subject: nxml-mode with Emacs In-Reply-To: <200311190855.03727.gavin.henry@magicfx.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311171959.28595.gavin.henry@magicfx.co.uk> <6.0.0.22.2.20031118175210.025e5a38@pop3.Nildram.co.uk> <200311190855.03727.gavin.henry@magicfx.co.uk> Message-ID: <20031119095932.GJ9702@redhat.com> On Wed, Nov 19, 2003 at 08:55:00AM +0000, Gavin Henry wrote: > Yes, at home when I open any of the fedora-docs C-RET doesn't work. When you open the document does it say "using vacuous schema"? Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gavin.henry at magicfx.co.uk Wed Nov 19 10:12:55 2003 From: gavin.henry at magicfx.co.uk (Gavin Henry) Date: Wed, 19 Nov 2003 10:12:55 +0000 Subject: nxml-mode with Emacs In-Reply-To: <20031119095932.GJ9702@redhat.com> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311190855.03727.gavin.henry@magicfx.co.uk> <20031119095932.GJ9702@redhat.com> Message-ID: <200311191012.59900.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 November 2003 9:59 am, Tim Waugh wrote: > On Wed, Nov 19, 2003 at 08:55:00AM +0000, Gavin Henry wrote: > > Yes, at home when I open any of the fedora-docs C-RET doesn't work. > > When you open the document does it say "using vacuous schema"? > > Tim. > */ It works now. It was usig the docbook schema, but I think the error was caused when I did M-x load-file then rng-auto.el then M-x nxml-mode. This worked, but when I then opened another file, it said cannot complete etc. - -- Regards, Gavin Henry http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/u0IqgNqd7Kng8UoRAhgIAKC/BoeHrbBluQNFA+OcdBNGEb+u5gCgwcb2 wh0yfxUUN6gGRQNC+s+Dik8= =tDR4 -----END PGP SIGNATURE----- From twaugh at redhat.com Wed Nov 19 10:20:30 2003 From: twaugh at redhat.com (Tim Waugh) Date: Wed, 19 Nov 2003 10:20:30 +0000 Subject: nxml-mode with Emacs In-Reply-To: <200311191012.59900.gavin.henry@magicfx.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311190855.03727.gavin.henry@magicfx.co.uk> <20031119095932.GJ9702@redhat.com> <200311191012.59900.gavin.henry@magicfx.co.uk> Message-ID: <20031119102030.GL9702@redhat.com> On Wed, Nov 19, 2003 at 10:12:55AM +0000, Gavin Henry wrote: > It works now. It was usig the docbook schema, but I think the error > was caused when I did M-x load-file then rng-auto.el then M-x > nxml-mode. You shouldn't need to M-x load-file rhn-auto.el, since that's done in /usr/share/emacs/site-lisp/site-start.d/nxml-init.el. Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gavin.henry at magicfx.co.uk Wed Nov 19 10:56:00 2003 From: gavin.henry at magicfx.co.uk (Gavin Henry) Date: Wed, 19 Nov 2003 10:56:00 +0000 Subject: nxml-mode with Emacs In-Reply-To: <20031119102030.GL9702@redhat.com> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311191012.59900.gavin.henry@magicfx.co.uk> <20031119102030.GL9702@redhat.com> Message-ID: <200311191056.05163.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 November 2003 10:20 am, Tim Waugh wrote: > On Wed, Nov 19, 2003 at 10:12:55AM +0000, Gavin Henry wrote: > > It works now. It was usig the docbook schema, but I think the error > > was caused when I did M-x load-file then rng-auto.el then M-x > > nxml-mode. > > You shouldn't need to M-x load-file rhn-auto.el, since that's done in > /usr/share/emacs/site-lisp/site-start.d/nxml-init.el. I haven't put anything in there, so I do :-) - -- Regards, Gavin Henry http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/u0xDgNqd7Kng8UoRAiKrAKCDGWu4fdUOYYA5TyOyaqaGFE8LKwCfZkQ7 bhfjkfbQYBmhIBOak4bG4Ac= =X5BT -----END PGP SIGNATURE----- From twaugh at redhat.com Wed Nov 19 11:13:50 2003 From: twaugh at redhat.com (Tim Waugh) Date: Wed, 19 Nov 2003 11:13:50 +0000 Subject: nxml-mode with Emacs In-Reply-To: <200311191056.05163.gavin.henry@magicfx.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311191012.59900.gavin.henry@magicfx.co.uk> <20031119102030.GL9702@redhat.com> <200311191056.05163.gavin.henry@magicfx.co.uk> Message-ID: <20031119111349.GN9702@redhat.com> On Wed, Nov 19, 2003 at 10:56:00AM +0000, Gavin Henry wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wednesday 19 November 2003 10:20 am, Tim Waugh wrote: > > On Wed, Nov 19, 2003 at 10:12:55AM +0000, Gavin Henry wrote: > > > It works now. It was usig the docbook schema, but I think the error > > > was caused when I did M-x load-file then rng-auto.el then M-x > > > nxml-mode. > > > > You shouldn't need to M-x load-file rhn-auto.el, since that's done in > > /usr/share/emacs/site-lisp/site-start.d/nxml-init.el. > > I haven't put anything in there, so I do :-) Oh, you didn't install from the RPM? Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gavin.henry at magicfx.co.uk Wed Nov 19 11:19:31 2003 From: gavin.henry at magicfx.co.uk (Gavin Henry) Date: Wed, 19 Nov 2003 11:19:31 +0000 Subject: nxml-mode with Emacs In-Reply-To: <20031119111349.GN9702@redhat.com> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311191056.05163.gavin.henry@magicfx.co.uk> <20031119111349.GN9702@redhat.com> Message-ID: <200311191119.39162.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 November 2003 11:13 am, Tim Waugh wrote: > On Wed, Nov 19, 2003 at 10:56:00AM +0000, Gavin Henry wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Wednesday 19 November 2003 10:20 am, Tim Waugh wrote: > > > On Wed, Nov 19, 2003 at 10:12:55AM +0000, Gavin Henry wrote: > > > > It works now. It was usig the docbook schema, but I think the error > > > > was caused when I did M-x load-file then rng-auto.el then M-x > > > > nxml-mode. > > > > > > You shouldn't need to M-x load-file rhn-auto.el, since that's done in > > > /usr/share/emacs/site-lisp/site-start.d/nxml-init.el. > > > > I haven't put anything in there, so I do :-) > > Oh, you didn't install from the RPM? > > Tim. > */ No, I am on debian here and fedora at home, so I used the source luke. Will try the rpm at home tonight. - -- Regards, Gavin Henry http://www.magicfx.co.uk http://www.suretecsystems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/u1HIgNqd7Kng8UoRAiQYAJ0TmVvWgQOczvTdv33Tfw2T09ItIACePfJ4 Ech5lU5gOu1XHXaHJSazpXM= =e8K2 -----END PGP SIGNATURE----- From dpawson at nildram.co.uk Wed Nov 19 18:25:57 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Wed, 19 Nov 2003 18:25:57 +0000 Subject: nxml-mode with Emacs In-Reply-To: <20031119111349.GN9702@redhat.com> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311191012.59900.gavin.henry@magicfx.co.uk> <20031119102030.GL9702@redhat.com> <200311191056.05163.gavin.henry@magicfx.co.uk> <20031119111349.GN9702@redhat.com> Message-ID: <6.0.0.22.2.20031119182350.02598220@pop3.Nildram.co.uk> At 11:13 19/11/2003, Tim Waugh wrote: >On Wed, Nov 19, 2003 at 10:56:00AM +0000, Gavin Henry wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Wednesday 19 November 2003 10:20 am, Tim Waugh wrote: > > > On Wed, Nov 19, 2003 at 10:12:55AM +0000, Gavin Henry wrote: > > > > It works now. It was usig the docbook schema, but I think the error > > > > was caused when I did M-x load-file then rng-auto.el then M-x > > > > nxml-mode. > > > > > > You shouldn't need to M-x load-file rhn-auto.el, since that's done in > > > /usr/share/emacs/site-lisp/site-start.d/nxml-init.el. > > > > I haven't put anything in there, so I do :-) > >Oh, you didn't install from the RPM? If you read the documentation with nxml, you'll see you need to add stuff to your .emacs (or whatever load file you use) to load nxml mode. If its loaded (shows at the bottom of the screen) and you have specified which schema you want used (C-c C-s to set the schema, and docbook is provided in the schema directory) then C-RET should work. It does for me, win32 and redhat. HTH DaveP From twaugh at redhat.com Wed Nov 19 18:42:25 2003 From: twaugh at redhat.com (Tim Waugh) Date: Wed, 19 Nov 2003 18:42:25 +0000 Subject: nxml-mode with Emacs In-Reply-To: <6.0.0.22.2.20031119182350.02598220@pop3.Nildram.co.uk> References: <200311171815.14128.gavin.henry@magicfx.co.uk> <200311191012.59900.gavin.henry@magicfx.co.uk> <20031119102030.GL9702@redhat.com> <200311191056.05163.gavin.henry@magicfx.co.uk> <20031119111349.GN9702@redhat.com> <6.0.0.22.2.20031119182350.02598220@pop3.Nildram.co.uk> Message-ID: <20031119184225.GR9702@redhat.com> On Wed, Nov 19, 2003 at 06:25:57PM +0000, Dave Pawson wrote: > If you read the documentation with nxml, you'll see you need > to add stuff to your .emacs (or whatever load file you use) > to load nxml mode. .. but the RPM on people.redhat.com adds a file to site-start.d to avoid the need for that. Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From qralston+ml.redhat-fedora-docs at andrew.cmu.edu Thu Nov 20 05:49:48 2003 From: qralston+ml.redhat-fedora-docs at andrew.cmu.edu (James Ralston) Date: Thu, 20 Nov 2003 00:49:48 -0500 Subject: nxml-mode for Emacs In-Reply-To: <20031117152959.GH5686@redhat.com> References: <20031117152959.GH5686@redhat.com> Message-ID: <76650000.1069307388@shieldbreaker.l33tskillz.org> On 2003-11-17 at 15:29:59+0000 Tim Waugh wrote: > Emacs users might find this interesting: > > http://www.xmlhack.com/read.php?item=2061 > > Packages are here: > > ftp://people.redhat.com/twaugh/docbook/nxml-mode This is completely bad-assed. :) It works much better for my purposes than SGML mode. Thanks for pointing this out... -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA From forrestx.taylor at intel.com Thu Nov 20 17:45:19 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Thu, 20 Nov 2003 09:45:19 -0800 Subject: Anaconda documents Message-ID: <1069350318.28747.16.camel@bad.jf.intel.com> Hi all, I am new to the list, although not new to Red Hat Linux. I am interested in writing docs for anaconda, so, is anyone was already working on them? Taking a look at the Documentation project site, I see that I need Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the learning curve for these? I have never done XML, and I am not an Emacs user (sorry to start a flamewar). Perhaps I could write the text and someone with more knowledge of XML/Emacs could put it into the right format. I am not unwilling to learn XML/Emacs, but my time might be spent better elsewhere. Let me know what you all think. Forrest From tdiehl at rogueind.com Thu Nov 20 18:02:38 2003 From: tdiehl at rogueind.com (Tom Diehl) Date: Thu, 20 Nov 2003 13:02:38 -0500 (EST) Subject: Anaconda documents In-Reply-To: <1069350318.28747.16.camel@bad.jf.intel.com> References: <1069350318.28747.16.camel@bad.jf.intel.com> Message-ID: On Thu, 20 Nov 2003, Taylor, ForrestX wrote: > Hi all, > > I am new to the list, although not new to Red Hat Linux. I am > interested in writing docs for anaconda, so, is anyone was already > working on them? > > Taking a look at the Documentation project site, I see that I need > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > learning curve for these? I have never done XML, and I am not an Emacs > user (sorry to start a flamewar). Perhaps I could write the text and > someone with more knowledge of XML/Emacs could put it into the right > format. I am not unwilling to learn XML/Emacs, but my time might be > spent better elsewhere. Are there non-Emacs solutions available for this?? ...................Tom From arau at schleese.com Thu Nov 20 19:10:09 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Thu, 20 Nov 2003 14:10:09 -0500 Subject: Anaconda documents Message-ID: I am in the same boat with Taylor. A good start might be to look at other docu projects to get a feel for what is needed. Any suggestions where and what to look for? AR From kwade at redhat.com Thu Nov 20 19:36:26 2003 From: kwade at redhat.com (Karsten Wade) Date: 20 Nov 2003 11:36:26 -0800 Subject: Anaconda documents In-Reply-To: References: <1069350318.28747.16.camel@bad.jf.intel.com> Message-ID: <1069356986.28841.2246.camel@erato.phig.org> On Thu, 2003-11-20 at 10:02, Tom Diehl wrote: > On Thu, 20 Nov 2003, Taylor, ForrestX wrote: > > > Hi all, > > > > I am new to the list, although not new to Red Hat Linux. I am > > interested in writing docs for anaconda, so, is anyone was already > > working on them? > > > > Taking a look at the Documentation project site, I see that I need > > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > > learning curve for these? I have never done XML, and I am not an Emacs > > user (sorry to start a flamewar). Perhaps I could write the text and > > someone with more knowledge of XML/Emacs could put it into the right > > format. I am not unwilling to learn XML/Emacs, but my time might be > > spent better elsewhere. > > Are there non-Emacs solutions available for this?? Any editor will suffice, but unless you have an intimate knowledge of DocBook XML, you will find it difficult to use an editor which does not have a mode similar to PSGML or nXML. If you know how to indent properly, etc., it's really less of an issue which editor you use and more of an issue for collaboration if you use the tab character instead of spaces for tabs. :) One editor I am keeping my eye on is http://www.conglomerate.org/. They are thinking in novel ways that make using a GUI editor tempting. At Red Hat, we have a relatively standardized way of doing things. We can share .emacs changes and keep everyone able to edit each other's projects, etc. It will be interesting to see how we resolve the lack of homogeneity in Fedora Project docs. These are, after all, open standards, so if you can accomplish the same thing using other tools, more power to you. - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From arau at schleese.com Thu Nov 20 20:14:32 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Thu, 20 Nov 2003 15:14:32 -0500 Subject: Anaconda documents In-Reply-To: <1069356986.28841.2246.camel@erato.phig.org> Message-ID: Took my lunch break to look into the creation of fedora-docs. And I have to agree with Taylor: "Taking a look at the Documentation project site, I see that I need Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the learning curve for these? I have never done XML, and I am not an Emacs user (sorry to start a flamewar). Perhaps I could write the text and someone with more knowledge of XML/Emacs could put it into the right format. I am not unwilling to learn XML/Emacs, but my time might be spent better elsewhere." This is very discouraging!! AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Karsten Wade Sent: 20 November 2003 14:36 To: fedora-docs-list at redhat.com Subject: Re: Anaconda documents On Thu, 2003-11-20 at 10:02, Tom Diehl wrote: > On Thu, 20 Nov 2003, Taylor, ForrestX wrote: > > > Hi all, > > > > I am new to the list, although not new to Red Hat Linux. I am > > interested in writing docs for anaconda, so, is anyone was already > > working on them? > > > > Taking a look at the Documentation project site, I see that I need > > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > > learning curve for these? I have never done XML, and I am not an Emacs > > user (sorry to start a flamewar). Perhaps I could write the text and > > someone with more knowledge of XML/Emacs could put it into the right > > format. I am not unwilling to learn XML/Emacs, but my time might be > > spent better elsewhere. > > Are there non-Emacs solutions available for this?? Any editor will suffice, but unless you have an intimate knowledge of DocBook XML, you will find it difficult to use an editor which does not have a mode similar to PSGML or nXML. If you know how to indent properly, etc., it's really less of an issue which editor you use and more of an issue for collaboration if you use the tab character instead of spaces for tabs. :) One editor I am keeping my eye on is http://www.conglomerate.org/. They are thinking in novel ways that make using a GUI editor tempting. At Red Hat, we have a relatively standardized way of doing things. We can share .emacs changes and keep everyone able to edit each other's projects, etc. It will be interesting to see how we resolve the lack of homogeneity in Fedora Project docs. These are, after all, open standards, so if you can accomplish the same thing using other tools, more power to you. - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From pantz at lqt.ca Thu Nov 20 20:35:17 2003 From: pantz at lqt.ca (Paul Pianta) Date: Thu, 20 Nov 2003 15:35:17 -0500 Subject: anaconda customization doc Message-ID: <3FBD2585.1090406@lqt.ca> ok im over on this list now (from anaconda-devel-list) a few of us from the anaconda-devel list are interested in helping out putting together some form of documentation for anaconda. whether it be a FAQ, a HOW-TO, a general guide or whatever it needs to be - we don't have much of an idea about how to get things rolling and/or what type of topics to cover in the doc. i'm hoping here we can get some advice and find a common meeting place for getting some stuff down on 'paper'. (p.s. - i hope no-one else posted a similar message b4 me - my mail is still playing up) pantz From forrestx.taylor at intel.com Thu Nov 20 20:45:01 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Thu, 20 Nov 2003 12:45:01 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069361100.28747.121.camel@bad.jf.intel.com> On Thu, 2003-11-20 at 12:14, Alexander Rau (work) wrote: > Took my lunch break to look into the creation of fedora-docs. And I have to > agree with Taylor: > > "Taking a look at the Documentation project site, I see that I need > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > learning curve for these? I have never done XML, and I am not an Emacs > user (sorry to start a flamewar). Perhaps I could write the text and > someone with more knowledge of XML/Emacs could put it into the right > format. I am not unwilling to learn XML/Emacs, but my time might be > spent better elsewhere." > > This is very discouraging!! Indeed. Let's focus on the actual documentation, and hopefully someone will step forward that can put it into XML. Otherwise, I'll try to read the docs on setting up XML/Emacs this weekend and try it out. Alexander, can you post your ideas for a Table of Contents? Forrest From paul at frields.com Thu Nov 20 20:52:19 2003 From: paul at frields.com (Paul W. Frields) Date: Thu, 20 Nov 2003 15:52:19 -0500 Subject: Anaconda documents In-Reply-To: References: <1069350318.28747.16.camel@bad.jf.intel.com> Message-ID: <1069360917.16197.77.camel@localhost.localdomain> On Thu, 2003-11-20 at 13:02, Tom Diehl wrote: > > Taking a look at the Documentation project site, I see that I need > > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > > learning curve for these? I have never done XML, and I am not an Emacs > > user (sorry to start a flamewar). Perhaps I could write the text and > > someone with more knowledge of XML/Emacs could put it into the right > > format. I am not unwilling to learn XML/Emacs, but my time might be > > spent better elsewhere. > > Are there non-Emacs solutions available for this?? I hadn't used Emacs or PSGML before trying them for this project; it is not too hard to learn. If you follow the Documentation Guide up at the Fedora pages, that's the best intro available right now for that toolbox, at least insofar as it concerns FDP. Also you can try out the RPM available at: ftp://people.redhat.com/twaugh/docbook/nxml-mode This makes the process a little easier and more automated, apparently. I don't particularly enjoy writing markup like this, and think it would be great if someone got templates for OO.o or LyX that worked correctly for the FDP, but I've got the hang of it under Emacs at this point. I've already written a very short updfstab tutorial. If someone would like me to edit their document and do the markup, let me know and I'll be happy to help. Furthermore, if anyone is interested in making OO.o or LyX work for FDP, we could try that too. The hardest part of the process, IMHO, is remembering where you need to use the markups. The way I'm getting used to it is assuming that anytime I need to make a point, there's probably a markup available. Then it just becomes a task of (1) finding the most appropriate one, and (2) trying to remember it for next time. -- Paul W. Frields, RHCE From arau at schleese.com Thu Nov 20 21:27:59 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Thu, 20 Nov 2003 16:27:59 -0500 Subject: Anaconda documents In-Reply-To: <1069361100.28747.121.camel@bad.jf.intel.com> Message-ID: Here are my suggestions for a Table of Contents (TOC) Just a brain storm and working copy: 1. Introduction 2. How anaconda works 2a) boot process 2b) actual anaconda process 2ba) probing for hardware (what is happening behind the scenes/what programs are doing what) 2bb) language selection 2bc) harddrive setup . . . . . . 2. Installation 3. What is needed to re-build anaconda (disk space, packages) 4. Tree structure 5. binaries (just quick explanation with details in later chapters) 5a) buildinstall . . . 6. mini how to editing and making rpms from source 7. Set up your build environment (tree structures needed and so on) 8. The comps.xml chapter (explanation and making your own comps.xml) 9. Step by step walkthrough the whole buildinstall process 10. Splitting distros 11. burning distros mkisofs 12. Links and useful tools 13. Acknowledgements ==================================== And here is the start for the Introduction chapter (straight from the fedora anaconda project site http://fedora.redhat.com/projects/anaconda-installer/) 1. Introduction Red Hat Installation Program (Anaconda) Anaconda is the installation program for Red Hat distributions. During installation, the system's hardware is identified and configured, and the appropriate file systems for the system's architecture are created. Finally, it allows the user to install the operating system software on the system. Optionally, it can upgrade existing Red Hat installations. Anaconda can run in a fully interactive mode (text or graphical), or in a kickstart mode, which is allows the installation to be scripted for unattended operation. This makes deploying hundreds or thousands of systems very easy. Anaconda is written in Python and C, and is distributed under the GPL. The graphical frontend is written with PyGtk. Using a scripting language (Python) for the majority of the code allows for easily distribution of updates and the quick development of new features. AR PS/ Hope this is a good start From forrestx.taylor at intel.com Thu Nov 20 21:30:14 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Thu, 20 Nov 2003 13:30:14 -0800 Subject: Anaconda documents In-Reply-To: <1069360917.16197.77.camel@localhost.localdomain> References: <1069350318.28747.16.camel@bad.jf.intel.com> <1069360917.16197.77.camel@localhost.localdomain> Message-ID: <1069363814.29919.4.camel@bad.jf.intel.com> On Thu, 2003-11-20 at 12:52, Paul W. Frields wrote: > I hadn't used Emacs or PSGML before trying them for this project; it is > not too hard to learn. If you follow the Documentation Guide up at the > Fedora pages, that's the best intro available right now for that > toolbox, at least insofar as it concerns FDP. Also you can try out the > RPM available at: > > ftp://people.redhat.com/twaugh/docbook/nxml-mode > > This makes the process a little easier and more automated, apparently. I > don't particularly enjoy writing markup like this, and think it would be > great if someone got templates for OO.o or LyX that worked correctly for > the FDP, but I've got the hang of it under Emacs at this point. I've > already written a very short updfstab tutorial. If someone would like me > to edit their document and do the markup, let me know and I'll be happy > to help. Furthermore, if anyone is interested in making OO.o or LyX work > for FDP, we could try that too. > > The hardest part of the process, IMHO, is remembering where you need to > use the markups. The way I'm getting used to it is assuming that anytime > I need to make a point, there's probably a markup available. Then it > just becomes a task of (1) finding the most appropriate one, and (2) > trying to remember it for next time. Thanks for your experience and volunteering to help. We may take you up on your offer to markup the document ;o) Since you didn't think that it was too difficult, I'll grab the docs and try out Emacs/XML. For those who want to help with anaconda, let's start with Alexander's TOC, and go from there. Forrest From forrestx.taylor at intel.com Thu Nov 20 21:44:16 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Thu, 20 Nov 2003 13:44:16 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069364655.29919.10.camel@bad.jf.intel.com> On Thu, 2003-11-20 at 13:27, Alexander Rau (work) wrote: > Here are my suggestions for a Table of Contents (TOC) > > Just a brain storm and working copy: > AR > > PS/ Hope this is a good start This is great--more than I would have thought of! I think that we also need a 'Required updates' section that will list updates required to get things functioning (such as the patch to buildinstall). Let's split this up as it is, and start writing some documentation. AR, pantz (others?) which sections do you want to start with? Forrest From pantz at lqt.ca Thu Nov 20 21:57:23 2003 From: pantz at lqt.ca (Paul Pianta) Date: Thu, 20 Nov 2003 16:57:23 -0500 Subject: Anaconda documents In-Reply-To: References: Message-ID: <3FBD38C3.8040009@lqt.ca> Alexander Rau (work) wrote: >Here are my suggestions for a Table of Contents (TOC) > >Just a brain storm and working copy: > >1. Introduction > > very nice and comprehensive TOC - good stuff. i just thought to myself .... what is it that most people want to do when customizing redhat/fedora/anaconda? these are some things i came up with that could maybe somehow be incorporated into the doc ... * creating a single cd from the 3 cd set with a cutdown version of packages and comps.xml and a kickstart file to automate the whole install * remove/replace all occurences of the words redhat/fedora from the anaconda install process (text and graphical) with their own custom text, logos, etc... * replace original redhat/fedora rpm packages with updated rpm packages (security updates or whatever) and reburn the cds so that they can have a version of RedHat 9 - six months after its release - with all security updates applied (and other packages updated) * add functionality to anaconda that didn't previously exist - eg. adding a new filesystem support, adding support for a new NIC, etc. (this one is more technical and would be rather difficult to incorporate into a generic anaconda doc.) (infact forget about this last one for inclusion ...) well they are my ideas thrown into the pile - lets go! pantz From arau at schleese.com Thu Nov 20 21:54:52 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Thu, 20 Nov 2003 16:54:52 -0500 Subject: Anaconda documents In-Reply-To: <1069363814.29919.4.camel@bad.jf.intel.com> Message-ID: It would be great if we had one destination where we could collect on publish our working documents AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Taylor, ForrestX Sent: 20 November 2003 16:30 To: fedora-docs-list at redhat.com Subject: Re: Anaconda documents On Thu, 2003-11-20 at 12:52, Paul W. Frields wrote: > I hadn't used Emacs or PSGML before trying them for this project; it is > not too hard to learn. If you follow the Documentation Guide up at the > Fedora pages, that's the best intro available right now for that > toolbox, at least insofar as it concerns FDP. Also you can try out the > RPM available at: > > ftp://people.redhat.com/twaugh/docbook/nxml-mode > > This makes the process a little easier and more automated, apparently. I > don't particularly enjoy writing markup like this, and think it would be > great if someone got templates for OO.o or LyX that worked correctly for > the FDP, but I've got the hang of it under Emacs at this point. I've > already written a very short updfstab tutorial. If someone would like me > to edit their document and do the markup, let me know and I'll be happy > to help. Furthermore, if anyone is interested in making OO.o or LyX work > for FDP, we could try that too. > > The hardest part of the process, IMHO, is remembering where you need to > use the markups. The way I'm getting used to it is assuming that anytime > I need to make a point, there's probably a markup available. Then it > just becomes a task of (1) finding the most appropriate one, and (2) > trying to remember it for next time. Thanks for your experience and volunteering to help. We may take you up on your offer to markup the document ;o) Since you didn't think that it was too difficult, I'll grab the docs and try out Emacs/XML. For those who want to help with anaconda, let's start with Alexander's TOC, and go from there. Forrest -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From arau at schleese.com Thu Nov 20 22:08:08 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Thu, 20 Nov 2003 17:08:08 -0500 Subject: Anaconda documents In-Reply-To: <1069364655.29919.10.camel@bad.jf.intel.com> Message-ID: 1. Well, I will check my notes from when I went through the whole process and then I will see what I can contribute. I will let you know tomorrow. 2. I would also appreciate honest feedback from you guys on my writing and grammar since English is not my first language. Maybe I can, once we are finished!!, translate the whole caboodle into German. 3. I am wondering if it wouldn't be helpful to get Jeremy on board!? AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Taylor, ForrestX Sent: 20 November 2003 16:44 To: Alexander Rau (work) Cc: fedora-docs-list at redhat.com Subject: RE: Anaconda documents On Thu, 2003-11-20 at 13:27, Alexander Rau (work) wrote: > Here are my suggestions for a Table of Contents (TOC) > > Just a brain storm and working copy: > AR > > PS/ Hope this is a good start This is great--more than I would have thought of! I think that we also need a 'Required updates' section that will list updates required to get things functioning (such as the patch to buildinstall). Let's split this up as it is, and start writing some documentation. AR, pantz (others?) which sections do you want to start with? Forrest -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From akbar501 at dslextreme.com Thu Nov 20 22:17:13 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Thu, 20 Nov 2003 14:17:13 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <3FBD3D69.7050304@dslextreme.com> Alexander Rau (work) wrote: > It would be great if we had one destination where we could collect on > publish our working documents I can think of three possible solutions: 1. Red Hat could open rw access to a CVS or Subversion repository (but from the site it will be a while b4 this happens) 2. One of us could setup a server and give access to the others (I may be able to help out here) 3. We could use a publicly accessible revision control repository such as sourceforge - Akbar From forrestx.taylor at intel.com Thu Nov 20 22:44:40 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Thu, 20 Nov 2003 14:44:40 -0800 Subject: Anaconda documents In-Reply-To: <3FBD3D69.7050304@dslextreme.com> References: <3FBD3D69.7050304@dslextreme.com> Message-ID: <1069368279.29919.17.camel@bad.jf.intel.com> On Thu, 2003-11-20 at 14:17, Akbar S. Ahmed wrote: > Alexander Rau (work) wrote: > > It would be great if we had one destination where we could collect on > > publish our working documents > > I can think of three possible solutions: > 1. Red Hat could open rw access to a CVS or Subversion repository (but > from the site it will be a while b4 this happens) > 2. One of us could setup a server and give access to the others (I may > be able to help out here) > 3. We could use a publicly accessible revision control repository such > as sourceforge Yes, this is something that we need. Like you said, I don't think that number 1 will happen anytime soon. Akbar, if you can set something up for us, that would probably be the quickest. Do you want to use CVS or a web page? Forrest -- From forrestx.taylor at intel.com Thu Nov 20 23:25:11 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Thu, 20 Nov 2003 15:25:11 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069370710.29919.29.camel@bad.jf.intel.com> On Thu, 2003-11-20 at 14:08, Alexander Rau (work) wrote: > 1. Well, I will check my notes from when I went through the whole process > and then I will see what I can contribute. I will let you know tomorrow. Okay. > 2. I would also appreciate honest feedback from you guys on my writing and > grammar since English is not my first language. Maybe I can, once we are > finished!!, translate the whole caboodle into German. No problem. You write better than most native English speakers. > 3. I am wondering if it wouldn't be helpful to get Jeremy on board!? Yes, it would. Although, he just posted to the anaconda list explaining why he hasn't. He did say, however, he would look over the documents once they exist. I'll look over your TOC, expand on it, and write up a few notes tonight. I guess that I'll post it to the list for now. Tammy/Karsten/Tim/etc., Does Red Hat have a method to collaborate on documents yet (CVS, web, etc.)? This is something that needs to be discussed if the documents are being written by more than one person. Thanks, Forrest From dpawson at nildram.co.uk Thu Nov 20 15:52:33 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Thu, 20 Nov 2003 15:52:33 +0000 Subject: nxml-mode for Emacs In-Reply-To: <76650000.1069307388@shieldbreaker.l33tskillz.org> References: <20031117152959.GH5686@redhat.com> <76650000.1069307388@shieldbreaker.l33tskillz.org> Message-ID: <6.0.0.22.2.20031120155125.025e5cd0@pop3.Nildram.co.uk> At 05:49 20/11/2003, James Ralston wrote: > > Packages are here: > > > > ftp://people.redhat.com/twaugh/docbook/nxml-mode > >This is completely bad-assed. :) > >It works much better for my purposes than SGML mode. James/Tim... anyone from 'tother side of the pond. What's the translation of this please :[ (I think he likes it... or not?) DaveP. From akbar501 at dslextreme.com Thu Nov 20 23:36:09 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Thu, 20 Nov 2003 15:36:09 -0800 Subject: Anaconda documents In-Reply-To: <1069368279.29919.17.camel@bad.jf.intel.com> References: <3FBD3D69.7050304@dslextreme.com> <1069368279.29919.17.camel@bad.jf.intel.com> Message-ID: <3FBD4FE9.3020703@dslextreme.com> Hi Taylor, Taylor, ForrestX wrote: > Akbar, if you can set something up > for us, that would probably be the quickest. Do you want to use CVS or > a web page? I actually just setup a page for us on SourceForge. Please sign up for an account here: https://sourceforge.net/account/register.php I have submitted a project and will email this list when we are given approval. The reason I chose Sourceforge instead of setting up a server myself is that this will give us greater visablity and I live in Northern CA (the power does go out here ;). Plus we get everything we need: CVS, web site, managed hosting, etc. Our project is: Descriptive name: Anaconda Documentation Project Project name: anacondadocs License: GNU Free Documentation License (FDL) Public description: This project contains detailed documentation of Anaconda, a Linux installer program, used by multiple Linux distributions including Fedora, Mandrake, Delixus Linux, and RHEL. Detailed instructions covering Anaconda usage and customization are included. Thanks, Akbar From arau at schleese.com Fri Nov 21 00:17:56 2003 From: arau at schleese.com (arau at schleese.com) Date: Thu, 20 Nov 2003 19:17:56 -0500 Subject: Anaconda documents In-Reply-To: <3FBD4FE9.3020703@dslextreme.com> Message-ID: That is fantastic! Thanks Akbar I am going through my notes now and we can reconvene tomorrow. I guess our logo will be an anaconda (duuuh!) Any ideas? I have a feeling that we are off to a good start and I am positive about the project. There is a good caliber of people here. AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Akbar S. Ahmed Sent: Thursday, November 20, 2003 6:36 PM To: fedora-docs-list at redhat.com Subject: Re: Anaconda documents Hi Taylor, Taylor, ForrestX wrote: > Akbar, if you can set something up > for us, that would probably be the quickest. Do you want to use CVS or > a web page? I actually just setup a page for us on SourceForge. Please sign up for an account here: https://sourceforge.net/account/register.php I have submitted a project and will email this list when we are given approval. The reason I chose Sourceforge instead of setting up a server myself is that this will give us greater visablity and I live in Northern CA (the power does go out here ;). Plus we get everything we need: CVS, web site, managed hosting, etc. Our project is: Descriptive name: Anaconda Documentation Project Project name: anacondadocs License: GNU Free Documentation License (FDL) Public description: This project contains detailed documentation of Anaconda, a Linux installer program, used by multiple Linux distributions including Fedora, Mandrake, Delixus Linux, and RHEL. Detailed instructions covering Anaconda usage and customization are included. Thanks, Akbar -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2534 bytes Desc: not available URL: From joden at malachi.lee.k12.nc.us Fri Nov 21 02:55:50 2003 From: joden at malachi.lee.k12.nc.us (James Olin Oden) Date: Thu, 20 Nov 2003 21:55:50 -0500 (EST) Subject: Anaconda documents In-Reply-To: <3FBD38C3.8040009@lqt.ca> Message-ID: On Thu, 20 Nov 2003, Paul Pianta wrote: > Alexander Rau (work) wrote: > > >Here are my suggestions for a Table of Contents (TOC) > > > >Just a brain storm and working copy: > > > >1. Introduction > > > > > very nice and comprehensive TOC - good stuff. > > i just thought to myself .... > what is it that most people want to do when customizing > redhat/fedora/anaconda? > > these are some things i came up with that could maybe somehow be > incorporated into the doc ... > > * creating a single cd from the 3 cd set with a cutdown version of > packages and comps.xml and a kickstart file to automate the whole install > > * remove/replace all occurences of the words redhat/fedora from the > anaconda install process (text and graphical) with their own custom > text, logos, etc... > > * replace original redhat/fedora rpm packages with updated rpm packages > (security updates or whatever) and reburn the cds so that they can have > a version of RedHat 9 - six months after its release - with all security > updates applied (and other packages updated) > > * add functionality to anaconda that didn't previously exist - eg. > adding a new filesystem support, adding support for a new NIC, etc. > (this one is more technical and would be rather difficult to incorporate > into a generic anaconda doc.) (infact forget about this last one for > inclusion ...) > Actually, what is required documentation wise with this last one is something that at a high level describes the architecture of anaconda (how it all fits together, what python modules exist, what service they provide. Also, things like something that actually describes anaconda's install process from boot to re-boot). A lot of this actually would be usefull for not only extending anaconda, but also for things like troubleshooting installs and better understanding how to interact with it from a kickstart perspective (for instance part of its install process is it reads the kickstart file initially, and then it re-reads it after post. This is of course really usefull for making kickstarts that use %pre to essentially query the system and then tailor the kickstart after this to the specific needs at hand). On, the other hand actually document the actual api of the various python modules should definately not be a first pass thing (though, it certainly could be a goal). Anyway, I think your last category is ultimately still quite usefull when you look at it from the architectual perspective rather than just giving examples or specifics of how to add particular bits of functionality. Just by 2 cents. Cheers...james From qralston+ml.redhat-fedora-docs at andrew.cmu.edu Fri Nov 21 05:44:39 2003 From: qralston+ml.redhat-fedora-docs at andrew.cmu.edu (James Ralston) Date: Fri, 21 Nov 2003 00:44:39 -0500 Subject: nxml-mode for Emacs In-Reply-To: <6.0.0.22.2.20031120155125.025e5cd0@pop3.Nildram.co.uk> References: <20031117152959.GH5686@redhat.com> <76650000.1069307388@shieldbreaker.l33tskillz.org> <6.0.0.22.2.20031120155125.025e5cd0@pop3.Nildram.co.uk> Message-ID: <15180000.1069393479@shieldbreaker.l33tskillz.org> On 2003-11-20 at 15:52:33+0000 Dave Pawson wrote: > At 05:49 20/11/2003, James Ralston wrote: > > > > Packages are here: > > > > > > ftp://people.redhat.com/twaugh/docbook/nxml-mode > > > > This is completely bad-assed. :) > > James/Tim... anyone from 'tother side of the pond. > What's the translation of this please :[ > (I think he likes it... or not?) Sorry about that; I wrote the first thing that came to my mind, which probably made little sense to most people here (given the international scope of this list). My apologies. What I was trying to say was that the nxml-mode package provides many useful features, and makes it much easier to write XML-based documents. I've only been testing it out for an hour or so total, but already it seems to be overwhelmingly superior to the other packages I've tried. :) From ml at elf.no-ip.org Fri Nov 21 07:31:06 2003 From: ml at elf.no-ip.org (Tadashi Jokagi) Date: Fri, 21 Nov 2003 16:31:06 +0900 Subject: filename Message-ID: <3fbdbf3a.4542%ml@elf.no-ip.org> Hi, It is a question about fedora-docs. Almost all the file names of fedora-docs do not correspond to multilingual. ex) documentation-guide/documentation-guide.xml developer-guide/developers-guide.xml Originally you should be as follows. ex) documentation-guide/documentation-guide-en.xml developer-guide/developers-guide-en.xml Is such correction made? ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ From felipe_alfaro at linuxmail.org Fri Nov 21 09:45:59 2003 From: felipe_alfaro at linuxmail.org (Felipe Alfaro Solana) Date: Fri, 21 Nov 2003 10:45:59 +0100 Subject: anaconda customization doc In-Reply-To: <3FBD2585.1090406@lqt.ca> References: <3FBD2585.1090406@lqt.ca> Message-ID: <1069407959.1687.0.camel@teapot.felipe-alfaro.com> On Thu, 2003-11-20 at 21:35, Paul Pianta wrote: > a few of us from the anaconda-devel list are interested in helping out > putting together some form of documentation for anaconda. And I would like to help in translating that document to Spanish :-) From felipe_alfaro at linuxmail.org Fri Nov 21 09:50:42 2003 From: felipe_alfaro at linuxmail.org (Felipe Alfaro Solana) Date: Fri, 21 Nov 2003 10:50:42 +0100 Subject: Anaconda documents In-Reply-To: <3FBD3D69.7050304@dslextreme.com> References: <3FBD3D69.7050304@dslextreme.com> Message-ID: <1069408242.1687.3.camel@teapot.felipe-alfaro.com> On Thu, 2003-11-20 at 23:17, Akbar S. Ahmed wrote: > I can think of three possible solutions: > 1. Red Hat could open rw access to a CVS or Subversion repository (but > from the site it will be a while b4 this happens) This is a good idea... There's already a CVS repository intended for translation purpouses, so maybe this one could be used for developing new documentarion papers. From pauln at truemesh.com Fri Nov 21 09:55:31 2003 From: pauln at truemesh.com (Paul Nasrat) Date: Fri, 21 Nov 2003 09:55:31 +0000 Subject: Anaconda documents In-Reply-To: <1069408242.1687.3.camel@teapot.felipe-alfaro.com> References: <3FBD3D69.7050304@dslextreme.com> <1069408242.1687.3.camel@teapot.felipe-alfaro.com> Message-ID: <20031121095529.GQ10042@ensim.rackshack.net> On Fri, Nov 21, 2003 at 10:50:42AM +0100, Felipe Alfaro Solana wrote: > On Thu, 2003-11-20 at 23:17, Akbar S. Ahmed wrote: > > > I can think of three possible solutions: > > 1. Red Hat could open rw access to a CVS or Subversion repository (but > > from the site it will be a while b4 this happens) > > This is a good idea... There's already a CVS repository intended for > translation purpouses, so maybe this one could be used for developing > new documentarion papers. This will happen AFAIK - see Sopwiths request for a few scripts on fedora-devel-list to provide cvs/ssh/auth stuff. Paul From arau at schleese.com Fri Nov 21 11:27:30 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Fri, 21 Nov 2003 06:27:30 -0500 Subject: anaconda documentation topics Message-ID: Well, I had a quick glance through my notes and I think I will try to start on: 3. What is needed to re-build anaconda (disk space, packages) (requirements) 7. Set up your build environment (tree structures needed and so on) and 9. Step by step walkthrough the whole buildinstall process (since I just went through the whole thing!) But I will wait till we are approved at sourceforge and until Taylor had a chance to improve the TOC. I will also try to contact Brian to see if we could mention his kickstart-tools that were so valuable for making my distro. AR From arau at schleese.com Fri Nov 21 11:27:57 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Fri, 21 Nov 2003 06:27:57 -0500 Subject: Anaconda documents Message-ID: That is fantastic! Thanks Akbar I am going through my notes now and we can reconvene tomorrow. I guess our logo will be an anaconda (duuuh!) Any ideas? I have a feeling that we are off to a good start and I am positive about the project. There is a good caliber of people here. AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Akbar S. Ahmed Sent: Thursday, November 20, 2003 6:36 PM To: fedora-docs-list at redhat.com Subject: Re: Anaconda documents Hi Taylor, Taylor, ForrestX wrote: > Akbar, if you can set something up > for us, that would probably be the quickest. Do you want to use CVS or > a web page? I actually just setup a page for us on SourceForge. Please sign up for an account here: https://sourceforge.net/account/register.php I have submitted a project and will email this list when we are given approval. The reason I chose Sourceforge instead of setting up a server myself is that this will give us greater visablity and I live in Northern CA (the power does go out here ;). Plus we get everything we need: CVS, web site, managed hosting, etc. Our project is: Descriptive name: Anaconda Documentation Project Project name: anacondadocs License: GNU Free Documentation License (FDL) Public description: This project contains detailed documentation of Anaconda, a Linux installer program, used by multiple Linux distributions including Fedora, Mandrake, Delixus Linux, and RHEL. Detailed instructions covering Anaconda usage and customization are included. Thanks, Akbar -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From tfox at redhat.com Fri Nov 21 13:48:22 2003 From: tfox at redhat.com (Tammy Fox) Date: Fri, 21 Nov 2003 08:48:22 -0500 Subject: filename In-Reply-To: <3fbdbf3a.4542%ml@elf.no-ip.org> References: <3fbdbf3a.4542%ml@elf.no-ip.org> Message-ID: <20031121134821.GA10230@redhat.com> Good point. I will make such corrections in CVS. Cheers, Tammy On Fri, Nov 21, 2003 at 04:31:06PM +0900, Tadashi Jokagi wrote: > Hi, > > It is a question about fedora-docs. > Almost all the file names of fedora-docs do not correspond to multilingual. > > ex) > documentation-guide/documentation-guide.xml > developer-guide/developers-guide.xml > > Originally you should be as follows. > > ex) > documentation-guide/documentation-guide-en.xml > developer-guide/developers-guide-en.xml > > Is such correction made? > > ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 > Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org > Yokukitana http://elf.no-ip.org/ > Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ > > From paul at frields.com Fri Nov 21 14:01:02 2003 From: paul at frields.com (Paul W. Frields) Date: Fri, 21 Nov 2003 09:01:02 -0500 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069423262.4902.38.camel@london.east.gov> On Thu, 2003-11-20 at 15:14, Alexander Rau (work) wrote: > Took my lunch break to look into the creation of fedora-docs. And I have to > agree with Taylor: > > "Taking a look at the Documentation project site, I see that I need > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > learning curve for these? I have never done XML, and I am not an Emacs > user (sorry to start a flamewar). Perhaps I could write the text and > someone with more knowledge of XML/Emacs could put it into the right > format. I am not unwilling to learn XML/Emacs, but my time might be > spent better elsewhere." > > This is very discouraging!! Alexander, Don't get discouraged; it's not nearly as hard as it seems... and believe me, my first reaction was *exactly* the same. I am more than happy to help move stuff to XML, but I would encourage you to give this a try. All you need to do is: 1. Make sure you have the "Authoring and Publishing" component (from redhat-config-packages), Emacs (in the "Editors" component), and the psgml package installed. 2. Follow the Documentation Guide to set up your ~/.emacs, parse/save/load the DTD, etc. I found it easiest to simply make a copy of the example-tutorial/ folder and then strip out the content and start from there. There's not that many keystrokes you need to learn to use Emacs effectively in this way, but I will be the first to admit I still find it cumbersome. I tend to use... er, that other editor. :-) In any case, if I was better at this sort of thing I would try and make this work in LyX, which is so much easier to use it's ridiculous. As Karsten (I think) mentioned, the hard part is getting your tool of choice to write everything to file the same way as everyone else, so that when we move to a community repository, no one is stepping on others' toes. To reiterate though, I will be happy to edit XML if you decide this is too painful. :-) -- Paul W. Frields, RHCE From paul at frields.com Fri Nov 21 14:06:54 2003 From: paul at frields.com (Paul W. Frields) Date: Fri, 21 Nov 2003 09:06:54 -0500 Subject: html-nochunks, and PDF papersize Message-ID: <1069423614.4902.43.camel@london.east.gov> Tammy, if it's not too much trouble, could you also add the following to the Makefile for people who need single HTML files for whatever reason: html-nochunks: @xmlto html-nochunks $(XMLFILE) And, just to show my blissful ignorance, can anyone tell me how to get my PDF's to build as US-letter size instead of A4? I am using FC1 and simply don't know enough about xmlto or the rest of the DocBook-XML toolset to figure this out. I've tried a number of things already and none appear to have any effect. -- Paul W. Frields, RHCE From arau at schleese.com Fri Nov 21 14:12:04 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Fri, 21 Nov 2003 09:12:04 -0500 Subject: Anaconda documents In-Reply-To: <1069423262.4902.38.camel@london.east.gov> Message-ID: That's great thanks. But the anaconda docs volunteer group needs to agree on a way of doing it: 1. Are we going to use the documentation project way or 2. are we using Akbar's sourceforge page? Any thoughts? AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Paul W. Frields Sent: 21 November 2003 09:01 To: fedora-docs-list at redhat.com Subject: RE: Anaconda documents On Thu, 2003-11-20 at 15:14, Alexander Rau (work) wrote: > Took my lunch break to look into the creation of fedora-docs. And I have to > agree with Taylor: > > "Taking a look at the Documentation project site, I see that I need > Docbook XML, stylesheets, Emacs PSGML (or NXML), etc. What is the > learning curve for these? I have never done XML, and I am not an Emacs > user (sorry to start a flamewar). Perhaps I could write the text and > someone with more knowledge of XML/Emacs could put it into the right > format. I am not unwilling to learn XML/Emacs, but my time might be > spent better elsewhere." > > This is very discouraging!! Alexander, Don't get discouraged; it's not nearly as hard as it seems... and believe me, my first reaction was *exactly* the same. I am more than happy to help move stuff to XML, but I would encourage you to give this a try. All you need to do is: 1. Make sure you have the "Authoring and Publishing" component (from redhat-config-packages), Emacs (in the "Editors" component), and the psgml package installed. 2. Follow the Documentation Guide to set up your ~/.emacs, parse/save/load the DTD, etc. I found it easiest to simply make a copy of the example-tutorial/ folder and then strip out the content and start from there. There's not that many keystrokes you need to learn to use Emacs effectively in this way, but I will be the first to admit I still find it cumbersome. I tend to use... er, that other editor. :-) In any case, if I was better at this sort of thing I would try and make this work in LyX, which is so much easier to use it's ridiculous. As Karsten (I think) mentioned, the hard part is getting your tool of choice to write everything to file the same way as everyone else, so that when we move to a community repository, no one is stepping on others' toes. To reiterate though, I will be happy to edit XML if you decide this is too painful. :-) -- Paul W. Frields, RHCE -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From twaugh at redhat.com Fri Nov 21 14:15:28 2003 From: twaugh at redhat.com (Tim Waugh) Date: Fri, 21 Nov 2003 14:15:28 +0000 Subject: html-nochunks, and PDF papersize In-Reply-To: <1069423614.4902.43.camel@london.east.gov> References: <1069423614.4902.43.camel@london.east.gov> Message-ID: <20031121141527.GL9702@redhat.com> On Fri, Nov 21, 2003 at 09:06:54AM -0500, Paul W. Frields wrote: > And, just to show my blissful ignorance, can anyone tell me how to > get my PDF's to build as US-letter size instead of A4? I am using > FC1 and simply don't know enough about xmlto or the rest of the > DocBook-XML toolset to figure this out. I've tried a number of > things already and none appear to have any effect. The paper size is decided by xmlto "magically" by looking at your locale. So if you set your locale to one that uses US Letter size (for example en_US.UTF-8), you should get US Letter size output. Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From arau at schleese.com Fri Nov 21 14:16:27 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Fri, 21 Nov 2003 09:16:27 -0500 Subject: anaconda documentation topics In-Reply-To: Message-ID: I have started on a topic for the anaconda-docs: ============================================================= Rebuilding source RPMS mini how-to (Taylor, you will recognize most of your work is from you in here!) When attempting to make changes to the anaconda source (and other source packages) there are two ways to do this: patching or untar/tar. 1. Patching source rpms First, install the src.rpm and build it with any patches already included: rpm -ivh anaconda-9.0-4.src.rpm cd /usr/src/redhat/SPEC rpmbuild -bp anaconda.spec Now, go to the BUILD directory and make an original copy of the source directory. cd /usr/src/redhat/BUILD cp -a anaconda-9.0 anaconda-9.0.orig Then go to the anaconda-9.0 directory and make any changes that you deem necessary. Once you are finished, make a patch of the differences between the two (make sure you are in the BUILD directory): diff -urN anaconda-9.0.orig anaconda-9.0 > ../SOURCES/my-changes.patch Now edit the spec file and rebuild: cd /usr/src/redhat/SPECS gedit anaconda-9.0 under Source: anaconda-%{PACKAGE_VERSION}.tar.bz2, add this line: Patch1: my-changes.patch under %setup -q, add this line: %patch1 -p1 under %changelog, add a few lines stating what changes you made. The first line should be date/name/email, the following lines should be about the changes that you made. Save the file, and run: rpmbuild -ba anaconda.spec (make sure you are in /usr/src/redhat/SPECS) which will create a new src.rpm (in /usr/src/redhat/SRPMS), as well as the binary i386.rpm files (in /usr/src/redhat/RPMS/i386). 2. The untar/tar way The second method involves untarring the source, retarring it and rebuilding the rpm: cd /usr/src/redhat/SOURCES tar xjvf anaconda-9.0.tar.bz2 tar cjvf anaconda-9.0.tar.bz2 anaconda-9.0 cd /usr/src/redhat/SPEC rpmbuild -ba anaconda.spec This method is probably simpler for the newbie, but it lacks the portability of the patch method. The advantage of the patching method is that this means that it is easier to send out a patch to others than it is to send out the src.rpm file. It is also easier when the next version of anaconda comes out to port patches over to the new release (if it hasn't been fixed in the newer version). Most people start out using the tar method, and found that it was much easier to use patches. Often you have to make changes to a newer version, and forgotten exactly what had been done in the source. Now, you can just look at the patches, and copy them over to the newer version. ================================================================== What do you guys think? AR Alexander Rau, Dipl.-Betriebswirt, A+, MCP, MCSA, MCSE, CISSP -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Alexander Rau (work) Sent: 21 November 2003 06:28 To: fedora-docs-list at redhat.com Subject: anaconda documentation topics Well, I had a quick glance through my notes and I think I will try to start on: 3. What is needed to re-build anaconda (disk space, packages) (requirements) 7. Set up your build environment (tree structures needed and so on) and 9. Step by step walkthrough the whole buildinstall process (since I just went through the whole thing!) But I will wait till we are approved at sourceforge and until Taylor had a chance to improve the TOC. I will also try to contact Brian to see if we could mention his kickstart-tools that were so valuable for making my distro. AR -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From paul at frields.com Fri Nov 21 14:44:19 2003 From: paul at frields.com (Paul W. Frields) Date: Fri, 21 Nov 2003 09:44:19 -0500 Subject: html-nochunks, and PDF papersize In-Reply-To: <20031121141527.GL9702@redhat.com> References: <1069423614.4902.43.camel@london.east.gov> <20031121141527.GL9702@redhat.com> Message-ID: <1069425859.4902.51.camel@london.east.gov> On Fri, 2003-11-21 at 09:15, Tim Waugh wrote: > > And, just to show my blissful ignorance, can anyone tell me how to > > get my PDF's to build as US-letter size instead of A4? I am using > > FC1 and simply don't know enough about xmlto or the rest of the > > DocBook-XML toolset to figure this out. I've tried a number of > > things already and none appear to have any effect. > > The paper size is decided by xmlto "magically" by looking at your > locale. So if you set your locale to one that uses US Letter size > (for example en_US.UTF-8), you should get US Letter size output. Hmm, my /etc/sysconfig/i18n contains: LANG="en_US.UTF-8" ...which also seems to be in my user environment as expected (both $LANG and $LANGVAR). If I set LC_ALL, this works. Is LANG not appropriate for taking care of this? -- Paul W. Frields, RHCE From twaugh at redhat.com Fri Nov 21 15:20:24 2003 From: twaugh at redhat.com (Tim Waugh) Date: Fri, 21 Nov 2003 15:20:24 +0000 Subject: html-nochunks, and PDF papersize In-Reply-To: <1069425859.4902.51.camel@london.east.gov> References: <1069423614.4902.43.camel@london.east.gov> <20031121141527.GL9702@redhat.com> <1069425859.4902.51.camel@london.east.gov> Message-ID: <20031121152024.GA6829@redhat.com> On Fri, Nov 21, 2003 at 09:44:19AM -0500, Paul W. Frields wrote: > Hmm, my /etc/sysconfig/i18n contains: > > LANG="en_US.UTF-8" > > ...which also seems to be in my user environment as expected (both $LANG > and $LANGVAR). If I set LC_ALL, this works. Is LANG not appropriate for > taking care of this? 'locale' will tell you what locale LC_PAPER picks up. Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From paul at frields.com Fri Nov 21 15:48:00 2003 From: paul at frields.com (Paul W. Frields) Date: Fri, 21 Nov 2003 10:48:00 -0500 Subject: html-nochunks, and PDF papersize In-Reply-To: <20031121152024.GA6829@redhat.com> References: <1069423614.4902.43.camel@london.east.gov> <20031121141527.GL9702@redhat.com> <1069425859.4902.51.camel@london.east.gov> <20031121152024.GA6829@redhat.com> Message-ID: <1069429680.4902.53.camel@london.east.gov> On Fri, 2003-11-21 at 10:20, Tim Waugh wrote: > > Hmm, my /etc/sysconfig/i18n contains: > > > > LANG="en_US.UTF-8" > > > > ...which also seems to be in my user environment as expected (both $LANG > > and $LANGVAR). If I set LC_ALL, this works. Is LANG not appropriate for > > taking care of this? > > 'locale' will tell you what locale LC_PAPER picks up. I get 'en-US.UTF-8' for everything except LC_ALL. -- Paul W. Frields, RHCE From ed at redhat.com Fri Nov 21 19:07:47 2003 From: ed at redhat.com (Edward C. Bailey) Date: Fri, 21 Nov 2003 14:07:47 -0500 Subject: Anaconda documents In-Reply-To: <3FBD3D69.7050304@dslextreme.com> (Akbar S. Ahmed's message of "Thu, 20 Nov 2003 14:17:13 -0800") References: <3FBD3D69.7050304@dslextreme.com> Message-ID: >>>>> "Akbar" == Akbar S Ahmed writes: Akbar> Alexander Rau (work) wrote: >> It would be great if we had one destination where we could collect on >> publish our working documents Akbar> I can think of three possible solutions: 1. Red Hat could open rw Akbar> access to a CVS or Subversion repository (but from the site it will Akbar> be a while b4 this happens) This is in the works (the hardware has been procured, and configuration/location/etc is being worked on). However, it is still going to take some time, as some big hurdles remain -- how to manage things on this machine, and how to keep things in sync with existing internal Red Hat infrastructure, for instance... Ed -- Ed Bailey Red Hat, Inc. http://www.redhat.com/ From ed at redhat.com Fri Nov 21 19:10:46 2003 From: ed at redhat.com (Edward C. Bailey) Date: Fri, 21 Nov 2003 14:10:46 -0500 Subject: Anaconda documents In-Reply-To: <1069370710.29919.29.camel@bad.jf.intel.com> (ForrestX Taylor's message of "Thu, 20 Nov 2003 15:25:11 -0800") References: <1069370710.29919.29.camel@bad.jf.intel.com> Message-ID: >>>>> "Taylor," == Taylor, ForrestX writes: Taylor,> Tammy/Karsten/Tim/etc., Well, I guess I'm "etc", but you can call me "Ed" :-) Taylor,> Does Red Hat have a method to collaborate on documents yet (CVS, Taylor,> web, etc.)? This is something that needs to be discussed if the Taylor,> documents are being written by more than one person. We use CVS internally (on the Red Hat Enterprise Linux documentation). My understanding is that CVS will be used for the Fedora project as well... Ed -- Ed Bailey Red Hat, Inc. http://www.redhat.com/ From ed at redhat.com Fri Nov 21 19:14:31 2003 From: ed at redhat.com (Edward C. Bailey) Date: Fri, 21 Nov 2003 14:14:31 -0500 Subject: Anaconda documents In-Reply-To: (Alexander Rau's message of "Fri, 21 Nov 2003 09:12:04 -0500") References: Message-ID: >>>>> "Alexander" == Alexander Rau (work) writes: Alexander> That's great thanks. But the anaconda docs volunteer group Alexander> needs to agree on a way of doing it: Alexander> 1. Are we going to use the documentation project way or 2. are Alexander> we using Akbar's sourceforge page? Alexander> Any thoughts? Well, since you asked, here's my $0.02... ;-) My feeling is that if you want to get started *right now*, you could go with Akbar's solution. Long-term, though, you'd probably want to move to the project's CVS server, as this would simplify integrating your documentation with the distribution proper... Ed -- Ed Bailey Red Hat, Inc. http://www.redhat.com/ From arau at schleese.com Fri Nov 21 19:33:20 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Fri, 21 Nov 2003 14:33:20 -0500 Subject: Anaconda documents In-Reply-To: Message-ID: Ed: Thanks for your $0.02 and I think you are right to think longterm if the project should succeed. Here is a problem I have and I know I will get ripped apart for that: I mostly have time in between projects at work (while the network is doing maintenance or the server is being backed up...). Unfortunately, I have not been able to convince management to implement Linux in our workstations (we have one server running linux). So when I get a window of opportunity to participate I am sitting on M$ windowz machine. Are/is the tools/software available for M$ XP? In order for me to participate the submission process needs to be hassle free and hopefully available for a M$ environment. Thanks AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Edward C. Bailey Sent: 21 November 2003 14:15 To: fedora-docs-list at redhat.com Subject: Re: Anaconda documents >>>>> "Alexander" == Alexander Rau (work) writes: Alexander> That's great thanks. But the anaconda docs volunteer group Alexander> needs to agree on a way of doing it: Alexander> 1. Are we going to use the documentation project way or 2. are Alexander> we using Akbar's sourceforge page? Alexander> Any thoughts? Well, since you asked, here's my $0.02... ;-) My feeling is that if you want to get started *right now*, you could go with Akbar's solution. Long-term, though, you'd probably want to move to the project's CVS server, as this would simplify integrating your documentation with the distribution proper... Ed -- Ed Bailey Red Hat, Inc. http://www.redhat.com/ -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From forrestx.taylor at intel.com Fri Nov 21 19:33:05 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 21 Nov 2003 11:33:05 -0800 Subject: Anaconda documents In-Reply-To: References: <1069370710.29919.29.camel@bad.jf.intel.com> Message-ID: <1069443184.5365.19.camel@bad.jf.intel.com> On Fri, 2003-11-21 at 11:10, Edward C. Bailey wrote: > >>>>> "Taylor," == Taylor, ForrestX writes: > > Taylor,> Tammy/Karsten/Tim/etc., > > Well, I guess I'm "etc", but you can call me "Ed" :-) Sorry, Ed. I didn't mean to leave you out. I never was a good speller ;o) > > Taylor,> Does Red Hat have a method to collaborate on documents yet (CVS, > Taylor,> web, etc.)? This is something that needs to be discussed if the > Taylor,> documents are being written by more than one person. > > We use CVS internally (on the Red Hat Enterprise Linux documentation). My > understanding is that CVS will be used for the Fedora project as well... Alright. Thanks. Forrest -- From forrestx.taylor at intel.com Fri Nov 21 19:34:34 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 21 Nov 2003 11:34:34 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069443274.5365.22.camel@bad.jf.intel.com> On Fri, 2003-11-21 at 11:14, Edward C. Bailey wrote: > >>>>> "Alexander" == Alexander Rau (work) writes: > > Alexander> That's great thanks. But the anaconda docs volunteer group > Alexander> needs to agree on a way of doing it: > > Alexander> 1. Are we going to use the documentation project way or 2. are > Alexander> we using Akbar's sourceforge page? > > Alexander> Any thoughts? > > Well, since you asked, here's my $0.02... ;-) > > My feeling is that if you want to get started *right now*, you could go > with Akbar's solution. Long-term, though, you'd probably want to move to > the project's CVS server, as this would simplify integrating your > documentation with the distribution proper... I agree. For now, let's go with Akbar's SourceForge repository, and we will move it over to Fedora Project CVS when Red Hat gets it setup. Forrest -- From forrestx.taylor at intel.com Fri Nov 21 19:51:03 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 21 Nov 2003 11:51:03 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069444263.5365.28.camel@bad.jf.intel.com> On Fri, 2003-11-21 at 11:33, Alexander Rau (work) wrote: > Ed: > > Thanks for your $0.02 and I think you are right to think longterm if the > project should succeed. > > Here is a problem I have and I know I will get ripped apart for that: > > I mostly have time in between projects at work (while the network is doing > maintenance or the server is being backed up...). Unfortunately, I have not > been able to convince management to implement Linux in our workstations (we > have one server running linux). So when I get a window of opportunity to > participate I am sitting on M$ windowz machine. Are/is the tools/software > available for M$ XP? > > In order for me to participate the submission process needs to be hassle > free and hopefully available for a M$ environment. If, like Ed said, they are going to use a CVS repository, you will be able to get the tools for Microsoft Windows. I recommend you get cygwin from http://www.cygwin.com, and install cvs. Cygwin is a command-line terminal for MS Windows. You can install ssh, vi, emacs, cvs, etc. on your workstation. I have also seen people use WinCVS (http://www.wincvs.org/), which is a GUI frontend for CVS. Forrest -- From pantz at lqt.ca Fri Nov 21 20:00:49 2003 From: pantz at lqt.ca (Paul Pianta) Date: Fri, 21 Nov 2003 15:00:49 -0500 Subject: Anaconda documents In-Reply-To: References: Message-ID: <3FBE6EF1.5090909@lqt.ca> Alexander Rau (work) wrote: >Are/is the tools/software >available for M$ XP? > > vmware? m$ virtual pc? (running linux) and does anyone know if 'conglomerate' is at a useable state yet for working on the doc? It looks like a promising project and it seems like it could make things alot easier regarding writing the doc. i would also like to say that i would probably serve the project better as a proof-reader, rather than creating sections for the doc. My experience with anaconda was limited and it was a while ago. However i'm keen to learn more and offer my help in whatever way i can. Call on me when you need me ... From ed at redhat.com Fri Nov 21 20:06:16 2003 From: ed at redhat.com (Edward C. Bailey) Date: Fri, 21 Nov 2003 15:06:16 -0500 Subject: Anaconda documents In-Reply-To: (Alexander Rau's message of "Fri, 21 Nov 2003 14:33:20 -0500") References: Message-ID: >>>>> "Alexander" == Alexander Rau (work) writes: Alexander> Ed: Thanks for your $0.02 and I think you are right to think Alexander> longterm if the project should succeed. Well, I'm a bit more hopeful than that. :-) Besides, whether people outside of Red Hat believe it or not, the Fedora project is considered *vitally* important to Red Hat's future. I've have seen comments by people claiming that Fedora Core is "abandonware", but I can state that this is categorically untrue. Alexander> Here is a problem I have and I know I will get ripped apart for Alexander> that: Alexander> I mostly have time in between projects at work (while the Alexander> network is doing maintenance or the server is being backed Alexander> up...). Unfortunately, I have not been able to convince Alexander> management to implement Linux in our workstations (we have one Alexander> server running linux). So when I get a window of opportunity to Alexander> participate I am sitting on M$ windowz machine. Are/is the Alexander> tools/software available for M$ XP? A quick google on "windows cvs client" returns some interesting hits. ;-) I have also seen posts on various Emacs-related newsgroups about people using Emacs under Windows, so the basics are covered. As for validating and/or producing HTML from XML on your Windows box, I don't know, but even if you couldn't do this yourself, I would imagine that you could pair up with someone with the necessary environment to help you... And to be honest, if you let psgml-mode (or that other mode mentioned here whose name I don't recall) handle insertion of tags and atrributes for you, validation errors should be relatively few and far between. Ed -- Ed Bailey Red Hat, Inc. http://www.redhat.com/ From forrestx.taylor at intel.com Fri Nov 21 18:32:08 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 21 Nov 2003 10:32:08 -0800 Subject: anaconda documentation topics In-Reply-To: References: Message-ID: <1069439528.5365.16.camel@bad.jf.intel.com> On Fri, 2003-11-21 at 06:16, Alexander Rau (work) wrote: > I have started on a topic for the anaconda-docs: > > 2. The untar/tar way > > What do you guys think? > > AR Looks good. One question though--do we even want to mention the untar/tar method? It is probably easier for the novice, but I think that we should be encouraging better methods. It may also be confusing to the novice to try to read both methods and then decide which one to use. I vote for the patch method. What do you all think? Forrest -- From tfox at redhat.com Fri Nov 21 21:21:10 2003 From: tfox at redhat.com (Tammy Fox) Date: Fri, 21 Nov 2003 16:21:10 -0500 Subject: Anaconda documents In-Reply-To: <1069370710.29919.29.camel@bad.jf.intel.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> Message-ID: <20031121212110.GB12282@redhat.com> On Thu, Nov 20, 2003 at 03:25:11PM -0800, Taylor, ForrestX wrote: > On Thu, 2003-11-20 at 14:08, Alexander Rau (work) wrote: > > 1. Well, I will check my notes from when I went through the whole process > > and then I will see what I can contribute. I will let you know tomorrow. > > Okay. > > > 2. I would also appreciate honest feedback from you guys on my writing and > > grammar since English is not my first language. Maybe I can, once we are > > finished!!, translate the whole caboodle into German. > > No problem. You write better than most native English speakers. > > > 3. I am wondering if it wouldn't be helpful to get Jeremy on board!? > > Yes, it would. Although, he just posted to the anaconda list explaining > why he hasn't. He did say, however, he would look over the documents > once they exist. > > I'll look over your TOC, expand on it, and write up a few notes > tonight. I guess that I'll post it to the list for now. > > Tammy/Karsten/Tim/etc., > > Does Red Hat have a method to collaborate on documents yet (CVS, web, > etc.)? This is something that needs to be discussed if the documents > are being written by more than one person. > http://fedora.redhat.com/participate/ This page was recently updated to let people know that the external CVS server will be available by the end of the year. I wish it was available now because everyone is eager to start and it is much easier to colloborate if you can see other people's changes instantly. Tammy > Thanks, > > Forrest > > From tfox at redhat.com Fri Nov 21 21:24:55 2003 From: tfox at redhat.com (Tammy Fox) Date: Fri, 21 Nov 2003 16:24:55 -0500 Subject: html-nochunks, and PDF papersize In-Reply-To: <1069423614.4902.43.camel@london.east.gov> References: <1069423614.4902.43.camel@london.east.gov> Message-ID: <20031121212455.GC12282@redhat.com> Sure. That is a reasonable request. I'll do this and rename the English XML files with the *-en.xml names this weekend. Cheers, Tammy On Fri, Nov 21, 2003 at 09:06:54AM -0500, Paul W. Frields wrote: > Tammy, if it's not too much trouble, could you also add the following to > the Makefile for people who need single HTML files for whatever reason: > > html-nochunks: > @xmlto html-nochunks $(XMLFILE) > > And, just to show my blissful ignorance, can anyone tell me how to get > my PDF's to build as US-letter size instead of A4? I am using FC1 and > simply don't know enough about xmlto or the rest of the DocBook-XML > toolset to figure this out. I've tried a number of things already and > none appear to have any effect. > > -- > Paul W. Frields, RHCE > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From forrestx.taylor at intel.com Fri Nov 21 21:58:50 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 21 Nov 2003 13:58:50 -0800 Subject: Anaconda documents In-Reply-To: <1069443274.5365.22.camel@bad.jf.intel.com> References: <1069443274.5365.22.camel@bad.jf.intel.com> Message-ID: <1069451929.5365.157.camel@bad.jf.intel.com> I basically wrote my notes in the TOC, but this is what I have. I added the notes from Alexander, and I have question marks near the things that I don't know about. Forrest ???TOC I.Introduction Red Hat Installation Program (Anaconda) Anaconda is the installation program for Red Hat distributions. During installation, the system's hardware is identified and configured, and the appropriate file systems for the system's architecture are created. Finally, it allows the user to install the operating system software on the system. Optionally, it can upgrade existing Red Hat installations. Anaconda can run in a fully interactive mode (text or graphical), or in a kickstart mode, which is allows the installation to be scripted for unattended operation. This makes deploying hundreds or thousands of systems very easy. Anaconda is written in Python and C, and is distributed under the GPL. The graphical frontend is written with PyGtk. Using a scripting language (Python) for the majority of the code allows for easily distribution of updates and the quick development of new features. II.How anaconda works A. boot process B. actual anaconda process i. probing for hardware (what is happening behind the scenes/what programs are doing what) ii. language selection iii. harddrive setup III. Installation IV. What is needed to rebuild anaconda A. Disk space 30-45 MB B. Required packages i. rpm-build (for /usr/src/redhat/*) ii. pump-devel (add something for RHEL about missing -devel packages) iii. kudzu-devel, pciutils-devel, bzip2-devel, e2fsprogs-devel, python-devel, gtk2-devel, rpm-python, newt-devel, rpm-devel, gettext, modutils-devel, rhpl, booty, libxml2-python, zlib-devel, bogl-devel, bogl-bterm, elfutils-devel, beecrypt-devel, dietlibc, parted (plus dependencies: Xfree86-devel, atk-devel, glib2-devel, pango-devel, bogl, gd, fontconfig-devel, freetype-devel) C. Required patches i. Patch for buildinstall (dies when trying to run buildinstall the second time) ii. Patch for changing RedHat to Fedora iii. Patch for new files (build-fc1, mkfedora-cd*, etc.) D. Time (on my Intel Pentium III 600 Mhz processor 256 MB RAM) i. rpmbuild -bp anaconda.spec ??? 0:11 ii. rpmbuild -bb anaconda.spec ??? 4:48 iii. rpmbuild -ba anaconda.spec ??? 4:49 V. Tree structure ??? about 2GB for the distribution without SRPMS (4GB with SRPMS), plus another 2GB (4GB with SRPMS) for the iso images. A. /fedora (I usually create a directory in a partition that has room, and then create a symlink for /fedora) B. /fedora/i386 ??? RPM packages C. /fedora/SRPMS ??? SRPM packages D. /fedora/build-fc1 ??? build script E. /fedora/new/new ??? directory for new and updated packages F. /fedora/RHupdates ??? directory for testing updated anaconda files VI. Anaconda binaries (just quick explanation with details in later chapters) A. buildinstall ??? script that builds the distribution B. checkcards.py ??? ?? C. checkisomd5 ??? see implantiosmd5 D. check-repository.py ??? old script that was used to check the repository for missing dependencies ??? we need to check if this still works FIX-ME It does not work for me even after changing RedHat to Fedora. It seems to need the original comps file (not comps.xml). Talk to Jeremy about getting it removed or replaced. E. filtermoddeps ??? ?? F. genhdlist ??? script that generated the hdlist (you must use the full path to your directories) G. getkeymaps ??? ?? H. implantiosmd5/checkisomd5 ??? script to implant/check the md5 sum used during installation to verify the discs (mediacheck boot option) I. libunicode-lite.so.1 ??? some library J. loader/ ??? directory that contains the loader programs K. makestamp.py ??? script that makes the .discinfo? L. mapshdr ??? ?? M. mk-images* ??? architecture-specific scripts that are called by buildinstall N. mk-rescueimage.i386 ??? creates the rescue image? O. moddeps ??? modify dependencies? P. modlist ??? modify list? Q. pkgorder ??? creates a package order???now called by buildinstall R. pyiosmd5sum.so ??? used by implantiosmd5/checkisomd5? S. pythondeps ??? python dependencies T. readmap ??? Read map? U. screenfont-i386.gz ??? fonts for the installer? V. scrubtree ??? scrub the installation tree???called by buildinstall W. splittree.py ??? formerly splitdistro???used to split the distribution into discs X. trimmodmap/trimpcitable ??? trim the modmap/pcitable? Y. upd-instroot ??? called by buildinstall???actual function?? Z. EXTRAS (that I use) i. build-fc1 ??? runs the needed scripts to generate a distribution ii. mkdvd ??? creates a DVD iso image iii. mkfedora-cd* ??? creates CD iso images iv. rpmupdates ??? copies the new/updated RPMs in /fedora/new/new to the installation area and moves out the old RPMs. VII. Mini HowTo editing and making rpms from source A. We need to decide if we are going to encourage using root to rebuild, or if we should document how to setup a build environment for a standard user. We have to be root to install rpms, so I guess that we should just do it as root B. Remove debug packages i. echo "%debug_package %{nil}" >> /root/.rpmmacros C. Let's show an example for anaconda i. Install the source rpm file a) rpm -ivh anaconda-9.2-2.src.rpm (notice the src.rpm extension) ii. Rebuild the original anaconda with any patches included a) cd /usr/src/redhat/SPEC b) rpmbuild -bp anaconda.spec iii. Go to the BUILD directory and make a copy of the original directory a) cd /usr/src/redhat/BUILD b) cp -a anaconda-9.0 anaconda-9.0.orig iv. Make your changes in the anaconda-9.0 directory v. Return to the BUILD directory and make a patch of the changes a) cd /usr/src/redhat/BUILD b) diff -urN anaconda-9.0.orig anaconda-9.0 > \ ../SOURCES/my-changes.patch vi. Edit the spec file and rebuild a) cd /usr/src/redhat/SPECS b) Edit anaconda.spec Below Source: anaconda-%{PACKAGE_VERSION}.tar.bz2, add this line: Patch1: my-changes.patch Below %setup -q, add this line: %patch1 -p1 Below %changelog, add a few lines about what you did, using the same format as you see there. You will need to change the %{date} (if it exists) to a real date. To get the real date that it was created, run this command and replace the %{date} line with this output (this is the output that I get) rpm -qp --changelog anaconda-9.2-2.src.rpm | head -1 * Thu Oct 30 2003 Anaconda team c) rpmbuild -ba anaconda.spec This will create the anaconda source rpm in /usr/src/redhat/SPMS, and the anaconda and anaconda-runtime i386.rpm files in /usr/src/redhat/RPMS/i386 (assuming that you use x86) d) Copy the binary files to /fedora/new/new, and the source file to /fedora/SRPMS. Run rpmupdates to copy the new files to the installation tree. VIII. Set up your build environment (tree structures needed and so on) A. Look at V. IX. The comps.xml chapter (explanation and making your own comps.xml) A. Formerly, we had the comps tarball as explained on the anaconda site, but now, it looks like we should just edit /fedora/i386/base/comps.xml directly. X. Step by step walkthrough the whole buildinstall process A. Running build-fc1 B. Time to build (35 minutes on my Dual Intel Pentium III 500MHz with 1GB RAM) XI. Splitting distros A. I have a seperate script for this. i. rm -rf i386-disc[123456789] (otherwise splittree.py will complain) ii. splittree.py --arch=i386 --total-discs=3 --bin-discs=3 \ --src-discs=1 --release-string=???Fedora Core 1??? --pkgorderfile=pkgfile --distdir=i386 --srcdir=SRPMS --productpath=Fedora XII. burning distros mkisofs A. I use a script for mkisofs i. genhdlist --withnumbers --fileorder pkgfile \ /fedora/i386-disc[123] ii. mkisofs -b isolinux/isolinux.bin -c isolinux/boot.cat -J -p \ ???my at email.address.com??? -V ???Fedora Core 1 with updates disc 1??? \ -r -T -v -A ???Fedora Core Linux/i386 1??? \ fedoracore1-disc1.iso -no-emul-boot -boot-load-size 4 \ -boot-info-table i386-disc1 iii. implantisomd5 --supported-iso fedoracore1-disc1.iso B. I use xcdroast to burn the iso images???recommend using CD-RWs XIII. How to test anaconda without burning discs A. anaconda --test -m nfs:/fedora/i386 (you don't need to run an NFS server for this to work, although it is easy to setup NFS and it is easy to do a network installation) XIV. Links and useful tools XV. Acknowledgements A. Jeremy Katz, et al. B. Alexander Rau From jvilla at isdesigndev.com Fri Nov 21 22:29:18 2003 From: jvilla at isdesigndev.com (Jonathan Villa) Date: Fri, 21 Nov 2003 16:29:18 -0600 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069453757.5974.31.camel@in-hoc-vince> >Besides, whether people outside of Red Hat believe it or not, the >Fedora project is considered *vitally* important to Red Hat's >future. >From what I've seen, alot of these are scoffers who have not even seen a single Fedora screenshot. When I installed yarrow, I was amazed and still am at how much RedHat it is. From my use, I don't see any changes except for enhancements. I use it as my day to day OS in a Windows environment at work, which includes document collaboration, development, and meetings. Alexander>I have not been able to convince management to implement Alexander>Linux in our workstations (we have one server running Alexander>linux). So when I get a window of opportunity to Alexander>participate... I salute you... That is what I have been trying to. I have helped with some dual boot installations and some people have even taken my installation CD's home to install at home, but I'm trying to show that a linux workstation can plug right in. On Fri, 2003-11-21 at 14:06, Edward C. Bailey wrote: > >>>>> "Alexander" == Alexander Rau (work) writes: > > Alexander> Ed: Thanks for your $0.02 and I think you are right to think > Alexander> longterm if the project should succeed. > > Well, I'm a bit more hopeful than that. :-) Besides, whether people > outside of Red Hat believe it or not, the Fedora project is considered > *vitally* important to Red Hat's future. I've have seen comments by people > claiming that Fedora Core is "abandonware", but I can state that this is > categorically untrue. > > Alexander> Here is a problem I have and I know I will get ripped apart for > Alexander> that: > > Alexander> I mostly have time in between projects at work (while the > Alexander> network is doing maintenance or the server is being backed > Alexander> up...). Unfortunately, I have not been able to convince > Alexander> management to implement Linux in our workstations (we have one > Alexander> server running linux). So when I get a window of opportunity to > Alexander> participate I am sitting on M$ windowz machine. Are/is the > Alexander> tools/software available for M$ XP? > > A quick google on "windows cvs client" returns some interesting hits. ;-) > I have also seen posts on various Emacs-related newsgroups about people > using Emacs under Windows, so the basics are covered. > > As for validating and/or producing HTML from XML on your Windows box, I > don't know, but even if you couldn't do this yourself, I would imagine that > you could pair up with someone with the necessary environment to help > you... > > And to be honest, if you let psgml-mode (or that other mode mentioned here > whose name I don't recall) handle insertion of tags and atrributes for you, > validation errors should be relatively few and far between. > > Ed From tfox at redhat.com Fri Nov 21 22:43:02 2003 From: tfox at redhat.com (Tammy Fox) Date: Fri, 21 Nov 2003 17:43:02 -0500 Subject: html-nochunks, and PDF papersize In-Reply-To: <1069423614.4902.43.camel@london.east.gov> References: <1069423614.4902.43.camel@london.east.gov> Message-ID: <20031121224302.GD12282@redhat.com> This won't process the existing XSLT. I'll make an XSLT that does no chunks instead of chunks and then add the target. Tam On Fri, Nov 21, 2003 at 09:06:54AM -0500, Paul W. Frields wrote: > Tammy, if it's not too much trouble, could you also add the following to > the Makefile for people who need single HTML files for whatever reason: > > html-nochunks: > @xmlto html-nochunks $(XMLFILE) > > And, just to show my blissful ignorance, can anyone tell me how to get > my PDF's to build as US-letter size instead of A4? I am using FC1 and > simply don't know enough about xmlto or the rest of the DocBook-XML > toolset to figure this out. I've tried a number of things already and > none appear to have any effect. > > -- > Paul W. Frields, RHCE > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From forrestx.taylor at intel.com Fri Nov 21 22:44:53 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 21 Nov 2003 14:44:53 -0800 Subject: nxml-mode for Emacs In-Reply-To: <20031117152959.GH5686@redhat.com> References: <20031117152959.GH5686@redhat.com> Message-ID: <1069454692.6888.0.camel@bad.jf.intel.com> On Mon, 2003-11-17 at 07:29, Tim Waugh wrote: > Emacs users might find this interesting: > > http://www.xmlhack.com/read.php?item=2061 > > Packages are here: > > ftp://people.redhat.com/twaugh/docbook/nxml-mode So, how does on start using nXML mode after installing the rpm? Thanks, Forrest From tfox at redhat.com Fri Nov 21 22:45:42 2003 From: tfox at redhat.com (Tammy Fox) Date: Fri, 21 Nov 2003 17:45:42 -0500 Subject: filename In-Reply-To: <20031121134821.GA10230@redhat.com> References: <3fbdbf3a.4542%ml@elf.no-ip.org> <20031121134821.GA10230@redhat.com> Message-ID: <20031121224542.GE12282@redhat.com> Done. I tested the guides, and they still build. Let me know if you see any problems. Tam On Fri, Nov 21, 2003 at 08:48:22AM -0500, Tammy Fox wrote: > Good point. I will make such corrections in CVS. > > Cheers, > Tammy > > On Fri, Nov 21, 2003 at 04:31:06PM +0900, Tadashi Jokagi wrote: > > Hi, > > > > It is a question about fedora-docs. > > Almost all the file names of fedora-docs do not correspond to multilingual. > > > > ex) > > documentation-guide/documentation-guide.xml > > developer-guide/developers-guide.xml > > > > Originally you should be as follows. > > > > ex) > > documentation-guide/documentation-guide-en.xml > > developer-guide/developers-guide-en.xml > > > > Is such correction made? > > > > ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 > > Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org > > Yokukitana http://elf.no-ip.org/ > > Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ > > > > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From gavin.henry at magicfx.co.uk Mon Nov 24 00:03:22 2003 From: gavin.henry at magicfx.co.uk (G Henry) Date: Mon, 24 Nov 2003 00:03:22 +0000 Subject: nxml-mode for Emacs In-Reply-To: <1069454692.6888.0.camel@bad.jf.intel.com> References: <20031117152959.GH5686@redhat.com> <1069454692.6888.0.camel@bad.jf.intel.com> Message-ID: <200311240003.27343.gavin.henry@magicfx.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 21 Nov 2003 10:44 pm, Taylor, ForrestX wrote: > On Mon, 2003-11-17 at 07:29, Tim Waugh wrote: > > Emacs users might find this interesting: > > > > http://www.xmlhack.com/read.php?item=2061 > > > > Packages are here: > > > > ftp://people.redhat.com/twaugh/docbook/nxml-mode > > So, how does on start using nXML mode after installing the rpm? > > Thanks, > > Forrest Load up a xml file and see!! :-) then type

References: <1069443274.5365.22.camel@bad.jf.intel.com> Message-ID: <3FBEA2B0.8050708@dslextreme.com> Taylor, ForrestX wrote: > I agree. For now, let's go with Akbar's SourceForge repository, and we > will move it over to Fedora Project CVS when Red Hat gets it setup. So here's the scoop, Sourceforge rejected the project for some reason (their site does not say why). I'm going to setup a server here, but I'll need a day or two to get hardware, configure everything, etc. Sorry about the delay. Thanks, Akbar From akbar501 at dslextreme.com Fri Nov 21 23:48:15 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Fri, 21 Nov 2003 15:48:15 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <3FBEA43F.8010202@dslextreme.com> Alexander Rau (work) wrote: > In order for me to participate the submission process needs to be hassle > free and hopefully available for a M$ environment. There is no problem in using these tools from Windows AFAIK. You can download GNU Emacs for Windows from here: http://ftp.gnu.org/gnu/windows/emacs/ I also like Textpad. It's not free, but at $25 who's complaining. It has the ability to do Unix \r\n end of line characters. Also, you can setup WinCVS for CVS access. All of the Windows developers at Delixus (my company) use WinCVS and find it very easy to use. You can download WinCVS from here: http://www.wincvs.org/download.html - Akbar From linux at bytebot.net Sat Nov 22 02:26:09 2003 From: linux at bytebot.net (Colin Charles) Date: Sat, 22 Nov 2003 13:26:09 +1100 Subject: Anaconda documents In-Reply-To: <1069356986.28841.2246.camel@erato.phig.org> References: <1069350318.28747.16.camel@bad.jf.intel.com> <1069356986.28841.2246.camel@erato.phig.org> Message-ID: <1069376208.9027.14.camel@hermione> On Fri, 2003-11-21 at 06:36, Karsten Wade wrote: > One editor I am keeping my eye on is http://www.conglomerate.org/. They > are thinking in novel ways that make using a GUI editor tempting. OpenOffice.org can export as an XML based document, as long as you have the Java stuff compiled in (so a default Fedora install will not be able to do it; either get the src.rpm's and recompile, or go ahead and download from www.openoffice.org). Is the support from OpenOffice.org's DocBook XML export feature good enough? -- Colin Charles, byte at aeon.com.my http://www.bytebot.net/ From kwade at redhat.com Mon Nov 24 08:13:15 2003 From: kwade at redhat.com (Karsten Wade) Date: 24 Nov 2003 00:13:15 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069661593.28841.11085.camel@erato.phig.org> On Fri, 2003-11-21 at 11:33, Alexander Rau (work) wrote: > In order for me to participate the submission process needs to be hassle > free and hopefully available for a M$ environment. Well, that's a difficult request; however, if M$ would just release their source code under a truly free license, then we could make building Fedora documentation under Windows hassle free. :-) ;-) If you have access to a Linux box from remote, such as one running at your home on broadband, you could try this method: 1. If you don't have an SSH client supplied on your Windows machine by your employer, grab a copy of PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/); this FL/OSS application has an SSH client, does SFTP, SCP and can support SSH tricks such as tunneling. 2. Shell into a remote Linux box (such as a Fedora Core install) where you have the FDP toolchain running. 3. Run your Emacs session as 'emacs -nw'; if you run it in a screen session, you provide yourself good protection against network or Windows problems messing up your work (see the screen manual page for more information). The best things about this method? * Your work is protected from any number of problems which are more likely to occur than a Fedora box going down -- network problems, power outages, Windows BSOD, etc. * The setup is considerably easier than getting cygwin, Emacs, cvs and ssh running under Win32. * You are safely doing your personal volunteer work on a remote system under your control, and not belonging to your employer. Then they have a harder time, for example, claiming copyright over anything you write while "on the clock". Of course, IANAL, so don't take this as advice on how to work on personal projects while on your employer's time. ^o_O^ - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From paul at frields.com Mon Nov 24 12:43:33 2003 From: paul at frields.com (Paul W. Frields) Date: Mon, 24 Nov 2003 07:43:33 -0500 Subject: html-nochunks, and PDF papersize In-Reply-To: <20031121224302.GD12282@redhat.com> References: <1069423614.4902.43.camel@london.east.gov> <20031121224302.GD12282@redhat.com> Message-ID: <1069677813.3630.1.camel@london.east.gov> On Fri, 2003-11-21 at 17:43, Tammy Fox wrote: > This won't process the existing XSLT. I'll make an XSLT that does no > chunks instead of chunks and then add the target. Thanks. I did notice the difference, but I thought that was intentional (i.e. produces a single HTML file with no external graphics/dependencies, etc.). In retrospect I guess that seems silly. :-) -- Paul W. Frields, RHCE From paul at frields.com Mon Nov 24 12:47:43 2003 From: paul at frields.com (Paul W. Frields) Date: Mon, 24 Nov 2003 07:47:43 -0500 Subject: anaconda documentation topics In-Reply-To: <1069439528.5365.16.camel@bad.jf.intel.com> References: <1069439528.5365.16.camel@bad.jf.intel.com> Message-ID: <1069678063.3630.5.camel@london.east.gov> On Fri, 2003-11-21 at 13:32, Taylor, ForrestX wrote: > On Fri, 2003-11-21 at 06:16, Alexander Rau (work) wrote: > > I have started on a topic for the anaconda-docs: > > > > 2. The untar/tar way > > > > What do you guys think? > > Looks good. One question though--do we even want to mention the > untar/tar method? It is probably easier for the novice, but I think > that we should be encouraging better methods. It may also be confusing > to the novice to try to read both methods and then decide which one to > use. I vote for the patch method. What do you all think? I agree that the patch method is the superior one. One thing you might also want to include is giving the user info on customizing %release to keep their custom RPMs distinct from the original Fedora versions. Just a thought.... -- Paul W. Frields, RHCE From brilong at cisco.com Mon Nov 24 16:33:31 2003 From: brilong at cisco.com (Brian Long) Date: Mon, 24 Nov 2003 11:33:31 -0500 Subject: anaconda documentation topics In-Reply-To: <1069439528.5365.16.camel@bad.jf.intel.com> References: <1069439528.5365.16.camel@bad.jf.intel.com> Message-ID: <1069691611.9135.57.camel@localhost.localdomain> > Looks good. One question though--do we even want to mention the > untar/tar method? It is probably easier for the novice, but I think > that we should be encouraging better methods. It may also be confusing > to the novice to try to read both methods and then decide which one to > use. I vote for the patch method. What do you all think? Patch. /Brian/ -- Brian Long Cisco Systems From dpawson at nildram.co.uk Mon Nov 24 16:39:54 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 24 Nov 2003 16:39:54 +0000 Subject: Anaconda documents In-Reply-To: <1069370710.29919.29.camel@bad.jf.intel.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> Message-ID: <6.0.0.22.2.20031124163925.026681d0@pop3.Nildram.co.uk> At 23:25 20/11/2003, Taylor, ForrestX wrote: >Does Red Hat have a method to collaborate on documents yet (CVS, web, >etc.)? This is something that needs to be discussed if the documents >are being written by more than one person. Anyone thought of using a wiki for this? regards DaveP From arau at schleese.com Mon Nov 24 16:47:49 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Mon, 24 Nov 2003 11:47:49 -0500 Subject: anaconda documentation topics In-Reply-To: <1069691611.9135.57.camel@localhost.localdomain> Message-ID: Patch vs. tar/untar method: Now that I have gone through the building process I have to agree with you guys that the patch method is the one to go with. However, when I was standing at the bottom of this high mountain I wanted to climb, I appreciated having both alternatives available to me (especially the tar/untar method made the mountain look a bit smaller). I also appreciated the explanation between the two methods Taylor offered, which then helped me to make a decision between the two (and this helped me understand the processes better, which I think should also be a goal of our how-to, not just a simple follow line by line recipe to make your own distro but provide learning options and understanding on how the install process really works!) Anyways, I assume that this is a democratic project and if it comes to a vote a will vote for the patch method for all the earlier mentioned reasons. -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Brian Long Sent: 24 November 2003 11:34 To: fedora-docs-list at redhat.com Subject: RE: anaconda documentation topics > Looks good. One question though--do we even want to mention the > untar/tar method? It is probably easier for the novice, but I think > that we should be encouraging better methods. It may also be confusing > to the novice to try to read both methods and then decide which one to > use. I vote for the patch method. What do you all think? Patch. /Brian/ -- Brian Long Cisco Systems -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From ml at elf.no-ip.org Mon Nov 24 17:02:37 2003 From: ml at elf.no-ip.org (Tadashi Jokagi) Date: Tue, 25 Nov 2003 02:02:37 +0900 Subject: filename In-Reply-To: <20031121224542.GE12282@redhat.com> References: <3fbdbf3a.4542%ml@elf.no-ip.org> <20031121134821.GA10230@redhat.com> <20031121224542.GE12282@redhat.com> Message-ID: <3fc239ad.2143%ml@elf.no-ip.org> Hi, Thanks your works. Regard. Tammy Fox's<20031121224542.GE12282 at redhat.com> wrote: >Done. I tested the guides, and they still build. Let me know if you >see any problems. > >Tam > >On Fri, Nov 21, 2003 at 08:48:22AM -0500, Tammy Fox wrote: >> Good point. I will make such corrections in CVS. >> >> Cheers, >> Tammy >> >> On Fri, Nov 21, 2003 at 04:31:06PM +0900, Tadashi Jokagi wrote: >> > Hi, >> > >> > It is a question about fedora-docs. >> > Almost all the file names of fedora-docs do not correspond to >multilingual. >> > >> > ex) >> > documentation-guide/documentation-guide.xml >> > developer-guide/developers-guide.xml >> > >> > Originally you should be as follows. >> > >> > ex) >> > documentation-guide/documentation-guide-en.xml >> > developer-guide/developers-guide-en.xml >> > >> > Is such correction made? >> > >> > ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 >> > Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org >> > Yokukitana http://elf.no-ip.org/ >> > Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ >> > >> > >> >> >> -- >> fedora-docs-list mailing list >> fedora-docs-list at redhat.com >> http://www.redhat.com/mailman/listinfo/fedora-docs-list > >-- > > >-- >fedora-docs-list mailing list >fedora-docs-list at redhat.com >http://www.redhat.com/mailman/listinfo/fedora-docs-list -- ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Setagaya city mailto:elf at elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/ From arau at schleese.com Mon Nov 24 17:11:29 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Mon, 24 Nov 2003 12:11:29 -0500 Subject: Anaconda documents In-Reply-To: <1069451929.5365.157.camel@bad.jf.intel.com> Message-ID: Taylor: Your TOC is fantastic. It gets better by the minute. We desperately need a central repository to get properly started. It looks like everybody is highly motivated but without the proper setup I am worried the wind in our sails will be dying down soon. AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Taylor, ForrestX Sent: 21 November 2003 16:59 To: fedora-docs-list at redhat.com Subject: Re: Anaconda documents I basically wrote my notes in the TOC, but this is what I have. I added the notes from Alexander, and I have question marks near the things that I don't know about. Forrest ???TOC I.Introduction Red Hat Installation Program (Anaconda) Anaconda is the installation program for Red Hat distributions. During installation, the system's hardware is identified and configured, and From dpawson at nildram.co.uk Mon Nov 24 17:49:34 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 24 Nov 2003 17:49:34 +0000 Subject: Anaconda documents In-Reply-To: <1069356986.28841.2246.camel@erato.phig.org> References: <1069350318.28747.16.camel@bad.jf.intel.com> <1069356986.28841.2246.camel@erato.phig.org> Message-ID: <6.0.0.22.2.20031124174809.02697610@pop3.Nildram.co.uk> At 19:36 20/11/2003, Karsten Wade wrote: > > Are there non-Emacs solutions available for this?? > >Any editor will suffice, but unless you have an intimate knowledge of >DocBook XML, you will find it difficult to use an editor which does not >have a mode similar to PSGML or nXML. What might help is www.docbook.org http://www.docbook.org/tdg/en/html/docbook.html specifically. Helps with markup. regards DaveP From dpawson at nildram.co.uk Mon Nov 24 17:54:29 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 24 Nov 2003 17:54:29 +0000 Subject: nxml-mode for Emacs In-Reply-To: <15180000.1069393479@shieldbreaker.l33tskillz.org> References: <20031117152959.GH5686@redhat.com> <76650000.1069307388@shieldbreaker.l33tskillz.org> <6.0.0.22.2.20031120155125.025e5cd0@pop3.Nildram.co.uk> <15180000.1069393479@shieldbreaker.l33tskillz.org> Message-ID: <6.0.0.22.2.20031124175403.025af6d8@pop3.Nildram.co.uk> At 05:44 21/11/2003, you wrote: >Sorry about that; I wrote the first thing that came to my mind, which >probably made little sense to most people here (given the >international scope of this list). My apologies. > >What I was trying to say was that the nxml-mode package provides many >useful features, and makes it much easier to write XML-based >documents. I've only been testing it out for an hour or so total, but >already it seems to be overwhelmingly superior to the other packages >I've tried. :) Thanks James :-) And I agree 100% btw. regards DaveP From forrestx.taylor at intel.com Mon Nov 24 18:09:03 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Mon, 24 Nov 2003 10:09:03 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069697300.24399.2.camel@bad.jf.intel.com> Yes, I agree. Our enthusiasm will curb shortly. I have requested a new project on savannah.gnu.org. They should let us know today if we can host it there. I'll let you know as soon as I hear anything. Hopefully we'll be able to find a site to host this on so that Akbar does not have to host it individually.\ Forrest -- On Mon, 2003-11-24 at 09:11, Alexander Rau (work) wrote: > Taylor: > > Your TOC is fantastic. It gets better by the minute. > > We desperately need a central repository to get properly started. It looks > like everybody is highly motivated but without the proper setup I am worried > the wind in our sails will be dying down soon. > > AR > > > > -----Original Message----- > From: fedora-docs-list-admin at redhat.com > [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Taylor, ForrestX > Sent: 21 November 2003 16:59 > To: fedora-docs-list at redhat.com > Subject: Re: Anaconda documents > > I basically wrote my notes in the TOC, but this is what I have. I added > the notes from Alexander, and I have question marks near the things that > I don't know about. > > Forrest > > > > ??????TOC > > I.Introduction > > Red Hat Installation Program (Anaconda) > Anaconda is the installation program for Red Hat distributions. During > installation, the system's hardware is identified and configured, and > > From dpawson at nildram.co.uk Mon Nov 24 17:59:49 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 24 Nov 2003 17:59:49 +0000 Subject: Anaconda documents In-Reply-To: <1069444263.5365.28.camel@bad.jf.intel.com> References: <1069444263.5365.28.camel@bad.jf.intel.com> Message-ID: <6.0.0.22.2.20031124175820.025b6eb0@pop3.Nildram.co.uk> At 19:51 21/11/2003, you wrote: > > In order for me to participate the submission process needs to be hassle > > free and hopefully available for a M$ environment. > >If, like Ed said, they are going to use a CVS repository, you will be >able to get the tools for Microsoft Windows. I recommend you get cygwin >from http://www.cygwin.com, and install cvs. CVS can be driven from win32 OS's. Cygwin is an option, there are others for those that are Redmond bound, for whatever reason. emacs, docbook etc all work well too surprisingly. regards DaveP From dpawson at nildram.co.uk Mon Nov 24 18:06:46 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Mon, 24 Nov 2003 18:06:46 +0000 Subject: Anaconda documents In-Reply-To: <1069661593.28841.11085.camel@erato.phig.org> References: <1069661593.28841.11085.camel@erato.phig.org> Message-ID: <6.0.0.22.2.20031124180319.0259f7e0@pop3.Nildram.co.uk> At 08:13 24/11/2003, Karsten Wade wrote: >On Fri, 2003-11-21 at 11:33, Alexander Rau (work) wrote: > > > In order for me to participate the submission process needs to be hassle > > free and hopefully available for a M$ environment. > >Well, that's a difficult request; I've never found sharing XML instances with Linux users and windows users hard work. Its one advantage of XML. >If you have access to a Linux box from remote, such as one running at >your home on broadband, you could try this method: >3. Run your Emacs session as 'emacs -nw'; if you run it in a screen >session, you provide yourself good protection against network or Windows >problems messing up your work (see the screen manual page for more >information). Putty is pretty good at screwing up a display. Particularly if utf-8 is used. >* The setup is considerably easier than getting cygwin, Emacs, cvs and >ssh running under Win32. emacs runs happily under windows. If anyone has a problem setting it up I've been there done that. Both for psgml and nxml-mode regards DaveP From brilong at cisco.com Mon Nov 24 18:41:43 2003 From: brilong at cisco.com (Brian Long) Date: Mon, 24 Nov 2003 13:41:43 -0500 Subject: Anaconda documents In-Reply-To: References: Message-ID: <1069699303.23844.4.camel@brilong-lnx2.cisco.com> Guys, I missed the initial discussion about Abkar and Sourceforge, but I could create a new directory in my CVS repository at kickstart-tools.sf.net. I would then have to add folks to the kickstart-tools project and allow you to commit into that new directory. Thoughts? /Brian/ On Mon, 2003-11-24 at 12:11, Alexander Rau (work) wrote: > Taylor: > > Your TOC is fantastic. It gets better by the minute. > > We desperately need a central repository to get properly started. It looks > like everybody is highly motivated but without the proper setup I am worried > the wind in our sails will be dying down soon. > > AR > > > > -----Original Message----- > From: fedora-docs-list-admin at redhat.com > [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Taylor, ForrestX > Sent: 21 November 2003 16:59 > To: fedora-docs-list at redhat.com > Subject: Re: Anaconda documents > > I basically wrote my notes in the TOC, but this is what I have. I added > the notes from Alexander, and I have question marks near the things that > I don't know about. > > Forrest > > > > ???TOC > > I.Introduction > > Red Hat Installation Program (Anaconda) > Anaconda is the installation program for Red Hat distributions. During > installation, the system's hardware is identified and configured, and > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s From arau at schleese.com Mon Nov 24 19:26:47 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Mon, 24 Nov 2003 14:26:47 -0500 Subject: Anaconda documents In-Reply-To: <1069699303.23844.4.camel@brilong-lnx2.cisco.com> Message-ID: Let's wait till Taylor hears back from savannah.gnu.org!? AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Brian Long Sent: 24 November 2003 13:42 To: fedora-docs-list at redhat.com Cc: forrestx.taylor at intel.com Subject: RE: Anaconda documents Guys, I missed the initial discussion about Abkar and Sourceforge, but I could create a new directory in my CVS repository at kickstart-tools.sf.net. I would then have to add folks to the kickstart-tools project and allow you to commit into that new directory. Thoughts? /Brian/ From akbar501 at dslextreme.com Mon Nov 24 19:52:19 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Mon, 24 Nov 2003 11:52:19 -0800 Subject: Anaconda documents In-Reply-To: References: Message-ID: <3FC26173.50805@dslextreme.com> Alexander Rau (work) wrote: > Let's wait till Taylor hears back from savannah.gnu.org!? Brian Long wrote: > I missed the initial discussion about Abkar and Sourceforge, but I could > create a new directory in my CVS repository at kickstart-tools.sf.net. > I would then have to add folks to the kickstart-tools project and allow > you to commit into that new directory. Just let me know what you'd like to do. I have the hardware ready and the OS installed. CVS pserver is up and running and I'm just working on locking it down. Should be finished today, but the gnu or sf sites would probably be better hosts. So, if either of those are possibilities then they would take priority over my solution. Thanks, Akbar From arau at schleese.com Mon Nov 24 20:09:08 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Mon, 24 Nov 2003 15:09:08 -0500 Subject: Anaconda documents In-Reply-To: <3FC26173.50805@dslextreme.com> Message-ID: Could we get started on yours and then transfer it over to whoever is able to host the project? AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Akbar S. Ahmed Sent: 24 November 2003 14:52 To: fedora-docs-list at redhat.com Cc: forrestx.taylor at intel.com; 'Brian Long' Subject: Re: Anaconda documents Alexander Rau (work) wrote: > Let's wait till Taylor hears back from savannah.gnu.org!? Brian Long wrote: > I missed the initial discussion about Abkar and Sourceforge, but I could > create a new directory in my CVS repository at kickstart-tools.sf.net. > I would then have to add folks to the kickstart-tools project and allow > you to commit into that new directory. Just let me know what you'd like to do. I have the hardware ready and the OS installed. CVS pserver is up and running and I'm just working on locking it down. Should be finished today, but the gnu or sf sites would probably be better hosts. So, if either of those are possibilities then they would take priority over my solution. Thanks, Akbar -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From forrestx.taylor at intel.com Mon Nov 24 20:20:33 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Mon, 24 Nov 2003 12:20:33 -0800 Subject: Anaconda documents In-Reply-To: <3FC26173.50805@dslextreme.com> References: <3FC26173.50805@dslextreme.com> Message-ID: <1069705232.24399.15.camel@bad.jf.intel.com> On Mon, 2003-11-24 at 11:52, Akbar S. Ahmed wrote: > Alexander Rau (work) wrote: > > Let's wait till Taylor hears back from savannah.gnu.org!? > > Brian Long wrote: > > > I missed the initial discussion about Abkar and Sourceforge, but I could > > create a new directory in my CVS repository at kickstart-tools.sf.net. > > I would then have to add folks to the kickstart-tools project and allow > > you to commit into that new directory. > > Just let me know what you'd like to do. I have the hardware ready and > the OS installed. CVS pserver is up and running and I'm just working on > locking it down. Should be finished today, but the gnu or sf sites would > probably be better hosts. So, if either of those are possibilities then > they would take priority over my solution. If you can get your solution setup today, let's start it there, and we can move it to savannah if/when it gets approved. As Alexander pointed out, the sooner we get this started, the better. Thanks, Forrest From kwade at redhat.com Tue Nov 25 00:05:49 2003 From: kwade at redhat.com (Karsten Wade) Date: 24 Nov 2003 16:05:49 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <20031121212110.GB12282@redhat.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> Message-ID: <1069718748.28841.12425.camel@erato.phig.org> On Fri, 2003-11-21 at 13:21, Tammy Fox wrote: > http://fedora.redhat.com/participate/ > > This page was recently updated to let people know that the external > CVS server will be available by the end of the year. I wish it was > available now because everyone is eager to start and it is much easier > to colloborate if you can see other people's changes instantly. For easing transition of external CVS maintained projects, is there anything about the construction of the Fedora Project CVS which is unique? Suggestions for module naming, construction, and practices, repository structure, branching dangers, etc.? Nothing is obvious to me from reading: http://fedora.redhat.com/participate/documentation-guide/ch-cvs.html This information would be useful creating standalone CVS repositories which are easily integrated when the main FP CVS is available. On a related topic, if anyone does put together a CVS repository of documentation and you make it available for anonymous CVS access, I'll be happy to mirror your repository until the main FP CVS is available. - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From akbar501 at dslextreme.com Tue Nov 25 00:09:35 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Mon, 24 Nov 2003 16:09:35 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <1069718748.28841.12425.camel@erato.phig.org> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> Message-ID: <3FC29DBF.4090209@dslextreme.com> Karsten Wade wrote: > On a related topic, if anyone does put together a CVS repository of > documentation and you make it available for anonymous CVS access, I'll > be happy to mirror your repository until the main FP CVS is available. I have finished setting up the CVS repository for Anaconda docs. As a heads up, it is a pserver that uses stunnel to encrypt the traffic. I have created an RPM to help you install the stunnel bridge (it is very easy :) ) I will also put up the SRPM for those who need to rebuild on something other than Fedora. I'll send a link to a page of setup instructions, plus my GPG key so you can encrypt the username and password that you want me to add to the cvs users list. BTW, you can cut and paste your encrypted password from /etc/shadow, but please create a new cvs only password. Thanks, Akbar From hugo at devin.com.br Tue Nov 25 02:09:47 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Mon, 24 Nov 2003 23:09:47 -0300 Subject: Brazilian Portuguese Message-ID: <3FC2B9EB.2090409@devin.com.br> Hi guys, Any brazilian guys here? We need to organize ourselves to begin working :) Please reply if you're interested in translating Fedora into pt_BR. []'s Hugo From lsdr at lsdr.net Tue Nov 25 05:05:16 2003 From: lsdr at lsdr.net (Luiz Rocha) Date: Tue, 25 Nov 2003 03:05:16 -0200 Subject: Brazilian Portuguese In-Reply-To: <3FC2B9EB.2090409@devin.com.br> References: <3FC2B9EB.2090409@devin.com.br> Message-ID: <200311250300.00671.lsdr@lsdr.net> > Any brazilian guys here? We need to organize ourselves to begin working > :) Please reply if you're interested in translating Fedora into pt_BR. Hey, I am brazillian. But what kind of translations? Docs or i18n? As far as I'm concerned there is already lots of pt_BR i18n for Fedora, which was inherited from RH. But those last months have been a little turbulent for me and I have been a little off what is going on in the fedora-docs and I can't really tell you much what is going on... :) Perhaps Tammy Fox can brief you better. I wonder if there is already a CVS repository for translations and other docs. Oh, and I almost forgot. You might want to talk to Daniel Brooke Peig (he can be reached at www.brookepeig.com). I read somewhere that he also want to do some work too, so would be great to invite him to join the list. BTW, Tammy: I didn't give up on the Configuring PDA tutorial, it is just that I haven't had much time later. I hope I can post a draft soon, for peer review. -- Luiz Rocha From hugo at devin.com.br Tue Nov 25 05:14:41 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Tue, 25 Nov 2003 02:14:41 -0300 Subject: Brazilian Portuguese In-Reply-To: <200311250300.00671.lsdr@lsdr.net> References: <3FC2B9EB.2090409@devin.com.br> <200311250300.00671.lsdr@lsdr.net> Message-ID: <3FC2E541.7000108@devin.com.br> Luiz Rocha wrote: >>Any brazilian guys here? We need to organize ourselves to begin working >>:) Please reply if you're interested in translating Fedora into pt_BR. > > Hey, I am brazillian. Ol?! :) > But what kind of translations? Docs or i18n? As far as I'm concerned there > is already lots of pt_BR i18n for Fedora, which was inherited from RH. Both... I want to first work on revision of .po files for i18n because I still see many Portuguese from Portugal grammar in the pt_BR language. It's a little annoying. > But those last months have been a little turbulent for me and I have been a > little off what is going on in the fedora-docs and I can't really tell you > much what is going on... :) Perhaps Tammy Fox can brief you better. > > I wonder if there is already a CVS repository for translations and other > docs. Yes, they gave the right directions on accessing CVS repository for the translations. Search for the thread with the subject: Issues related to translation I already got my account, and I want to begin working. > Oh, and I almost forgot. You might want to talk to Daniel Brooke Peig (he > can be reached at www.brookepeig.com). I read somewhere that he also want to > do some work too, so would be great to invite him to join the list. Hummm... I will contact him. He should subscribe here too... > -- > Luiz Rocha []'s Hugo From akbar501 at dslextreme.com Tue Nov 25 07:18:02 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Mon, 24 Nov 2003 23:18:02 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <3FC29DBF.4090209@dslextreme.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> <3FC29DBF.4090209@dslextreme.com> Message-ID: <3FC3022A.1020606@dslextreme.com> Hi, CVS is setup and ready to go. I think we should be able to get everything into CVS today without any problems. All we need now is a CVS directory structure and to decide who will do what. I'll also add anonymous access soon for mirroring purposes. Here's the scoop. There are 5 easy steps to get you setup to connect to the CVS server. 1. Please send me an email with your desired username and password. Use the crypt() function to encrypt your password, or just take one out of /etc/shadow. It would probably be best if you could import my PGP key to your email client and send me an encrypted email with the user name and password. I have placed my public key at the end of this file, you can also get it from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search String". At this point I'll add you to the CVS users list. 2. Go to http://www.delixus.com/downloads/ccvssh/ (sorry about the advertisement on the page) and read the directions. Just download ccvssh-0.9.1-1.i586.rpm and install it. I followed 3rd party practice and put the binary in a subdirectory of /opt. The RPM and SRPM are signed with the Delixus corporate GPG key so you can verify the integrity of the packages (assuming you trust me as a reliable source). Please note: I only created an RPM for Fedora, but I also put up the SRPM so you can easily rebuild the CCVSSH client. It is GPL BTW. Also, let me know if you need it rebuilt for another OS and I'll try to get it done. 3. Setup environment variables in your .bash_profile file. See http://www.delixus.com/downloads/ccvssh/ for instructions. 4. Login to the CVS server. 5. Use standard CVS commands to interact with the server, but enjoy encrypted communication with the server FYI: I'll be out of the office until approx. 9:30 AM PST tomorrow, but will get to the username/password requests ASAP. This software is fairly cool. It redirects pserver traffic over SSL using stunnel. It gives the best of both pserver and the SSH ext method. It should be very easy to setup, but if not just send me a complaint email and I'll see if I can help. Thanks, Akbar My personal public key: Public key for 0xCF3FC7AB4FF3176F -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.3 (MingW32) mQGiBD/C0u8RBACmfRBaKBC1qrmTz18XcsP0NOgZRzFeE1aC85DcyO56MhQGxiI5 r3tApdMmKrq8n6K/0X16A8ilH45vi9vv4hjhD/qVrmhz0ko8sr7mEk7xA7dATX/Z QMMqdpQl1fc5X+3sYzgL1ZoOH7RQaV8f1WDVWpKJt/vkISkoXYk/dq6yIwCg4jTZ f7SnVG35Y/VSxNg5ZHz6AIkEAKSeNnoo6jgYv1Uk5CS+Pk0Laema5j/ZgYUhz3cC tAk4f9GaFWpx3X5WkolCz4jsj6zv4OSe8UQocqTwxEw6nV1sTavg9oi6l9qPnjjz XUNy6EzmrW9f3ggNptur10TTYT0aZLzScZyzyfs+IbQoaLu9rq0DERRBpN10YoXJ Pb2wBACW6DWzgR4V1/1t6vdA2b8LzOetTPNNPGbUHiVU18u6kwMCcd7chu1rcDAK Paobb6o0UUPic5JymOLR/KPg7kj1t2ZaiNSxeZdWS8ZcMumzMEzMwwoiEIomLgUB NH7Eb9YPuz0dXdK1blR9Co2eBCw/M+FVrjU3krd81YcRlbrJr7ROQWtiYXIgUy4g QWhtZWQgKFBlcnNvbmFsIEdQRyBrZXkgZm9yIEFrYmFyIFMuIEFobWVkKSA8YWti YXI1MDFAZHNsZXh0cmVtZS5jb20+iFsEExECABsFAj/C0u8GCwkIBwMCAxUCAwMW AgECHgECF4AACgkQzz/Hq0/zF2+b7wCgrzu6peifPwlM3QJsISgWeHlQQW4AoL0x FQEzrtVxFTsMfDASTBC6T5QSuQENBD/C0vEQBADeRkAO2j7yAiNVvPMKrrG7Bscq dhJbzG6uxeuN8Gxc8thHb7f95Yzqa/jOpfuY3vbj+0/jGQkoKTdszkDkPSEmvMxi snLCrFBuOGLCBVUICf4Z8LI5XfBWnrvG6QTCyfVd3Vyz86XgSrv4W7O71tKhBdey bHjPDKad2Y2hkvF/jwADBwQAulAk39fHLOaXkABIYv+oWmKYKvOOgX5JCA+ZN5yK UcZWwogkWVlhL78XeXQjdlZOLif3WsDDX3EMw87y0fpUj2FMVPcrMHLzh00RnBQV RJvJHQNjBNBhyom+9ObqNGuIMir8aY3kLTi6ABc9vvZ7U1qZ2lAAqNmFklCeeAcF SiqIRgQYEQIABgUCP8LS8QAKCRDPP8erT/MXb/MBAKCjsBc+ZRnwXjxQrzCk/ANv NcBR3QCgkXWYeRo3J++pzWDPwfj8wl9eHvk= =O2m5 -----END PGP PUBLIC KEY BLOCK----- From igorvc at bol.com.br Tue Nov 25 08:58:47 2003 From: igorvc at bol.com.br (Igor Vitorio Custodio) Date: Tue, 25 Nov 2003 06:58:47 -0200 Subject: Brazilian Portuguese References: <3FC2B9EB.2090409@devin.com.br> Message-ID: <002901c3b332$56b6e7b0$0300000a@igor> Hello !!! I'm braziliam and I would like to help with any kind of translate !!! []'s ---- ------- -------- ~ Igor Vit?rio Cust?dio (igorvc) ' v ' PLACA - ENC 03 / / \ \ E-Mail: igorvc at bol.com.br / ( ) \ http://www.comp.ufscar.br/~igorvc ^ ` ~' ^ ----- Original Message ----- From: "Hugo Cisneiros" To: Sent: Tuesday, November 25, 2003 12:09 AM Subject: Brazilian Portuguese > Hi guys, > > Any brazilian guys here? We need to organize ourselves to begin working > :) Please reply if you're interested in translating Fedora into pt_BR. > > []'s > Hugo > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list > From ed at redhat.com Tue Nov 25 16:05:17 2003 From: ed at redhat.com (Edward C. Bailey) Date: Tue, 25 Nov 2003 11:05:17 -0500 Subject: CVS in the meantime In-Reply-To: <1069718748.28841.12425.camel@erato.phig.org> (Karsten Wade's message of "24 Nov 2003 16:05:49 -0800") References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> Message-ID: >>>>> "Karsten" == Karsten Wade writes: Karsten> On Fri, 2003-11-21 at 13:21, Tammy Fox wrote: >> http://fedora.redhat.com/participate/ >> >> This page was recently updated to let people know that the external CVS >> server will be available by the end of the year. I wish it was available >> now because everyone is eager to start and it is much easier to >> colloborate if you can see other people's changes instantly. Karsten> For easing transition of external CVS maintained projects, is Karsten> there anything about the construction of the Fedora Project CVS Karsten> which is unique? Suggestions for module naming, construction, and Karsten> practices, repository structure, branching dangers, etc.? Nothing Karsten> is obvious to me from reading: Karsten> http://fedora.redhat.com/participate/documentation-guide/ch-cvs.html Karsten> This information would be useful creating standalone CVS Karsten> repositories which are easily integrated when the main FP CVS is Karsten> available. ... I'll go out on a limb here and give my two cents on the matter. It would seem to me that it would be best to put some sort of hierarchy in place on the CVS server(s). At the least, put modules under something like "fedora-docs". That would at least eliminate the possibility of collisions with the software folks on the project's CVS box. As for eliminating collisions between separate docs projects, the most obvious solution is just to have everyone use the same interim CVS server... :-) Ed -- Ed Bailey Red Hat, Inc. http://www.redhat.com/ From kwade at redhat.com Tue Nov 25 18:55:19 2003 From: kwade at redhat.com (Karsten Wade) Date: 25 Nov 2003 10:55:19 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <3FC3022A.1020606@dslextreme.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> <3FC29DBF.4090209@dslextreme.com> <3FC3022A.1020606@dslextreme.com> Message-ID: <1069786519.6254.3.camel@erato.phig.org> On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote: > 1. Please send me an email with your desired username and password. Use > the crypt() function to encrypt your password, or just take one out of > /etc/shadow. /sbin/grub-md5-crypt will encrypt your password admirably. -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Enterprise Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From gose at mcs.anl.gov Tue Nov 25 20:06:44 2003 From: gose at mcs.anl.gov (Scott Gose) Date: Tue, 25 Nov 2003 14:06:44 -0600 Subject: emacs sgml Message-ID: <20031125200644.GD15936@mcs.anl.gov> Hello, I'm having trouble getting sgml to work in emacs. I'm getting the same error as this user here: http://www.redhat.com/archives/fedora-docs-list/2003-October/msg00046.html I installed all the emacs, docbook and sgml packages I could find. But I still get the error: XML requires a system ID after a public ID This is when I invoke xemacs like this: [144 13:33 gose at winters:~/fedora-docs/documentation-guide] xemacs documentation-guide-en.xml And run 'DTD -> Parse DTD'. Any ideas? ------------------------------------------- [root at winters gose]# rpm -qa | grep sgml sgml-common-0.6.3-14 psgml-1.2.5-1 [root at winters gose]# rpm -qa | grep emac xemacs-sumo-20031003-3 mew-xemacs-3.3-1 xemacs-sumo-el-20031003-3 emacs-leim-21.3-7 xemacs-21.4.14-3 xemacs-info-21.4.14-3 xemacs-el-21.4.14-3 xemacs-sumo-info-20031003-3 ddskk-xemacs-11.6.0-12 emacs-el-21.3-7 emacs-21.3-7 apel-xemacs-10.6-1 flim-xemacs-1.14.5-1 emacspeak-17.0-4 wl-xemacs-2.10.1-1.1 [root at winters gose]# rpm -qa | grep xml perl-libxml-perl-0.07-28 xml-common-0.6.3-14 libxml-devel-1.8.17-9 nxml-mode-0.20031031.1-0.1 libxml2-2.5.11-1 perl-libxml-enno-1.02-29 libxml-1.8.17-9 xmlto-0.0.15-1 libxml2-python-2.5.11-1 libxml2-devel-2.5.11-1 xmltex-20000118-14.1 [root at winters gose]# rpm -qa | grep docbook docbook-style-xsl-1.61.2-2.1 docbook-style-dsssl-1.78-2 docbook-dtds-1.0-22.1 docbook-utils-pdf-0.6.13-7 docbook-utils-0.6.13-7 ------------------------------------------- -- Scott Gose gose at mcs.anl.gov From tfox at redhat.com Tue Nov 25 21:11:13 2003 From: tfox at redhat.com (Tammy Fox) Date: Tue, 25 Nov 2003 16:11:13 -0500 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <3FC3022A.1020606@dslextreme.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> <3FC29DBF.4090209@dslextreme.com> <3FC3022A.1020606@dslextreme.com> Message-ID: <20031125211112.GA17407@redhat.com> On Mon, Nov 24, 2003 at 11:18:02PM -0800, Akbar S. Ahmed wrote: > Hi, > > CVS is setup and ready to go. I think we should be able to get > everything into CVS today without any problems. All we need now is a CVS > directory structure and to decide who will do what. I'll also add > anonymous access soon for mirroring purposes. > To answer Karsten's earlier question about the current CVS structure: The directory structure looks like the following: |-- common |-- css |-- developer-guide |-- documentation-guide |-- example-tutorial |-- install-guide |-- stylesheet-images `-- xsl common: contains any DocBook XML and image files shared between 2 or more documents; for example, cvs-en.xml is shared between the Developer Guide and the Documentation Guide; legalnotice-en.xml should be included in all docs css: contains the common CSS file used for the HTML versions of the documents stylesheet-images: contains the admonition graphics used in the documents xsl: contains the XSLT stylesheets used for processing the DocBook XML into different formats A directory should exist for each document, and the parent file should be the same name as the directory with the -.xml added on to it. This directory should contain a Makefile Images for each document should be in a figs directory under the directory for the document. Each document directory should contain a po directory for the translation files. (pgampe is working on this for the existing ones) All DocBook XML files should use the format -.xml. If you use this structure and use the shared file in common, we should be able to plug your files into fedora-docs once we have public access to it. A great place to start is the example-tutorial directory. It contains a template document you can start from. (Since I took the time to write this up, I'll add it to the Documentation Guide. ;-) ) Tammy > Here's the scoop. There are 5 easy steps to get you setup to connect to > the CVS server. > > 1. Please send me an email with your desired username and password. Use > the crypt() function to encrypt your password, or just take one out of > /etc/shadow. > > It would probably be best if you could import my PGP key to your email > client and send me an encrypted email with the user name and password. I > have placed my public key at the end of this file, you can also get it > from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search String". > > At this point I'll add you to the CVS users list. > > 2. Go to http://www.delixus.com/downloads/ccvssh/ (sorry about the > advertisement on the page) and read the directions. Just download > ccvssh-0.9.1-1.i586.rpm and install it. I followed 3rd party practice > and put the binary in a subdirectory of /opt. > > The RPM and SRPM are signed with the Delixus corporate GPG key so you > can verify the integrity of the packages (assuming you trust me as a > reliable source). > > Please note: I only created an RPM for Fedora, but I also put up the > SRPM so you can easily rebuild the CCVSSH client. It is GPL BTW. Also, > let me know if you need it rebuilt for another OS and I'll try to get it > done. > > 3. Setup environment variables in your .bash_profile file. > See http://www.delixus.com/downloads/ccvssh/ for instructions. > > 4. Login to the CVS server. > > 5. Use standard CVS commands to interact with the server, but enjoy > encrypted communication with the server > > FYI: I'll be out of the office until approx. 9:30 AM PST tomorrow, but > will get to the username/password requests ASAP. > > This software is fairly cool. It redirects pserver traffic over SSL > using stunnel. It gives the best of both pserver and the SSH ext method. > > It should be very easy to setup, but if not just send me a complaint > email and I'll see if I can help. > > Thanks, > Akbar > > My personal public key: > > Public key for 0xCF3FC7AB4FF3176F > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: GnuPG v1.2.3 (MingW32) > > mQGiBD/C0u8RBACmfRBaKBC1qrmTz18XcsP0NOgZRzFeE1aC85DcyO56MhQGxiI5 > r3tApdMmKrq8n6K/0X16A8ilH45vi9vv4hjhD/qVrmhz0ko8sr7mEk7xA7dATX/Z > QMMqdpQl1fc5X+3sYzgL1ZoOH7RQaV8f1WDVWpKJt/vkISkoXYk/dq6yIwCg4jTZ > f7SnVG35Y/VSxNg5ZHz6AIkEAKSeNnoo6jgYv1Uk5CS+Pk0Laema5j/ZgYUhz3cC > tAk4f9GaFWpx3X5WkolCz4jsj6zv4OSe8UQocqTwxEw6nV1sTavg9oi6l9qPnjjz > XUNy6EzmrW9f3ggNptur10TTYT0aZLzScZyzyfs+IbQoaLu9rq0DERRBpN10YoXJ > Pb2wBACW6DWzgR4V1/1t6vdA2b8LzOetTPNNPGbUHiVU18u6kwMCcd7chu1rcDAK > Paobb6o0UUPic5JymOLR/KPg7kj1t2ZaiNSxeZdWS8ZcMumzMEzMwwoiEIomLgUB > NH7Eb9YPuz0dXdK1blR9Co2eBCw/M+FVrjU3krd81YcRlbrJr7ROQWtiYXIgUy4g > QWhtZWQgKFBlcnNvbmFsIEdQRyBrZXkgZm9yIEFrYmFyIFMuIEFobWVkKSA8YWti > YXI1MDFAZHNsZXh0cmVtZS5jb20+iFsEExECABsFAj/C0u8GCwkIBwMCAxUCAwMW > AgECHgECF4AACgkQzz/Hq0/zF2+b7wCgrzu6peifPwlM3QJsISgWeHlQQW4AoL0x > FQEzrtVxFTsMfDASTBC6T5QSuQENBD/C0vEQBADeRkAO2j7yAiNVvPMKrrG7Bscq > dhJbzG6uxeuN8Gxc8thHb7f95Yzqa/jOpfuY3vbj+0/jGQkoKTdszkDkPSEmvMxi > snLCrFBuOGLCBVUICf4Z8LI5XfBWnrvG6QTCyfVd3Vyz86XgSrv4W7O71tKhBdey > bHjPDKad2Y2hkvF/jwADBwQAulAk39fHLOaXkABIYv+oWmKYKvOOgX5JCA+ZN5yK > UcZWwogkWVlhL78XeXQjdlZOLif3WsDDX3EMw87y0fpUj2FMVPcrMHLzh00RnBQV > RJvJHQNjBNBhyom+9ObqNGuIMir8aY3kLTi6ABc9vvZ7U1qZ2lAAqNmFklCeeAcF > SiqIRgQYEQIABgUCP8LS8QAKCRDPP8erT/MXb/MBAKCjsBc+ZRnwXjxQrzCk/ANv > NcBR3QCgkXWYeRo3J++pzWDPwfj8wl9eHvk= > =O2m5 > -----END PGP PUBLIC KEY BLOCK----- > > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-docs-list -- From forrestx.taylor at intel.com Tue Nov 25 22:47:03 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 25 Nov 2003 14:47:03 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <3FC3022A.1020606@dslextreme.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> <3FC29DBF.4090209@dslextreme.com> <3FC3022A.1020606@dslextreme.com> Message-ID: <1069800422.28856.15.camel@bad.jf.intel.com> On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote: > Hi, > > CVS is setup and ready to go. I think we should be able to get > everything into CVS today without any problems. All we need now is a CVS > directory structure and to decide who will do what. I'll also add > anonymous access soon for mirroring purposes. Great job, Akbar. Will you be able to host this until at least the end of the year? If not, let's go to Brian's kickstart-tools repository and set it up there. I still haven't heard back from savannah. It looks like the directory structure will be just like the Red Hat CVS repository for fedora-docs: http://fedora.redhat.com/participate/documentation-guide/ch-getting-files.html Just download the files and import them into the new repository. Tammy gave an explanation about what each of the files are and where we should put new files. Forrest From forrestx.taylor at intel.com Tue Nov 25 23:05:14 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 25 Nov 2003 15:05:14 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <3FC3022A.1020606@dslextreme.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> <3FC29DBF.4090209@dslextreme.com> <3FC3022A.1020606@dslextreme.com> Message-ID: <1069801514.28856.18.camel@bad.jf.intel.com> On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote: > 1. Please send me an email with your desired username and password. Use > the crypt() function to encrypt your password, or just take one out of > /etc/shadow. > > It would probably be best if you could import my PGP key to your email > client and send me an encrypted email with the user name and password. I > have placed my public key at the end of this file, you can also get it > from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search String". Does anyone know how to get evolution to use Akbar's PGP key? I cannot seem to find a way to import it. Thanks, Forrest From arau at schleese.com Wed Nov 26 02:48:04 2003 From: arau at schleese.com (Alexander Rau (work)) Date: Tue, 25 Nov 2003 21:48:04 -0500 Subject: CVS in the meantime (was Re: Anaconda documents) Message-ID: This PGP stuff is new to me, too I downloaded PGP. Wrote the email Copied it in the clipboard encrypted the clipboard with Akbar's key pasted the clipboard in my email to Akbar. Hope this helps AR -----Original Message----- From: fedora-docs-list-admin at redhat.com [mailto:fedora-docs-list-admin at redhat.com] On Behalf Of Taylor, ForrestX Sent: Tuesday, November 25, 2003 6:05 PM To: fedora-docs-list at redhat.com Subject: Re: CVS in the meantime (was Re: Anaconda documents) On Mon, 2003-11-24 at 23:18, Akbar S. Ahmed wrote: > 1. Please send me an email with your desired username and password. Use > the crypt() function to encrypt your password, or just take one out of > /etc/shadow. > > It would probably be best if you could import my PGP key to your email > client and send me an encrypted email with the user name and password. I > have placed my public key at the end of this file, you can also get it > from http://pgp.mit.edu/, then put "Akbar S. Ahmed" in "Search String". Does anyone know how to get evolution to use Akbar's PGP key? I cannot seem to find a way to import it. Thanks, Forrest -- fedora-docs-list mailing list fedora-docs-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list From hugo at devin.com.br Wed Nov 26 05:07:33 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Wed, 26 Nov 2003 02:07:33 -0300 Subject: Brazilian Portuguese In-Reply-To: <3FC2B9EB.2090409@devin.com.br> References: <3FC2B9EB.2090409@devin.com.br> Message-ID: <3FC43515.20907@devin.com.br> Well, three people appeared with this message. I think many people willing to contribute don't know the existence of this list... I'm thinking on creating a list devoted to this language. What do you think? It'll be better to discute translation to this specific language. Any ideas? :) I began working on CVS revising anaconda .po files... []'s Hugo Hugo Cisneiros wrote: > Hi guys, > > Any brazilian guys here? We need to organize ourselves to begin working > :) Please reply if you're interested in translating Fedora into pt_BR. From akbar501 at dslextreme.com Wed Nov 26 05:53:24 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Tue, 25 Nov 2003 21:53:24 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) In-Reply-To: <1069800422.28856.15.camel@bad.jf.intel.com> References: <1069370710.29919.29.camel@bad.jf.intel.com> <20031121212110.GB12282@redhat.com> <1069718748.28841.12425.camel@erato.phig.org> <3FC29DBF.4090209@dslextreme.com> <3FC3022A.1020606@dslextreme.com> <1069800422.28856.15.camel@bad.jf.intel.com> Message-ID: <3FC43FD4.8070702@dslextreme.com> Taylor, ForrestX wrote: > Will you be able to host this until at least the end > of the year? If not, let's go to Brian's kickstart-tools repository and > set it up there. I could host it till the end of the year, but Brian's kickstart-tools repository on sf.net would probably be better. sf.net has better bandwidth than I have here. If we switch to sf.net, when will this be done? Should we start on my system and then switch or just start with sf.net? Personally, either way is fine with me. I have a system up and running, but nobody except Alexander has send their CVS username/password. There are a few kinks that Alexander and I are working out, but I'm sure everything can be fixed. Thanks, Akbar From baldrick at terra.es Wed Nov 26 11:36:43 2003 From: baldrick at terra.es (Josep Puigdemont) Date: Wed, 26 Nov 2003 12:36:43 +0100 Subject: Translation project -- Catalan Message-ID: <1069846603.3358.339.camel@deimos> (I posted this message in fedora-devel-list at redhat.com, and I was suggested to post it this list also, so here we go!) Hi!! I have recently joined Fedora's translation project, and would like to start working on the translation to the Catalan language. I hope I am not posting to the wrong list (should I post at i18n at redhat.com?), if I do, please tell me and accept my apologies :) I have some questions: I've got CVS access, checked out "translate" module, and reviewed. Now, Catalan is a new language (there is no ca.po for any application), so to start with anaconda, for instance, I created it using msginit like this: $ msginit --locale=ca -i anaconda.pot Is that how you would normally do it? Then, once the file is translated, do I have rights to commit (and thus add a new file) into the repository, or is there someone coordinating the translation efforts that should do it? Shall I file a RFE requesting the addition of a new language, maybe? If it exists a FAQ or documentation about this, let me know! Thanks, Josep P.S.: If there are subscribers here that would like to help to translate Fedora into catalan, we're going to coordinate from http://www.softcatala.org/llistes/ (list "Fedora"). From jamesd at jml.net Wed Nov 26 17:48:59 2003 From: jamesd at jml.net (James Davis) Date: Wed, 26 Nov 2003 17:48:59 +0000 (GMT) Subject: I'd like to volunteer please... :-) Message-ID: Hello all, I've just downloaded and installed Fedora Core 1, replacing my existing RH9 setup and so far so good, I'm very impressed. I've always wanted to contribute something back to the distribution I use and feel that Fedora might be the ideal chance. Since security is the area of computing I know best (and what earns me my paycheque) I'd love to write some form of "Securing Fedora" guide. Would this be something useful to the project? I've just checked out fedora-docs from CVS and I'll start to look over those files and the documentation guide. James -- http://jamesd.ukgeeks.co.uk/ From paul at frields.com Wed Nov 26 18:32:21 2003 From: paul at frields.com (Paul W. Frields) Date: Wed, 26 Nov 2003 13:32:21 -0500 Subject: I'd like to volunteer please... :-) In-Reply-To: References: Message-ID: <1069871541.3627.85.camel@london.east.gov> On Wed, 2003-11-26 at 12:48, James Davis wrote: > Since security is the area of computing I know best (and what earns me my > paycheque) I'd love to write some form of "Securing Fedora" guide. Would > this be something useful to the project? I've just checked out fedora-docs > from CVS and I'll start to look over those files and the documentation > guide. Speaking for no one but myself, I'd say that this sounds very worthwhile. Red Hat started to produce a Security Guide in the documentation portion of later incarnations of Red Hat Linux, so a set of Fedora security guides seems like a good idea as well. I think the push has been for the Docs Project to produce small, self-contained tutorials. Perhaps in the interest of preserving continuity, the best starting point would be to think of how the security guides could be broken up... perhaps into groups like file/resource security, general host security, and service security (with each service represented separately). I could also see general IT security and incident response being covered by tutorials as well. I have a background in investigative forensic media analysis, and although I don't have a CISSP or comparable rating, this still piques my interest. :-) -- Paul W. Frields, RHCE From jamesd at jml.net Wed Nov 26 18:46:56 2003 From: jamesd at jml.net (James Davis) Date: Wed, 26 Nov 2003 18:46:56 +0000 (GMT) Subject: I'd like to volunteer please... :-) In-Reply-To: <1069871541.3627.85.camel@london.east.gov> Message-ID: On Wed, 26 Nov 2003, Paul W. Frields wrote: > I think the push has been for the Docs Project to produce small, > self-contained tutorials. Perhaps in the interest of preserving > continuity, the best starting point would be to think of how the > security guides could be broken up... perhaps into groups like > file/resource security, general host security, and service security > (with each service represented separately). I could also see general IT > security and incident response being covered by tutorials as well. I was on the bus home that perhaps a good starting point would be to cover security through installation and the first boot. For example the firewall, services, user configuration tools, the choices you have and reasons to make your choices. After that, extending to core packages directly involved with security and then to secure configuration of other common core packages. I wasn't thinking of anything along the lines of "linux security" or "general computer security" at least not in the immediate future, I think that's too much of an under taking, and likely to lose momentum. James -- http://jamesd.ukgeeks.co.uk/ From dpawson at nildram.co.uk Wed Nov 26 19:57:20 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Wed, 26 Nov 2003 19:57:20 +0000 Subject: emacs sgml In-Reply-To: <20031125200644.GD15936@mcs.anl.gov> References: <20031125200644.GD15936@mcs.anl.gov> Message-ID: <6.0.0.22.2.20031126195519.025c0860@pop3.Nildram.co.uk> At 20:06 25/11/2003, Scott Gose wrote: >Hello, > >I'm having trouble getting sgml to work in emacs. > >I'm getting the same error as this user here: > > >http://www.redhat.com/archives/fedora-docs-list/2003-October/msg00046.html > >I installed all the emacs, docbook and sgml packages I could find. >But I still get the error: > > XML requires a system ID after a public ID I.e. if you include the public id (SGML remnant) then you must also include the system id, which is the url where the Docbook DTD may be found. That could be on your system (relative, or /dir/dir/file) or on the net, if you are using a catalog. HTH DaveP From kwade at redhat.com Wed Nov 26 20:41:15 2003 From: kwade at redhat.com (Karsten Wade) Date: 26 Nov 2003 12:41:15 -0800 Subject: Fedora Docs FAQ - update 26 Nov 2003 Message-ID: <1069879275.3247.1477.camel@erato.phig.org> Please accept this humble FAQ. Please direct comments to the list, harsh criticism to me where I shall file it in its proper location. If we like this (which means no one says they don't like it?), then I'll propose either XML inclusion in the Doc Guide, or posting on the http://fedora.redhat.com/projects/docs/ page. FAQ originally proposed in http://www.redhat.com/archives/fedora-docs-list/2003-November/msg00029.html, now brought to you in living email color: ## begin FAQ Does Fedora Project need writers/editors? Yes! Writers are needed right now more then editors, until we have something to edit. What documents does FP need? FP documents are going to be of the tutorial/HOWTO variety. This is the most useful information we can gather at this time, and it works well with the distributed project. Currently, the only full-length guide is the Installation Guide. How is the docs project organized? Rather loosely right now. Tammy Fox (tfox at redhat.com) is the project leader. It has been proposed that translators can work in teams by languages. We may want to organize so that every writer has two-editors, and contributors can work in either or both roles. This makes for a more cumbersome process, but the quality control is higher. What is the process/procedure for translating documents? Details are currently outlined in this email: http://www.redhat.com/archives/fedora-docs-list/2003-November/msg00040.html What are PO files? PO files are textual, editable files used in translation. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC7 What are some of the tutorial/HOWTOs currently proposed? From the mailing list: * Installing an SSH server with public/private key authentication * Configuring and using digital cameras * Anaconda documentation (in process) * Security considerings in installation * Security other (by topic, i.e. filesystems, host, etc.) * Configuring PDA Can I translate the legal notice? The legal notice page can be translated, but a statement that the translation is provided for convenience only and that the English language version takes precedence must be on the top of the page. What are the tools for writing documents? http://fedora.redhat.com/projects/docs details how to get the Documentation Guide source and tools. The toolchain is explained on that page, with the exception of PO files (see What are PO files?). Currently, there is a problem with PDF production (refer to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104983). If you have TeX experience and can help us resolve that one, please dive in! I have a tutorial in HTML, how do I convert it to DocBook? Grab html2db from http://www.cise.ufl.edu/~ppadala/tidy/ . What are some resources for learning DocBook? The definitive DocBook reference written and maintained by Norm Walsh is available at http://docbook.org/tdg/en/html/docbook.html . A combination tutorial and reference book is available at http://www.sagehill.net/docbookxsl/index.html . Dave Pawson maintains a DocBook FAQ at http://www.dpawson.co.uk/docbook/ . Can I have CVS write access? Eventually, we intend for full contributors to have write access to CVS, as well as access to other build environments. This is being worked out across the entire Fedora Project, and is due to be completed by the end of calendar year 2003. In the meantime, you can contact the docs project leader Tammy Fox (tfox at redhat.com) with your changes. If you wish to setup your own CVS repository, or join one that others are using while waiting for the main Fedora Project CVS to be set up, please see the mail thread starting at: http://www.redhat.com/archives/fedora-docs-list/2003-November/msg00140.html What else is can I do to help? Have ideas for admonition graphics? ## 30 ## -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From paul at frields.com Wed Nov 26 21:39:16 2003 From: paul at frields.com (Paul W. Frields) Date: Wed, 26 Nov 2003 16:39:16 -0500 Subject: I'd like to volunteer please... :-) In-Reply-To: References: Message-ID: <1069882756.17563.10.camel@bettie.internal.frields.org> On Wed, 2003-11-26 at 13:46, James Davis wrote: > On Wed, 26 Nov 2003, Paul W. Frields wrote: > > > I think the push has been for the Docs Project to produce small, > > self-contained tutorials. Perhaps in the interest of preserving > > continuity, the best starting point would be to think of how the > > security guides could be broken up... perhaps into groups like > > file/resource security, general host security, and service security > > (with each service represented separately). I could also see general IT > > security and incident response being covered by tutorials as well. > > I was on the bus home that perhaps a good starting point would be to cover > security through installation and the first boot. For example the > firewall, services, user configuration tools, the choices you have and > reasons to make your choices. After that, extending to core packages > directly involved with security and then to secure configuration of other > common core packages. I wasn't thinking of anything along the lines of > "linux security" or "general computer security" at least not in the > immediate future, I think that's too much of an under taking, and likely > to lose momentum. Your points are well-taken, and you should only bite off as much as you feel it worth doing, of course. I do think that what you'll find is that with any well-written documentation, making any salient points about a fairly complex subject requires some groundwork... otherwise you are not informing the reader, simply throwing esoterica at them and hoping some of it sticks. On the other hand, the tutorial format is task-oriented. I think it's a bit of a balancing act, and the docs project will likely take some time to find the right tone, where the tutorials are short enough to read but long enough to offer some insight so that the reader is not simply following a cookbook without gaining any knowledge. I think I was not really saying that you should feel personally responsible for doing a large portion of the subject matter I mentioned; it was more a way of breaking down the task into some reasonable division. If we have an overall feeling for where each tutorial should stop, it's easier to see a larger picture as well, such as how many such tutorials the docs project might reasonably aim for in the long run. Just my $0.02, of course. -- Paul W. Frields, RHCE From hugo at devin.com.br Wed Nov 26 21:44:32 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Wed, 26 Nov 2003 18:44:32 -0300 Subject: Red Hat vs. Fedora Message-ID: <3FC51EC0.5080409@devin.com.br> Hi, I was revising the pt_BR.po file from the anaconda-po translation, and noticed that I still see many Red Hat Linux names instead of Fedora. We should leave it? For example... anaconda.pot - : ../partIntfHelpers.py:401 msgid "" "You have chosen to use a pre-existing partition for this installation " "without formatting it. Red Hat recommends that you format this partition to " "make sure files from a previous operating system installation do not cause " "problems with this installation of Linux. However, if this partition " "contains files that you need to keep, such as a users home directories, then " "you should continue without formatting this partition." msgstr "" - #: ../rescue.py:257 #, python-format msgid "" "The rescue environment will now attempt to find your Red Hat Linux " "installation and mount it under the directory %s. You can then make any " "changes required to your system. If you want to proceed with this step " "choose 'Continue'. You can also choose to mount your file systems read-only " "instead of read-write by choosing 'Read-Only'.\n" "\n" "If for some reason this process fails you can choose 'Skip' and this step " "will be skipped and you will go directly to a command shell.\n" "\n" msgstr "" - #: ../upgrade.py:475 msgid "" "This system appears to have third party packages installed that overlap with " "packages included in Red Hat Linux. Because these packages overlap, " "continuing the upgrade process may cause them to stop functioning properly " "or may cause other system instability. Please see the release notes for " "more information.\n" "\n" "Do you wish to continue the upgrade process?" msgstr "" - Call the developers? Change and commit the changes to CVS? Or just leave this alone? []'s Hugo From akbar501 at dslextreme.com Wed Nov 26 22:11:23 2003 From: akbar501 at dslextreme.com (Akbar S. Ahmed) Date: Wed, 26 Nov 2003 14:11:23 -0800 Subject: Red Hat vs. Fedora In-Reply-To: <3FC51EC0.5080409@devin.com.br> References: <3FC51EC0.5080409@devin.com.br> Message-ID: <3FC5250B.2060805@dslextreme.com> Hugo Cisneiros wrote: > I was revising the pt_BR.po file from the anaconda-po translation, and > noticed that I still see many Red Hat Linux names instead of Fedora. We > should leave it? For example... I'm not sure of the official line on this, but personnally I think we should go with Fedora. The last thing we want to do is confuse new users. Also, as we move forward I'm sure everyone will want to give Fedora its own flavor and "branding". However, work that is done by Red Hat should of course stay copyright Red Hat. Alternative opinions are welcome. - Akbar From hugo at devin.com.br Wed Nov 26 23:00:12 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Wed, 26 Nov 2003 20:00:12 -0300 Subject: Brazilian Portuguese In-Reply-To: <3FC43515.20907@devin.com.br> References: <3FC2B9EB.2090409@devin.com.br> <3FC43515.20907@devin.com.br> Message-ID: <3FC5307C.80300@devin.com.br> Hugo Cisneiros wrote: > Well, three people appeared with this message. I think many people > willing to contribute don't know the existence of this list... I'm > thinking on creating a list devoted to this language. What do you think? > It'll be better to discute translation to this specific language. Any > ideas? :) Hi, I created two lists: fedora-br fedora-i18n-br The first is for Brazilian users, and the second is for Brazilian translators. If you're interested, you can subscribe sending a blank e-mail to: fedora-br-subscribe at devin.com.br or fedora-i18n-br-subscribe at devin.com.br And wait for confirmation. Discussions will be in Brazilian Portuguese. I appreciate any feedback :) []'s Hugo From jamesd at jml.net Wed Nov 26 23:03:14 2003 From: jamesd at jml.net (James Davis) Date: Wed, 26 Nov 2003 23:03:14 +0000 (GMT) Subject: I'd like to volunteer please... :-) In-Reply-To: <1069882756.17563.10.camel@bettie.internal.frields.org> Message-ID: On Wed, 26 Nov 2003, Paul W. Frields wrote: > I do think that what you'll find is that with any well-written > documentation, making any salient points about a fairly complex subject > requires some groundwork... Agreed, I want to write something that users of Fedora will both benefit and learn from, not just read to achieve a set of objectives. > other hand, the tutorial format is task-oriented. I think it's a bit of > a balancing act I have a feeling that this may just depend on the exact subject you set for an individual tutorial. Something explaining the security implications of installation options has a lot more scope for explaining principles than say a document covering how to install/configure sudo. I think however that by approaching security from installation, first boot, up2date the documents will remain focused on Fedora and not on issues that may be seen as too general. Should I suggest a starting point of writing docs for "Keeping your Fedora installation patched" and an introduction to Fedora-security? These sound like managable sized peices of security related documentation from which the rest of our ideas can follow. James -- http://jamesd.ukgeeks.co.uk/ From polo3565 at wanadoo.fr Thu Nov 27 00:08:15 2003 From: polo3565 at wanadoo.fr (Polo3565) Date: 27 Nov 2003 01:08:15 +0100 Subject: Fedora in French is it a good idea ??? Message-ID: <1069891695.1047.10.camel@Polo> Hello all, I am ready to translate parts of documentation for Fedora project. If Developpers give me their docs to translate for french francophony, I an ready to do this.To day I use RH 9.0 and I hope that is not very different.I wait for directives (texts, paper format, size and fonts to use, ......etc).Please, contact me if you want help. Regards Yves (near Aix en Provenve) FRANCE From deathbird1981 at brturbo.com Thu Nov 27 02:14:08 2003 From: deathbird1981 at brturbo.com (deathbird1981 at brturbo.com) Date: Thu, 27 Nov 2003 00:14:08 -0200 (BRST) Subject: Help to translate for brazilian portuguese Message-ID: <17970609.1069899248576.JavaMail.nobody@webmail3.brturbo.com> Hey guys, you can count with me to translate for brazilian portuguese, ok?:) Ps.: Will be more better this discurssion in brazilian portuguese of that in english or we create an discurssion list, you don't thing? . Joao Emanuel From paul at frields.com Thu Nov 27 01:21:15 2003 From: paul at frields.com (Paul W. Frields) Date: Wed, 26 Nov 2003 20:21:15 -0500 Subject: New ENTITY declarations? Message-ID: <1069896075.18667.17.camel@bettie.internal.frields.org> Do we need a block of additional ENTITY declarations as a standard in the templates, or are they up to the tutorial authors to use? I have been removing the existing block of Red Hat-specific declarations, and replacing them with more Fedora-specific ones, such as: http://fedora.redhat.com/"> http://fedora.redhat.com/projects/docs/"> I don't see a need to standardize just for the sake of it; if this is something that authors are expected to do for themselves, that's ducky by me. I just don't want to step on any toes since I'm new to this part. :-) -- Paul W. Frields, RHCE From forrestx.taylor at intel.com Thu Nov 27 02:16:03 2003 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Wed, 26 Nov 2003 18:16:03 -0800 Subject: CVS in the meantime (was Re: Anaconda documents) Message-ID: We just got approved for a savannah project. Those interested in starting on anaconda documents, please go to http://savannah.nongnu.org and create an account (new user via SSL). You can then search for anacondadocs (or surf to http://savannah.nongnu.org/projects/anacondadocs). Send me your usernames, and I'll add you to the group. I am going on vacation for a few weeks, but I'll be checking mail on and off. I'll try to set someone else up as an administrator so that they can add accounts as well. Forrest From hugo at devin.com.br Thu Nov 27 04:16:19 2003 From: hugo at devin.com.br (Hugo Cisneiros) Date: Thu, 27 Nov 2003 01:16:19 -0300 Subject: Help to translate for brazilian portuguese In-Reply-To: <17970609.1069899248576.JavaMail.nobody@webmail3.brturbo.com> References: <17970609.1069899248576.JavaMail.nobody@webmail3.brturbo.com> Message-ID: <3FC57A93.9060101@devin.com.br> deathbird1981 at brturbo.com wrote: > Hey guys, you can count with me to translate for brazilian portuguese, ok?:) > Ps.: Will be more better this discurssion in brazilian portuguese of that in english or we create an discurssion list, you don't thing? . Hi Joao :) I set up a list for co-ordinating the work, and to discuss in our language. See this URL: http://www.redhat.com/archives/fedora-docs-list/2003-November/msg00165.html > Joao Emanuel []'s Hugo From pmal at velic.com Thu Nov 27 10:47:38 2003 From: pmal at velic.com (Philippe MALINGE) Date: Thu, 27 Nov 2003 11:47:38 +0100 Subject: Status of french translation Message-ID: <1069930058.1676.26.camel@raft.velic.com> Hello all, I checked out the 'translate' package and it seems that all fr.po files are already translated in french. Is there any coordinator on this list? What's the job not been done yet? Thanks. -- Philippe MALINGE From lsdr at lsdr.net Thu Nov 27 12:55:58 2003 From: lsdr at lsdr.net (Luiz Rocha) Date: Thu, 27 Nov 2003 10:55:58 -0200 Subject: New ENTITY declarations? In-Reply-To: <1069896075.18667.17.camel@bettie.internal.frields.org> References: <1069896075.18667.17.camel@bettie.internal.frields.org> Message-ID: <200311271056.07190.lsdr@lsdr.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 26 November 2003 23:21, Paul W. Frields wrote: > I don't see a need to standardize just for the sake of it; if this is > something that authors are expected to do for themselves, that's ducky > by me. I just don't want to step on any toes since I'm new to this part. I think is a nice idea. Not just for the sake of it, but because I think it will be useful. Writers will end up doing similar things, using similar entities, so I think establishing a standard to all docs would be a Good Thing, since it would spare the writers the time to do it again and again to every doc. My 2 cents, though. - -- Luiz Rocha -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/xfRkN2+4JlrxCYYRAkgaAKCWYB1oBA4JtT7MO0NWfhxtYbg3jACfZ4sa fLyU9M70dUAZyixtkqN5yQ4= =U5SC -----END PGP SIGNATURE----- From dpawson at nildram.co.uk Thu Nov 27 18:10:42 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Thu, 27 Nov 2003 18:10:42 +0000 Subject: Fedora Docs FAQ - update 26 Nov 2003 In-Reply-To: <1069879275.3247.1477.camel@erato.phig.org> References: <1069879275.3247.1477.camel@erato.phig.org> Message-ID: <6.0.0.22.2.20031127180853.02670150@pop3.Nildram.co.uk> At 20:41 26/11/2003, you wrote: >Please accept this humble FAQ. good start Do you want it marked up in docbook website.. a subset of docbook? Would make a start for a fedora offering? /then additions could be done in docbook qandaentry? Guidance (from redhat people?) on major divisions please... if the answer is yes. regards DaveP From dpawson at nildram.co.uk Thu Nov 27 19:00:26 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Thu, 27 Nov 2003 19:00:26 +0000 Subject: New ENTITY declarations? In-Reply-To: <1069896075.18667.17.camel@bettie.internal.frields.org> References: <1069896075.18667.17.camel@bettie.internal.frields.org> Message-ID: <6.0.0.22.2.20031127185929.02570f40@pop3.Nildram.co.uk> At 01:21 27/11/2003, you wrote: >Do we need a block of additional ENTITY declarations as a standard in >the templates, Yes please. Save's typing! They need adding to the DTD/schema IMHO. Surely there are a group from redhat that can be adopted and added to? regards DaveP From ml at elf.no-ip.org Fri Nov 28 09:35:45 2003 From: ml at elf.no-ip.org (Tadashi Jokagi) Date: Fri, 28 Nov 2003 18:35:45 +0900 Subject: mistake entity (was: filename) In-Reply-To: <20031121224542.GE12282@redhat.com> References: <3fbdbf3a.4542%ml@elf.no-ip.org> <20031121134821.GA10230@redhat.com> <20031121224542.GE12282@redhat.com> Message-ID: <3fc716f1.2171%ml@elf.no-ip.org> Hi, I thought that it would contribute to bugzilla. However, since a category was not found, it gave up;-) ENTITY has a mistake. RCS file: /usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.1 diff -r1.1 fedora-install-guide-en.xml 12c12 < --- > -- ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitawiki http://elf.no-ip.org/wiki/ Yokukitablog http://elf.no-ip.org/blog/ From dpawson at nildram.co.uk Fri Nov 28 18:05:43 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Fri, 28 Nov 2003 18:05:43 +0000 Subject: mistake entity (was: filename) In-Reply-To: <3fc716f1.2171%ml@elf.no-ip.org> References: <3fbdbf3a.4542%ml@elf.no-ip.org> <20031121134821.GA10230@redhat.com> <20031121224542.GE12282@redhat.com> <3fc716f1.2171%ml@elf.no-ip.org> Message-ID: <6.0.0.22.2.20031128180457.02622e28@pop3.Nildram.co.uk> At 09:35 28/11/2003, you wrote: >Hi, > >I thought that it would contribute to bugzilla. >However, since a category was not found, it gave up;-) >ENTITY has a mistake. > >RCS file: >/usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v >retrieving revision 1.1 >diff -r1.1 fedora-install-guide-en.xml >12c12 >< Would a net address be easier, then we could map it to a local file via a catalog? Tammy? regards DaveP From kwade at redhat.com Sat Nov 29 08:06:47 2003 From: kwade at redhat.com (Karsten Wade) Date: 29 Nov 2003 00:06:47 -0800 Subject: New ENTITY declarations? In-Reply-To: <6.0.0.22.2.20031127185929.02570f40@pop3.Nildram.co.uk> References: <1069896075.18667.17.camel@bettie.internal.frields.org> <6.0.0.22.2.20031127185929.02570f40@pop3.Nildram.co.uk> Message-ID: <1070093206.3247.5102.camel@erato.phig.org> On Thu, 2003-11-27 at 11:00, Dave Pawson wrote: > At 01:21 27/11/2003, you wrote: > >Do we need a block of additional ENTITY declarations as a standard in > >the templates, > > Yes please. Save's typing! Agreed, entities are a must. They promote consistency and give you a single location to change a name/term/application/etc. without manual search and replace. Quick summary of the ideas below before I get into the details, especially as this is a request for the project lead (Tammy Fox) to notice: * Have a common entities file for all documentation, fedora-entities.xml * Have a common XML directory for all doxen, fedora-common-xml/ * fedora-entities.xml has useful and specific entities created for all to use * Individual dox have unique and local entities declared in the parent XML file > They need adding to the DTD/schema IMHO. We use a common set available to all document writers, following the format of fedora-entities.sgml. The contents of that file would be pulled into the parent XML like: %FEDORA-ENTITIES; I'm not 100% certain that my syntax is accurate for the XML DTD; it works for SGML. Let us know if there any differences. Following is an example scheme based on what we are using at Red Hat. The target file in the common directory is called via a relative path, i.e. it's always in an expected location of off the Fedora docs cvsroot, ../fedora-common-xml/fedora-entities.xml. This means fedora-common-xml/ is a module in CVS that you need to check-out in order to build your docs (if you call anything from there, of course), and which makes it easy to distribute changes globally, i.e. if Fedora Core becomes F3d0ra C0r3, then we only need to 'cd fedora-common-xml/ && cvs up'. ;) fedora-entities.xml would have a number of lines, grouped logically with comment block headers: http://fedora.redhat.com/"> ... Also useful are The parent XML file can then have localized content such as a series of repetitious items related to that particular document. I'd much rather write &X; than "X window system" over and over and over. Another good thing to have in the parent XML file is anything related to version and release, e.g.: ... If you want separate files for either chapters or sections, you can then have: ... This is helpful when people are working on different

s of an overall document; the parent document just looks like:
Article Title ... &INTRO; &OVERVIEW; ...
Everyone works on his/her own own file e.g. overview.xml, without stepping on the toes of other authors; it's easy to a particular &SECTION; which is having build problems, etc. > Surely there are a group from redhat that can be adopted and added to? I honestly don't think they'd be helpful; they're very specific to Red Hat products, services and versions. Here are some ideas I got from looking through which may be applicable (the suffix convention used here is of X meaning a short version of a name, XS meaning shortest possible): Because of the number of smaller tutorials possible, a common set would have longer abbreviations like SECTTR instead of e.g. ST if you only had a handful of tutorials, or even SG if you have a single Security Guide. It's nice to break down to the smallest possible elements as well as often used elements, which build on each other: This let's you build: ... &FDP; &SECTTR; /aka/ &FDPXSECTTRX; for &FC; &FEDVER; ... This creates a document with the title ... Fedora Documentation Project Security Tutorial /aka/ FDP SecHOWTO for Fedora Core 1.0 ... Whoops, we want "SecHOWTO" to become "SecHowTo"? Just go back to the fedora-entities.xml and change it ... you get the idea. :) hth - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From kwade at redhat.com Sat Nov 29 08:30:41 2003 From: kwade at redhat.com (Karsten Wade) Date: 29 Nov 2003 00:30:41 -0800 Subject: Status of french translation In-Reply-To: <1069930058.1676.26.camel@raft.velic.com> References: <1069930058.1676.26.camel@raft.velic.com> Message-ID: <1070094641.3247.5152.camel@erato.phig.org> On Thu, 2003-11-27 at 02:47, Philippe MALINGE wrote: > Hello all, > > I checked out the 'translate' package and it seems that all fr.po files > are already translated in french. Are you perhaps talking about translating Fedora Core (apps, tools, Gnome, etc.)? Discussion about translation of Fedora Core appears to happen on i18n-list at redhat.com (http://www.redhat.com/mailman/listinfo/i18n-list). On-topic discussion for this list includes translation of documentation (guides, tutorials, HOWTOs), much of which has not been written (in English or any other language). Sorry if I have missed the point entirely; I haven't been keeping fully informed on how translation is coordinated. Did you actually find that the existing Fedora Project documentation (i.e. the Documentation Guide) was already translated??? HTH - Karsten -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From kwade at redhat.com Sat Nov 29 08:32:36 2003 From: kwade at redhat.com (Karsten Wade) Date: 29 Nov 2003 00:32:36 -0800 Subject: FDP on IRC Message-ID: <1070094756.3247.5158.camel@erato.phig.org> Along with the plethora of other #fedora* channels on irc.freenode.net, a very few of us have been camping on #fedora-docs. Please feel free to come discuss anything on-topic, including and especially current list topics! - Karsten (quaid) -- Karsten Wade : Tech Writer, RHCE : o: +1.831.466.9664 kwade at redhat.com : http://rhea.redhat.com/ : c: +1.831.818.9995 Red Hat Applications : WAF, CMS, Portal Server -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- From dpawson at nildram.co.uk Sun Nov 30 10:04:06 2003 From: dpawson at nildram.co.uk (Dave Pawson) Date: Sun, 30 Nov 2003 10:04:06 +0000 Subject: New ENTITY declarations? In-Reply-To: <1070093206.3247.5102.camel@erato.phig.org> References: <1069896075.18667.17.camel@bettie.internal.frields.org> <6.0.0.22.2.20031127185929.02570f40@pop3.Nildram.co.uk> <1070093206.3247.5102.camel@erato.phig.org> Message-ID: <6.0.0.22.2.20031130095728.026320e8@pop3.Nildram.co.uk> At 08:06 29/11/2003, Karsten Wade wrote: >We use a common set available to all document writers, following the >format of fedora-entities.sgml. The contents of that file would be >pulled into the parent XML like: > > >"../fedora-common-xml/fedora-entities.xml"> >%FEDORA-ENTITIES; Which is fine if the structure on an authors machine reflects that on the fedora build. 1. Is that the intention. 2. Is that structure documented? (That's why I suggested the use of a uri on the redhat site, and a local catalog entry to map that to the local instance for local use) >I'm not 100% certain that my syntax is accurate for the XML DTD; it >works for SGML. Which is fedora working in? I've assumed XML. Is there much SGML legacy? > Let us know if there any differences. Following is an >example scheme based on what we are using at Red Hat. > >The target file in the common directory is called via a relative path, >i.e. it's always in an expected location of off the Fedora docs cvsroot, >../fedora-common-xml/fedora-entities.xml. Are all authors expected to work with that relative path? >This means fedora-common-xml/ is a module in CVS that you need to >check-out in order to build your docs (if you call anything from there, >of course), and which makes it easy to distribute changes globally, i.e. >if Fedora Core becomes F3d0ra C0r3, then we only need to 'cd >fedora-common-xml/ && cvs up'. ;) No problems with that... so long as all understand it.. and its documented :-) >hth - Karsten Very much so Karsten. Very clear. .... Is this to be marked up and added to the documentation howto :-) regards DaveP From sigematu at impress.co.jp Sun Nov 30 17:15:51 2003 From: sigematu at impress.co.jp (Naoki Shigematsu) Date: Mon, 01 Dec 2003 02:15:51 +0900 Subject: Japanese Translation Message-ID: <200311301715.hAUHFom2005090@proxy6.impress.co.jp> Hi, In Japan, Fedora JP Project started up and activity is begun. There are about 20 staff with an activity. First, we are beginning to translate the document. Web Developer's Guide and Doucumentation guide. software po etc. Now, when Red Hat Linux was released, Japanese Documents were translated in Australia. This time, does the schedule exist? Thanks. -- Naoki Shigematsu From sigematu at impress.co.jp Sun Nov 30 19:54:00 2003 From: sigematu at impress.co.jp (Naoki Shigematsu) Date: Mon, 01 Dec 2003 04:54:00 +0900 Subject: mistake entity (was: filename) In-Reply-To: <6.0.0.22.2.20031128180457.02622e28@pop3.Nildram.co.uk> References: <3fc716f1.2171%ml@elf.no-ip.org> <6.0.0.22.2.20031128180457.02622e28@pop3.Nildram.co.uk> Message-ID: <200311301954.hAUJs0m2012729@proxy6.impress.co.jp> Hi, > >RCS file: > >/usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v > >retrieving revision 1.1 > >diff -r1.1 fedora-install-guide-en.xml > >12c12 > >< > > Would a net address be easier, Sure -- It seems to be better to use Content Negotiation. Example: index.html.en index.html.ja index.html.de Although it is not a not good way, It is realizable if a docbook html template is changed. It is necessary to also change fedora-docs/*/Makefile. It is as follows if it does by this method. developers-guide/*.html.en *.html.ja *.html.de Other ideas? [/usr/share/xmlto/format/docbook/html] == --- html.default 2003-12-01 03:05:46.000000000 +0900 +++ html 2003-12-01 04:47:33.000000000 +0900 @@ -7,6 +7,11 @@ echo "http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl" ;; post-process) - cp -- * "$OUTPUT_DIR" + if [ ! -z "$LANG" ] + then + for i in *; do + cp -- $i "$OUTPUT_DIR"/$i.$LANG + done + fi ;; esac [$FEDORA-DOCS/*/Makefile] == --- Makefile.default 2003-11-22 07:39:22.000000000 +0900 +++ Makefile 2003-12-01 04:03:34.000000000 +0900 @@ -10,8 +10,9 @@ XSLPDF = ../xsl/main-pdf.xsl XSLHTML = ../xsl/main-html.xsl LANG = en -DOCNAME = developers-guide-$(LANG) -XMLFILE = $(DOCNAME).xml +#DOCNAME = developers-guide-$(LANG) +DOCNAME = developers-guide +XMLFILE = $(DOCNAME)-$(LANG).xml ###################################################### html: -- Naoki Shigematsu From ml at elf.no-ip.org Sun Nov 30 23:09:47 2003 From: ml at elf.no-ip.org (Tadashi Jokagi) Date: Mon, 01 Dec 2003 08:09:47 +0900 Subject: mistake entity (was: filename) In-Reply-To: <200311301954.hAUJs0m2012729@proxy6.impress.co.jp> References: <3fc716f1.2171%ml@elf.no-ip.org> <6.0.0.22.2.20031128180457.02622e28@pop3.Nildram.co.uk> <200311301954.hAUJs0m2012729@proxy6.impress.co.jp> Message-ID: <3fca78bb.2183%ml@elf.no-ip.org> Hi, I propose creating the directory of a language name. ex) - /de/developers-guide/index.html - /en/developers-guide/index.html - /ja/developers-guide/index.html Reason - There is no reason in being intermingled by many languages. -- However, there may be a merit about a web page. - It is hard to treat with a local file system. - Finally, the number of files becomes huge. As far as I know, as for a many languages manual, PHP's is consulted very much. If there is time, please make it reference. http://pear.php.net/manual/ http://cvs.php.net/cvs.php/peardoc -- ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf at elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitawiki http://elf.no-ip.org/wiki/ Yokukitablog http://elf.no-ip.org/blog/