- openSUSE Documentation

[opensuse-doc] Re: [opensuse] Documentation - SDB and Wiki (was [SOLVED] "Undefined mode 348")
by Kim Leyendecker 24 Dec '11

24 Dec '11

On 24.12.2011 12:53, Rajko M. wrote: > On Saturday, December 24, 2011 11:26:46 AM Istvan Gabor wrote: > ... >>> Because everybody expects that someone else takes boring task of writing > ... >> I find SDB much less user-friendly than before. >> For example earlier SDB had a page when all the titles of >> the published SDB articles were listed in chronological >> order. It was easier to find a specific article by browsing >> that page than searching with the 'search sdb' option now. > ... >> So it would be very good to make available all the published >> SDB articles (the titles only of course with links to the articles) >> on one page again, including _all_ articles in chronological order, >> no matter how old they are. > Not imposible, I did some kind of index in now old wiki, as a > http://old-en.opensuse.org/Portal > but as stated above, everybody expects that someone else will take the time > and create that index. > > There is no others. Others that created and maintained that old S.u.S.E. > database either don't work for SUSE, or work in completely different areas. > We, users are left alone and have to take care of documents that we need, from > creating those that we need, maintaining them (fixing errors and updating with > new development), to taking care that we can find them when we need them. > > On a side note, time based sort is only one of many that can be applied. Some > readers will rememeber few words from the title, so they will need search, or > sort by keywords. Keywords and key phrases can be listed in a wiki article in > in a [[Category:<keyword>]], and later you can create browsing trees that will > give you article in a few steps. But, someone has to make them. There is no > others, it is you, me, or anybody with login that has to take time and fix > little bit of this, little bit of that, and one day there will be, surprise, > good wiki, like wikipedia. > > Anybody that has login for forums, bugzilla, build service, or any other site > in opensuse.org domain, can log in with that into wiki and ork on it. > Although, it is better to read a bit first: > http://en.opensuse.org/Portal:Wiki > as it will save some time. Also, don't take too much time to understand all > details that are written, but rather be flexible and ready to take advice from > those that spent and still spending a lot of their free time maintaining wiki. > > We have some nice tools in a new wiki, like CategoryTree that can list, as the > name tells, wiki categories in a tree layout, but also it can list categories > and pages, or only pages in some category. There is also many other tools, > some with similar scope, some for different purpose, that make wiki editing > much easier then in the old wiki. > > > >> Istvan I guess this is also relevant to the openSUSE documentation team, since a wiki is some kind of good documentation. Maybe they can give better explanations.... -- kind regards, -o) German Wiki Team Kim Leyendecker /\\ Documentation& marketing www.opensuse.org _\_v leyendecker(a)opensuse.org ===================================================== my GPG Key: 664265369547B825 | IRC: k-d-l Twitter: kim_d_ley | Wiki-Username: openLHAG openSUSE - Linux for open minds - get it free today! -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

1 0

[opensuse-doc] PDF build error
by Guillaume Gardet 13 Dec '11

13 Dec '11

