From kwade at redhat.com Thu Dec 1 18:48:17 2005 From: kwade at redhat.com (Karsten Wade) Date: Thu, 01 Dec 2005 10:48:17 -0800 Subject: help with the SELinux FAQ In-Reply-To: <200512011023.20342.csellers@tresys.com> References: <1133302866.19569.38.camel@erato.phig.org> <200512011023.20342.csellers@tresys.com> Message-ID: <1133462897.19569.212.camel@erato.phig.org> On Thu, 2005-12-01 at 10:23 -0500, Chad Sellers wrote: > We definitely want to make sure that many of the changes (move to reference > policy/policy v2, move to managed policy, move to policy modules, etc.) get > into the FAQ. Let me know what I can do to help. The main thing is to review the current content and make the following changes: * Remove out-of-date information * Update FAQs to reflect current reality * Add new content The best and fastest way to do this is directly in the XML in CVS. The FAQ is written in DocBook, and is very straightforward. If you haven't written in DocBook before, it is about 10% more difficult than HTML, and 100% more rewarding. To set this up, go through this page ... you want to follow the steps in "Signing Up". The most important step is 4., where you sign up for CVS access. "Submitting Your Own Documentation" covers the details of using DocBook and CVS in this project. http://fedoraproject.org/wiki/DocsProject/NewWriters If you cannot take that route, people in the Fedora Documentation Project can take your changes and incorporate them ourselves. For simplicity sake, I recommend that you use a plain text output of the FAQ to edit. We can then run a diff against another plain text output, and manually make the changes in the XML. Here is a plain text output of the latest (1.3-8): http://people.redhat.com/kwade/fedora-docs/selinux-faq-en-1.3-8.txt The next version starts at 1.5, as I've been using the minor release to indicate which version of Fedora Core this version of the FAQ relates to. Thanks very much for your interest, - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Thu Dec 1 18:52:31 2005 From: kwade at redhat.com (Karsten Wade) Date: Thu, 01 Dec 2005 10:52:31 -0800 Subject: {RFC] XSLT for draft watermarking? In-Reply-To: <1133356769.3446.24.camel@localhost.localdomain> References: <1133312660.3089.9.camel@localhost.localdomain> <1133355080.14939.8.camel@flatline.devel.redhat.com> <1133356769.3446.24.camel@localhost.localdomain> Message-ID: <1133463151.19569.214.camel@erato.phig.org> On Wed, 2005-11-30 at 08:19 -0500, Paul W. Frields wrote: > If I remember correctly, there's an order to how XSL stuff is inherited, > right? Like, "whoever's first wins," although it could be the opposite, > I'm not sure. I think it's the last instruction wins, but I also am not sure. :) - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Thu Dec 1 19:23:52 2005 From: kwade at redhat.com (Karsten Wade) Date: Thu, 01 Dec 2005 11:23:52 -0800 Subject: {RFC] XSLT for draft watermarking? In-Reply-To: <20051130114105.3003620b.Tommy.Reynolds@MegaCoder.com> References: <1133312660.3089.9.camel@localhost.localdomain> <20051130114105.3003620b.Tommy.Reynolds@MegaCoder.com> Message-ID: <1133465032.19569.231.camel@erato.phig.org> On Wed, 2005-11-30 at 11:41 -0600, Tommy Reynolds wrote: > Uttered "Paul W. Frields" , spake thus: > > > Both and
in DocBook support a CDATA attribute called > > "status". (I.e., or something like that.) > > Does this mean we could have XSLT do the work of deciding which > > stylesheet to use, without having to have a new "make" target? > > Maybe I know this, but I can't remember it at the moment. I need a > little more thinking on this. My question is: > > When is an FDP document "published"? +1 to all your observations, you are totally on track. Our objective is to: * Make it an easy, automated process for a document to move to the state of being published. * Restrict who can do that task, so that it is truly formal. As Paul alluded to, I'm certain we are going to be doing automation on top of this. Imagine a workbench that writers and editors use, essentially a customized and streamlined CMS built on our systems. On the front side it allows writers to add draft content, work with it in their editor of choice on- or off-line, then push that content to the editors. The editors can approve or deny, and may or may not be allowed to edit. This can then be pushed to publish, or, if flagged for it, pushed to a publisher, who does the final approval. What is happening on the back side is dependent on what we choose here. This was the basis for my agreeing with Paul's idea in concept. Something that can be done to a module to make it publish, checked in and tagged or branched, and have that publication approval stick to just that tag or branch. Then revert back to a draft status. The alternative to this is to capture the publish/draft information in a database and work up some metadata about it. That's what traditional CMS does. But we have CVS doing all that for us, why mess with it? > Official, production-quality documents are located (where?) and > produced by (whom?). Only those copies need have the draft > watermarking revoked. For now, we need to do it manually. Sorry. We just need to document the process (on the Wiki) and adhere to it. > Docs included in the distribution are "production". Where else do > the official docs reside? Who places them there? How do they know > when to do this? Part of our process, and eventually tool, is to put the proper CSS in the packaged documentation. Do my concepts answer your conceptual questions? I see this workbench landing in chunks, pieces by quarter ... three months, six months, etc. > I don't think the document itself should know whether it is released > or not. It is too easy to leave the blessing in the document as > modifications are in progress. An external mechanism makes sense to > me. Is CVS okay for this? That is, the tag or branch has meaning or a specific string (PUB). Wherever you build, check the tag on the file in order to use the for-publish stylesheets. This would disable off-line builds of for-publish documents, as CVS would be required. That makes the toolchain enforce behavior > We really need only one CSS stylesheet in the docs CVS: the > fedora-draft.css file, and we have that. > > Any official-looking document renderings should come from whom ever > is constructing the official-looking release, but anything in our CVS > is strictly for draft documents. I don't know about moving this to another repository ... how about a 'publish' module with ACLs? > Does this mean that document authors can't generate official document > renderings? Yes, if by that you mean "Fedora Documentation Project" > official copies. Anyone wanting to produce their own published > renderings are free to take the "fedora-draft.css" stylesheet and > edit as desired. Agreed, make it easy for people to comply with the trademark guidelines ... by making it harder for them to use the trademarked material incorrectly. :) > I would agree to change the XSLT and Makefile.common stuff to > reference "fedora.css" and to make "fedora.css" a symlink to the > "fedora-draft.css" file. That would make switching the CSS > stylesheet easier because a change would not corrupt the local CVS > image. +1 > Comments? Suggestions? Donations? Two out of three ain't bad for today. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Thu Dec 1 20:49:14 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Thu, 1 Dec 2005 14:49:14 -0600 Subject: {RFC] XSLT for draft watermarking? In-Reply-To: <1133463151.19569.214.camel@erato.phig.org> References: <1133312660.3089.9.camel@localhost.localdomain> <1133355080.14939.8.camel@flatline.devel.redhat.com> <1133356769.3446.24.camel@localhost.localdomain> <1133463151.19569.214.camel@erato.phig.org> Message-ID: <20051201144914.d5cd9849.Tommy.Reynolds@MegaCoder.com> Uttered Karsten Wade , spake thus: > On Wed, 2005-11-30 at 08:19 -0500, Paul W. Frields wrote: > > > If I remember correctly, there's an order to how XSL stuff is inherited, > > right? Like, "whoever's first wins," although it could be the opposite, > > I'm not sure. > I think it's the last instruction wins, but I also am not sure. :) "Most important" wins. You can only set a or once, no matter how many appearances are made. Importance is determined by the "nesting level" of the instance. For example, assume an XSL include() arrangement like this: #1 xsl/main-html.xsl #2 /usr/shar/sgml/docbook/xsl-stylesheets/html/docbook.xsl #3 /what/ever/goes/on/in/there.xsl #3 /its/a/mystery/to/me.xsl #3 /tommy/can/you/hear/me.xsl #2 redhat.xsl #2 html-common.xsl The left column represents the priority of the definitions in a file. The right colum shows the XSL include hierarchy. So definitions in #1, xsl/main-html.xsl take precedence over any definitions further down the include tree. This is how we can override any foolish settings deep within the DocBook distribution without resorting to rocket surgery on the files... At a given precedence, first definition wins. HTH -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Thu Dec 1 21:16:59 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Thu, 1 Dec 2005 15:16:59 -0600 Subject: {RFC] XSLT for draft watermarking? In-Reply-To: <1133465032.19569.231.camel@erato.phig.org> References: <1133312660.3089.9.camel@localhost.localdomain> <20051130114105.3003620b.Tommy.Reynolds@MegaCoder.com> <1133465032.19569.231.camel@erato.phig.org> Message-ID: <20051201151659.bdc02733.Tommy.Reynolds@MegaCoder.com> Uttered Karsten Wade , spake thus: > > When is an FDP document "published"? > +1 to all your observations, you are totally on track. Our objective is > to: > * Make it an easy, automated process for a document to move to the state > of being published. > * Restrict who can do that task, so that it is truly formal. > As Paul alluded to, I'm certain we are going to be doing automation on > top of this. I hear and obey. Actually, the trouble is getting me to listen ;-) Using the excellent suggestion made by James Laska yesterday, I've added two more macros to "docs-common/Makefile.common" that give the maker control over the CSS stylesheet selection. I'll have a more visible email about this composed shortly. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Thu Dec 1 21:33:46 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Thu, 1 Dec 2005 15:33:46 -0600 Subject: [ANN] Draft Document Rendering Message-ID: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> Hi, Folks! Unless you are involved, or interested in, the Fedora Doc publishing infrastructure you can skip this but you're welcome to stay. We are keeping the default behaviour of watermarking the HTML documents produced from the CVS files as "DRAFT / NOT FOR REFERENCE". Per the discussion and suggestions on this list, I've made using different CSS stylesheets much easier. This should allow a batch building process to choose, at rendering time, which CSS stylesheet to use. Two new "docs-common/Makefile.common" macros have been added: ${HTMLCSS} should contain the path to whatever CSS stylesheet should be used. ${HTMLCSSEXTRA} should list any additional files needed by the CSS stylesheet, such as the "images/watermark.png" file used by the default stylesheet. Currently there are several ways of specifying any of the "docs-common/Makefile.common" macros: 1) Do nothing and accept the default values coded in "docs-common/Makefile.common". 2) Add the definitions at the top of the document "Makefile". This is NOT recommended. 3) Create the file "Make.paths" in the document directory and place the macro definitions in there, just as if they were part of "docs-common/Makefile.common". 4) Export the macro definitions into your environment before doing the make. 5) Define the macro on the make command line: $ make HTMLCSS=/path/to/my.css html For now, I recommend either method #3 or #5, depending on how many times you need to build the document. As always, suggestions, comments and bribes are cheerfully accepted. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 2 16:09:35 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 2 Dec 2005 10:09:35 -0600 Subject: [ANN] Draft Document Rendering In-Reply-To: <1133530916.2603.8.camel@flatline.devel.redhat.com> References: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> <1133530916.2603.8.camel@flatline.devel.redhat.com> Message-ID: <20051202100935.e1b7fcdc.Tommy.Reynolds@MegaCoder.com> Uttered James Laska , spake thus: Please keep this on the list, thanks. > Not sure if that was intentional or not, but I think the file paths > might be incorrect for the html-nochunks path. The HTMLCSS and > HTMLCSSEXTRA are being copied to the DOCBASE-$(1)/ and not the pwd. > I filed bug#174805 to address that. Ah, the perils of cut'n paste. "I hate meeses to pieces" Japan doesnt't call me nogui-san for nothing ;-) Fixed in CVS. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From csellers at tresys.com Fri Dec 2 16:34:04 2005 From: csellers at tresys.com (Chad Sellers) Date: Fri, 02 Dec 2005 11:34:04 -0500 Subject: Self-Introduction: Chad Sellers Message-ID: <4390777C.9000102@tresys.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, my name is Chad Sellers. I currently live in Columbia, MD, USA. I work for Tresys Technology as a software developer focused on security. I've been working on SELinux projects for a couple of years now, so I would like to help with the Fedora SELinux FAQ. My Fedora CVS username is csellers. GPG info: pub 1024D/0260F126 2005-12-02 Key fingerprint = 83DE 0CE7 C659 F74D 8FEA 0DA5 BFF3 424B 0260 F126 uid Chad Sellers sub 4096g/F1BFB58B 2005-12-02 Thanks, Chad - -- - ---------------------- Chad Sellers Tresys Technology, LLC csellers at tresys.com http://www.tresys.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDkHd8v/NCSwJg8SYRAs29AJ0QKwBwETV4bM8Qn+/jWKPRyyfEIgCfWDuc QloyyzmDbrKRt/NJc55S8kA= =Jy3f -----END PGP SIGNATURE----- From stickster at gmail.com Fri Dec 2 17:27:36 2005 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 02 Dec 2005 12:27:36 -0500 Subject: Self-Introduction: Chad Sellers In-Reply-To: <4390777C.9000102@tresys.com> References: <4390777C.9000102@tresys.com> Message-ID: <1133544456.15137.53.camel@localhost.localdomain> On Fri, 2005-12-02 at 11:34 -0500, Chad Sellers wrote: > Hello, my name is Chad Sellers. I currently live in Columbia, MD, USA. > I work for Tresys Technology as a software developer focused on > security. I've been working on SELinux projects for a couple of years > now, so I would like to help with the Fedora SELinux FAQ. > > My Fedora CVS username is csellers. Brilliant! I know Karsten will appreciate the help. Have you visited the wiki page at http://fedoraproject.org/wiki/DocsProject yet? There's info there on how to get started if you need it, but if you've seen Karsten's earlier post[1] then you know we can shortcut where necessary to get you into a position to contribute efficiently. Welcome and please post any questions to the list, we'll help wherever we can. [1] http://www.redhat.com/archives/fedora-docs-list/2005-December/msg00000.html -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Dec 6 22:20:00 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 06 Dec 2005 14:20:00 -0800 Subject: [RFC] DocsRawhide enhancements Message-ID: <1133907600.8794.71.camel@erato.phig.org> The DocsRawhide (rawhide of documentation) beta has been live for a little while: http://webtest.fedora.redhat.com/docs/ There are many purposes this basic technology can be used for. At it's core, it checks out the latest content from CVS and builds it at static URLs. This is fully draft, may burn your computer documentation. It's purpose is to let anyone view what is in CVS without needing a build environment. What are your ideas of what to do with this tool? What should we make it do? - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stuart at elsn.org Tue Dec 6 23:50:01 2005 From: stuart at elsn.org (Stuart Ellis) Date: Tue, 06 Dec 2005 23:50:01 +0000 Subject: Minutes of FDSCo Meeting Dec 6 2005 Message-ID: <1133913001.2807.24.camel@localhost.localdomain> Attending: --------- Karsten Wade (quaid) Tommy Reynolds (megacoder) Paul Frields (stickster) Stuart Ellis (elliss) Regrets: -------- Gavin Henry (G2) Tammy Fox (tcf) - leave of absence Schedule of Tasks: ------------------ http://www.fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule Highlights: ----------- * Karsten: The content of the Fedora site at redhat.com has been revised: http://fedora.redhat.com/ * Karsten: Work has begun on enabling the FOP system to run on open source Java platforms. Once this work is complete, the FDP may integrate FOP into the toolchain to enable PDF generation. For more technical details, see the Apache Wiki: http://wiki.apache.org/xmlgraphics/GnuClasspathCompatibility PDF generation with FOP is not expected to be live before the release of Fedora Core 5. * Karsten: A discussion on future enhancements to DocsRawhide will be started on the fedora-docs-list. DocsRawhide shows HTML versions of the documents in the FDP CVS, automatically updated every hour: http://webtest.fedora.redhat.com/docs/ Full IRC Log: ------------- https://www.redhat.com/archives/fedora-dsco-list/2005-December/msg00002.html -- Stuart Ellis stuart at elsn.org Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at redhat.com Wed Dec 7 10:36:30 2005 From: sundaram at redhat.com (Rahul Sundaram) Date: Wed, 07 Dec 2005 16:06:30 +0530 Subject: [RFC] DocsRawhide enhancements In-Reply-To: <1133907600.8794.71.camel@erato.phig.org> References: <1133907600.8794.71.camel@erato.phig.org> Message-ID: <4396BB2E.6050103@redhat.com> Karsten Wade wrote: >The DocsRawhide (rawhide of documentation) beta has been live for a >little while: > >http://webtest.fedora.redhat.com/docs/ > >There are many purposes this basic technology can be used for. > >At it's core, it checks out the latest content from CVS and builds it at >static URLs. > >This is fully draft, may burn your computer documentation. It's purpose >is to let anyone view what is in CVS without needing a build >environment. > >What are your ideas of what to do with this tool? What should we make >it do? > > My original idea behind the suggestion was to enhance visibility to the documentation in progress and potentially get more reviewers and contributors and bring in transparency to the project. Fedora Documentation could sit into a portal with links and search for the following information * End user docs * Printed books - Fedora books from http://fedoraproject.org/wiki/Marketing/Books and perhaps http://www.redhat.com/magazine/013nov05/features/bookreview/, * Red Hat magazine * Manual and info pages - see http://fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule * In progress docs (docs rawhide) with appropriate warnings * RPM Package lists with meta data information about the packages. RPM The package descriptions in many cases are vague or outdated. I saw a reference to the SELinux in the IRC meeting logs which applies RPM package descriptions too. The Fedora documentation project should be accountable for the end user docs, man and info pages, keeping track of printed books and active involvement and coordination towards getting more such books published even from the formal Fedora docs. package description and website content etc to cover everything comprehensively. regards Rahul From stickster at gmail.com Wed Dec 7 12:31:42 2005 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 07 Dec 2005 07:31:42 -0500 Subject: [RFC] DocsRawhide enhancements In-Reply-To: <4396BB2E.6050103@redhat.com> References: <1133907600.8794.71.camel@erato.phig.org> <4396BB2E.6050103@redhat.com> Message-ID: <1133958702.3214.2.camel@localhost.localdomain> On Wed, 2005-12-07 at 16:06 +0530, Rahul Sundaram wrote: > Karsten Wade wrote: > > >The DocsRawhide (rawhide of documentation) beta has been live for a > >little while: > > > >http://webtest.fedora.redhat.com/docs/ > > > >There are many purposes this basic technology can be used for. > > > >At it's core, it checks out the latest content from CVS and builds it at > >static URLs. > > > >This is fully draft, may burn your computer documentation. It's purpose > >is to let anyone view what is in CVS without needing a build > >environment. > > > >What are your ideas of what to do with this tool? What should we make > >it do? > > > > > My original idea behind the suggestion was to enhance visibility to the > documentation in progress and potentially get more reviewers and > contributors and bring in transparency to the project. Fedora > Documentation could sit into a portal with links and search for the > following information > > * End user docs > * Printed books - Fedora books from > http://fedoraproject.org/wiki/Marketing/Books and perhaps > http://www.redhat.com/magazine/013nov05/features/bookreview/, > * Red Hat magazine > * Manual and info pages - see > http://fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule > * In progress docs (docs rawhide) with appropriate warnings > * RPM Package lists with meta data information about the packages. This sounds like a good application for Fedora Unity IMHO. > RPM The package descriptions in many cases are vague or outdated. I saw > a reference to the SELinux in the IRC meeting logs which applies RPM > package descriptions too. The Fedora documentation project should be > accountable for the end user docs, man and info pages, keeping track of > printed books and active involvement and coordination towards getting > more such books published even from the formal Fedora docs. package > description and website content etc to cover everything comprehensively. Tell you what, as soon as the contributors start the stampede, we'll get right on this. ;-) In the meantime, with only a few people contributing actively we're at our limit just for the things we feel are absolutely necessary - the Installation Guide, Release Notes, etc. It's a good target to shoot for, if we get more manpower. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at redhat.com Wed Dec 7 12:38:22 2005 From: sundaram at redhat.com (Rahul Sundaram) Date: Wed, 07 Dec 2005 18:08:22 +0530 Subject: [RFC] DocsRawhide enhancements In-Reply-To: <1133958702.3214.2.camel@localhost.localdomain> References: <1133907600.8794.71.camel@erato.phig.org> <4396BB2E.6050103@redhat.com> <1133958702.3214.2.camel@localhost.localdomain> Message-ID: <4396D7BE.9080803@redhat.com> Hi >Tell you what, as soon as the contributors start the stampede, we'll get >right on this. ;-) In the meantime, with only a few people contributing >actively we're at our limit just for the things we feel are absolutely >necessary - the Installation Guide, Release Notes, etc. It's a good >target to shoot for, if we get more manpower. > > > Exactly. Never meant to imply that this is what should be happening now. Just a glimpse of my vision for the future ;-) regards Rahul From kwade at redhat.com Wed Dec 7 18:22:36 2005 From: kwade at redhat.com (Karsten Wade) Date: Wed, 07 Dec 2005 10:22:36 -0800 Subject: manual and info pages (was Re: [RFC] DocsRawhide enhancements) In-Reply-To: <4396BB2E.6050103@redhat.com> References: <1133907600.8794.71.camel@erato.phig.org> <4396BB2E.6050103@redhat.com> Message-ID: <1133979756.8794.100.camel@erato.phig.org> On Wed, 2005-12-07 at 16:06 +0530, Rahul Sundaram wrote: > The Fedora documentation project should be > accountable for the end user docs, man and info pages, I have vacillated about who should be accountable for manual and info pages. It is impossible for FDP to be responsible, since we are typically too far removed from the coding. Until the developers are positioned to work on these, FDP cannot take accountability for the manual and info pages. Alternately, if we get together a group of motivated people who want to tackle this problem that is valuable for all distros ... then we will definitely empower them to do so. > keeping track of > printed books and active involvement and coordination towards getting > more such books published even from the formal Fedora docs. package > description and website content etc to cover everything comprehensively. Definitely, when we have the resources and activity. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Wed Dec 7 20:02:33 2005 From: kwade at redhat.com (Karsten Wade) Date: Wed, 07 Dec 2005 12:02:33 -0800 Subject: latest relnotes updated, now with it and ru versions Message-ID: <1133985754.8794.119.camel@erato.phig.org> The latest relnotes for FC5test1 have been updated: http://fedora.redhat.com/docs/release-notes/ Update features: * Italian (it) and Russian (ru) translations are now updated as latest, since these have been updated since the test1 translation freeze. * The [Tip] at the top of the release notes now links to a Wiki page of updated common problems; note this only appears in the English version of the [Tip]: http://fedoraproject.org/wiki/FC5Test1CommonProblems If you are interested in watching the tip of the creation process for the relnotes, put a watch on the beats pages in the Wiki with this regular expression: 1. Go to http://fedoraproject.org/wiki/UserPreferences 2. In the Subscribed wiki pages (one regex per line) field at the bottom of page, put in this regular expression: Docs/Beats.* http://fedoraproject.org/wiki/Docs/Beats Thanks beat writers, editors, and translators for providing Fedora testers with updated content. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Wed Dec 7 23:54:03 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Wed, 7 Dec 2005 17:54:03 -0600 Subject: [ANN] Draft Document Rendering In-Reply-To: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> References: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> Message-ID: <20051207175403.daaedd27.Tommy.Reynolds@MegaCoder.com> Uttered Tommy Reynolds , spake thus: > Unless you are involved, or interested in, the Fedora Doc publishing > infrastructure you can skip this but you're welcome to stay. We > are keeping the default behaviour of watermarking the HTML documents > produced from the CVS files as "DRAFT / NOT FOR REFERENCE". If someone will send me translations for the "DRAFT / NOT FOR REFERENCE" notation, I'll try to incorporate it as a per-language watermark. Please take a look at "docs-common/images/watermark.svg" if you savy SVG. If not, please just post the translated strings to the list. Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Wed Dec 7 23:54:03 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Wed, 7 Dec 2005 17:54:03 -0600 Subject: [ANN] Draft Document Rendering In-Reply-To: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> References: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> Message-ID: <20051207175403.daaedd27.Tommy.Reynolds@MegaCoder.com> Uttered Tommy Reynolds , spake thus: > Unless you are involved, or interested in, the Fedora Doc publishing > infrastructure you can skip this but you're welcome to stay. We > are keeping the default behaviour of watermarking the HTML documents > produced from the CVS files as "DRAFT / NOT FOR REFERENCE". If someone will send me translations for the "DRAFT / NOT FOR REFERENCE" notation, I'll try to incorporate it as a per-language watermark. Please take a look at "docs-common/images/watermark.svg" if you savy SVG. If not, please just post the translated strings to the list. Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 9 03:22:49 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Thu, 8 Dec 2005 21:22:49 -0600 Subject: [FYI] Apache FOP 0.90BETA1 Trial Message-ID: <20051208212249.9c4e8e9b.Tommy.Reynolds@MegaCoder.com> Hello, all! This is a status update. As you probably know, FDP intend to use Apache FOP to render the PDF versions of our documents. The 0.20.5 version is quite old; furious development is underway. The Apache FOP team have made available a beta release of their heavily-rewritten product. You can find out more from their http://xmlgraphics.apache.org/fop/relnotes.html web site. I tried it out against the CVS versions of the Fedora Release Notes and thought you might like to see the results. You can find the English and Italian versions here: http://www.megacoder.com/nobots/RELEASE-NOTES-en.pdf http://www.megacoder.com/nobots/RELEASE-NOTES-it.pdf The Japanese version built, but the wrong font was used, so everything was a '#' character. The Russian version aborted. I think they look remarkably good, given that I used the original, mostly-generic PDF stylesheets. I haven't tried to compile this using GCJ; that's out of my range. Perhaps one of you might make one attempt, just to see what happens. As Karsten mentioned earlier, we should be getting some help with the graphics rendering component -- so we can avoid the closed-source libraries FOP uses. However, if we stick with .JPG and .EPS input graphics, the built-in FOP support should be quite good enough. We just need to get the GCJ compile going... Still, I prefer .PNG image files and am looking forward to the "correct" solution. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From andrewm at inventa.ru Fri Dec 9 09:17:18 2005 From: andrewm at inventa.ru (Andrew Martynov) Date: Fri, 9 Dec 2005 12:17:18 +0300 Subject: [ANN] Draft Document Rendering In-Reply-To: <20051207175403.daaedd27.Tommy.Reynolds@MegaCoder.com> References: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> <20051207175403.daaedd27.Tommy.Reynolds@MegaCoder.com> Message-ID: <20051209091718.GA25208@mk61.inventa.ru> Hello, Tommy! I just commited translated SVG file (and produced PNG) into CVS. Russian watermark: "docs-common/images/watermark-ru.svg". Regards, Andrew Martynov On Wed, Dec 07, 2005 at 05:54:03PM -0600, Tommy Reynolds wrote: > Uttered Tommy Reynolds , spake thus: > > > Unless you are involved, or interested in, the Fedora Doc publishing > > infrastructure you can skip this but you're welcome to stay. We > > are keeping the default behaviour of watermarking the HTML documents > > produced from the CVS files as "DRAFT / NOT FOR REFERENCE". > > If someone will send me translations for the "DRAFT / NOT FOR > REFERENCE" notation, I'll try to incorporate it as a per-language > watermark. > > Please take a look at "docs-common/images/watermark.svg" if you savy > SVG. If not, please just post the translated strings to the list. > > Thanks! > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list From kwade at redhat.com Fri Dec 9 13:04:56 2005 From: kwade at redhat.com (Karsten Wade) Date: Fri, 09 Dec 2005 05:04:56 -0800 Subject: [FYI] Apache FOP 0.90BETA1 Trial In-Reply-To: <20051208212249.9c4e8e9b.Tommy.Reynolds@MegaCoder.com> References: <20051208212249.9c4e8e9b.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134133496.8794.255.camel@erato.phig.org> On Thu, 2005-12-08 at 21:22 -0600, Tommy Reynolds wrote: > Hello, all! > > This is a status update. Thanks! > I think they look remarkably good, given that I used the original, > mostly-generic PDF stylesheets. Yeah, I'm hoping the rendering weirdness in the PDFs can be resolved with the stylesheets. Definitely want to restyle the , the default makes a difficult to read, two-column format. Also, multiple problems mostly with fixed-width font rendering. Still, pretty cool. We'll have to supply the Apache team with some bug reports. :) - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 9 16:28:51 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 9 Dec 2005 10:28:51 -0600 Subject: [ANN] Draft Document Rendering In-Reply-To: <20051209091718.GA25208@mk61.inventa.ru> References: <20051201153346.3a323ea5.Tommy.Reynolds@MegaCoder.com> <20051207175403.daaedd27.Tommy.Reynolds@MegaCoder.com> <20051209091718.GA25208@mk61.inventa.ru> Message-ID: <20051209102851.1bab6892.Tommy.Reynolds@MegaCoder.com> Uttered Andrew Martynov , spake thus: > I just commited translated SVG file (and produced PNG) into CVS. > Russian watermark: "docs-common/images/watermark-ru.svg". Beautiful. Thank you. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 9 17:06:30 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 9 Dec 2005 11:06:30 -0600 Subject: zh_CN watermark added Message-ID: <20051209110630.f2a00576.Tommy.Reynolds@MegaCoder.com> bbbush, Thank you for submitting the watermark-zh_CN.* files. I'm having trouble recreating the .PNG, though. Forgive my ignorance on this matter. Where can I find the font "AR PL ZenKai Uni"? Is that a standard Fedora font? If so, from what package? Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 9 22:09:04 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 9 Dec 2005 16:09:04 -0600 Subject: [RFC] Image filename conventions Message-ID: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> Hello, ya'll! Some folk have their document images in a "figs/" subdirectory tree under the document directory. Large documents may have additional "figs/part1" style subdirectories, too. The lack of a formal filenaming scheme makes selectively copying files awkward. Below is our current convention: -. such as "watermark-ru.png". Simple, eh? The problem is that some filenames use the "-" minus sign to separate words in the filename: this-is-my-picture.png Is "picture" part of the filename or the language designation? It is difficult for a shell script to decode this just by looking at the filename. I propose a file naming scheme to simplify the selective copying of files. This will help reduce the complexity of the RPM packaging tools. Only three formal rules are needed: 1) The minus sign "-" may not be used as part of the filename component. 1) The minus sign only introduces the locale for the file. 1) Filenames without a locale component are considered language neutral. With these conventions in place: "foo.png" is a language-neutral graphic. "foo-it.png" is a graphic with Italian text. "foo-bar.png" is not permitted usage. Comments? Alternatives? Bribes? Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Sat Dec 10 01:46:59 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 9 Dec 2005 19:46:59 -0600 Subject: [ANN] Draft Document Rendering In-Reply-To: <1134170612.3604.5.camel@localhost.localdomain> References: <1134170612.3604.5.camel@localhost.localdomain> Message-ID: <20051209194659.b06b0ee5.Tommy.Reynolds@MegaCoder.com> Uttered Francesco Tombolini , spake thus: > Hallo Tommy, the translation for "DRAFT / NOT FOR > REFERENCE" notation in italian language is "BOZZA / NON PER RIFERIMENTO" Thank you, Francesco. I've added it to CVS. Ciao -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bbbush.yuan at gmail.com Sat Dec 10 04:49:47 2005 From: bbbush.yuan at gmail.com (Yuan Yijun) Date: Sat, 10 Dec 2005 12:49:47 +0800 Subject: zh_CN watermark added In-Reply-To: <20051209110630.f2a00576.Tommy.Reynolds@MegaCoder.com> References: <20051209110630.f2a00576.Tommy.Reynolds@MegaCoder.com> Message-ID: <76e72f800512092049m86f7927u@mail.gmail.com> 2005/12/10, Tommy Reynolds : It is in fonts-chinese, of course :) Please install the latest 3.0x version of fonts-chinese in rawhide. -- bbbush ^_^ From kwade at redhat.com Sat Dec 10 03:42:36 2005 From: kwade at redhat.com (Karsten Wade) Date: Fri, 09 Dec 2005 19:42:36 -0800 Subject: relnotes XML in CVS is now canonical Message-ID: <1134186156.28941.21.camel@erato.phig.org> For a short while, we used the Wiki as the canonical resource for release notes, until snapshots were taken for specific releases. Those pages [1] continue to hold very current content, but it is truly draft information. With the creation of the DocsRawhide [2], we can now show the latest build from CVS directly. This removes the need to use the convenience of the Wiki to show content to readers. For now, integration of content between the Wiki and the XML is done semi-manually. This means that the Wiki may have updated information, but it is not reliable until it is in the XML in CVS. Thanks - Karsten [1] http://fedoraproject.org/wiki/Docs/Beats [2] http://webtest.fedora.redhat.com/docs/ is the beta home -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Sat Dec 10 05:43:43 2005 From: kwade at redhat.com (Karsten Wade) Date: Fri, 09 Dec 2005 21:43:43 -0800 Subject: [RFC] Image filename conventions In-Reply-To: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134193424.30324.11.camel@erato.phig.org> On Fri, 2005-12-09 at 16:09 -0600, Tommy Reynolds wrote: > I propose a file naming scheme to simplify the selective copying of > files. This will help reduce the complexity of the RPM packaging > tools. > > Only three formal rules are needed: > > 1) The minus sign "-" may not be used as part of the filename > component. We could use other separators, e.g. the fabulous_underbar_for_this-en ? > 1) The minus sign only introduces the locale for the file. > > 1) Filenames without a locale component are considered language > neutral. > > With these conventions in place: > > "foo.png" is a language-neutral graphic. > > "foo-it.png" is a graphic with Italian text. > > "foo-bar.png" is not permitted usage. > > Comments? Alternatives? Bribes? Looks good to me. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Sat Dec 10 12:11:25 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Sat, 10 Dec 2005 06:11:25 -0600 Subject: [RFC] Image filename conventions In-Reply-To: <1134193424.30324.11.camel@erato.phig.org> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134193424.30324.11.camel@erato.phig.org> Message-ID: <20051210061125.29f203db.Tommy.Reynolds@MegaCoder.com> Uttered Karsten Wade , spake thus: > > Only three formal rules are needed: > > 1) The minus sign "-" may not be used as part of the filename > > component. > We could use other separators, e.g. the fabulous_underbar_for_this-en ? Certainly. > > 1) The minus sign only introduces the locale for the file. > > 1) Filenames without a locale component are considered language Three rules numbered #1? Proves I should not work when I should be sleeping. > > Comments? Alternatives? Bribes? > Looks good to me. Good. If no one objects in a day or two, I'll make the change. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bbbush.yuan at gmail.com Sat Dec 10 13:15:04 2005 From: bbbush.yuan at gmail.com (Yuan Yijun) Date: Sat, 10 Dec 2005 21:15:04 +0800 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> Message-ID: <76e72f800512100515sf273247v@mail.gmail.com> 2005/12/10, jtr Tommy Reynolds : > - ? ? ? ? > + ? ? ? ? could you please explain it? -- bbbush ^_^ From Tommy.Reynolds at MegaCoder.com Sat Dec 10 14:26:00 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Sat, 10 Dec 2005 08:26:00 -0600 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <76e72f800512100515sf273247v@mail.gmail.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> <76e72f800512100515sf273247v@mail.gmail.com> Message-ID: <20051210082600.0610f51b.Tommy.Reynolds@MegaCoder.com> Uttered Yuan Yijun , spake thus: > 2005/12/10, jtr Tommy Reynolds : > > - ? ? ? ? > > + ? ? ? ? > > could you please explain it? Sorry, my i18n ignorance is showing again. Apologies if I've bungled this. The font-family is a list of candidate fonts to render the text. List items are separated by either commas or whitespace. A comma is exactly equivalent to a space. The original "AR PL ZenKai Uni" was interpreted as a list of four individual fonts. The "'AR PL ZenKai Uni'" quoting makes that whole string a single font family name. Was the original string four fonts or only one? Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bbbush.yuan at gmail.com Sat Dec 10 14:45:00 2005 From: bbbush.yuan at gmail.com (Yuan Yijun) Date: Sat, 10 Dec 2005 22:45:00 +0800 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <76e72f800512100515sf273247v@mail.gmail.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> <76e72f800512100515sf273247v@mail.gmail.com> Message-ID: <76e72f800512100645p594b43e3m@mail.gmail.com> ? 05-12-10?Yuan Yijun ??? > 2005/12/10, jtr Tommy Reynolds : > > - ? ? ? ? > > + ? ? ? ? > I think it is wrong to "triple quote" it. According to the output png file in current build, it is using the default chinese font, not the one specified. -- bbbush ^_^ From bbbush.yuan at gmail.com Sat Dec 10 14:55:21 2005 From: bbbush.yuan at gmail.com (Yuan Yijun) Date: Sat, 10 Dec 2005 22:55:21 +0800 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <20051210082600.0610f51b.Tommy.Reynolds@MegaCoder.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> <76e72f800512100515sf273247v@mail.gmail.com> <20051210082600.0610f51b.Tommy.Reynolds@MegaCoder.com> Message-ID: <76e72f800512100655t3b48d09fy@mail.gmail.com> 2005/12/10, Tommy Reynolds : > Uttered Yuan Yijun , spake thus: > > > Sorry, my i18n ignorance is showing again. Apologies if I've bungled > this. > > The font-family is a list of candidate fonts to render the text. > > List items are separated by either commas or whitespace. A comma is > exactly equivalent to a space. > > The original "AR PL ZenKai Uni" was interpreted as a list of four > individual fonts. The "'AR PL ZenKai Uni'" quoting makes that whole > string a single font family name. > > Was the original string four fonts or only one? > > Cheers > Thank you! Well I use gimp and inkscape to render that svg and both appear to use the specified font-family. But in current build, the png files are using a wrong one. This is very strange to me. :( -- bbbush ^_^ From Tommy.Reynolds at MegaCoder.com Sat Dec 10 15:45:33 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Sat, 10 Dec 2005 09:45:33 -0600 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <76e72f800512100645p594b43e3m@mail.gmail.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> <76e72f800512100515sf273247v@mail.gmail.com> <76e72f800512100645p594b43e3m@mail.gmail.com> Message-ID: <20051210094533.2864b89d.Tommy.Reynolds@MegaCoder.com> Uttered Yuan Yijun , spake thus: > I think it is wrong to "triple quote" it. According to the output png > file in current build, it is using the default chinese font, not the > one specified. Please check this version. I didn't have the RawHide fonts-chinese installed, so I didn't really have the correct font. Thanks -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bbbush.yuan at gmail.com Sat Dec 10 20:55:02 2005 From: bbbush.yuan at gmail.com (Yuan Yijun) Date: Sun, 11 Dec 2005 04:55:02 +0800 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <20051210094533.2864b89d.Tommy.Reynolds@MegaCoder.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> <76e72f800512100515sf273247v@mail.gmail.com> <76e72f800512100645p594b43e3m@mail.gmail.com> <20051210094533.2864b89d.Tommy.Reynolds@MegaCoder.com> Message-ID: <76e72f800512101255t31ffb59r@mail.gmail.com> 2005/12/10, Tommy Reynolds : > Uttered Yuan Yijun , spake thus: > > > I think it is wrong to "triple quote" it. According to the output png > > file in current build, it is using the default chinese font, not the > > one specified. > > Please check this version. I didn't have the RawHide fonts-chinese > installed, so I didn't really have the correct font. > 1.1 and 1.4 are the same, 1.2 and 1.3 are the same (or 1.3 is worse that text is not lined up). I have just received this letter, which is very strange: it should not be that slow :( -- bbbush ^_^ From Tommy.Reynolds at MegaCoder.com Sun Dec 11 02:35:37 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Sat, 10 Dec 2005 20:35:37 -0600 Subject: docs-common/images Makefile, 1.5, 1.6 watermark-de.png, 1.1, 1.2 watermark-en.png, 1.1, 1.2 watermark-it.png, 1.1, 1.2 watermark-ja_JP.png, 1.1, 1.2 watermark-ru.png, 1.1, 1.2 watermark-zh_CN.png, 1.1, 1.2 watermark-zh_CN.svg, 1.1, 1.2 In-Reply-To: <76e72f800512101255t31ffb59r@mail.gmail.com> References: <200512101243.jBAChwNA031835@cvs-int.fedora.redhat.com> <76e72f800512100515sf273247v@mail.gmail.com> <76e72f800512100645p594b43e3m@mail.gmail.com> <20051210094533.2864b89d.Tommy.Reynolds@MegaCoder.com> <76e72f800512101255t31ffb59r@mail.gmail.com> Message-ID: <20051210203537.93fbc014.Tommy.Reynolds@MegaCoder.com> Uttered Yuan Yijun , spake thus: > > Please check this version. I didn't have the RawHide fonts-chinese > > installed, so I didn't really have the correct font. > 1.1 and 1.4 are the same, 1.2 and 1.3 are the same (or 1.3 is worse > that text is not lined up). I have just received this letter, which is > very strange: it should not be that slow :( Your latest looks very good, even if I can't read anything about it. As long as we get the results by using some batch process such as rsvg(1), I am happy. Thanks for tolerating my meddling. Cheers! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jlaska at redhat.com Mon Dec 12 15:34:09 2005 From: jlaska at redhat.com (James Laska) Date: Mon, 12 Dec 2005 10:34:09 -0500 Subject: [RFC] Image filename conventions In-Reply-To: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134401649.2920.4.camel@flatline.devel.redhat.com> Greetings, What is the benefit of enforcing image filename conventions? We label our images many times by where they exist in the document (figs/ch/section-name.). I could even see a format such as "figs//.". Is the main goal to simplify the spec file %files? Thanks, James Laska On Fri, 2005-12-09 at 16:09 -0600, Tommy Reynolds wrote: > Hello, ya'll! > > Some folk have their document images in a "figs/" subdirectory tree > under the document directory. Large documents may have additional > "figs/part1" style subdirectories, too. > > The lack of a formal filenaming scheme makes selectively copying > files awkward. Below is our current convention: > > -. > > such as "watermark-ru.png". Simple, eh? > > The problem is that some filenames use the "-" minus sign to separate > words in the filename: > > this-is-my-picture.png > > Is "picture" part of the filename or the language designation? It is > difficult for a shell script to decode this just by looking at the > filename. > > I propose a file naming scheme to simplify the selective copying of > files. This will help reduce the complexity of the RPM packaging > tools. > > Only three formal rules are needed: > > 1) The minus sign "-" may not be used as part of the filename > component. > > 1) The minus sign only introduces the locale for the file. > > 1) Filenames without a locale component are considered language > neutral. > > With these conventions in place: > > "foo.png" is a language-neutral graphic. > > "foo-it.png" is a graphic with Italian text. > > "foo-bar.png" is not permitted usage. > > Comments? Alternatives? Bribes? > > Cheers > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list From Tommy.Reynolds at MegaCoder.com Mon Dec 12 16:40:52 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Mon, 12 Dec 2005 10:40:52 -0600 Subject: [RFC] Image filename conventions In-Reply-To: <1134401649.2920.4.camel@flatline.devel.redhat.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134401649.2920.4.camel@flatline.devel.redhat.com> Message-ID: <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> Uttered James Laska , spake thus: > What is the benefit of enforcing image filename conventions? We label > our images many times by where they exist in the document > (figs/ch/section-name.). I could even see a format such as > "figs//.". Is the main goal to simplify > the spec file %files? AFAICT, there are two classes of figures: language-specific and language-neutral. All neutral files should always be copied into the HTML chunk tree, or placed into the RPM. Only the matching language-specific files should be copied to the HTML chunk tree or to the RPM, because image files can get disproportionately large. When copying the "figs/" hierarchy, we need a batch method to determine the appropriateness of each file. My proposed grammar of: -. is considered language-specific . is considered language-neutral is unambiguous, so a batch method can easily select the proper files. Selection is simple to understand. I considered relaxing the part to be , but that requires heuristics to guess about the content. The "Makefile" knows the allowed set of ${LANGUAGES}, so the batch copy process could compare the final after-the-dash component against that list: language matches get copied, rejects don't. What about the file name "i-am-a-file.jpg"? It doesn't match any known language, so we could assume it is language-neutral and copy it, but then we have to deal with a filename such as "eng-to-ru.png", where no component has anything to do with the language context. This gets very complicated really fast. I hate complicated: Beauty is Elegance, Elegance is Simplicity, Simplicity is Not-Much-To-Remember, Not-Much-To-Remember is Perfection, Perfection is Beauty. Sorry, I couldn't help it ;-) Anyway, the suggested naming convention applies only to image files. If the convention causes an unreasonable burden, you can use the "Manifest-${LANG}" feature I just added. Create the file "figs/Manifest-${LANG}" whose content is the pathname, relative to "figs/" of *every* file to be copied. No filtering is done against the names read from "figs/Manifest-${LANG}", although CVS files are still ignored. Create the "figs/Manifest-${LANG}" file like this: $ cd figs $ rm -f Manifest-${LANG} $ find * -print >/tmp/Manifest-${LANG} $ mv /tmp/Manifest-${LANG} Manifest-${LANG} or any comparable way that puts relative pathnames into the file. You want: foo.png and not: figs/foo.png -or- /path/to/doc/figs/foo.png Hope this helps. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Mon Dec 12 17:01:01 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Mon, 12 Dec 2005 11:01:01 -0600 Subject: Documentation Guide Chapter 9 Message-ID: <20051212110101.77875b30.Tommy.Reynolds@MegaCoder.com> The current Documentation Guide Chapter 9 "Converting to HTML and PDF" is insufficient. Does any one mind if I update it? Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jlaska at redhat.com Mon Dec 12 17:43:55 2005 From: jlaska at redhat.com (James Laska) Date: Mon, 12 Dec 2005 12:43:55 -0500 Subject: [RFC] Image filename conventions In-Reply-To: <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134401649.2920.4.camel@flatline.devel.redhat.com> <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134409436.2920.25.camel@flatline.devel.redhat.com> On Mon, 2005-12-12 at 10:40 -0600, Tommy Reynolds wrote: > AFAICT, there are two classes of figures: language-specific and > language-neutral. All neutral files should always be copied into the > HTML chunk tree, or placed into the RPM. Only the matching > language-specific files should be copied to the HTML chunk tree or to > the RPM, because image files can get disproportionately large. Yeah I like this ... saves you from pulling in other lang specific images. > This gets very complicated really fast. I hate complicated: Couldn't agree more. We'll need to have the images/figures section of the documentation-guide (2.5. Diagrams and Image) updated to reflect these rules. Are you already set on this format? Something about leaving the image filenames open to the authors appeals to me. What are your thoughts on a directory structure instead of filename rules? Perhaps something like: figs/$lang/ figs/common/ or just figs/ If we force all images to be in the figs/ subdirectory, this will make it difficult for large documents to remain sane. Thoughts/concerns? Thanks, James Laska -- ========================================== James Laska -- jlaska at redhat.com Quality Engineering -- Red Hat, Inc. ========================================== From stickster at gmail.com Mon Dec 12 18:04:17 2005 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 12 Dec 2005 13:04:17 -0500 Subject: Documentation Guide Chapter 9 In-Reply-To: <20051212110101.77875b30.Tommy.Reynolds@MegaCoder.com> References: <20051212110101.77875b30.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134410657.12873.0.camel@localhost.localdomain> On Mon, 2005-12-12 at 11:01 -0600, Tommy Reynolds wrote: > The current Documentation Guide Chapter 9 "Converting to HTML and > PDF" is insufficient. Does any one mind if I update it? You may, and I'll do the editing/review. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Mon Dec 12 23:41:57 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Mon, 12 Dec 2005 17:41:57 -0600 Subject: [RFC] Image filename conventions In-Reply-To: <1134409436.2920.25.camel@flatline.devel.redhat.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134401649.2920.4.camel@flatline.devel.redhat.com> <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> <1134409436.2920.25.camel@flatline.devel.redhat.com> Message-ID: <20051212174157.333bbd53.Tommy.Reynolds@MegaCoder.com> Uttered James Laska , spake thus: > Are you already set on this format? Something about leaving the image > filenames open to the authors appeals to me. What are your thoughts on > a directory structure instead of filename rules? Perhaps something > like: > figs/$lang/ > figs/common/ or just figs/ > If we force all images to be in the figs/ subdirectory, this will make > it difficult for large documents to remain sane. > Thoughts/concerns? Yeah, I'm going to be pretty stubborn on the filename convention. This format mimics the decision we have for the various document translations themselves. We have a base filename ${DOCBASE}, a ${LANG} specifier, and an .xml extention. However, with the images we also allow generic images to omit the ${LANG} component. I don't really care how the "figs/" files are organized. Make a flat directory, make tons of subdirs, it all works for me. The "docs-common/bin/copy-figs" script traverses the "figs/" tree, copying individual files into corresponding subdirs in the destination. I have added the "figs/Manifest-${LANG}" file, mentioned in my previous email, so you can name your files using whatever convention you choose; the cost is having to explicity identify the files. Sound OK, now? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jlaska at redhat.com Tue Dec 13 14:23:51 2005 From: jlaska at redhat.com (James Laska) Date: Tue, 13 Dec 2005 09:23:51 -0500 Subject: [RFC] Image filename conventions In-Reply-To: <20051212174157.333bbd53.Tommy.Reynolds@MegaCoder.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134401649.2920.4.camel@flatline.devel.redhat.com> <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> <1134409436.2920.25.camel@flatline.devel.redhat.com> <20051212174157.333bbd53.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134483831.3490.21.camel@flatline.devel.redhat.com> On Mon, 2005-12-12 at 17:41 -0600, Tommy Reynolds wrote: > I have added the "figs/Manifest-${LANG}" file, mentioned in my > previous email, so you can name your files using whatever convention > you choose; the cost is having to explicity identify the files. > > Sound OK, now? It should also be noted in the documentation-guide (or where ever these rules land), that you need to include the directories in the Manifest as well. My apologies if that was stated already. Additionally, should the Manifest-${LANG} should reference images relative to the figs/ directory? For example $ cat figs/Manifest-en ch-intro/one.png ch-asdf/foo/bar.png ch-qwerty/one.png If that is the case then ../docs-common/bin/copy-figs is able to find them, however for htmlchunked output it places those files in ... ${DOCBASE}-${LANG}/ch-intro/one.png ${DOCBASE}-${LANG}/ch-asdf/foo/bar.png ${DOCBASE}-${LANG}/ch-qwerty/one.png Which now differs from how html-nochunks refers to these images: figs/ch-intro/one.png figs/ch-asdf/foo/bar.png figs/ch-qwerty/one.png For consistency, and working figures, I would suggest that copy-figs put all figures under a figs/ directory within ${DOCBASE}-${LANG} (like ${DOCBASE}-${LANG}/figs)? Am I using the Manifest-${LANG} incorrectly? Thanks, James -- ========================================== James Laska -- jlaska at redhat.com Quality Engineering -- Red Hat, Inc. ========================================== From calennert at gmail.com Tue Dec 13 15:11:42 2005 From: calennert at gmail.com (Chris Lennert) Date: Tue, 13 Dec 2005 10:11:42 -0500 Subject: Self-Introduction: Chris Lennert Message-ID: <439EE4AE.2040407@gmail.com> Full Name: Chris Lennert Location: Greenville, SC, USA (Eastern Standard Time) Profession: Network Administrator and developer Company: Woodward Governor Company Goals 1. What do you want to write about? I would be willing to cover the ServerTools beat. In addition, if the primary authors permit, I would be interested in contributing to the DesktopUserGuide and the Hardening Tutorial. 2. What other documentation do you want to see published? A Fedora-specific remote access tutorial that covers setting up VPN tunnels to several of the major firewall distros/products and which would serve as a starting point for folks looking to connect to corporate networks. Unless I am mistaken, I don't believe one exists. 3. Do you want to edit for grammar/writing and/or technical accuracy? As a former high school science teacher, I would be happy to correct grammar, "wordsmith" documents, and verify content. 4. Anything else special? I've been a dedicated consumer of FOSS for many years and have contributed in smaller ways in the past. Diving into the heart of the Fedora documentation efforts is one way for me to get off my arse and start contributing in a major way. Historical Qualifications 1. What other projects or writing have you worked on in the past? Since my job responsibilities in recent years have included user support, I have written various end-user-oriented documents. Several of these have been DocBook-based HTMLHelp documents (CHM's) for my predominantly Windows-based users. 2. What level and type of computer skills do you possess? I would characterize my level of skill as broad with moderate depth. I tend to prefer development-oriented tasks, but since my current employment also requires network/system administration and user support, I don't feel I qualify for the lofty title of "developer". Nevertheless, I am very comfortable with Java, XHTML/CSS, XSLT, DocBook markup and many of the Apache Java libraries. I have used most of the major Linux and BSD distributions though I tend to stay close to the Red Hat world. I have experience (implementation, at the least) with many of the most luminary FOSS applications. 3. What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. I like to think of myself as an All-Around Nice Guy(TM). :) 4. What makes you an excellent match for the project? * Broad level of experience covering network & system administration, user support, and software development. * Java development experience * Experience with DocBook-related toolchains (mostly Ant-, Saxon- and Apache FOP-based) and XSL customization GPG KEYID and Fingerprint KEYID: DE8B9506 [calennert at rutherford ~]$ gpg --fingerprint DE8B9506 pub 1024D/DE8B9506 2005-12-09 [expires: 2007-12-09] Key fingerprint = E199 9CAD 955D 5CB7 ADB3 B05F EACC ACF9 DE8B 9506 uid Christopher Lennert sub 2048g/6741E0E0 2005-12-09 [expires: 2007-12-09] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From Tommy.Reynolds at MegaCoder.com Tue Dec 13 16:52:07 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Tue, 13 Dec 2005 10:52:07 -0600 Subject: [RFC] Image filename conventions In-Reply-To: <1134483831.3490.21.camel@flatline.devel.redhat.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134401649.2920.4.camel@flatline.devel.redhat.com> <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> <1134409436.2920.25.camel@flatline.devel.redhat.com> <20051212174157.333bbd53.Tommy.Reynolds@MegaCoder.com> <1134483831.3490.21.camel@flatline.devel.redhat.com> Message-ID: <20051213105207.a2c27208.Tommy.Reynolds@MegaCoder.com> Uttered James Laska , spake thus: > > Sound OK, now? > It should also be noted in the documentation-guide (or where ever these > rules land), that you need to include the directories in the Manifest as > well. My apologies if that was stated already. Good idea. That was not explicitly stated. I've just checked in a new version of "copy-figs" that will create path components automatically if the Manifest-${LANG} omits the directories. > Additionally, should the Manifest-${LANG} should reference images > relative to the figs/ directory? For example Ah, caught another one! I've fixed the copy-figs script to work correctly now. A Manifest-${LANG} file should look like this: $ find figs -print >/tmp/foo && mv /tmp/foo figs/Manifest-${LANG} $ cat figs/Manifest-${LANG} figs/a/b/c/d/e/foo.png figs/Fedora_Desktop.eps figs/Fedora_Desktop.png It's OK, but no longer necessary, if directories are listed in the Manifest-${LANG} file. Also "*/CVS/*" and "*/.svn/*" entries continue to be ignored. Cheers! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jlaska at redhat.com Tue Dec 13 17:05:18 2005 From: jlaska at redhat.com (James Laska) Date: Tue, 13 Dec 2005 12:05:18 -0500 Subject: [RFC] Image filename conventions In-Reply-To: <20051213105207.a2c27208.Tommy.Reynolds@MegaCoder.com> References: <20051209160904.16f86b07.Tommy.Reynolds@MegaCoder.com> <1134401649.2920.4.camel@flatline.devel.redhat.com> <20051212104052.803b1926.Tommy.Reynolds@MegaCoder.com> <1134409436.2920.25.camel@flatline.devel.redhat.com> <20051212174157.333bbd53.Tommy.Reynolds@MegaCoder.com> <1134483831.3490.21.camel@flatline.devel.redhat.com> <20051213105207.a2c27208.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134493519.3490.41.camel@flatline.devel.redhat.com> Greetings, Now that's response time ;) Works great on my end, thanks very much for your help! Thanks, James On Tue, 2005-12-13 at 10:52 -0600, Tommy Reynolds wrote: > Uttered James Laska , spake thus: > > > > Sound OK, now? > > It should also be noted in the documentation-guide (or where ever these > > rules land), that you need to include the directories in the Manifest as > > well. My apologies if that was stated already. > > Good idea. That was not explicitly stated. I've just checked in a > new version of "copy-figs" that will create path components > automatically if the Manifest-${LANG} omits the directories. > > > Additionally, should the Manifest-${LANG} should reference images > > relative to the figs/ directory? For example > > Ah, caught another one! > > I've fixed the copy-figs script to work correctly now. A > Manifest-${LANG} file should look like this: > > $ find figs -print >/tmp/foo && mv /tmp/foo figs/Manifest-${LANG} > $ cat figs/Manifest-${LANG} > figs/a/b/c/d/e/foo.png > figs/Fedora_Desktop.eps > figs/Fedora_Desktop.png > > It's OK, but no longer necessary, if directories are listed in the > Manifest-${LANG} file. Also "*/CVS/*" and "*/.svn/*" entries > continue to be ignored. > > Cheers! > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list -- ========================================== James Laska -- jlaska at redhat.com Quality Engineering -- Red Hat, Inc. ========================================== From stuart at elsn.org Tue Dec 13 22:37:55 2005 From: stuart at elsn.org (Stuart Ellis) Date: Tue, 13 Dec 2005 22:37:55 +0000 Subject: Minutes of FDSCo Meeting Dec 13 2005 Message-ID: <1134513475.2802.29.camel@localhost.localdomain> Attending: --------- Karsten Wade (quaid) Tommy Reynolds (megacoder) Gavin Henry (G2) Tammy Fox (tcf_home) Stuart Ellis (elliss) Regrets: -------- Paul Frields (stickster) Schedule of Tasks: ------------------ http://www.fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule Highlights: ----------- * Karsten: Discussion of possible DocsRawHide enhancements. Useful developments might include: e-mail build errors to document maintainers, building of branches other than the current branch, listing of documents on Fedora Project website(s). * Tommy: Currently working on the handling of images in the document build process. * Tommy: Documentation Guide to be updated to match current build processes. * Karsten: There are still open slots for Release Note beats. An e-mail will be sent out to request a writer for the Legacy beat, and for writers to cover a new Extras beat. Other open slots: Kernel, File Systems, Development Tools, Samba, System Daemons, x86-specific content, x86_64-specific content, Database Servers, and Backwards Compatibility. Full IRC Log: ------------- https://www.redhat.com/archives/fedora-dsco-list/2005-December/msg00004.html -- Stuart Ellis stuart at elsn.org Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Tue Dec 13 22:12:38 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Tue, 13 Dec 2005 16:12:38 -0600 Subject: Self-Introduction: Chris Lennert In-Reply-To: <439EE4AE.2040407@gmail.com> References: <439EE4AE.2040407@gmail.com> Message-ID: <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> Uttered Chris Lennert , spake thus: Chris, Welcome to the FDP! First, be sure to visit the site: http://fedoraproject.org/wiki/DocsProject/NewWriters for info on how to gain full access to the project. You might consider assisting in multiple areas. Certainly the new docs you mentioned are good candidates, but FDP also has some more immediate needs, such as beat writers, so please consider that as well. We also would value your help in the tools area. We're using Apache FOP and xsltproc to render the documents into HTML and PDF, but PDF is mostly broken. You could give that some attention. These are all just suggestions to whet your appetite. Feel free to tackle one or more, or some others. Again, welcome to the club. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Wed Dec 14 03:43:45 2005 From: kwade at redhat.com (Karsten Wade) Date: Tue, 13 Dec 2005 19:43:45 -0800 Subject: Self-Introduction: Chris Lennert In-Reply-To: <439EE4AE.2040407@gmail.com> References: <439EE4AE.2040407@gmail.com> Message-ID: <1134531825.17984.61.camel@erato.phig.org> On Tue, 2005-12-13 at 10:11 -0500, Chris Lennert wrote: > Full Name: Chris Lennert Welcome, Chris. I'm 'quaid' on #fedora-docs, say howdy next time you are around. > Location: Greenville, SC, USA (Eastern Standard Time) > Profession: Network Administrator and developer > Company: Woodward Governor Company > > Goals > 1. What do you want to write about? > I would be willing to cover the ServerTools beat. Accepted! I added you to EditGroup (and DocWritersGroup) so you can control content within Docs/Beats. That area has lighter ACLs than the rest of the site, btw. > In addition, if the > primary authors permit, I would be interested in contributing to the > DesktopUserGuide and the Hardening Tutorial. Yes, I think formal Fedora end user documentation is somewhere we need deep attention. Welcome, - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Wed Dec 14 19:39:14 2005 From: kwade at redhat.com (Karsten Wade) Date: Wed, 14 Dec 2005 11:39:14 -0800 Subject: [ANN] Wiki is about to freeze for trans for test2, help needed for conversion Message-ID: <1134589154.17984.135.camel@erato.phig.org> I've been heads down on other projects and forgot to ride the schedule for the relnotes. D'oh! Mea culpa. We are two days late for freeze for translation, so have missed our agreed upon scheduling. We need to freeze soonest for test2 for trans. Freeze begins at 08:00 UTC 15 December. This gives the West Coast of the US, i.e., me, time to be useful. Is there anyone interested in helping with the conversion from MoinMoin to our XML for relnotes? The first step is automated (thanks Patrick!), so we get well-formed XML from fp.org/Docs/Beats. I need help with diffing and merging. I've been doing visual diffs, i.e., using my eyes, but I reckon that xmldiff or something similar could be really useful. I'll be working tonight, -0800 UTC (US West Coast) from before and after the 08:00 UTC freeze. I'll certainly be working on it by 21:00 PST/05:00 UTC. I also think an XML diff is useful for the translators. We need to work on getting that within our toolchain. I apologize to our friends in translation. Hopefully the content is not going to change that much, perhaps 10% churn and 15% added? Once I have a snapshot of the Wiki, at a few minutes after 08:00 UTC, I'll unfreeze the Wiki for changes. The Wiki is snapshot[1] again on 21 December at Midnight UTC for the Web-only release of the updated relnotes. That content is available for translation from CVS starting on 22 December by announcement to f-trans- list. Thanks - Karsten [1] That's right, I verbified that sucker. -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Wed Dec 14 19:42:35 2005 From: kwade at redhat.com (Karsten Wade) Date: Wed, 14 Dec 2005 11:42:35 -0800 Subject: Self-Introduction: Chris Lennert In-Reply-To: <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> References: <439EE4AE.2040407@gmail.com> <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> Message-ID: <1134589355.17984.140.camel@erato.phig.org> On Tue, 2005-12-13 at 16:12 -0600, Tommy Reynolds wrote: > Uttered Chris Lennert , spake thus: > > Chris, > > Welcome to the FDP! > > First, be sure to visit the site: > > http://fedoraproject.org/wiki/DocsProject/NewWriters > > for info on how to gain full access to the project. > > You might consider assisting in multiple areas. Certainly the new > docs you mentioned are good candidates, but FDP also has some more > immediate needs, such as beat writers, so please consider that as > well. cut-and-paste-- ;-P Chris signed up for the Server Config Tools beat (system-config-*), and he gets his chance to put in content for test2. Chris -- be sure to check out these pages in particular for beat information, if you haven't seen them already: http://fedoraproject.org/wiki/Docs/Beats/HowTo http://fedoraproject.org/wiki/DocsProject/WritingUsingTheWiki In writing this email I just discovered that I forgot to freeze the Wiki for translation of release notes content. We are two days over schedule, and I just sent details in an announcement. Freeze is 08:00 UTC 15 December. So, if you have anything for test2, now is the time to get it in. In addition, if you want to work in the XML directly, I can expedite the CVS and related. Make sure you follow this and subsequent pages to get access: https://admin.fedora.redhat.com/accounts/ > We also would value your help in the tools area. We're using Apache > FOP and xsltproc to render the documents into HTML and PDF, but PDF > is mostly broken. You could give that some attention. Yes, we can fill you in on this area, much continuing help is needed. Satisfy your content and programming monkeys! - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From calennert at gmail.com Wed Dec 14 21:30:02 2005 From: calennert at gmail.com (Chris Lennert) Date: Wed, 14 Dec 2005 16:30:02 -0500 Subject: Self-Introduction: Chris Lennert In-Reply-To: <1134589355.17984.140.camel@erato.phig.org> References: <439EE4AE.2040407@gmail.com> <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> <1134589355.17984.140.camel@erato.phig.org> Message-ID: <43A08EDA.3070400@gmail.com> Thanks for the welcome! Karsten Wade wrote: --snip-- > Chris signed up for the Server Config Tools beat (system-config-*), and > he gets his chance to put in content for test2. --snip-- > So, if you have anything for test2, now is the time to > get it in. I am currently subscribed to the fedora-announce-list and fedora-relnotes-content lists ATM. The Docs/Beats/HowTo states that membership in the relnotes at fedoraproject.org mail alias is currently suspended. Has anything passed via this alias that is test2 & ServerTools relevant that I should know about? > In addition, if you want to work in the XML directly, I can expedite the > CVS and related. Make sure you follow this and subsequent pages to get > access: > > https://admin.fedora.redhat.com/accounts/ I went through the Fedora account steps before I sent out the Self Introduction. The cla_done membership is complete with status 'approved'. The cvsdocs membership is still pending with status 'unapproved'. >>We also would value your help in the tools area. We're using Apache >>FOP and xsltproc to render the documents into HTML and PDF, but PDF >>is mostly broken. You could give that some attention. Already working on it! :) With a couple of changes to Makefile.common (docs-common), I have the Hardening guide PDF build working via Saxon and Apache FOP 0.20.5. But, the Documentation Guide fails miserably. Before I get too far, I should get a deeper understanding of which software licenses are kosher for incorporation into this project's toolchain (strictly GPL?). > Yes, we can fill you in on this area, much continuing help is needed. > Satisfy your content and programming monkeys! > > - Karsten > Thanks again! Sincerely, Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From sundaram at redhat.com Wed Dec 14 21:38:57 2005 From: sundaram at redhat.com (Rahul Sundaram) Date: Thu, 15 Dec 2005 03:08:57 +0530 Subject: Self-Introduction: Chris Lennert In-Reply-To: <43A08EDA.3070400@gmail.com> References: <439EE4AE.2040407@gmail.com> <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> <1134589355.17984.140.camel@erato.phig.org> <43A08EDA.3070400@gmail.com> Message-ID: <43A090F1.50804@redhat.com> Hi >Before I get too >far, I should get a deeper understanding of which software licenses are kosher >for incorporation into this project's toolchain (strictly GPL?). > > Any Free and open source license and it should be legally unencumbered. regards Rahul From Tommy.Reynolds at MegaCoder.com Thu Dec 15 04:20:17 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Wed, 14 Dec 2005 22:20:17 -0600 Subject: [ANN] Wiki is about to freeze for trans for test2, help needed for conversion In-Reply-To: <1134589154.17984.135.camel@erato.phig.org> References: <1134589154.17984.135.camel@erato.phig.org> Message-ID: <20051214222017.c76bf813.Tommy.Reynolds@MegaCoder.com> Uttered Karsten Wade , spake thus: > I also think an XML diff is useful for the translators. We need to work > on getting that within our toolchain. Claiming expediency, I've entered a 95% solution into "docs-common/bin/xmldiff" that may be enough to give your eyes a rest. HTH -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nman64 at n-man.com Sat Dec 17 13:12:11 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Sat, 17 Dec 2005 07:12:11 -0600 Subject: freenode Message-ID: <43A40EAB.7000605@n-man.com> Over the last 20 hours, freenode has been trying to deal with a massive botnet attack. Over the course of that time, they removed the irc.freenode.net server to chat.freenode.net. Service has now been restored to irc.freenode.net, but freenode is considering a permanent transition to chat.freenode.net. In order to prepare for whatever changes freenode may make, I have adjusted references to irc.freenode.net on the wiki to point at the freenode website (http://freenode.net/) instead. For more information, or if you have trouble connecting to freenode, please see the news on their website at http://freenode.net/news.shtml I would encourage anyone who maintains websites or documentation to update their information in a similar manner. While we can expect irc.freeenode.net to remain operational for a long time to come, pointing to freenode's website rather than a server directly avoids dependency upon that server, and users will likely experience better service by visiting freenode's site and selecting a server that is geographically close to their location. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From bbbush.yuan at gmail.com Sat Dec 17 14:21:02 2005 From: bbbush.yuan at gmail.com (Yuan Yijun) Date: Sat, 17 Dec 2005 22:21:02 +0800 Subject: docs rawhide install guide zh_CN is not built by default Message-ID: <76e72f800512170621m221f056bk@mail.gmail.com> Hi, I committed an updated version of translation but it was not built during last hour. What should I do to enable building? -- bbbush ^_^ From nman64 at n-man.com Sat Dec 17 14:42:06 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Sat, 17 Dec 2005 08:42:06 -0600 Subject: docs rawhide install guide zh_CN is not built by default In-Reply-To: <76e72f800512170621m221f056bk@mail.gmail.com> References: <76e72f800512170621m221f056bk@mail.gmail.com> Message-ID: <43A423BE.7020608@n-man.com> Yuan Yijun wrote: > Hi, > > I committed an updated version of translation but it was not built > during last hour. What should I do to enable building? > > > -- > bbbush ^_^ > > It appears to have built with the most recent round at 0900 U.S. Eastern time. Can you verify this? http://webtest.fedora.redhat.com/docs/RELEASE-NOTES/zh_CN/ -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From Tommy.Reynolds at MegaCoder.com Sat Dec 17 14:54:58 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Sat, 17 Dec 2005 08:54:58 -0600 Subject: docs rawhide install guide zh_CN is not built by default In-Reply-To: <76e72f800512170621m221f056bk@mail.gmail.com> References: <76e72f800512170621m221f056bk@mail.gmail.com> Message-ID: <20051217085458.e3df073c.Tommy.Reynolds@MegaCoder.com> Uttered Yuan Yijun , spake thus: > I committed an updated version of translation but it was not built > during last hour. What should I do to enable building? A prior document doesn't build from CVS. I get a message: "No rule to make target fedora-install-guide-adminoptions-ja-JP.xml" and the make(1) stops. I'll update the "docs-common/bin/bulkbuild". Stickster, hope you don't mind to review it and promote the file to wherever it goes to be actually used. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nman64 at n-man.com Sat Dec 17 15:20:57 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Sat, 17 Dec 2005 09:20:57 -0600 Subject: docs rawhide install guide zh_CN is not built by default In-Reply-To: <20051217085458.e3df073c.Tommy.Reynolds@MegaCoder.com> References: <76e72f800512170621m221f056bk@mail.gmail.com> <20051217085458.e3df073c.Tommy.Reynolds@MegaCoder.com> Message-ID: <43A42CD9.2040007@n-man.com> Tommy Reynolds wrote: > Uttered Yuan Yijun , spake thus: > > > I committed an updated version of translation but it was not built > > during last hour. What should I do to enable building? > > A prior document doesn't build from CVS. I get a message: > > "No rule to make target > fedora-install-guide-adminoptions-ja-JP.xml" > > and the make(1) stops. > > I'll update the "docs-common/bin/bulkbuild". > > Stickster, hope you don't mind to review it and promote the file to > wherever it goes to be actually used. > > Cheers > Let me know whenever you have your fixes in CVS. There are some problems with access to the webtest server right now caused by some of the work going on for FAIP, so it may be a little while before I can apply the changes. I'm working to get that resolved ASAP. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From nman64 at n-man.com Sat Dec 17 15:25:13 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Sat, 17 Dec 2005 09:25:13 -0600 Subject: docs rawhide install guide zh_CN is not built by default In-Reply-To: <43A423BE.7020608@n-man.com> References: <76e72f800512170621m221f056bk@mail.gmail.com> <43A423BE.7020608@n-man.com> Message-ID: <43A42DD9.5060307@n-man.com> Patrick Barnes wrote: > Yuan Yijun wrote: > > Hi, > > > > I committed an updated version of translation but it was not built > > during last hour. What should I do to enable building? > > > > > > -- > > bbbush ^_^ > > > > > It appears to have built with the most recent round at 0900 U.S. Eastern > time. Can you verify this? > > http://webtest.fedora.redhat.com/docs/RELEASE-NOTES/zh_CN/ > > ^^ Disregard this message ^^ I was looking at the wrong component, sorry. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From mjbrej at sbcglobal.net Sat Dec 17 22:10:20 2005 From: mjbrej at sbcglobal.net (Martin Joseph Brej) Date: Sat, 17 Dec 2005 14:10:20 -0800 Subject: Self Introduction: Martin Joseph Brej Message-ID: <1134857420.2968.21.camel@localhost.localdomain> 1. Full legal name: Martin Joseph Brej * City, Country, Timezone: Monterey, California, USA (Pacific Time) * Profession: Software Consulting Manager * Company: International Business Machines Corporation * My goals in the Fedora Project: I enjoy using Fedora as a platform for my home personal computing needs and would very much like to help others become open source users as well--to help take the technology mainstream. I am not a coder, but do consider myself to be a power-user with strong familiarity with software development processes. I am a liberal arts major with a passion for explaining technology to others. * What do you want to write about? I am open to writing for any area within Fedora that most needs the help. My personal experience is that many programs are not documented or have documentation that is "rough and ready". I could help cover areas no one else currently is or supplement areas which are currently documented but in need of some polishing. * What other documentation do you want to see published? I have often looked at the documentation to get the answer to a configuration setting or to solve a problem on my own and found that it did not answer my question. * Do you want to edit for grammar/writing and/or technical accuracy? I am happy to edit for grammar/"read-ability" and technical accuracy if that is where I can best contribute immediately. I am not a professional writer, so that may be a good way for me to break in as a documentation contributor for Fedora. * Anything else special? I am an enthusiastic guy--what I may lack in experience, I know I will make up for in dedication and enthusiasm. Between work and family life, I do not have a ton of free time, but will commit realistically to deliverables and deadlines and deliver high quality work. My goal will be to write the doc that I wish were there when I needed to use it. * Historical qualifications * What other projects or writing have you worked on in the past? I have been on numerous software implementation projects as a programmer, designer, architect and project manager over my 17 years in the industry. I have written many presentations for customers and some training materials and documentation for the systems delivered. I have never been a documentation professional, however. * What level and type of computer skills do you have? I would label myself a "power-user". I like to diddle around and see how things work and learn the advanced configuration options, etc. It have been many years since I have been at the code level. I have played around recently with learning Java and scripting on the side, but have no serious programming skills to speak of anymore. * What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. I am a very organized worker--part of my project management background, so over time, that may be an area that I can contribute as well. * What makes you an excellent match for the project? I spend most of my free time using Fedora and am passionate about building great software that is useful to others (and ideally, easy to use!) I think I express myself clearly and would like to contribute to Fedora instead of just consuming other people's excellent work without giving anything back. * GPG KEYID and fingerprint * pub 1024D/14A0CF3B 2005-12-02 [expires: 2006-12-02] * Key fingerprint = 202E 9B0A 2D20 C9B6 D703 1504 51D1 E1E8 14A0 CF3B * uid Martin Joseph Brej (Marty) * sub 1024g/273B7E4A 2005-12-02 [expires: 2006-12-02] --------------------------------------- Martin Joseph Brej 326 Monroe Street Monterey, CA 93940-2218 831-375-2735 h 831-521-3925 m mjbrej at sbcglobal.net e martinbrej (Yahoo!) im Ask me about getting a personal digital certificate. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: seal_wot.gif Type: image/gif Size: 3060 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3168 bytes Desc: not available URL: From kwade at redhat.com Mon Dec 19 18:40:12 2005 From: kwade at redhat.com (Karsten Wade) Date: Mon, 19 Dec 2005 10:40:12 -0800 Subject: [Fwd: Fedora Core 5 Test 2 slipping until January 16] Message-ID: <1135017612.30772.116.camel@erato.phig.org> My friends, FYI, information below about the FC5 test2 schedule slip. Sorry to all about the delay from the documentation side. We missed our freeze last week. Fortunately, we now have more time to fix the problems in our process and make our promise next time! I am updating our documentation schedule this evening to reflect these new dates. Thanks - Karsten -------- Forwarded Message -------- From: Jesse Keating Reply-To: For testers of Fedora Core development releases To: List for Fedora Package Maintainers , For testers of Fedora Core development releases , fedora-devel-list at redhat.com Subject: Fedora Core 5 Test 2 slipping until January 16 Date: Mon, 19 Dec 2005 09:14:42 -0800 Dashing through the builds In a one cup holder desk O're the build errors we go Swearing all the way! Phones on dev's desks ring Making Managers frown What fun it is to cuss and swear re-baseing on GCC! Oh, software sucks, Software sucks, Software really sucks! Oh what fun it is to slip our release for a month! Software sucks, Software sucks, Software really sucks! Oh, what fun it is to slip our release for a month! We rebuilt java* once It wasn't very nice we rebuilt everything else to our user's delight! Broken deps still there Making testing fun We really thing we need to test for another month! Oh, software sucks, Software sucks, Software really sucks! Oh what fun it is to slip our release for a month! Oh What Fun It Is To Slip Our Release For A Monnnnnnnnnnnnnnnnth!!! Ok, it won't be a full month, but due to the recent upgrade of gcc and the subsequent full rebuild of everything that does (and doesn't, whoops!) get built with gcc, including java stuff with gcj, and the need to further test package selection windows in Anaconda, system-config-packages for upgrades, and the development tree in general once we settle down the rebuilds, we have decided to delay test2. Here is a new schedule that we will be working toward: * Test2 freeze date to 9 January * Test2 release, 16 January * Test3 freeze, 6 February * Test3 release, 13 February * Final absolute freeze, 6 March * Release, 15 March We are going to try very hard to have a stable(ish) tree suitable for testing over the holidays, so that Test2 will be better for the slip and keep us in line with getting Test3 and eventually the final release out in the best shape possible. Thank you all for your hard work in helping us develop the best distribution we can! -- Jesse Keating Release Engineer: Fedora -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stuart at elsn.org Mon Dec 19 19:27:47 2005 From: stuart at elsn.org (Stuart Ellis) Date: Mon, 19 Dec 2005 19:27:47 +0000 Subject: Self Introduction: Martin Joseph Brej In-Reply-To: <1134857420.2968.21.camel@localhost.localdomain> References: <1134857420.2968.21.camel@localhost.localdomain> Message-ID: <1135020467.9191.41.camel@localhost.localdomain> On Sat, 2005-12-17 at 14:10 -0800, Martin Joseph Brej wrote: > 1. Full legal name: Martin Joseph Brej > > * City, Country, Timezone: Monterey, California, USA (Pacific > Time) > > * Profession: Software Consulting Manager > > * Company: International Business Machines Corporation > > * My goals in the Fedora Project: I enjoy using Fedora as a > platform for my home personal computing needs and would very > much like to help others become open source users as well--to > help take the technology mainstream. I am not a coder, but do > consider myself to be a power-user with strong familiarity > with software development processes. I am a liberal arts > major with a passion for explaining technology to others. > > * What do you want to write about? I am open to writing > for any area within Fedora that most needs the help. > My personal experience is that many programs are not > documented or have documentation that is "rough and > ready". I could help cover areas no one else > currently is or supplement areas which are currently > documented but in need of some polishing. Welcome to the project ! There are several documents where an additional writer would be extremely helpful: - Release Notes: we have vacancies for writers to cover some of the sections. This doesn't require much of time commitment, and is a fairly easy way to get started. The page is here: http://www.fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats - Documents in progress: There are half-a-dozen documents in early phases, and an additional writer would be welcome for any of them: http://www.fedoraproject.org/wiki/Docs/Drafts You could also pick up one of these, or propose your own subject: http://www.fedoraproject.org/wiki/DocsProject/DocIdeas Probably the best thing to do is to have a look through, and pick an area that interests you personally. To get started, you can then either e-mail, or join the IRC channel (#fedora-docs on Freenode). -- Stuart Ellis stuart at elsn.or -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Tue Dec 20 03:57:11 2005 From: kwade at redhat.com (Karsten Wade) Date: Mon, 19 Dec 2005 19:57:11 -0800 Subject: Self-Introduction: Chris Lennert In-Reply-To: <43A08EDA.3070400@gmail.com> References: <439EE4AE.2040407@gmail.com> <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> <1134589355.17984.140.camel@erato.phig.org> <43A08EDA.3070400@gmail.com> Message-ID: <1135051031.30772.131.camel@erato.phig.org> On Wed, 2005-12-14 at 16:30 -0500, Chris Lennert wrote: > Thanks for the welcome! > > Karsten Wade wrote: > --snip-- > > Chris signed up for the Server Config Tools beat (system-config-*), and > > he gets his chance to put in content for test2. > --snip-- > > So, if you have anything for test2, now is the time to > > get it in. > > I am currently subscribed to the fedora-announce-list and > fedora-relnotes-content lists ATM. The Docs/Beats/HowTo states that membership > in the relnotes at fedoraproject.org mail alias is currently suspended. Has > anything passed via this alias that is test2 & ServerTools relevant that I > should know about? Nothing yet, but I'll look through the bug reports again to confirm. > > In addition, if you want to work in the XML directly, I can expedite the > > CVS and related. Make sure you follow this and subsequent pages to get > > access: > > > > https://admin.fedora.redhat.com/accounts/ > > I went through the Fedora account steps before I sent out the Self Introduction. > The cla_done membership is complete with status 'approved'. The cvsdocs > membership is still pending with status 'unapproved'. You are approved now. I didn't receive the request, something is not working as expected to automatically tell us about requests. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From nman64 at n-man.com Tue Dec 20 05:20:55 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Mon, 19 Dec 2005 23:20:55 -0600 Subject: docs rawhide install guide zh_CN is not built by default In-Reply-To: <20051217085458.e3df073c.Tommy.Reynolds@MegaCoder.com> References: <76e72f800512170621m221f056bk@mail.gmail.com> <20051217085458.e3df073c.Tommy.Reynolds@MegaCoder.com> Message-ID: <43A794B7.8070207@n-man.com> Tommy Reynolds wrote: > Uttered Yuan Yijun , spake thus: > > > I committed an updated version of translation but it was not built > > during last hour. What should I do to enable building? > > A prior document doesn't build from CVS. I get a message: > > "No rule to make target > fedora-install-guide-adminoptions-ja-JP.xml" > > and the make(1) stops. > > I'll update the "docs-common/bin/bulkbuild". > > Stickster, hope you don't mind to review it and promote the file to > wherever it goes to be actually used. > > Cheers > I've uploaded the new script and initiated its first run with the new flag switched on. I've also updated the cron job to use the new flag. The new script has also been rolled into the package I've been working on. You can grab the latest version of that 'build-docs' package (as an SRPM) at http://fedora.n-man.com/fedora/devel/SRPMS/ -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From calennert at gmail.com Tue Dec 20 11:34:11 2005 From: calennert at gmail.com (Chris Lennert) Date: Tue, 20 Dec 2005 06:34:11 -0500 Subject: Self-Introduction: Chris Lennert In-Reply-To: <1135051031.30772.131.camel@erato.phig.org> References: <439EE4AE.2040407@gmail.com> <20051213161238.c6388b26.Tommy.Reynolds@MegaCoder.com> <1134589355.17984.140.camel@erato.phig.org> <43A08EDA.3070400@gmail.com> <1135051031.30772.131.camel@erato.phig.org> Message-ID: <43A7EC33.3000704@gmail.com> Karsten Wade wrote: > On Wed, 2005-12-14 at 16:30 -0500, Chris Lennert wrote: > >>Thanks for the welcome! >> >>Karsten Wade wrote: >>--snip-- >> >>>Chris signed up for the Server Config Tools beat (system-config-*), and >>>he gets his chance to put in content for test2. >> >>--snip-- >> >>>So, if you have anything for test2, now is the time to >>>get it in. >> >>I am currently subscribed to the fedora-announce-list and >>fedora-relnotes-content lists ATM. The Docs/Beats/HowTo states that membership >>in the relnotes at fedoraproject.org mail alias is currently suspended. Has >>anything passed via this alias that is test2 & ServerTools relevant that I >>should know about? > > > Nothing yet, but I'll look through the bug reports again to confirm. I don't want to make work for you. I just wanted to make sure that nothing had been noted via that alias. >>>In addition, if you want to work in the XML directly, I can expedite the >>>CVS and related. Make sure you follow this and subsequent pages to get >>>access: >>> >>>https://admin.fedora.redhat.com/accounts/ >> >>I went through the Fedora account steps before I sent out the Self Introduction. >> The cla_done membership is complete with status 'approved'. The cvsdocs >>membership is still pending with status 'unapproved'. > > > You are approved now. I didn't receive the request, something is not > working as expected to automatically tell us about requests. Thanks. I was able to checkout via :ext:clennert as of last Thursday and I'm now entertaining myself with PDF generation. All in all, the wiki docs for getting started in the Docs Project and setting up the various accounts are excellent...which is what you would expect from a group of documentation writers. :) Take care, Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From stickster at gmail.com Tue Dec 20 12:31:11 2005 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 20 Dec 2005 07:31:11 -0500 Subject: [Fwd: Fedora Core 5 Test 2 slipping until January 16] In-Reply-To: <1135017612.30772.116.camel@erato.phig.org> References: <1135017612.30772.116.camel@erato.phig.org> Message-ID: <1135081871.12125.2.camel@localhost.localdomain> On Mon, 2005-12-19 at 10:40 -0800, Karsten Wade wrote: > My friends, FYI, information below about the FC5 test2 schedule slip. > > Sorry to all about the delay from the documentation side. We missed our > freeze last week. Fortunately, we now have more time to fix the > problems in our process and make our promise next time! > > I am updating our documentation schedule this evening to reflect these > new dates. Not such a bad thing from where I'm sitting... With the holidays and family commitments it's been difficult cutting time to work on docs packaging. With a week off between the Christmas and New Year holidays I hope to dedicate some time on that issue. Hope everyone has a safe and happy holiday! -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From andrewm at inventa.ru Tue Dec 20 16:37:09 2005 From: andrewm at inventa.ru (Andrew Martynov) Date: Tue, 20 Dec 2005 19:37:09 +0300 Subject: [FYI] Apache FOP 0.90BETA1 Trial In-Reply-To: <20051208212249.9c4e8e9b.Tommy.Reynolds@MegaCoder.com> References: <20051208212249.9c4e8e9b.Tommy.Reynolds@MegaCoder.com> Message-ID: <20051220163709.GA14550@mk61.inventa.ru> Hello, Tommy! Sorry for long reply. Could you show me how to build PDF using new FOP version? Please copy-paste couple of lines from your .bash_history. I tried to generate Russian and other variants. All of my efforts was aborted with PDF file size just some bytes. My build platform: - RHEL 4 Update 2 - IBM Java machine from Extras channel - FOP (new version) Regards, Andrew Martynov On Thu, Dec 08, 2005 at 09:22:49PM -0600, Tommy Reynolds wrote: > Hello, all! > > This is a status update. As you probably know, FDP intend to use > Apache FOP to render the PDF versions of our documents. The 0.20.5 > version is quite old; furious development is underway. > > The Apache FOP team have made available a beta release of their > heavily-rewritten product. You can find out more from their > > http://xmlgraphics.apache.org/fop/relnotes.html > > web site. I tried it out against the CVS versions of the Fedora > Release Notes and thought you might like to see the results. You can > find the English and Italian versions here: > > http://www.megacoder.com/nobots/RELEASE-NOTES-en.pdf > http://www.megacoder.com/nobots/RELEASE-NOTES-it.pdf > > The Japanese version built, but the wrong font was used, so everything > was a '#' character. The Russian version aborted. > > I think they look remarkably good, given that I used the original, > mostly-generic PDF stylesheets. > > I haven't tried to compile this using GCJ; that's out of my range. > Perhaps one of you might make one attempt, just to see what happens. > > As Karsten mentioned earlier, we should be getting some help with the > graphics rendering component -- so we can avoid the closed-source > libraries FOP uses. However, if we stick with .JPG and .EPS input > graphics, the built-in FOP support should be quite good enough. We > just need to get the GCJ compile going... Still, I prefer .PNG image > files and am looking forward to the "correct" solution. > > Cheers > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list -- Andrew Martynov Inventa phone +7(095)7758777 fax +7(095)9270981 http://www.rhd.ru andrewm at inventa.ru From Tommy.Reynolds at MegaCoder.com Tue Dec 20 20:48:44 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Tue, 20 Dec 2005 14:48:44 -0600 Subject: [FYI] Apache FOP 0.90BETA1 Trial In-Reply-To: <20051220163709.GA14550@mk61.inventa.ru> References: <20051208212249.9c4e8e9b.Tommy.Reynolds@MegaCoder.com> <20051220163709.GA14550@mk61.inventa.ru> Message-ID: <20051220144844.a0055024.Tommy.Reynolds@MegaCoder.com> Uttered Andrew Martynov , spake thus: > Could you show me how to build PDF using new FOP version? I'm using the new FOP built from CVS, along with the xmlto(1) RPM that I patched to use FOP. I use my own FOP wrapper; I've included it here: ==[/opt/bin/fop]== #!/bin/zsh # export FOP=fop.sh # export FOP_HOME=/opt/fop-0.20.5/ # export FOP_HOME=/opt/fop-0.90svn/ export FOP_HOME=/opt/fop-0.90alpha1/ export FOP=fop export FOP_OPTS=-Xmx500m exec ${FOP_HOME}/${FOP} $@ ==[/opt/bin/fop]== You can get a copy of the xmlto RPM from: ftp://ftp.megacoder.com/pub/xmlto-0.0.18-7.src.rpm ftp://ftp.megacoder.com/pub/xmlto-0.0.18-7.i386.rpm With these two items in place, all I did was: $ cd release-notes $ make LANGUAGES=ru html Let me know how this works for you. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Thu Dec 22 18:45:42 2005 From: kwade at redhat.com (Karsten Wade) Date: Thu, 22 Dec 2005 10:45:42 -0800 Subject: [Fwd: Fedora Core 5 Test 2 slipping until January 16] In-Reply-To: <1135081871.12125.2.camel@localhost.localdomain> References: <1135017612.30772.116.camel@erato.phig.org> <1135081871.12125.2.camel@localhost.localdomain> Message-ID: <1135277142.30772.250.camel@erato.phig.org> On Tue, 2005-12-20 at 07:31 -0500, Paul W. Frields wrote: > On Mon, 2005-12-19 at 10:40 -0800, Karsten Wade wrote: > > My friends, FYI, information below about the FC5 test2 schedule slip. > Not such a bad thing from where I'm sitting... Oh, I never complain about more time ... unless I'm the consumer who has to wait longer! > With the holidays and > family commitments it's been difficult cutting time to work on docs > packaging. With a week off between the Christmas and New Year holidays > I hope to dedicate some time on that issue. I'll be around in the evenings PST time (after 8 pm) and on some early mornings. *sssh* Don't tell RHAT, we're all supposed to be on holiday. :) > Hope everyone has a safe > and happy holiday! Wherever you are, either the days are getting longer or getting shorter. Be cheery and well, my friends. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From calennert at gmail.com Thu Dec 22 20:39:19 2005 From: calennert at gmail.com (Chris Lennert) Date: Thu, 22 Dec 2005 15:39:19 -0500 Subject: Docs/Beats/Samba page update Message-ID: <43AB0EF7.5020000@gmail.com> Anyone mind if I update the Docs/Beats/Samba relnote page? In diving into some of the Docs/Beats/ServerTools BZ items, it appears that the Samba browsing warning is no longer warranted. Since the beat is uncovered, I don't mind updating the page to at least reflect this (welcome) change for FC5. -- Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From sundaram at redhat.com Thu Dec 22 20:51:20 2005 From: sundaram at redhat.com (Rahul Sundaram) Date: Fri, 23 Dec 2005 02:21:20 +0530 Subject: Docs/Beats/Samba page update In-Reply-To: <43AB0EF7.5020000@gmail.com> References: <43AB0EF7.5020000@gmail.com> Message-ID: <43AB11C8.4070208@redhat.com> Chris Lennert wrote: >Anyone mind if I update the Docs/Beats/Samba relnote page? In diving into some >of the Docs/Beats/ServerTools BZ items, it appears that the Samba browsing >warning is no longer warranted. Since the beat is uncovered, I don't mind >updating the page to at least reflect this (welcome) change for FC5. > >-- Chris > > If you want to edit of any pages go ahead. We can revert back changes if necessary at any point of time. -- Rahul Learn. Network. Experience open source. Red Hat Summit Nashville | May 30 - June 2, 2006 Learn more: http://www.redhat.com/promo/summit/ From kwade at redhat.com Fri Dec 23 17:26:33 2005 From: kwade at redhat.com (Karsten Wade) Date: Fri, 23 Dec 2005 09:26:33 -0800 Subject: Docs/Beats/Samba page update In-Reply-To: <43AB11C8.4070208@redhat.com> References: <43AB0EF7.5020000@gmail.com> <43AB11C8.4070208@redhat.com> Message-ID: <1135358793.30772.253.camel@erato.phig.org> On Fri, 2005-12-23 at 02:21 +0530, Rahul Sundaram wrote: > Chris Lennert wrote: > > >Anyone mind if I update the Docs/Beats/Samba relnote page? In diving into some > >of the Docs/Beats/ServerTools BZ items, it appears that the Samba browsing > >warning is no longer warranted. Since the beat is uncovered, I don't mind > >updating the page to at least reflect this (welcome) change for FC5. > > > >-- Chris > > > > > If you want to edit of any pages go ahead. We can revert back changes > if necessary at any point of time. Agreed. In fact, the ideal job of a beat writer is to watch and edit changes that _others_ make. You know, treat it like a Wiki. :) So, please help each other, and encourage others to edit the Docs/Beats directly. Especially the developers within the projects. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Fri Dec 23 17:41:40 2005 From: kwade at redhat.com (Karsten Wade) Date: Fri, 23 Dec 2005 09:41:40 -0800 Subject: Self Introduction: Martin Joseph Brej In-Reply-To: <1134857420.2968.21.camel@localhost.localdomain> References: <1134857420.2968.21.camel@localhost.localdomain> Message-ID: <1135359700.30772.261.camel@erato.phig.org> On Sat, 2005-12-17 at 14:10 -0800, Martin Joseph Brej wrote: > 1. Full legal name: Martin Joseph Brej > > * City, Country, Timezone: Monterey, California, USA (Pacific > Time) Let's get together at a LUG sometime soon and discuss Fedora Ambassador ideas, as well as general geeking. SMAUG (Santa Cruz Microsoft Alternatives Users Group) meets every Monday night at 8 pm at Tiny's in Capitola, and I'm sure the Gentoosians there would love to ridicule our efforts. ;-D Grand! Welcome, looks like you'll fit in quite nicely. I think we may need to review the self-intro, as it is quite writer focused. We have needs beyond writing/editing, although that is obviously the bulk of who should be on the project. For example, I'm going to send out a request for scriptwriting and video editing to this list, as we work on a Fedora Tour. Very different set of skills than your run-of-the-mill tech writing background. :) > * What other skills do you have that might be > applicable? User interface design, other so-called > soft skills (people skills), programming, etc. I am a > very organized worker--part of my project management > background, so over time, that may be an area that I > can contribute as well. One area that I think Fedora, and most FLOSS projects, need is good project management. We don't have to launch a formal effort necessarily, but any ideas you have in this regard for the Fedora Documentation Project are much appreciated. I've worked in PS organizations with real PMs, and what an amazing difference a well run project is. I aspire to doing that within FDP. We can then export our ideas, processes, templates, etc. to other projects. cheers - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Tue Dec 27 16:14:12 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Tue, 27 Dec 2005 10:14:12 -0600 Subject: OpenOffice stylesheets Message-ID: <20051227101412.bfc9c062.Tommy.Reynolds@MegaCoder.com> Greetings, If memory serves me correctly, and there's always a first time, someone looked into using OpenOffice to output DocBook. Doesn't this need a stylesheet or something? I thouht it may be time to revisit this. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nman64 at n-man.com Wed Dec 28 01:45:06 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Tue, 27 Dec 2005 19:45:06 -0600 Subject: OpenOffice stylesheets In-Reply-To: <20051227101412.bfc9c062.Tommy.Reynolds@MegaCoder.com> References: <20051227101412.bfc9c062.Tommy.Reynolds@MegaCoder.com> Message-ID: <43B1EE22.4030104@n-man.com> Tommy Reynolds wrote: > Greetings, > > If memory serves me correctly, and there's always a first time, > someone looked into using OpenOffice to output DocBook. Doesn't this > need a stylesheet or something? I thouht it may be time to revisit > this. > > Cheers > DocBook export is a feature of OpenOffice.org 2.0. All you need is to install the openoffice.org-xsltfilter and openoffice.org-javafilter packages to enable it. I've not looked into the quality of the DocBook output it produces, but I'm sure we could come up with ways to clean it up or templates/guidelines to follow to get it producing what we need. I'm not sure if it can import DocBook, but I don't even know if we'd need it to. I suppose it is a similar situation to what we have with the wiki. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From nman64 at n-man.com Wed Dec 28 01:47:49 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Tue, 27 Dec 2005 19:47:49 -0600 Subject: OpenOffice stylesheets In-Reply-To: <43B1EE22.4030104@n-man.com> References: <20051227101412.bfc9c062.Tommy.Reynolds@MegaCoder.com> <43B1EE22.4030104@n-man.com> Message-ID: <43B1EEC5.5050309@n-man.com> Patrick Barnes wrote: > Tommy Reynolds wrote: > > Greetings, > > > > If memory serves me correctly, and there's always a first time, > > someone looked into using OpenOffice to output DocBook. Doesn't this > > need a stylesheet or something? I thouht it may be time to revisit > > this. > > > > Cheers > > > DocBook export is a feature of OpenOffice.org 2.0. All you need is to > install the openoffice.org-xsltfilter and openoffice.org-javafilter > packages to enable it. I've not looked into the quality of the DocBook > output it produces, but I'm sure we could come up with ways to clean it > up or templates/guidelines to follow to get it producing what we need. > I'm not sure if it can import DocBook, but I don't even know if we'd > need it to. I suppose it is a similar situation to what we have with > the wiki. > > On a further note, since the OpenDocument format is XML, I would imagine it wouldn't be too difficult to find or produce a solution in XSLT to 'import' the DocBook back into OpenOffice.org. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ -- Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From mrj at debian.org Wed Dec 28 01:51:46 2005 From: mrj at debian.org (Mark Johnson) Date: Tue, 27 Dec 2005 20:51:46 -0500 Subject: OpenOffice stylesheets In-Reply-To: <43B1EEC5.5050309@n-man.com> References: <20051227101412.bfc9c062.Tommy.Reynolds@MegaCoder.com> <43B1EE22.4030104@n-man.com> <43B1EEC5.5050309@n-man.com> Message-ID: <43B1EFB2.3010907@debian.org> Patrick Barnes wrote: >> [...] >> > On a further note, since the OpenDocument format is XML, I would imagine > it wouldn't be too difficult to find or produce a solution in XSLT to > 'import' the DocBook back into OpenOffice.org. Absolutely doable. The problem, as usual, is finding someone who has the time... Cheers, Mark -- ___________________________________________________________ Mark Johnson Debian XML/SGML: Home Page: GPG fp: DBEA FA3C C46A 70B5 F120 568B 89D5 4F61 C07D E242 From Tommy.Reynolds at MegaCoder.com Wed Dec 28 21:02:31 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Wed, 28 Dec 2005 15:02:31 -0600 Subject: OpenOffice stylesheets In-Reply-To: <43B1EFB2.3010907@debian.org> References: <20051227101412.bfc9c062.Tommy.Reynolds@MegaCoder.com> <43B1EE22.4030104@n-man.com> <43B1EEC5.5050309@n-man.com> <43B1EFB2.3010907@debian.org> Message-ID: <20051228150231.233f709c.Tommy.Reynolds@MegaCoder.com> Uttered Mark Johnson , spake thus: > > On a further note, since the OpenDocument format is XML, I would imagine > > it wouldn't be too difficult to find or produce a solution in XSLT to > > 'import' the DocBook back into OpenOffice.org. > Absolutely doable. The problem, as usual, is finding someone who has the > time... I finally went to Google for this. I turned up this link: http://xml.openoffice.org/xmerge/docbook/supported_tag_table.html which seems to be an on-going project to support import and export of DocBook within the OpenOffice framework. Before I spend much time looking at this, has anyone here seen this before? Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From stickster at gmail.com Wed Dec 28 22:13:02 2005 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 28 Dec 2005 17:13:02 -0500 Subject: Packaging progress Message-ID: <1135807982.31955.35.camel@localhost.localdomain> Hi Docs gangstas, I am steadily making progress toward a packaging solution. Thanks to Tommy jumping in with XSLT-based solutions, I learned a lot (although not nearly enough, of course) about how to solve other problems using the same building blocks. I also -- finally! -- figured out how to package documentation for KDE's khelpcenter, and believe me, it's not self-evident. Or rather, the end-state is comprehensible, but the procedure for getting there cleanly is not. In any case, that's solved too. Also, the "fedora-doc-common" RPM is just about ready for rollout and will contain (hopefully) everything required for people not operating out of CVS to build docs. Mostly this just involves including our XSL snippets, entities, custom scripts, and so forth. This is not to say that by installing this RPM people will be able to just happily build away, but it puts that goal within reach. Since the fedora-doc-* stuff will probably live in Fedora Extras, and because that is a rolling repository, it is much easier for us to work on this in phases. Phase One goals are for our currently available documents to be installable by an end user using yum, and that those documents should show up prominently in each of the locations a user might expect: 1. Launching "Desktop -> Help" for GNOME or KDE 2. Launching "Documentation -> [title]" I don't know yet what Phase Two entails, but some goals might include: 1. Nice Python scripts for creating new XML document templates 2. " " " for building DRAFT-marked documents? Some items I am still in the process of solving, by which I mean I should be able to finish them for Phase One: - The rpm-info.dtd needs some lovin': - Packages should not get separate versions, too confusing - Docs should not get releases, also confusing - Figure out a way to condense generic person entries for use as authors, editors, translators, and/or packagers? Alternately, remove those not needed -- e.g. packagers only need full name and email, authors, editors and translators need "component" names, and people performing revisions only need initials. Some reference to dbpoolx.mod shows this shouldn't be too hard to do. - Provide functionality to automatically sort "doc" or "rpm" revisions. Because RPM is particular about things like date formats in %changelog entries, we may need to "encourage" proper formatting using the DTD. We already have a *strong* hint there in the attributes Tommy provided, but I don't think there's anything built in to a DTD to check for ordering; I believe, however, that XSLT can sort. Anything we can do to bulletproof the process is probably good. If it proves too cumbersome to complete RSN, I'll push this off until Phase Two. That's it from my neck of the woods. Hope everyone is enjoying the holidays. The holiday break and the patience of my ever-lovin' wife are the main reason I've been able to work on this stuff for the last few days. Best to all, and here's to a Happy New Year! -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Thu Dec 29 01:27:30 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Wed, 28 Dec 2005 19:27:30 -0600 Subject: Packaging progress In-Reply-To: <1135807982.31955.35.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> Message-ID: <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> Uttered "Paul W. Frields" , spake thus: > I am steadily making progress toward a packaging solution. Thanks to > Tommy jumping in with XSLT-based solutions, I learned a lot (although > not nearly enough, of course) about how to solve other problems using > the same building blocks. I also -- finally! -- figured out how to > package documentation for KDE's khelpcenter, and believe me, it's not > self-evident. Or rather, the end-state is comprehensible, but the > procedure for getting there cleanly is not. In any case, that's solved > too. I've seen that fast and furious activity ;-) Cheers that it is finally coming together. Even more, that you have drilled down for the crufty details for interfacing with those infuriating GUI's. > Also, the "fedora-doc-common" RPM is just about ready for rollout and > will contain (hopefully) everything required for people not operating > out of CVS to build docs. Mostly this just involves including our XSL > snippets, entities, custom scripts, and so forth. This is not to say > that by installing this RPM people will be able to just happily build > away, but it puts that goal within reach. Yes, necessary precursor step. > Phase One goals are for our currently available documents to be > installable by an end user using yum, and that those documents > should show up prominently in each of the locations a user might > expect: > 1. Launching "Desktop -> Help" for GNOME or KDE > 2. Launching "Documentation -> [title]" Agreed. Phase One should be getting our Docs and tools in place. > I don't know yet what Phase Two entails, but some goals might include: > 1. Nice Python scripts for creating new XML document templates > 2. " " " for building DRAFT-marked documents? Reasonable. Why the python focus ;-? Not that I'm actually against it. I would like to see a starter RPM that would explode into a new document skeleton and automatically connect to the docs-common RPM. > Some items I am still in the process of solving, by which I mean I > should be able to finish them for Phase One: > > - The rpm-info.dtd needs some lovin': > - Packages should not get separate versions, too confusing > - Docs should not get releases, also confusing > - Figure out a way to condense generic person entries for use as > authors, editors, translators, and/or packagers? Alternately, remove > those not needed -- e.g. packagers only need full name and email, > authors, editors and translators need "component" names, and people > performing revisions only need initials. Some reference to dbpoolx.mod > shows this shouldn't be too hard to do. Use caution in trying to compress the person stuff. While the minimal information needed varies according to that person's current role, the information pool in "rpm-info.xml" is not large, not redundant, and not an issue. Consider if this is over-optimization. Take a tip from the RDBMS crowd and collect all the person info into a central location (maybe just a .. set) and then use ID linkage to pull the necessary stuff out of that. > Provide functionality to automatically sort "doc" or "rpm" revisions. > Because RPM is particular about things like date formats in %changelog > entries, we may need to "encourage" proper formatting using the DTD. We > already have a *strong* hint there in the attributes Tommy provided, but > I don't think there's anything built in to a DTD to check for ordering; > I believe, however, that XSLT can sort. Anything we can do to > bulletproof the process is probably good. If it proves too cumbersome > to complete RSN, I'll push this off until Phase Two. I considered this, but skipped it because of our current crazy numberings. Besides, with that strong hint, we can just shoot whomever screws it up. Updating the revision info isn't a frequent activity and just didn't seem worth the effort until everything else was working. I wouldn't mind the XSLT doing a lint on the ordering, unless RPM will do that later. > That's it from my neck of the woods. Hope everyone is enjoying the > holidays. The holiday break and the patience of my ever-lovin' wife are > the main reason I've been able to work on this stuff for the last few > days. Best to all, and here's to a Happy New Year! Right back at 'cha. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From stickster at gmail.com Fri Dec 30 05:46:29 2005 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 30 Dec 2005 00:46:29 -0500 Subject: Packaging progress In-Reply-To: <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> Message-ID: <1135921589.14503.9.camel@localhost.localdomain> On Wed, 2005-12-28 at 19:27 -0600, Tommy Reynolds wrote: > Uttered "Paul W. Frields" , spake thus: > > Also, the "fedora-doc-common" RPM is just about ready for rollout and > > will contain (hopefully) everything required for people not operating > > out of CVS to build docs. Mostly this just involves including our XSL > > snippets, entities, custom scripts, and so forth. This is not to say > > that by installing this RPM people will be able to just happily build > > away, but it puts that goal within reach. > > Yes, necessary precursor step. And as I write this, that goal is very, VERY close. [...snip...] > > I don't know yet what Phase Two entails, but some goals might include: > > 1. Nice Python scripts for creating new XML document templates > > 2. " " " for building DRAFT-marked documents? > > Reasonable. Why the python focus ;-? Not that I'm actually against > it. See any recent quasi-rant by Seth Vidal on f-devel-l regarding tools for the platform. > I would like to see a starter RPM that would explode into a new > document skeleton and automatically connect to the docs-common RPM. No new RPM needed, this will simply be a small script in the docs-common RPM. > > Some items I am still in the process of solving, by which I mean I > > should be able to finish them for Phase One: > > > > - The rpm-info.dtd needs some lovin': > > - Packages should not get separate versions, too confusing > > - Docs should not get releases, also confusing > > - Figure out a way to condense generic person entries for use as > > authors, editors, translators, and/or packagers? Alternately, remove > > those not needed -- e.g. packagers only need full name and email, > > authors, editors and translators need "component" names, and people > > performing revisions only need initials. Some reference to dbpoolx.mod > > shows this shouldn't be too hard to do. > > Use caution in trying to compress the person stuff. While the > minimal information needed varies according to that person's current > role, the information pool in "rpm-info.xml" is not large, not > redundant, and not an issue. Consider if this is over-optimization. > > Take a tip from the RDBMS crowd and collect all the person info into > a central location (maybe just a .. set) and then > use ID linkage to pull the necessary stuff out of that. I like what you did with the worker stuff. I am going to change one small thing to make the option field "#IMPLIED" for othername as I believe is customary, but it's pretty much 6 of one, half-dozen of t'other. > > Provide functionality to automatically sort "doc" or "rpm" revisions. > > Because RPM is particular about things like date formats in %changelog > > entries, we may need to "encourage" proper formatting using the DTD. We > > already have a *strong* hint there in the attributes Tommy provided, but > > I don't think there's anything built in to a DTD to check for ordering; > > I believe, however, that XSLT can sort. Anything we can do to > > bulletproof the process is probably good. If it proves too cumbersome > > to complete RSN, I'll push this off until Phase Two. > > I considered this, but skipped it because of our current crazy > numberings. Besides, with that strong hint, we can just shoot > whomever screws it up. Updating the revision info isn't a frequent > activity and just didn't seem worth the effort until everything else > was working. I had an interesting thought about this, which is that rather than having a "version" and "release" attribute, only one of which is applicable for each type of revision, why not use a single "revnumber" attribute? For docs, this would be a version change, and for new package rolls it would be a release change. The latest version for the doc and the RPM would always be the "revnumber" attribute of the topmost role="doc" revision, and the RPM's release would always be the "revnumber" attribute of the topmost role="rpm" revision. > I wouldn't mind the XSLT doing a lint on the ordering, unless RPM will > do that later. I thought the same thing, I'll see what I can do. The only possible issue I see in the commit you made to rpm-info.dtd this evening is in requiring copyright holders to be workers. For example, Red Hat, Inc. and the Fedora Foundation won't fit that type of element, although one or both of them will certainly be copyright holders on several of our works. If we're not going to keep it as PCDATA, perhaps using subelements (worker|corp) might work. I think the KISS method, though, might dictate punting this one. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Fri Dec 30 07:22:22 2005 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 30 Dec 2005 02:22:22 -0500 Subject: Packaging progress In-Reply-To: <1135921589.14503.9.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> Message-ID: <1135927342.14503.21.camel@localhost.localdomain> And in other news, RPM building now works for example-tutorial. To witness the awe-inspiring power, update your docs-common and example-tutorial modules. Then do the following: 1. cd docs-common 2. make rpm 3. su -c 'yum localinstall fedora-doc-common*.noarch.rpm' 4. cd ../example-tutorial # your path may be a little different 5. make rpm 6. su -c 'yum localinstall fedora-doc-example-tutorial*.noarch.rpm' Note that the goodness comes through on both the GNOME and KDE menus, and if you are running Rawhide (FC5test1 or above), you'll also see our entries in the global "Help" menu. (Yes, the draft watermark is still there, but it will take me about 30 sec to get rid of that, but I'm too tired right now.) There are still a few minor quirks to iron out, like how to make respectable %changelog entries that meet Fedora standards. And building from SRPM will work after I get some sleep. ;-) But these are pretty minor compared to the work already done. 2006 is looking pretty good, at least from where I'm standing! -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Fri Dec 30 17:07:33 2005 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 30 Dec 2005 12:07:33 -0500 Subject: Packaging progress In-Reply-To: <1135927342.14503.21.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> <1135927342.14503.21.camel@localhost.localdomain> Message-ID: <1135962454.3375.30.camel@localhost.localdomain> On Fri, 2005-12-30 at 02:22 -0500, Paul W. Frields wrote: > And in other news, RPM building now works for example-tutorial. To > witness the awe-inspiring power, update your docs-common and > example-tutorial modules. Then do the following: > > 1. cd docs-common > 2. make rpm > 3. su -c 'yum localinstall fedora-doc-common*.noarch.rpm' > 4. cd ../example-tutorial # your path may be a little different > 5. make rpm > 6. su -c 'yum localinstall fedora-doc-example-tutorial*.noarch.rpm' > > Note that the goodness comes through on both the GNOME and KDE menus, > and if you are running Rawhide (FC5test1 or above), you'll also see our > entries in the global "Help" menu. (Yes, the draft watermark is still > there, but it will take me about 30 sec to get rid of that, but I'm too > tired right now.) Sorry to reply to myself, but that's fixed now. Though the list would like to know. ;-) > There are still a few minor quirks to iron out, like how to make > respectable %changelog entries that meet Fedora standards. And building > from SRPM will work after I get some sleep. ;-) But these are pretty > minor compared to the work already done. Building from SRPM now works too, and HTML stuff has the draft watermark if the SRPM is the source for the build. Still remaining: %changelog lint stuff, and one added challenge: Need to draft watermark the XML stuff rendered in yelp by default. I think the DocBook in yelp may be rendered to HTML using the stuff in /usr/share/yelp, but if anyone could pitch in an explanation and advice, that would be great. Please don't be afraid to be pedantic, it helps not only me but the googlemind as well. (*grumble grumble* meinproc *grumble*) -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 30 18:05:57 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 30 Dec 2005 12:05:57 -0600 Subject: Packaging progress In-Reply-To: <1135962454.3375.30.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> <1135927342.14503.21.camel@localhost.localdomain> <1135962454.3375.30.camel@localhost.localdomain> Message-ID: <20051230120557.7cd8091a.Tommy.Reynolds@MegaCoder.com> Uttered "Paul W. Frields" , spake thus: > Sorry to reply to myself, but that's fixed now. Though the list would > like to know. ;-) Confirmed: RPM building now works for docs-common and example-tutorial. Great work, Paul! I'll consider it as a late Christmas present ;-) The "example-tutorial/Makefile" is ugly; once this stabilizes a bit, we can work on migrating it to either "docs-common/Makefile.common" or some separate shell scripts. That should be trivial, I think. Major milestone, here. Take the rest of the year off... Cheers! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 30 13:39:56 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 30 Dec 2005 07:39:56 -0600 Subject: Packaging progress In-Reply-To: <1135921589.14503.9.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> Message-ID: <20051230073956.9f5040bc.Tommy.Reynolds@MegaCoder.com> Uttered "Paul W. Frields" , spake thus: > I had an interesting thought about this, which is that rather than > having a "version" and "release" attribute, only one of which is > applicable for each type of revision, why not use a single "revnumber" > attribute? For docs, this would be a version change, and for new > package rolls it would be a release change. The latest version for the > doc and the RPM would always be the "revnumber" attribute of the topmost > role="doc" revision, and the RPM's release would always be the > "revnumber" attribute of the topmost role="rpm" revision. Which ever is easier to parse. Personally, I prefer the two-attribute approach because that seems more parallel to the actual update process: just change the version and release, similar to what would be done to manually construct the SPEC file. The 'role="rpm"' seems a bit artificial to me; perhaps it's just NIH syndrome. > The only possible issue I see in the commit you made to rpm-info.dtd > this evening is in requiring copyright holders to be workers. For > example, Red Hat, Inc. and the Fedora Foundation won't fit that type of > element, although one or both of them will certainly be copyright > holders on several of our works. If we're not going to keep it as > PCDATA, perhaps using subelements (worker|corp) might work. I think the > KISS method, though, might dictate punting this one. Oops, I forgot about corporate ownership. OK, I'll revert it. /me updates CVS Done! Happy New Year! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Tommy.Reynolds at MegaCoder.com Fri Dec 30 13:29:20 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Fri, 30 Dec 2005 07:29:20 -0600 Subject: Packaging progress In-Reply-To: <1135927342.14503.21.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> <1135927342.14503.21.camel@localhost.localdomain> Message-ID: <20051230072920.e3898016.Tommy.Reynolds@MegaCoder.com> Uttered "Paul W. Frields" , spake thus: > 1. cd docs-common > 2. make rpm This step failed for me: + for i in xmlformat xmldiff copy-figs bulkbuild tidy-bowl + install -m 755 /home/reynolds/src/f/fedora-docs/docs-common/rpmbuild/BUILD/fedora-doc-common-cvs20051230/bin/xmlformat /var/tmp/fedora-doc-common-0.1-cvs20051230-root-reynolds//usr/share/fedora/doc/docs-common/bin/ install: cannot stat `/home/reynolds/src/f/fedora-docs/docs-common/rpmbuild/BUILD/fedora-doc-common-cvs20051230/bin/xmlformat': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.58603 (%install) > 3. su -c 'yum localinstall fedora-doc-common*.noarch.rpm' > 4. cd ../example-tutorial # your path may be a little different > 5. make rpm > 6. su -c 'yum localinstall fedora-doc-example-tutorial*.noarch.rpm' Didn't try these, though. > Note that the goodness comes through on both the GNOME and KDE menus, > and if you are running Rawhide (FC5test1 or above), you'll also see our > entries in the global "Help" menu. (Yes, the draft watermark is still > there, but it will take me about 30 sec to get rid of that, but I'm too > tired right now.) I'll add support for the Enlightenment E16, since that is really the window manager everybody should be using ;-) > There are still a few minor quirks to iron out, like how to make > respectable %changelog entries that meet Fedora standards. And building > from SRPM will work after I get some sleep. ;-) But these are pretty > minor compared to the work already done. > 2006 is looking pretty good, at least from where I'm standing! Well, done, good and faithful coder! I'll recommend that quaid gives you a 15% raise! P.S.: try to get this done before New Year's Eve, or just wait a few days... Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From stickster at gmail.com Sat Dec 31 12:34:13 2005 From: stickster at gmail.com (Paul W. Frields) Date: Sat, 31 Dec 2005 07:34:13 -0500 Subject: Packaging progress In-Reply-To: <20051230072920.e3898016.Tommy.Reynolds@MegaCoder.com> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> <1135927342.14503.21.camel@localhost.localdomain> <20051230072920.e3898016.Tommy.Reynolds@MegaCoder.com> Message-ID: <1136032453.17582.5.camel@localhost.localdomain> On Fri, 2005-12-30 at 07:29 -0600, Tommy Reynolds wrote: > Uttered "Paul W. Frields" , spake thus: > > > 1. cd docs-common > > 2. make rpm > > This step failed for me: > > + for i in xmlformat xmldiff copy-figs bulkbuild tidy-bowl > + install -m 755 /home/reynolds/src/f/fedora-docs/docs-common/rpmbuild/BUILD/fedora-doc-common-cvs20051230/bin/xmlformat /var/tmp/fedora-doc-common-0.1-cvs20051230-root-reynolds//usr/share/fedora/doc/docs-common/bin/ > install: cannot stat `/home/reynolds/src/f/fedora-docs/docs-common/rpmbuild/BUILD/fedora-doc-common-cvs20051230/bin/xmlformat': No such file or directory > error: Bad exit status from /var/tmp/rpm-tmp.58603 (%install) WORKSFORME with a brand-new user. Does the 'xmlformat' binary appear in your ~/src/f/fedora-docs/docs-common/bin/ directory where it should? Part of the RPM specfile does a 'cvs up' in 'docs-common' -- are you doing a .cvsignore that prevents it from restoring this program, if it doesn't appear there already? -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Sat Dec 31 12:50:37 2005 From: stickster at gmail.com (Paul W. Frields) Date: Sat, 31 Dec 2005 07:50:37 -0500 Subject: Packaging progress In-Reply-To: <20051230073956.9f5040bc.Tommy.Reynolds@MegaCoder.com> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> <20051230073956.9f5040bc.Tommy.Reynolds@MegaCoder.com> Message-ID: <1136033437.17582.22.camel@localhost.localdomain> On Fri, 2005-12-30 at 07:39 -0600, Tommy Reynolds wrote: > Uttered "Paul W. Frields" , spake thus: > > > I had an interesting thought about this, which is that rather than > > having a "version" and "release" attribute, only one of which is > > applicable for each type of revision, why not use a single "revnumber" > > attribute? For docs, this would be a version change, and for new > > package rolls it would be a release change. The latest version for the > > doc and the RPM would always be the "revnumber" attribute of the topmost > > role="doc" revision, and the RPM's release would always be the > > "revnumber" attribute of the topmost role="rpm" revision. > > Which ever is easier to parse. > > Personally, I prefer the two-attribute approach because that seems > more parallel to the actual update process: just change the version > and release, similar to what would be done to manually construct the > SPEC file. The 'role="rpm"' seems a bit artificial to me; perhaps > it's just NIH syndrome. This seems counter-intuitive to me, since documents have a version, not a release -- any document change means a version change (or it should if the editor is doing his job). Meanwhile, RPMs have a release, and the version is tied to the document source inside. The RPM may change versions, but only in conjunction with a document source change. And documents may change versions several times without any release, as they are progressively edited -- especially now that we have the webtest host where drafts are rolled during the work-in-progress. This might be just the occasion to move out of the attribute space and into the subelement space, thus: 0.15
Style changes
 1
