gmane.linux.gentoo.documentation

Re: This months GMN

Josh Saddler — 2008-11-30T20:12:31

Wrong list. The GDP has nothing to do with the GMN, aside from a developer that's on both teams (me). I've already been writing the newsletter -- it's much, much further along than this copy; I sent mine to Anant earlier today.

This months GMN

Douglas Anderson — 2008-11-30T13:00:50

Re: Handbook,Devbook,etc to PDF conversation

Josh Saddler — 2008-11-30T10:21:24

Assuming such a thing is possible and works as well as the HTML generated from the original GuideXML, then scripts that do this would be appreciated. Right now the closest thing you'll get to a "print" layout is the one we made that's suitable for, well, printing: http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?style=printable&full=1 Append ?style=printable&full=1 to the desired architecture. That's about as far as we can go. If someone can turn this (or the original web layout) into a *useful* PDF via scripts, please provide 'em.

Re: Handbook,Devbook,etc to PDF conversation

Behzat Erte — 2008-11-28T09:12:18

Thanks Douglas, I want to say this exactly. Regards, Behzat. 2008/11/28 Douglas Anderson gmail.com>:

Re: Handbook,Devbook,etc to PDF conversation

Douglas Anderson — 2008-11-28T09:10:03

to you. Obviously gentoo isn't going to open pages in oo! I was saying to Behzat that, for whatever reason, if he needs a one-off copy of the handbook in PDF, there *are* a few ways to make it by going off the html version instead of straight from guidexml to pdf. -Doug

Re: Handbook,Devbook,etc to PDF conversation

Behzat Erte — 2008-11-28T09:07:54

Hello again, I want to printing all related gentoo books and reduce to -really- book. At this juncture PDF type is a example. May be it should be djvu or something else type. Regards, Behzat. 2008/11/28 Jan Kundrát gentoo.org>:

Re: Handbook,Devbook,etc to PDF conversation

Jan Kundrát — 2008-11-28T09:02:26

We don't want to provide a PDF just "so that we have a PDF", so printing a web page to PDF is not really an option. If you want to improve your XSLT-FO skills, feel free to write the stylesheets; if you manage to use only the technologies that are already available on our web nodes (nope, we won't open HTML in OpenOffice, thank you), we can give it a try. But there's no point in generating "a PDF" without all fancy features like a book-like layout, inter-document links etc. Why do you *need* the PDF at all? Cheers, -jkt

Re: Handbook,Devbook,etc to PDF conversation

Douglas Anderson — 2008-11-28T08:57:36

this: https://addons.mozilla.org/en-US/firefox/addon/636 or saving and opening the html page in openoffice, then exporting to pdf, or....... ? -Doug

Re: Handbook,Devbook,etc to PDF conversation

Jan Kundrát — 2008-11-28T08:55:16

It used to be possible some years ago, but nobody felt the need to maintain the stylesheets, so nope, it isn't possible anymore. Cheers, -jkt

Handbook,Devbook,etc to PDF conversation

Behzat Erte — 2008-11-28T08:43:00

Hello everyone, I still searching everywhere about this case but I do not have any solution yet. Is this possible ? Regards, Behzat.

Japanese translated docs have been maintained

shindo — 2008-11-19T16:22:52

Hi all, I'm (actual lead) translator of Japanese Gentoo docs. This 6 month, Japanese translation team has been activated, so then translations of Handbook Part1(x86), Alternative Installation Guide, Security handbook and ALSA Configuration Guide are completely updated. And Handbook Part2 is almost updated, all part2 docs will be completed soon. Of course, our team will translate other docs step by step. Can Japanese come back to available language list on www.gentoo.org? (Translations is maintained already!) Shindo

Re: unsubscribe+gentoo-doc< at >lists.gentoo.org

Chema Alonso — 2008-11-18T21:12:47

http://www.gentoo.org/main/en/lists.xml can also help Cheers! AllenJB escribió:

Re: unsubscribe+gentoo-doc< at >lists.gentoo.org

AllenJB — 2008-11-18T18:02:19

Hi, You need to send an email to the address you've put in the subject line to unsubscribe. Hope that helps AllenJB Th. Rikl wrote:

unsubscribe+gentoo-doc< at >lists.gentoo.org

Th. Rikl — 2008-11-18T17:31:36

Re: Wiki, Take #whatever

AllenJB — 2008-11-18T17:26:43

If there's already a high quality document on the wiki, why is there a need to duplicate efforts? Surely it's the areas NOT already covered by high quality documentation that should be concentrated on. Again, you're suggesting duplication of efforts. What point would this have? What problem would it fix? While this was true of the old wiki, it is certainly not true of the documents on the new Gentoo Wiki - they are being checked for accuracy and errors by a team of volunteers as they are being entered. We will be doing our best to keep it this way. We're also already considering methods of indicating documents which we believe to be particularly good or particularly bad. Why can't, where they exist, the wiki document both? You're not going to be able to stop people documenting certain things on the wiki (and as an admin of the wiki, I don't believe you'd want to). How is it good for users? Now they have to judge which document to follow. I don't see what this analogy has to do with this discussion at all. It seems to be totally unrelated to me. In my opinion, the Gentoo Documentation Project is there to maintain documentation on issues specifically related to Gentoo and issues which you'd expect to find official documents on. Things like upgrading to baselayout 2 or upgrading to a newer profile. Meanwhile the wiki is there to basically document everything else. How to install and configure software or hardware (perhaps in a specific way). There will always be some crossover, but that's the main "areas of responsibility" that I see each covering. AllenJB

Re: Wiki, Take #whatever

wireless — 2008-11-18T17:09:09

Your docs on your wiki, should follow whatever semantic you like. Nobody is talking about hi-jacking your (wiki) docs. I'm talking about maybe one out of fifty docs that one typically finds on a wiki, could be motivation (and yes some ideas) on creating a similar doc that is officially bless and maintained, to a much higher standard and address things such that they can influence some of the existing official docs. Um, I think your both confused what I'm trying to say. I'll restate it, hopefully a little bit more clearly. Running a wiki, which usually has many folks actively involved, where the emphasis is on quantity of docs, not rigid uniformity, and where the particular selection of docs will usually be vastly larger than any official distro docs, you have completely different semantics, so they cannot be merged, without great pain, compromise and huge amounts of time. Let the wiki, (or any number of wikis) exist unto themselves. However, if a really good topic comes up, then those officially under much tighter constraints, such as GDP or infra, should consider maintaining a similar doc, that is held to much tighter (semantics) controls. Let's face it. We all re-hash much of the same content on different linux distros, or even the same linux distro, so *I* do not see any big deal with this concept. Google for something and often you find multiple wikis that address a given subject with different docs, but with much that is common. Occasionally one will see a reference to that original doc that inspired the derivative. Often the wiki docs are old and not maintained, for a variety of reason. Just google for how to install a camera on a linux machine for a myriad of ideas. It sure would be nice to have an officially maintain basic video setup on gentoo, either using capture cards or a cheap webcam, as a baseline for folks to get something working. (using my previous example). It would not have to be encompassing but it should be maintained to GDP or such standards. Then let the wiki document, via dozens of different documents, many of the finer, fast moving aspects of cameras and video. I.E. *Complimentary documents* not competing documents.... Two docs that address the same subject, one on a wiki, the other part of the official gentoo docs is good for users. The official docs will never be as numerous as other docs folks use to solve a problem or at least get some ideas how to install or fix something. However what is part of the official docs should be rigorously maintained, and held to a much higher standard, than the typical wiki, imho. There is a reason we have many motorcycles and many vehicles with 4 wheels. However, how often do you see a three-wheeled vehicle? Sure they exist, but, they are not common and they are very easily wrecked. Remember the early ones for recreational vehicles in the 1980s? They have been baned here in the US, because they were prone to catastrophic failure. Ditto for merging a wiki and official distro docs. ymmv, James

unsubscribe+gentoo-doc< at >lists.gentoo.org

Th. Rikl — 2008-11-18T11:24:56

unsubscribe+gentoo-doc< at >lists.gentoo.org

Re: Wiki, Take #whatever

Josh Saddler — 2008-11-18T11:03:57

Actually, I'm not sure that guy had anything to say, really. But yeah, you're right; basically, it's a bad idea. If you write the article, best to keep it someplace where you know it'll easily receive TLC.

Re: Wiki, Take #whatever

AllenJB — 2008-11-18T10:19:40

Request for clarification: So you're proposing that if I write a good article on the wiki, the Gentoo devs should take that article, XMLify it and put it on the static site where I can't update it easily? AllenJB wireless wrote:

Re: Wiki, Take #whatever

wireless — 2008-11-18T01:48:03

NO !!! Sorry for the delayed response, I've been unplugged for a while..... After reading the entire thread, a rather simple solution seems obvious. The GDP or Infra or whatever official group should stay out of the the wiki business, for many aforementioned reasons. However, if what ever the new wiki(s) pop up for the ashes of any previous efforts, it seem like a natural place for 'official gentoo folks' to peruse, parse, filter and/or glean information for good ideas and (tested) content into one of the existing gentoo semantics (GDP infra whatever), but leave the morass of a wiki to the user community at large. That way folks could first look to the trunk of Gentoo for docs on a given subject and if nothing there exist, THEN go to any of these community wikis. For example, installing a webcam is pretty important and very, very common among needs for any distro. Yet if you google for webcam, install and gentoo, you get a variety of 'hash' mostly outdated. Those talent folks within the official gentoo structure, should recognize this and build docs somewhere, of high quality, that walk a gentoo user through how to set up a capture card (ntsc/pal) or a web cam. But for every issue that really needs a good doc, there will be many wikis with a variety of quality, mostly due to the lack of maintenance over time. Smart folks with lots of current responsibilities, should stay focused on current goals. However, as the external gentoo wikis mature, but the others in the gentoo community, folks can glean good idea to increase the officially maintained docs. YMMV, James

Re: Re: Wiki, Take #whatever

Peter Volkov — 2008-11-12T18:09:11

В Срд, 12/11/2008 в 16:14 +0100, Ben de Groot пишет: Until there existed context, like this discussion, I don't see where I could fit this information. And I didn't want to start discussion about wiki by myself. But since it's started see the facts.