Hi, I tried to build HTML doc (no problem) and PDF doc but I get a bunch of errors with PDF build. Full error log can be found here: http://guillaume.gardet.free.fr/tmp/log.txt I used those commands to build: daps --envfile=ENV-opensuse-all dist-html daps --envfile=ENV-opensuse-all color-pdf Any idea how to solve the problem? Here is the beginning of the error log, it seems daps cannot find some fonts: ******************************************************************************** ******************************************************************************** Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font "DejaVuSans,normal,700" not found. Substituting with "DejaVuSans,normal,400". Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font "Symbol,normal,700" not found. Substituting with "Symbol,normal,400". Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font "ZapfDingbats,normal,700" not found. Substituting with "ZapfDingbats,normal,400". Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Content overflows the viewport of the fo:region-before on page 1 in block-progression direction by 14000 millipoints. (See position 6932:60) Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Content overflows the viewport of the fo:region-after on page 1 in block-progression direction by 3500 millipoints. (See position 7025:59) Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Content overflows the viewport of the fo:region-before on page 2 in block-progression direction by 14000 millipoints. (See position 6998:60) Nov 22, 2011 10:05:00 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Content overflows the viewport of the fo:region-after on page 2 in block-progression direction by 3500 millipoints. (See position 7070:59) Nov 22, 2011 10:05:01 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Line 1 of a paragraph overflows the available area by more than 50 points. (See position 7228:42) Nov 22, 2011 10:05:01 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Content overflows the viewport of an fo:block-container in block-progression direction by 2647 millipoints. (See position 7246:165) ***** CSSEngine: exception property.syntax.error:org.w3c.css.sac.CSSParseException: Unexpected token: 7 (see LexicalUnits). AttrValue:FreeSans,DejaVuSans,suse.sans Exception:org.w3c.css.sac.CSSParseException org.w3c.css.sac.CSSParseException: Unexpected token: 7 (see LexicalUnits). at org.apache.batik.css.parser.Parser.createCSSParseException(Unknown Source) at org.apache.batik.css.parser.Parser.parseTerm(Unknown Source) at org.apache.batik.css.parser.Parser.parseExpression(Unknown Source) at org.apache.batik.css.parser.Parser.parsePropertyValueInternal(Unknown Source) at org.apache.batik.css.parser.Parser.parsePropertyValue(Unknown Source) at org.apache.batik.css.engine.CSSEngine.getCascadedStyleMap(Unknown Source) at org.apache.batik.css.engine.CSSEngine.getComputedStyle(Unknown Source) at org.apache.batik.bridge.CSSUtilities.getComputedStyle(Unknown Source) at org.apache.batik.bridge.CSSUtilities.convertDisplay(Unknown Source) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source) at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source) at org.apache.batik.bridge.GVTBuilder.build(Unknown Source) at org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:93) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:227) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:183) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:148) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingDocument(AbstractIFPainter.java:297) at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:204) at org.apache.fop.render.intermediate.IFRenderer.renderForeignObject(IFRenderer.java:1189) at org.apache.fop.render.AbstractRenderer.renderViewport(AbstractRenderer.java:745) at org.apache.fop.render.AbstractPathOrientedRenderer.renderViewport(AbstractPathOrientedRenderer.java:709) at org.apache.fop.render.intermediate.IFRenderer.renderViewport(IFRenderer.java:860) at org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:634) at org.apache.fop.render.intermediate.IFRenderer.renderInlineArea(IFRenderer.java:912) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:609) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:544) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:581) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:976) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:534) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:581) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:976) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:534) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:581) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:976) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:534) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:581) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:976) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:534) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:581) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:976) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:534) at org.apache.fop.render.AbstractRenderer.renderFlow(AbstractRenderer.java:432) at org.apache.fop.render.AbstractPathOrientedRenderer.renderFlow(AbstractPathOrientedRenderer.java:665) at org.apache.fop.render.AbstractRenderer.renderMainReference(AbstractRenderer.java:411) at org.apache.fop.render.AbstractRenderer.renderBodyRegion(AbstractRenderer.java:345) at org.apache.fop.render.AbstractRenderer.renderRegionViewport(AbstractRenderer.java:292) at org.apache.fop.render.intermediate.IFRenderer.renderRegionViewport(IFRenderer.java:731) at org.apache.fop.render.AbstractRenderer.renderPageAreas(AbstractRenderer.java:265) at org.apache.fop.render.AbstractRenderer.renderPage(AbstractRenderer.java:230) at org.apache.fop.render.intermediate.IFRenderer.renderPage(IFRenderer.java:580) at org.apache.fop.area.RenderPagesModel.addPage(RenderPagesModel.java:114) at org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.finishPage(AbstractPageSequenceLayoutManager.java:312) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.finishPage(PageSequenceLayoutManager.java:167) at org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.makeNewPage(AbstractPageSequenceLayoutManager.java:284) at org.apache.fop.layoutmgr.PageBreaker.handleBreakTrait(PageBreaker.java:538) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:143) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:132) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:337) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:85) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:107) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:238) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:120) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:349) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:299) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:130) at org.apache.fop.cli.Main.startFOP(Main.java:174) at org.apache.fop.cli.Main.main(Main.java:204) ***** CSSEngine: exception.... Nov 22, 2011 10:05:01 AM org.apache.fop.events.LoggingEventListener processEvent SEVERE: SVG error: file:/home/guillaume/perso/opensuse-doc_svn/svn-berlios/en/build/.tmp/: The attribute "font-family" represents an invalid CSS value ("FreeSans,DejaVuSans,suse.sans"). Original message: Unexpected token: 7 (see LexicalUnits). ******************************************************************************** ******************************************************************************** -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

2 3

[opensuse-doc] French translation for openSUSE Doc
by Guillaume Gardet 25 Nov '11

25 Nov '11

Hi, We (french community) started some time ago to translate the official documentation using POT/PO files generated from the english xml files, using www.vertaal.com.ar but I would like to use the official SVN to store the datas needed to have a translated doc. How do you translate xml files and update them ? Copy XML from english and then edit directly in XML ? If so, how do you deal with updates ? Can you create a french sub-directory on the server and give me write access so that I can update the files ? Best regards, Guillaume -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

2 6

[opensuse-doc] opensuse-doc svn repository moves to svn.opensuse.org
by Thomas Schraitle 25 Nov '11

25 Nov '11

Hi all, tomorrow we will move the opensuse-doc repository from svn.berlios.de to svn.opensuse.org. Thursday 17.00 h NUE time(UTC+1) we will set the Berlios repository to read-only.(http://www.timeanddate.com/worldclock/converter.html) Please, check-in all your files until then. On Friday 12.00 h NUE time(UTC+1) the new server is available(svn.opensuse.org) and a new e-mail will be sent with instructions how to switch your working directories. All accounts and passwords will be transferred from svn.berlios.de to svn.opensuse.org. opensuse-i18n is not affected. It's possible to change your account names. Please, drop an e-mail to jzwickl(a)suse.de jw(a)suse.de jdsn(a)suse.de -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org

2 2

[opensuse-doc] Refresh obs guides on http://doc.opensuse.org
by Michal Hrusecky 13 Oct '11

13 Oct '11

Hi, some time ago I sent a patch to the openSUSE Build Service Best Practice Guide which was accepted, but latest trunk version is not available on http://doc.opensuse.org yet. I wanted to ask whether it would be possible to refresh the snapshot available on the web... Or what is the official procedure to get it refreshed? While refreshing it, would it be possible to refresh the other one (OBS Reference Guide) as well? I noticed that there were some interesting stuff in trunk... -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz

2 4

[opensuse-doc] Build Service & upstream documentation patches
by Michal Hrusecky 29 Aug '11

29 Aug '11

Hi, apart from the conference, last of the things we were focusing to in openSUSE Boosters team was to make it for upstream projects easier to use openSUSE Build Service for publishing binaries of their software. Part of it was documenting how upstream can use OBS. So here comes few patches for OBS Best Practices book. Rendered version is available temporally on my server[1] (mainly upstream part[2] that changed) for more convenient reading. Feedback and potential integration will be appreciated. [1] https://michal.hrusecky.net/tmp/obs-best-practices/ [2] https://michal.hrusecky.net/tmp/obs-best-practices/cha.obs.best-practices.u… -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz

2 1

Re: [opensuse-doc] Re: Novell / opensuse documentatie vertalen
by Frank Sundermeyer 01 Aug '11

01 Aug '11

On Sat, 23 Jul 2011 13:30:00 +0200 MadMax wrote: Hi, first a big sorry: Since we just finished with daps the documentation of our toolchain is hopelessly outdated. > I asked earlier the help you offered. But after some attempts to make > the PDF I realised I missed something. So I installed susedoc and now > I am able to reproduce a PDF. My first step is made. hmm. It is _not_ necessary to install susedoc when having installed daps (once the final version of daps will be released, it will not be possible to install both programs in parallel). daps is the successor of susedoc. > Again, I never worked with documentation programs, so I need a crash > course to read somewhere. I am an absolute beginner in writing > documentation with xml. OK - the most important part to begin with is: don't be scared off by XML source code - it's _much, much easier_ than it seems. Have you ever written HTML pages with a non WYSIWYG editor or are you able to understand HTML source code? Writing DocBook XML is almost the same as writing HTML (The main differences are different tag names and a bit more structure in DocBook). > So, where do I start to read? When I joined the Documentation Team I simply opened a PDF with one of our manuals and the corresponding XML files side-by-side. I read the XML source code and whenever I was unsure what a certain tag/structure would look like, I had a look at the PDF. If that does not work for you, we can schedule an IRC session where I can teach you the most important things. > Maybe it is a good idea to use the opensuse > wiki for documenting my experience. I can write my experience and > things I think I needed on > http://en.opensuse.org/openSUSE:Documentation_Contribute Sounds good. > What I did so far. > I downloaded the xml source with svn. I recognize text in the xml > files. I browsed through some files. I think I can work with that. > I installed DAPS. But all my attempts with DAPS will not deliver any > PDF. I have an idea why - the format of the ENV-files has changed from susedoc to daps and the tags directory has the susedoc-ENVfiles. Sorry that I missed that in my initial mail. I have created a new directory for you https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents/distribut… which you can use for your translations (you should have read-write permissions tomorrow at latest). I have updated the ENVfiles to be daps compatible. Assuming you downloaded the SVN stuff to ~/suse/doc/trunk/documents/distribution/nl/ All you need to do to build a PDF from the e.g. Start Up manual is to cd ~/suse/doc/trunk/documents/distribution/nl/ daps -e ENV-opensuse-startup color-pdf > I found the editor EMACS, but don't know what to do with it. I read > the emacs macro link somewhere to simplify the use of xml dtd schema. > But how, I do not understand. Even after reading > http://en.opensuse.org/openSUSE:Documentation_Emacs_Docbook_Macros > > I am used to Kate for php programming, or editing other basic text > documents. So I need to learn Emacs, if that is the tool for docbook > xml. Can you give directions here? I understand its a struggle to > choose the right tools from > http://en.opensuse.org/openSUSE:Documentation_Contribute#How_to_Contribute More often than not tools are subjects of religious wars rather than subject of a neutral discussion. There is only _one_ aspect that matters in regards of tools: _You_ have to be familiar with them and you have to like them. So if you are familiar with Kate, use Kate to edit the DocBook XML files. Kate has a (DocBook) XML mode and is well suited for editing XML documents (see http://l10n.kde.org/docs/tools.php) [My editor of choice is emacs. To make my life easier, I have written a macro package for emacs that automates some common tasks when writing DocBook XML. But that macro package just adds a bit of convenience, nothing more. there is absolutely no need to learn emacs in order to write DocBook. _Every_ text editor is suited to write DocBook. However, some editors, among them Kate and emacs, have special XML plugins which make it easier to write DocBook.] With KDE 4.5 the Kate XML plugin also supports auto-completion of tags, which makes editing XML very comfortable. > I subsribed to berlios. Username Max_23. So I can use svn if I knew > how. OK, here is a very brief instruction on SVN. SVN (subversion) is a version control system. Such a system keeps control of all versions of the files it hosts and allows multiple users to work on the same files. The "master copy" of the files is hosted on the subversion server. When you are working on files hosted on an subversion server, you first have to "check them out" (download them) in order to create your own local copy. Now you can start working on your files _locally_. All the changes you do you do to your local files only. If you want to push your changes into the master copy on the server, you have to "commit" (upload) your local changes. The server then computes the differences between your submission and the master copy (diff) and merges these changes into the master copy. Using such a mechanism allows it to merge submissions from different contributors into one master copy. Only when two persons made changes on the same part of a file such a merger results into a conflict which has to be solved manually. The most important svn commands (see svn help or svn <command> help for more information): svn checkout: Initial check out (download) from server. Needs to be done only _once_ svn update: Update your working copy to the latest version (called HEAD) of the master copy on the server svn log: View the history of a file svn commit: Commit (upload) your local changes to the server svn revert: Revert your local changes of a file and restore the latest version from the server svn diff: Show differences between your local file and the one on the server svn add: Add a file/directory svn status: Compare your local working directory with the one on the server to see waht has changed locally (e.g. which files have been modified, deleted or added) The important paradigmas you need to understand are: * _Everything_ (incuding adding, deleting or moving files) you do will happen within your _local_ copy _only_ until you commit your changes. So before commiting your changes, make sure everything in your local copy is as you would like to have it (make use of svn status) * It is almost impossible to entirely break things. Since subversion keeps track of all revisions of all files, you can always go back to an old version of a file, a subdirectory or even of the complete repository * Submit early and often - subversion is your external backup > I don't understand which work flow to follow. Pretty easy: 0. Initial step, need to do it once: Check out your working directory from the server: svn co \ https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents/distribut… And then, your normal routine would look like the following: 1. Update your local working copy: svn up 2. Open <FILE> in editor and edit/translate it kate <FILE> 3. Save the file Once finished, check if the DocBook XML is still valid: daps -e ENV-openSUSE-all validate 4. If not valid, fix your XML -> back to step 2. 5. Build a PDF or an HTML version of the book you are currently translating to check what you have done daps -e <ENVfile> color-pdf 5. If valid, submit your changes to the server: svn ci -m "Started translation of FILE, still WIP" <FILE> (The text you specify with -m is a log message that can be seen with svn log - always use meaningful log messages!) 6. start over with 1. > I read a big part of docbook.org. But all that teached me of xml use. > I gave up there. Don't confuse yourself with too much reading about DocBook. Just look at the existing files and if there is something you do not understand, ask on IRC or via mail. As said above, it's much easier than it looks like. > I like to find some story about the opensuse books, how it all works > together. I understand it must be simple. But how? Finally a general not about our working environment: 1. The directory structure: distribution/nl/ |-ENV-opensuse-* |--images/ | |--src/ | | |--dia/*.dia | | |--fig/*.fig | | |--png/*.png | | |--svg/*.svg |--xml/*.xml 2. XML files the xml files are placed under the XML subdirectory. In DocBook you can include one xml file into another with <xi:include ...> statements. Thus you do not need to have only one huuuuge file for each book but rather a set of small files and you can also reuse files in different books. We name our files according to the hierachy: xml/MAIN.opensuse.xml (the complste set: all openSUSE books) xml/book.* (a single book) xml/*.xml (the rest, singles chapter or sections usually (but not always) prefixed with the book name, e.g. security-*) 3. ENVfiles The configuration files for the books. Each ENVfile represents on book and therefore needs to be specified with each daps command. ENV-opensuse-all The complete set (all openSUSE books) ENV-opensuse-html The complete set (all openSUSE books) ENV-opensuse-kvm Virtualization with KVM ENV-opensuse-reference Reference Guide ENV-opensuse-security Security Guide ENV-opensuse-startup Start-Up ENV-opensuse-tuning Tuning Guide 4. Which files belong to which book: XML files: daps -e <ENVFILE> projectfiles -p Images: daps -e <ENVFILE> projectgraphics -p -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) "Reality is always controlled by the people who are most insane" Dogbert -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

4 11

Re: [opensuse-doc] Re: Novell / opensuse documentatie vertalen
by ben.henderson＠planet.nl 19 Jul '11

19 Jul '11

Goodmorning all, THX`s for all the info, i saw a lot of possibility`s for translating. I going to try Daps i think. @ Max, Yep there are some tools for the translation. But i`m allready buzzy with opensuse reference in Draw, i will try to get it transfer in to Daps. Ben Henderson Op Mon, 18 Jul 2011 18:36:06 +0200 schreef MadMax <madmax(a)teenspirit.nl>: > Hi All, Thank you for these detailed answers. > > @Jos, thanks for forwarding. It seems that some information could be > found on the wiki by me. But I'm happy with yours answers. I have to > learn some community communication stuff, I think. So if you have more > teaching to offer, I'm eager to learn. > @Frank, thanks for the help offered regarding infrastructure. I'm not a > technical guy, so I have to put some effort in understanding the > directions you gave us. I have a fulltime day job, so I'll do this > trying in my spare evenings. I think I need till the end of the week to > come back on understanding the directions. And on the workload I have > asked for. :-) > @Ben, do you understand the directions, help we got, and what to do? > Let's e-mail further (in Dutch) about tasks if you figured out what you > need. > > I will report back to you at the end of the week. > > Greetings, > > Max > > > Frank Sundermeyer wrote: >> On Mon, 18 Jul 2011 09:12:40 +0200 Thomas Schraitle wrote: >> >> Hi Max, >> >>>> I'm shamelessly replying to you sending this to the person whom I >>>> think of when someone mentions openSUSE translations - Thomas >>>> Schraitle. I've also CC'ed the opensuse-doc mailinglist (no idea if >>>> I'm subscribed or what'll happen when I turn out not to be). >>> Thanks for the fame, but I'm not involved in translations at all. ;) >>> I think, Karl is the right person to ask (he reads opensuse-doc too) >>> and he does all the good things in and with translations. >>> >> sounds like you want to translate our manuals. If so, we can offer you >> all the infrastructure you need. >> >>> To create HTML or PDF, you need daps (Document Authoring and >>> Publishing Suite), the successor of susedoc. You can install it from >>> OBS, repo Documentation:Tools. >> http://download.opensuse.org/repositories/Documentation:Tools/ >> to be precise. This is one part of the infrastructure we can offer. If >> you need help with daps, just contact me. daps --help should give you a >> first impression of what the tool can do. If you have already worked >> with it's predecessor susedoc, there is a transition guide >> at /usr/share/doc/packages/daps/README.upgrade_from_susedoc_4.x >> >> We can also offer you SVN access to our documentation SVN at BerliOS >> (http://developer.berlios.de/projects/opensuse-doc/) and add a >> directory for your translations at >> http://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents/distributi… >> >> The Hungarian, Japanese, Portuguese, and Russian translators are also >> using the SVN. >> >> And last but not least we can offer you support. If you have any >> questions (incl. daps, stylesheets, svn, etc), contact us on this >> list. The other translators are also subscribed here, so you might >> benefit from their knowledge as well. >> >> Regarding the BerliOS SVN: >> You can anonymously checkout from the svn. "subversion" needs to be >> installed on your machine. To check out the final 11.4 openSUSE >> documentation, use the following command: >> >> svn co \ >> http://svn.berlios.de/svnroot/repos/opensuse-doc/tags/documents/openSUSE/11… >> >> If you want to use the BerliOS SVN for your translations, please create >> a BerliOS log in at https://developer.berlios.de/account/register.php >> and let me know your Login Names. >> >> When I know them I can grant you access to the project including >> SVN check-in permission. Then I would copy the final Englisch 11.4 >> documentation sources to >> http://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents/distributi… >> and you can start ... ;-) >> > -- Gemaakt met Opera's revolutionaire e-mailprogramma: http://www.opera.com/mail/ -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

1 0

[opensuse-doc] Re: Novell / opensuse documentatie vertalen
by Jos Poortvliet 18 Jul '11

18 Jul '11

Max, I'm shamelessly replying to you sending this to the person whom I think of when someone mentions openSUSE translations - Thomas Schraitle. I've also CC'ed the opensuse-doc mailinglist (no idea if I'm subscribed or what'll happen when I turn out not to be). So your question is: where is the source of the starters guide to openSUSE 11.4 to be found? The original is still to be found on the Novell site (soon to be the SUSE.com site). Now I had a look at the webpage of the documentation team: http://en.opensuse.org/openSUSE:Documentation_team And apparently they suck developers' brains out. Scary. But that page also told me about this how-to: http://en.opensuse.org/openSUSE:Documentation_Contribute and I think you are looking for this: http://en.opensuse.org/openSUSE:Documentation_Contribute#SVN_Structure However, I might be wrong (it's been noted to happen) and in that case, I'm sure Thomas or some other openSUSE documentation Wichtl (?) will set me straight. Cheers, Jos On 2011-07-16 MadMax wrote: > Hoi Jos, > > Ik heb twee e-mailadressen van je gevonden en ga beide proberen. > > Op het Nederlandse opensuseforum heeft Ben Henderson zijn vertaling > geplaatst van Start-up guide van Novell. > http://forums.opensuse.org/nederlands-dutch/community/nl-how-tos/4621 > 79-opensuse-11-4-nl-starters-gids.html > > Het origineel staat hier: > http://www.novell.com/documentation/opensuse114/ > > Ik heb aangeboden deze gids na te kijken op type- en spelfouten. > Alleen heeft Ben zijn werk gebaseerd op de PDF die je kunt > downloaden. Dat is een monnikenwerk qua vertaling. Nu lees ik bij de > Novelldocumentatie dat deze is gemaakt in DocBook. Of eigenlijk een > Novellvariant daarvan. Het is vast een stuk eenvoudiger dit in de > DocBook te vertalen. > Ik heb deze wijsheid uit: > About the Making of This Manual > > This book is written in Novdoc, a subset of DocBook (see > http://www.docbook.org) The XML source files were validated by > xmllint, processed by xsltproc, and converted into XSL-FO using a > customized version of Norman Walsh's stylesheets. The final PDF is > formatted through XEP from RenderX. The open source tools and the > environment used to build this manual are available in the package > susedoc that is shipped with openSUSE. > > > Aangezien jij als Ambassadeur en ook werknemer van Novell misschien > weet wie ik kan benaderen om een kopie van de DocBook-xml te vragen. > Wij zouden graag een Nederlandse vertaling maken. Denk je dat > mogelijk is? > > Groet, > > Max

4 3

[opensuse-doc] Re: [opensuse-wiki] PING (preferred term in German ?) - IS: [opensuse-wiki-de] Repository/Repositorys oder Depot/Depots oder ... : Welche Bezeichnung vorzugsweise (in Artikelnamen und meist im Text)?
by Christian Boltz 23 May '11

23 May '11

Hello, on Sonntag, 15. Mai 2011, pistazienfresser (see profile) wrote: > does someone else like also to contribute to the discussion on the > matter how a directory for software packages and metadata > - in English in openSUSE: repository, pl.: repositories - > should be named in the new openSUSE-Wiki for German language? > This is referring on the term that should be used in names of > articles (apart from redirects) and in the text (apart from > introductions). > > In case you are interested it would be nice if you would visit the > following discussion page/talk page: > http://dewiki.opensuse.org/Diskussion:Paket_Repositories > (until the end of Monday). IMHO we should get this in sync with the "official" documentation, which is the reason why I'm CC'ing the documentation mailinglist. (I also removed some lists from CC because I'm not subscribed there.) @Documentation team: Is there an "official" german translation for "repository"? BTW: My personal opinion is that "Repository" should also be used in the german wiki. I don't really like the idea to use "Depot". Regards, Christian Boltz -- The speed at which a mistyped command executes is directly proportional to the amount of damage done. [Joe Zeff] -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

5 4