Update to 0.15
 But frankly, that doesn't get easier to parse for people, which I was under the impression was the whole point behind XML and DTDs. Plus it leaves wiggle room for valid but erroneous entries. We might be well-served by making the DTD do the work for us:
Style changes
Update to 0.15
 This may be a case where it's good to sacrifice compactness on the altar of comprehensibility. > > The only possible issue I see in the commit you made to rpm-info.dtd > > this evening is in requiring copyright holders to be workers. For > > example, Red Hat, Inc. and the Fedora Foundation won't fit that type of > > element, although one or both of them will certainly be copyright > > holders on several of our works. If we're not going to keep it as > > PCDATA, perhaps using subelements (worker|corp) might work. I think the > > KISS method, though, might dictate punting this one. > > Oops, I forgot about corporate ownership. OK, I'll revert it. > /me updates CVS > Done! Saw this, thanks. For some reason I'm getting your mail to the list really late, which is why my response is so delayed in real time. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Tommy.Reynolds at MegaCoder.com Sat Dec 31 16:09:59 2005 From: Tommy.Reynolds at MegaCoder.com (Tommy Reynolds) Date: Sat, 31 Dec 2005 10:09:59 -0600 Subject: Packaging progress In-Reply-To: <1136033437.17582.22.camel@localhost.localdomain> References: <1135807982.31955.35.camel@localhost.localdomain> <20051228192730.c824b4e3.Tommy.Reynolds@MegaCoder.com> <1135921589.14503.9.camel@localhost.localdomain> <20051230073956.9f5040bc.Tommy.Reynolds@MegaCoder.com> <1136033437.17582.22.camel@localhost.localdomain> Message-ID: <20051231100959.468aa1fb.Tommy.Reynolds@MegaCoder.com> Uttered "Paul W. Frields" , spake thus: > > >
Style changes
> > > >
Update to 0.15
> > This may be a case where it's good to sacrifice compactness on the altar > of comprehensibility. Since we simply disagree, let's just pick one, use it for a while, and then see which works better in the long run. Since we have multiple solutions, let evolution take its course. Pick one. > Saw this, thanks. For some reason I'm getting your mail to the list > really late, which is why my response is so delayed in real time. Yeah, I saw them arrive long after they were sent. Thank BellSouth for blocking all 25/tcp and 25/udp access unless its to their very own SMTP server. They claim it is to help prevent relaying; they don't seem to believe there are other solutions. At that, they're better than the Charter setup that's my only alternative. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: