Re: [opensuse-doc] SGML IDE
Hi Jason, > I recently installed daps and set up the demo article recipe. Cool! :) > Is there > an SGML IDE that you would suggest for making coding SGML easier? You mean probably XML, not SGML. Regardless of any acronyms, there are a couple of options you may want to try: * Emacs * vi * jEdit and certainly some more which I haven't mentioned. These are open source XML editors and you may probably spend some time to get used to it. You may also read some introducery material from our DAPS User Guide: https://opensuse.github.io/daps/doc/cha.daps.user.edit.html#sec.daps.user.edit.editor > Is > the SGML that LyX outputs compatible with OpenSUSE documentation? Very likely not. -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany_\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] PDF creation: element errors
Hi Marguerite, I did it! Cool, congratulations! 1. pick an open source Chinese font 2. create metrics for it using fop-fontmetrics 3. edit /etc/fop.xconf as mentioned before. (Chinese has no italic so you have to bind it to normal) 4. edit /usr/share/xml/docbook/stylesheet/suse/common/l10n/zh_cn.xml add WenQuanYi Micro Hei and WenQuanYi Micro Hei Mono to relevant tags. Do we have a package for them? now: daps --docconfig=DC-opensuse-startup color-pdf it works amazing! Perfect! Many thanks! If I'm not mistaken, this is the old approach to define and use fonts in FOP. I had the impression that you don't have to create metrics files anymore. FOP searches all fonts for you. Could you try to do the same, but without any metrics? I would propose to read the following link first: http://xmlgraphics.apache.org/fop/1.1/fonts.html Also make sure to use the correct font name in your FO file, otherwise it won't work. If your Chinese font contains spaces (like the one above), you need to put them in single quotes. For example, this could look like this: fo:inline font-family=FreeSerif,'WenQuanYi Micro Hei',serif... If the font name is correct, FOP should find them. To avoid guessing, better install fontforge (a font editor), load the font, and click the Element Font Info... menu item. There you should see the font name and family name. I think, you need the string in Family Name, but I'm not sure. And I found a potential bug: both zh_cn.xml and zh_tw.xml use a Chinese and a ChineseMono as their fonts. Ahh, right. This is a mistake. I don't know if they're alias (I didn't find anything definitions in /usr/share/xml for them), but if they are real, it will be a bug. I think, we can consider it as a bug. :) This originates from XEP; it allows using alias names and define the aliases in the XEP configuration file. The advantage of this is, that you don't have to transform your XML file again and again just to test another Chinese font. With an alias name, you can just change the definition. Unfortunately, this works only for XEP, not FOP. I guess, it was a copy and paste error. Because there's no actual font named Chinese. Actually Simplified Chinese and Tranditional one are totally different in font industry. Right. And there's also a bug in susedoc: Because there's no FZSongTi available in openSUSE at all. These are commercial fonts. As I'm not familiar with Chinese and its typography, could you recommend a good Chinese font? Preferably open source. :)) Can you confirm these? I'm preparing fixes. I think your analysis is correct. Maybe you should try the configuration without the metrics. They should work as well. Could you send us your fixes? Just to let you know, tomorrow is a public holiday in Germany and I'm not here for the next 3 weeks. Probably one of my collegues will take and submit your patches. Thanks for your efforts, well done! -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] PDF creation: element errors
Hi Marguerite, On Wed, 29 May 2013 16:03:24 +0800 Marguerite Su i...@marguerite.su wrote: Do we have a package for them? Yes, package name wqy-microhei-fonts` in OSS, developed at M17N:fonts This is good news! If I'm not mistaken, this is the old approach to define and use fonts in FOP. I had the impression that you don't have to create metrics files anymore. FOP searches all fonts for you. Could you try to do the same, but without any metrics? Oh yes, I commented fop.xconf and they still work well. Brilliant! According to the link that I've sent you, FOP 1.1 doesn't need metrics anymore. So I guess it's better to avoid them altogether. [...] it was a copy and paste error. I see, then I'll SR a patch to suse-xsl-stylesheets. As they're not on git, I can just open a ticket on sf. Please do. :) We could add that as a requirement/recommendation for the suse-xsl-stylesheet package. These are commercial fonts. As I'm not familiar with Chinese and its typography, could you recommend a good Chinese font? Preferably open source. :)) I recommend wqy-*-fonts. Good. I guess we need all, right? wqy(文泉驿) is the main open source project for Chinese fonts: http://wenq.org/wqy2/index.cgi?Home led by Chinese students in MIT. They provided an easy to use web interface to create fonts. Every user can contribute, thus their fonts covered a lot more glyphs than any commerical fonts. BTW, the Chinese part of Google Droid fonts are based on this project. Actually modern linux (sles needs to be stable, so it's a little old) all use their fonts as default. And using wqy can avoid the problem that you have to install FZSongTi, then openSUSE automatcially set it as your ugly display font. FZ fonts are used for printing, they didn't display well on LC/EDs. Thanks for the information, I didn't know. :) Could you send us your fixes? Just to let you know, tomorrow is a public holiday in Germany and I'm not here for the next 3 weeks. Probably one of my collegues will take and submit your patches. Sure. I'll fix suse-xsl-stylesheets and susedoc. You can omit susedoc as this is really too old and we don't support that anymore. Any fixes should go into daps or suse-xsl-stylesheets packages now. Holiday is the 1st priority, so just enjoy life. fixes can wait. :-)) Thanks. If you submit your changes today, I can look at them and approve them. -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH(o Maxfeldstrasse 5/\\Documentation Specialist 90409 Nuernberg, Germany _\_vhttp://www.suse.com| HRB 21284 SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] PDF creation: element errors
Hi Marguerite, sorry, missed your mail and with all the public holidays in between, it vanished... I tried to produce a pdf, but I got these errors: $ daps --docconfig=DC-opensuse-startup color-pdf MAIN.opensuse.xml:211: element filename: validity error : Element filename is not declared in filename list of possible children MAIN.opensuse.xml:15: element abstract: validity error : Element abstract content does not follow the DTD, expecting (title? , para+), got () This means, you haven't inserted neither title nor at least one para. MAIN.opensuse.xml:46: element menuchoice: validity error : Element menuchoice content does not follow the DTD, expecting (shortcut? , guimenu+), got (guimenu CDATA guimenu) ^ There is some non-space character between your consecutive guimenus. Inside menuchoice only other elements are allowed, no text. MAIN.opensuse.xml:173: element guimenu: validity error : Element guimenu was declared #PCDATA but contains non text nodes You can't add other elements inside guimenu. Only text is allowed. MAIN.opensuse.xml:11: element xref: validity error : Element xref was declared EMPTY this one has content The xref/ element is empty, neither text nor elements, even spaces are not allowed. Just use xref linkend=.../ MAIN.opensuse.xml:482: element xref: validity error : IDREF attribute linkend references an unknown ID ex.welt.zone MAIN.opensuse.xml:578: element xref: validity error : IDREF attribute linkend references an unknown ID sec.basicnet.manconf.hosts MAIN.opensuse.xml:33: element xref: validity error : IDREF attribute linkend references an unknown ID sec.apparmor.start.update You need to insert an id attribute into example and section (or sect1, sect2, ...) elements. when I tried to fix them, I found MAIN.opensuse.xml:XX actually does not have the error it warned, eg: [...] I can't see anything wrong. If I remember correctly, some old xmllint parser couldn't deal with correct line numbering. Usually this happens when a XML file is splitted up into different files and the references are resolved later. Use the daps bigfile command. This creates an XML file where everything is resolved. You can find it under build/.tmp/. This makes it a bit easier for debugging. -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] PDF creation: element errors
Hi Marguerite, On Tue, 21 May 2013 20:21:16 +0800 Marguerite Su i...@marguerite.su wrote: Can I just create a single pdf for DC-opensuse-startup: daps --docconfig=DC-opensuse-startup color-pdf bigfile You can either create the PDF (with the color-pdf subcommand) or validate and create a bigfile. You can't have both. ;) Do you use the source from our SVN repository? But the number doesn't match, eg: /home/marguerite/opensuse-doc/zh_CN/build/.profiled/x86-amd64-em64t_osuse_/MAIN.opensuse.xml:94: element keycombo: validity error : Element keycombo content does not follow the DTD, expecting (keycap)+, got According to the above error message, you have something like this: keycombo ... /keycombo Unfortunately, you've cut the important part after the got ... ;) No problem, we can deal without it. However, the DTD expects at least one keycap like this: keycombo keycapF2/keycap /keycombo Well, one keycap in keycombo doesn't really make sense, so keycombo is only useful for more than one. The reason for this is, a keycombo represents a key press of two or more keys. Something like this: keycombo keycapAlt/keycap keycapF2/keycap /keycombo Actually build/.tmp/book.opensuse.startup.xml:94 is: varlistentry not the error. even no keycombo in it. I know, the numbers can be a pain. I've looked at the zh_CN source and there seem to be some validation errors. Usually it's best to run a daps --docconfig=DC-opensuse-startup validate and go through all the error messages. For example, I got the following validation error (like you): nm.xml:78: element menuchoice: validity error : Element menuchoice content does not follow the DTD, expecting (shortcut? , guimenu+), got (guimenu CDATA guimenu) That means, it's in the nm.xml file under the subdirectory xml/. Unfortunately, you can't rely on the line number. A better(?) approach could be to first generate the so-called bigfile (everything is in one file) and then validate it again. Something like this: 1. Run daps --docconfig=DC-opensuse-startup bigfile = Gives you the complete file, saved under build/.tmp/book.opensuse.startup.xml 2. Load that file into a editor (Emacs, vi, ...) 3. Validate separately with the command: $ xmllint --valid --noout build/.tmp/book.opensuse.startup.xml \ 2 validation-errors.txt 4. Open the validation-errors.txt files and fix the errors step by step. If I do that, I get same error, but with a correct line number: build/.tmp/book.opensuse.startup.xml:37766: element menuchoice: validity error : Element menuchoice content does not follow the DTD, expecting (shortcut? , guimenu+), got (guimenu CDATA guimenu) guimenu网络设备/guimenu⏎ guimenu网络设置/guimenu/menuchoice If I now open the build/.tmp/book.opensuse.startup.xml file, I can jump to the respective line. There is a ⏎ between each guimenu. That's not allowed, the stylesheets inserts a character automatically (actually, it's a different one). Notice, don't fix the error in the temporary file, fix it in the original(!) file. If you scroll up to the first section, you see a sect1 element with the id=sec.nm.activate. Use that information for your grep command to find all the occurances of this ID: $ grep sec.nm.activate xml/*.xml The only file which contains an id=... line is xml/nm.xml. Open that file, jump to the same structure (line numbers are different!), fix the problem and validate it again. The error should disappear. -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH(o Maxfeldstrasse 5/\\Documentation Specialist 90409 Nuernberg, Germany _\_vhttp://www.suse.com| HRB 21284 SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] suse-xsl-stylesheets 1.9.19 not in factory
Hi, I am building a french openSUSE manual package but latest sources need suse-xsl-stylesheets 1.9.19 to build and Factory have only 1.9.18. Update request have been declined: https://build.opensuse.org/request/show/161597 Would it be possible to fix that, please? Thanks for the reminder, Guillaume! The request was declined as there was a conflict between the suse-xsl-stylesheets and susedoc packages. The susedoc package is obsolete now, so I've submitted a delete request for Factory. I've submitted the new version again to Factory, see submit request 173909. Hope it will be accepted this time. ;-) Currently, it builds fine in home repo linking to Documentation:Tools project but if I submit it to Documentation project, it won't build anymore. Sure. Good hint, thanks! -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] Update http://doc.opensuse.org/
Hi, Only a few days left until 12.2 gets released. Who is going to update http://doc.opensuse.org/ with the 12.2 docu? Thanks, Ludwig. Unfortunately, I don't have write permission on our server and most of our team is on vacation. :) However, next week is a good chance. -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-marketing] Does SUSE have good documentation?
Hi, [...] I think susedoc package is already available in official 12.1 oss repository: http://paste.opensuse.org/86757157 It's still there, yes, but it will vanish in 12.2. We hadn't had the time to release and replace it with daps yet. [OOT] But I wonder why susedoc should require Inkscape to be installed? http://paste.opensuse.org/44708850 We need Inkscape to generate PNG from SVG. Fill new bug for it? Thanks for the offer, but it's not a bug, it's a feature. :)) Hopefully I'll start working on it before the end of this month.. =) If you have further question, you can also discuss these things on our opensuse-doc mailinglist. :-) -- 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-marketing+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-marketing+ow...@opensuse.org
Re: [opensuse-doc] PDF build error
Hi Guillaume, Le 24/11/2011 10:44, Thomas Schraitle a écrit : [...] $ rpm -q xmlgraphics-fop xmlgraphics-fop-1.0-11.noarch xmlgraphics-fop-1.0-12.1.3.noarch Looks good. $ rpm -q freefont dejavu freefont-0.20101118-4.4.noarch dejavu-2.32-2.1.noarch freefont-0.20110523-4.1.3.noarch dejavu-2.33-4.1.1.noarch Also ok. [...] It helps for the CSS error be I get lots of errors like this one : org.w3c.dom.DOMException: The current document is unable to create an element of the requested type (namespace: http://www.w3.org/2000/svg, name: flowRoot). at org.apache.batik.dom.AbstractNode.createDOMException(Unknown Source) at It seems the above error is caused by a strange SVG graphic. Which JVM/JRE do you use to build the doc? I am using openJDK. Me too on openSUSE 12.1: $ java -version java version 1.6.0_22 OpenJDK Runtime Environment (IcedTea6 1.10.4) (suse-1.2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Please note that the following generates a PDF without error: daps --envfile=ENV-opensuse-kvm color-pdf daps --envfile=ENV-opensuse-reference color-pdf daps --envfile=ENV-opensuse-security color-pdf daps --envfile=ENV-opensuse-startup color-pdf That's a good tip! It was the Tuning Guide which does not build. After some investigation, it's the cgroups1.svg graphic to blame. If you save a SVG graphic as normal Inkscape SVG it introduces strange -inkscape-bla attributes which causes this error. You have to explicitly save it as Plain SVG to avoid such attributes. I mention it so you can avoid such problems. It hit me in the past sometimes. ;) I've committed the fixed SVG and it builds now. However, the graphic looks garbled... Last request, it cannot find productname nor productnamereg in html and pdf, so it generates empty productname and I get Documentation de (french for Documentation of) without openSUSE, just a blank. Where could it come from? I will look into this. -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-marketing] Does SUSE have good documentation?
Hi, [...] Its odd that I have to hunt through Novell site for the actual manuals. http://doc.opensuse.org gives the current manuals. Seems this is not well-known yet ;-( Well, at least, if you go to http://software.opensuse.org/ you can see not only the Download Method, but also a link to Documentation in the third column. I don't know where Roger searched for the manuals so I've played with the search field. I've started with http://opensuse.org and entered documentation. This drove me straight to http://en.opensuse.org/Documentation. Only the term doc was not clearly resolved. Roger, which URL did you use to search for documentation? -- 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-marketing+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-marketing+ow...@opensuse.org
Re: [opensuse-marketing] Does SUSE have good documentation?
Hi Roger, Am Samstag, 3. Dezember 2011, 01:34:52 schrieb Roger Luedecke: That we are low in the polls says ... Sorry, but I disagree. I don't think this poll has any relevance. It can be a lot of reasons why we are low. One reason is that it is a Russian site so we can assume it is geographical focused on Russia. That means, it excludes all users who cannot read or understand Russian. That makes the hole poll very distorted. »There are three kinds of lies: lies, dirty lies and statistics.« :-) ... we need to make our documentation much more obvious and accesible. +1 The documentation should be much more visible. Its odd that I have to hunt through Novell site for the actual manuals. Further, though they can be installed from repos... they aren't obvious as to where they went. Right, again, I fully agree with you. We've started in my team some initiatives to raise the visibility/awareness, but it needs some time to see the effects. Thanks for taking the time to care about documentation. :-) -- Gruß/Regards, Tom -- SUSE LINUX Products GmbH (o Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany_\_v http://www.suse.com SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 -- To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-marketing+ow...@opensuse.org
Re: [opensuse-marketing] Does SUSE have good documentation?
Hi, This is a poll about documentation of which distro is complete and intelligible: http://translate.google.ru/translate?hl=ruie=UTF8prev=_tsl=rutl=entwu=1u=http://www.linux.org.ru/polls/polls/7009480%3Fhighlight%3D11391%26highlight%3D11392 It seems SUSE and openSUSE anre outsiders... Interesting, but I don't think this is reliable. There are so many factors that can influence the result that I doubt such polls have any value. (By the way, my opinion would be the same, if openSUSE would be the winner.) For example, the poll doesn't answer *why* the documentation of Arch Linux is considered better than Gentoo, Debian, etc. A total vote of 1160 is not statistically relevant either... So, relax, take a deep breath and move further. :-) -- 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-marketing+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-marketing+ow...@opensuse.org
Re: [opensuse-doc] opensuse-doc svn repository moved to svn.opensuse.org (DONE!)
Hi, On Friday 25 November 2011 Juergen Weigert wrote: The move is done! The new server is alive and kicking. Faster than we thought. Well done, Jürgen and Julian! Thanks a lot for your efforts! The new checkout URL for the opensuse-doc repo is: svn co https://svn.opensuse.org/svn/opensuse-doc A browser view is available at: http://svn.opensuse.org/viewvc/opensuse-doc/ I migrated my existing working directory by $ cd to_the_dir_countaining_trunk $ svn info | grep URL $ svn switch --relocate svn+ssh://jnwei...@svn.berlios.de/svnroot/repos/opensuse-doc https://svn.opensuse.org/svn/opensuse-doc $ svn up [...] Just for the records: In my working directory, I have a https URL instead of the svn+ssh schema. When I did the switch, I've got the following error message: $ svn switch --relocate \ https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk \ https://svn.opensuse.org/svn/opensuse-doc svn: Relocate can only change the repository part of an URL To fix that, I needed a slightly different procedure: 1. $ cd to_the_dir_countaining_trunk 2. Determine your root URL: $ svn info | grep URL https://svn.berlios.de/svnroot/repos/opensuse-doc 3. Use the root URL from step 2 and combine the new opensuse URL plus the trunk path: $ svn switch --relocate \ https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk \ https://svn.opensuse.org/svn/opensuse-doc/trunk 4. Update: $ svn up That have worked for me. I could successfully commit to the new openSUSE SVN. Thanks! :-) -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] French translation for openSUSE Doc
Hi Guillaume, On Monday 21 November 2011 Guillaume Gardet wrote: [...] Oh, and by the way, make sure you install the daps package. It is the successor of the susedoc package and is needed to build HTML or PDF. Hope we can announce it soon. Yes, I noticed that the old way did not work (I replaced my PC due to hard disk crash) and see on the wiki that daps is now used. I tested it and it seems to works fine. Perfect! Yes, we were a bit silent about it, but we wanted to announce it after all major bugs are removed and at least some documentation is available. -- 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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-doc+ow...@opensuse.org
Re: [opensuse-doc] Re: Novell / opensuse documentatie vertalen
Hi Max, On Wednesday 27 July 2011 MadMax wrote: [...] 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). I'm not scared easily of a little learning. I can read several languages, so xml won't be a big problem. Only the implementation of the dtd and the choice of variables are still puzzling. But I'll learn that later. What do you mean by choice of variables? From your paragraph I guess you mean the element names, right? In my opinion, you don't have to learn it in a classical way like a poem. Usually most element names are self explanatory and can be guessed easily. It's true, in comparision to HTML are DocBook element names a bit longer; however, terseness was not a design issue for XML, neither for DocBook. :) With a good XML editor, this is also not an issue. [...] I managed that already (with susedoc) and will continue with daps. More help will be asked. But I start with translating the para text. Congratulations! [...] I think I make some time coming weekend to submit the first work. I made the first PDF and it's looking good. I'm used to usefull messaging when updating work (by example in a wiki). I hope to continue that with svn. Sure, it's up to you to give meaningful log messages when you commit your files. :) I would recommend to submit your files as often as possible. Small changes are easier to track and it's easier to revert them if something goes wrong. How often you submit your files is subject to your personal preference. [...] So, to work then! I get do something, makes me excited. Great! Whenever you need help, just ask. -- 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+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: [opensuse-doc] Re: Novell / opensuse documentatie vertalen
Hi Jos, (removed my private address) On Sunday 17 July 2011 Jos Poortvliet wrote: 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. 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). The source code is not available from the Novell site; it contains only the end product (read: HTML and PDF). The sources can be found in our documentation SVN at BerliOS: https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents The project is hosted at BerliOS: http://developer.berlios.de/projects/opensuse-doc/ 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. [...] 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. The structure is still correct. Hope I could clarify some questions. If you still have some questions, just ask. :) -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Tel: +49-(0)911-740 53 131 Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: [opensuse-marketing] Toward further improvement of openSUSE Weekly News
Hi, On Wednesday 26 January 2011 Sascha 'saigkill' Manns wrote: [...] I think pdf is an excellent work. Thanks! :) I do not like that the links are in the bottom. I think a list must be made at the end of the pdf with the links or an internet page containing those links or something like More Information at http://news.opensuse.org; Hmm. I must search in the Stylesheets if its possible. ATM all Links a generates automaticly while the transferingprocess to PDF. Complete disable the Links are'nt possible. Because we have one Sourcecode who is used for both Outputformats. The finished HTML Code makes the Link direct executable. And in the finished PDF it is just placed on the bottom. What maybe is possible is to collect all Links and put it on an seperate Page on the End of the Weekly News. But that i doesn't know exactly. For that i must read the Documentation. On the other Hand, would every like to have all Links on 3 separate Pages on the End? Just to add some notes, as I was the one who mainly developed the layout: I've positioned the links as footnotes at the bottom of the page, because mainly due to hyphenation and convenience issues. Well, I've integrated some code which indeed hyphenate URLs correctly (hopefully), but it can be quite hairy in some cases. About the convenience: You've suggested to collect the links at the end of the PDF (also called endnotes). This is probably also a solution, but could also lead to frustration. :) Although a footnote might be not the best in a all cases, readers can just look at the botton and find it quickly. They don't have to turn the page. This is probably more anoying when you print the PDF instead of reading it on screen. By the way: Thanks to the well developed DocBook stylesheets, the behaviour about links in footnotes can be easily changed: just change the parameter ulink.footnotes from 1 to 0 (zero) (hint for Sascha :) -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
Re: Re: [opensuse-doc] Acess on Berlios SVN
Tuesday 28 December 2010 Luiz Fernando Ranghetti elcheviv...@gmail.com writes: Could someone grant me acess on berlios SVN, specially in the to be created pt_BR folder? Yes :) Please, send me your berlios account name, and then Jürgen must probably adjust some settings. I think, Jürgen did something to make it easier. For translations, only the account name is needed now which has to be added to the opensuse-doc project. Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ - -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: Re: [opensuse-doc] Acess on Berlios SVN
Hi Luiz, Tuesday 28 December 2010 [...] I'm having some problems trying to create pt_BR subfolder. The message says its forbidden. Ok, I've created a subfolder trunk/documents/distribution/pt_BR for you with the corresponding content. Could you check out the pt_BR directory, add some content and try to commit it? I'm also having problems with distribution/hu/images/src like the screenshot attached which says basically that the ifolder_main.png.svn-base cannot be found. Hmn. This looks supicious to me. Did you just copied something from the hu or en image directory? This would be not a good idea as you would copy the .svn directory too. However, a .svn directory is specific to the location. -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ - -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: Re: Re: [opensuse-doc] Acess on Berlios SVN
Hi, Tuesday 28 December 2010 [...] This happens (errors on hu images) when I do a checkout in distributions folder. I think it is because there is two files with the same name (ifolder_main.png and iFolder_main.png - and I'm using Windows right now), but no problem as I will use only en and pt_BR folders. Ahh, ok I misread your sentence, sorry. Usually SVN does just fine with case sensitive filenames. However, I think the problem is on the Windows side, probably a filesystem issue. I checkout the pt_BR and now I can upload thinks. Ok, adding a new directory did the trick. :) I've inserted you also to the opensuse-doc-commit mailinglist. Have fun! Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ - -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: [opensuse-marketing] openSUSE distribution Versus the openSUSE project
Hi, On Wednesday 10 November 2010 Andreas Jaeger wrote: On Tuesday 09 November 2010 17:57:32 Kostas Koudaras wrote: [...] First: * distribution * OBS (main part of tools) and SUSE Studio * community * communication Second - lower prio: * YaST * libzypp/zypper * openSUSE Education (LI-F-E) * openSUSE Medical ok,but you still haven't told me what is the available promotional material about all this. Many of that material needs to be created ;-( At least for SUSE Studio there _is_ some documentation[1] -- if it is suffice for marketing it's a different questions. :) [1] http://www.novell.com/documentation/suse_studio/ -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
Re: [opensuse-marketing] openSUSE distribution Versus the openSUSE project
Hi Javier, On Thursday 11 November 2010 Javier Llorente wrote: [...] [1] http://www.novell.com/documentation/suse_studio/ Perhaps it's something to be added to doc.o.o? ;) That was the plan, yes. :) BTW, I can't find any link on http://en.opensuse.org/Portal:SUSE_Studio to http://www.novell.com/documentation/suse_studio/ I've added a new section in the FAQ: http://en.opensuse.org/openSUSE:SUSE_Studio_Faq -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
[opensuse-doc] Re: [opensuse-marketing] The openSUSE Handbook proposal
as it can change easily. Better use the section title or an anchor from HTML. :) But even if you give out SVN write access, I'm afraid that not many people will contribute to the XML source because of the learning curve. What makes you so sure? To cite Tim Berners-Lee: »If you use the original World Wide Web program, you never see a URL or have to deal with HTML. That was a surprise to me - that people were prepared to painstakingly write HTML.« You have to switch from the rendered manual (HTML, PDF, ...) to the XML source, and you have to know at least some XML basics. In Wikis you have to know some Wiki basics. What's the point here? :) OTOH the wiki is more like a long(er)-term solution, but makes contribution much easier - just click Edit. Sorry, I'm not convienced. DocBook exists for more than 10 years! It's well- matured, very well documented, and it's one defacto standard for technical documentation. Ok, maybe you can count DITA as well. Although I'm not that much into the Wiki topic, I have the impression the Wiki syntax is not very well established: One Wiki supports a certain syntax, another don't. If this is really the case, I wouldn't call Wikis a long-term solution. For easier contribution: See my idea above. Yes, writing a good wiki-to-XML tool will need some work, but it is possible. And it is worth the effort IMHO. Why should we write some wiki-to-XML converter when we have already everything in place, ready to be used? [...] You've seen the numbers from Rajko - around 90 active users in the last 3 months. That's still 89 more than in the lessons for lizards *g,dr* You compare apples with oranges. :) -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: [opensuse-marketing] The openSUSE Handbook proposal
as it can change easily. Better use the section title or an anchor from HTML. :) But even if you give out SVN write access, I'm afraid that not many people will contribute to the XML source because of the learning curve. What makes you so sure? To cite Tim Berners-Lee: »If you use the original World Wide Web program, you never see a URL or have to deal with HTML. That was a surprise to me - that people were prepared to painstakingly write HTML.« You have to switch from the rendered manual (HTML, PDF, ...) to the XML source, and you have to know at least some XML basics. In Wikis you have to know some Wiki basics. What's the point here? :) OTOH the wiki is more like a long(er)-term solution, but makes contribution much easier - just click Edit. Sorry, I'm not convienced. DocBook exists for more than 10 years! It's well- matured, very well documented, and it's one defacto standard for technical documentation. Ok, maybe you can count DITA as well. Although I'm not that much into the Wiki topic, I have the impression the Wiki syntax is not very well established: One Wiki supports a certain syntax, another don't. If this is really the case, I wouldn't call Wikis a long-term solution. For easier contribution: See my idea above. Yes, writing a good wiki-to-XML tool will need some work, but it is possible. And it is worth the effort IMHO. Why should we write some wiki-to-XML converter when we have already everything in place, ready to be used? [...] You've seen the numbers from Rajko - around 90 active users in the last 3 months. That's still 89 more than in the lessons for lizards *g,dr* You compare apples with oranges. :) -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
[opensuse-marketing] Re: [opensuse-doc] NovDoc Usage
Hi Christian, On Friday 01 October 2010 Bryant, Christian wrote: ... I love the susedoc style sheets Thanks! :) Actually I'm the person who is in charge of the susedoc package. ... but I'm not clear on the usage requirements and wanted to make sure that I can use susedoc to create manuals for my appliances that look exactly like the actual openSUSE manuals. I know the code for susedoc is GPL but are there some documentation guidelines for folks like me that have this type of project in mind? At the moment, the current project is hosted on BerliOS: http://developer.berlios.de/projects/opensuse-docmaker/ If you are interested in the technical background, the following link points to a PDF which may be useful for you: https://svn.berlios.de/svnroot/repos/opensuse- docmaker/trunk/doc/susemakedoc.pdf If you have further questions, don't hesitate to let us know on the opensuse- doc mailinglist. :) -- Gruß/Regards, Thomas Schraitle -- SUSE LINUX Products GmbH (o Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-marketing+h...@opensuse.org
Re: [opensuse-doc] Re: questions for susedoc (Japanese fonts in susedoc)
Hi, On Friday 22 January 2010 Yasuhiko Kamata wrote: [...] You can see the results here: http://www.suse.de/~toms/opensuse-man-ja/opensuse-html-xep.pdf (It takes some time to synchronize.) Oh, that's great! :-) Surely problems which appears on FOP disappeared; I can see texts as expected. So I'll use XEP instead of FOP from now. XEP is a commercial application. There is also a Personal Edition, but it prints a logo in the bottom of the page. I think, it must also work for FOP, but at the moment, our stylesheets are a bit untested as we use XEP internally. If you don't mind, I would like to suggest some improvements in your SVN repository: [...] Thank you for advice. SVN repository is now under constructing; I'll arrange the structure later (after 50% completion or so). Whatever fits best do your needs. It was just an idea. Do whatever you want/need. :-) Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://lizards.opensuse.org/author/thomas-schraitle/ - -- To unsubscribe, e-mail: opensuse-doc+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-doc+h...@opensuse.org
Re: [opensuse-doc] Re: Issues with building Novell documentation (RESOLVED?)
Hi Nikolay, On Donnerstag, 16. August 2007, Thomas Schraitle wrote: On Donnerstag, 16. August 2007, Nikolay Derkach wrote: [...] Seems that default confgiuration file ~/.susedoc/fop-config.xml misses required fonts: Ok, I think, I have now a better understanding of the problem. :) It seems there is an inconsistency between the FOP config file and the fo/fonts.xsl stylesheet in regard of the font names. This stylesheet is responsible for selecting the correct fonts for XEP or FOP. Probably I will release a new version of susedoc tomorrow, if my tests are successful. According to my tests, I think I found it. I installed the package on a test computer and it works. There is (still) a small issue about hyphenation but I will take care of it later. Could you download the latest version and try it again, please? See http://download.opensuse.org/repositories/home:/thomas-schraitle/openSUSE_Factory/noarch/ Thanks, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: Issues with building Novell documentation (RESOLVED)
Hi Nikolay, On Freitag, 17. August 2007, Nikolay Derkach wrote: [...] Yes, the font issue is fixed. I am very happy to hear that. :) But for some reason (most likely unrelated to susedoc) I get the following when building startup: http://opensuse.homelinux.com/logs/fop-java.txt Yes, I got the same errors. Quickstart packages were built but with some minor issues: http://opensuse.homelinux.com/pdfs/opensuse-gnomequick-fop-online.p df http://opensuse.homelinux.com/pdfs/opensuse-kdequick-fop-online.pdf I think, that's mostly FOP related. However, you can try to reduce the image size, so the first image fits on the page. I have to admit, there are some areas in the XSLT stylesheets that are problematic for FOP. When I wrote these stylesheets, FOP couldn't handle lots of XSL-FO issues. Luckily this situation has improved and the latest version is much better, although there are still some problems. Thanks for your patience, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: Issues with building Novell documentation (RESOLVED?)
Hi, On Donnerstag, 16. August 2007, Nikolay Derkach wrote: [...] The above line creates a PDF with an embedded AndaleSans font. I don't have XEP installed. make FOP=suse-fop produces pretty the same result. Moreover if ./tmp directory is empty in simply fails (doesn't create it). Yes, but that's because you have version 2.6.29 of libxml2 which contains this error. Maybe you should try to install the previous version and rebuild it again? I tried it with your XML sources and I can create a PDF with FOP (although I see some warnings.) Maybe should I intall some additional font package in addition to the previous? Not really, the agfa-fonts and freefonts packages are enough. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: Issues with building Novell documentation (RESOLVED?)
Hi Nikolay, On Donnerstag, 16. August 2007, Nikolay Derkach wrote: [...] 3. Do you have the agfa-fonts installed? Get it from here (you have to rebuild it for 10.3, probably adapt the SPEC file): ftp://ftp.suse.com/pub/suse/i386/10.1/SUSE-Linux10.1-GM-Extra/sus e/src/agfa -fonts-2003.03.19-28.src.rpm Sure I have them installed. Just with a bit modified spec (for font path), though it doesn't matter. Ok, let's try another idea: 4. Rename your FOP config with old ~/.susedoc/fop-config.xml and rebuild the book. Do you see any changes? Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: Issues with building Novell documentation (RESOLVED?)
Hi, On Donnerstag, 16. August 2007, Nikolay Derkach wrote: [...] Seems that default confgiuration file ~/.susedoc/fop-config.xml misses required fonts: Ok, I think, I have now a better understanding of the problem. :) It seems there is an inconsistency between the FOP config file and the fo/fonts.xsl stylesheet in regard of the font names. This stylesheet is responsible for selecting the correct fonts for XEP or FOP. Probably I will release a new version of susedoc tomorrow, if my tests are successful. Let's get the fingers crossed. ;) Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: Issues with building Novell documentation
Hi Nikolay, On Dienstag, 14. August 2007, Nikolay Derkach wrote: [...] runtime error: file /usr/share/susedoc/xslt/misc/svg.color2grayscale.xsl line 75 element copy Attribute nodes must be added before any child nodes to an element. Have you tried it with the latest release? Yes, I have. This happens on every SVG file from opensuse-manual. A snip of make log is here: http://svn.team.org.ru:8000/trac/browser/test/svg_errors.txt?form at=txt Also: if I overcome these svgs this is unfortunately not the end: /usr/share/susedoc/bin/fopchangefontpath.py /usr/share/susedoc/etc/FOP/fop-suse.xml -o /home/nderkach/.susedoc/fop-config.xml Traceback (most recent call last): File /usr/share/susedoc/bin/fopchangefontpath.py, line 254, in module fop.process() File /usr/share/susedoc/bin/fopchangefontpath.py, line 209, in process fontres[0], IndexError: list index out of range make: *** [/home/nderkach/.susedoc/fop-config.xml] Error 1 I checked out your files from svn://svn.team.org.ru/trunk/merged/ and build all books with XEP some with FOP and they work. I guess there are two possibilities: 1. Missing Packages or Wrong Versions There is a bug related to SVG in the 0.95 release of dia (published in 10.2). In my repository [1] you can find a patched version from Berthold. Please check your package versions and compare it with the following list: $ rpm -q susedoc inkscape transfig ImageMagick xml-commons-resolver docbook-xsl-stylesheets svg-dtd freefont agfa-fonts fop dia susedoc-4.2_20070813-1 inkscape-0.44.1-26.2 transfig-3.2.5_alpha7-1 ImageMagick-6.3.0.0-27.6 xml-commons-resolver-1.1-43 docbook-xsl-stylesheets-1.73.0-2 svg-dtd-20030114-192 freefont-0.20060718-28 agfa-fonts-2003.03.19-53 fop-0.93-2.1 dia-0.96.1-5.1 2. Old SVG Graphics Did you try a make clean? If make finds an already processed SVG graphic, it will not create it from the original source. For this reason remove some old files and rebuild the book from scratch. I had this bug last time too but I am pretty sure it is fixed now. The last error about fop-config.xml looks really strange but I think is has something to do with one of the issues before. Hope this helps, Tom [1] http://software.opensuse.org/download/home:/thomas-schraitle/ -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL question: how-to subdivide very big articles ?
Hi Alexey, On Samstag, 28. Juli 2007, Alexey Eremenko wrote: I have LfL question: how-to subdivide very big articles ? That is: I have VirtualBox article - a big guide actually. I want to have it's chapters to be available as links at the top of the article. Thomas once told me about using chapter IDs, but I didn't understood then. I will try now... So, can you help with example XML code ? Sure. You will see, it's pretty easy after you get the idea behind. For example, you want to link from a paragraph to a chapter. These are the steps that you need: 1. Determine the ID value of the chapter that you want to link to. You can also link to sections, figures, tables, appendices, etc. the method is the same. It should look like this: chapter id=chap.foo !-- _ Your ID value -- titleSomething about Foo/title ... 2. If you do not find an ID value, define your own ID value. Insert an attribute id with your ID value in the respective element. The ID value should be legible so that any writer have at least some idea what is this chapter about. :) Look for other examples. Be careful, the definied ID value must be unique (appears only once in the whole document), otherwise you get validation errors. 3. Go back to your paragraph and insert a xref element. This is the cross reference to your ID and looks like this: para... See xref linkend=chap.foo/ for more information ... /para You can insert as many xrefs to your chapter as you like. That's all! The stylesheets take care of how the xref appears in your text. Usually you get something like this: See Chapter 1, »Something about Foo« for more information. Does it help? Have fun, Tom -- -- SUSE LINUX Products GmbH o) Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL doesn't compiles on openSUSE 10.3 a4!
Hi, On Donnerstag, 24. Mai 2007, Alexey Eremenko wrote: [...] Writing html/lessons4lizards/ln-id2583250.html for legalnotice runtime error: file file:///usr/share/xml/docbook/stylesheet/nwalsh/1.72.0/lib/lib.xsl line 212 element value-of Internal error in xsltValueOf(): failed to cast an XPath object to string. make: *** [html/lessons4lizards/index.html] Error 10 Anybody has the same problem ? Mee too. :-( It looks like a bug in libxslt. You could downgrade to an earlier version of libxslt. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL doesn't compiles on openSUSE 10.3 a4!
Hi, On Freitag, 25. Mai 2007, Alexey Eremenko wrote: Should I open a bug report? Or you already take care of this issue? It would be perfect, if you could open a bug report. I don't know the component, but use libxslt. Thanks, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL: Roles
Hi Alexey, On Donnerstag, 17. Mai 2007, Alexey Eremenko wrote: [...] Even through I'm thinking about nmap and AppArmor, I don't consider writing about those soon. Just for the sake of completeness, there are already two books about AppArmor, an Quick Start Guide and an Administration Guide, see http://www.novell.com/documentation/opensuse102/ :-) Have fun, Tom -- -- SUSE LINUX Products GmbH o) Tel: +49-(0)911-740 53 131 Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] lfl: New chapter on digikam magic
Hi Christian, On Donnerstag, 17. Mai 2007, Christian Boltz wrote: on Montag, 14. Mai 2007, Jana Jaeger wrote: [...] In the long run, we should look at having more frequent releases of the LFL doc on http://forgeftp.novell.com/lfl/.html/. But in as a short term workaround, I could send you PDFs or HTML files whenever I consider a certain milestone to be reached (like the completion of a section ...). Does forgeftp.novell.com allow to run cronjobs? As far as I know, Novellforge does not support cronjobs. :-( If someone knows more about this issue please let me know. I can help writing some scripts if needed (I have a similar cronjob running on the german FAQ, the only difference is that it's CVS instead of SVN). Thanks, Frank did that somehow already, however on his local machine. :) Bye, Tom -- -- SUSE LINUX Products GmbH o) Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL: Roles
Hi Thomas, On Donnerstag, 17. Mai 2007, Thomas R. Jones wrote: I have been reviewing the LfL project over the last few days. It seems the project is in its infancy but shows promise. How has the process of editing been handled? At the moment there is no editing or proofing at all. The idea was to collect the topics first, to get suggestions, request for enhancements etc. After the text is stable enough we can proofread it -- whowever does this important task. I have noticed a considerable amount of broken English --- as is commonly the case when an individual writes in a secondary language. Yes, very true. [...] How would I be able to extend to the community my hand as an editor? I feel very comfortable wearing both the author and editorial hats; but definitely would like to refrain from stepping on any toes so to speak. You can, as a suggestion, announce what you are proofing (or going to proof). So your corrections don't collide with others. :) Does this sound reasonable? Also, there are a few topics that I began to write for fedora that I would like to go ahead and present to the opensuse community as well: Securing Filesystems Host Integrity Monitoring Installation of OVAL Installation of XSDL OVAL Administration Digitally signed and encrypted firewall rulesets I feel more comfortable in XML, XSLT, ... or the like than your topics, so I am afraid I can't help you here. There should be others on this list who can give you a helping hand. You can ask on opensuse as well. Where are all the experts? :) Come on! Have fun, Tom -- -- SUSE LINUX Products GmbH o) Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL: Few Questions
Hi Thomas, welcome to opensuse-doc! :-) On Mittwoch, 16. Mai 2007, Thomas R. Jones wrote: I was wondering what the target grading was for readability? Well, I assume you mean for which readers we write, right? We try to target it to normal users but this term can be stretched. :) There are topics that are very system administrative, for example. Also, is there not a common novell/suse/opensuse entity file for inclusion into all documents? For LfL we have one file that includes every topic. Is that what you mean? Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Online Manual input source
Hi Hylton, On Dienstag, 15. Mai 2007, Hylton Conacher (ZR1HPC) wrote: Sorry for the delay in replying. Not a problem. :) On Dienstag, 8. Mai 2007, Hylton Conacher (ZR1HPC) wrote: Have you looked into the Lessons for Lizards project? It might be an excellent way to get the information you consider important into an easily-accessible format. I have, and find that it is not categorised and as structured as I would have expected and the menu is faar too long as I am almost sure many of the subheadings could be grouped under a single parent heading. We have started it only a few months ago so it takes time everybody get used to it. It might look a bit unbalanced. OK, although I think with a better structure of what topics ned writing on would be better as then writers can choose and be allocated to a writing/contributing to a task. We have a template that each topic should use, see here: https://forgesvn1.novell.com/svn/lfl/trunk/common/xml/topic-template.xml The idea was to create chapters that deal with certain topics like Installation, Networking, System Administration, etc. If someone writes a topic it is easier to include it under an available category. I think the structure of the above template should be sufficient for many topics. Do you think there is anything missing? Do you have something special in mind? I am very interested in listing to your suggestions. Could you elaborate your ideas a bit more? Is it the structure itself or the content of some articles, or anything else? Thank you for taking the time to listen. As I said earlier, I think it is the structure itself. The online book/manual is going to be an ever changing and growing, so readers need to know where to look for help on the problem they are experiencing, as opposed to having to basically scour the whole manual. Ok. Do you have an example that illustrates your problem? I am not sure if I understand your issue completely. [...] For more details look here: http://developer.novell.com/wiki/index.php/Lfl/Tasks I had a look and seem to fit in as a designer but more for the layout/structure of the LFL book. If you want to improve the stylesheets or need a place for your ideas I can give you access to the Subversion repository. Send me a private mail with your login name. [...] Well I think i would be more use in helping design the base structure or Contents that the various writers are going to write articles for. With the structure in place it can also give the writer a little guidance on how technical or newbie they have to write. Everybody can participate in this project. In the end there should be consensus of what you propose. You can write a Request for Improvements and discuss it with others here on this mailinglist. :) [...] Thanks for asking! :-) Sorry, What did I ask ? :) Well, that was a over-simplification on my side. :-) Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Fwd: [Gimp-docs] ODF Support
Hi, On Freitag, 4. Mai 2007, Alexey Eremenko wrote: The GIMP teams says they found a way to generate ODF from DocBook XML. Maybe we could do the same... This could be beneficial for LfL. Here is the original message: [...] http://open.comsultia.com/docbook2odf/ [...] I have made already a package. It is in my repository, see http://repos.opensuse.org/home:/thomas-schraitle/openSUSE_10.2/noarch/ I hadn't have enough time to test it. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Fwd: [Gimp-docs] ODF Support
Hi, On Freitag, 4. Mai 2007, Thomas Schraitle wrote: Hi, On Freitag, 4. Mai 2007, Alexey Eremenko wrote: The GIMP teams says they found a way to generate ODF from DocBook XML. Maybe we could do the same... This could be beneficial for LfL. Here is the original message: [...] http://open.comsultia.com/docbook2odf/ [...] I have made already a package. It is in my repository, see http://repos.opensuse.org/home:/thomas-schraitle/openSUSE_10.2/noar ch/ I saw it was a pretty old package with a weird version number. I have updated to 0.211 and fixed some small packaging problems. FYI it's building at the moment but should be finished in a few minutes. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL: Some minor fixes for the VirtualBox article
Hi Alexey, On Sonntag, 22. April 2007, Alexey Eremenko wrote: A spell check might help. Especially if you use the SUSE-enhanced dictionary. Nice. But how-to setup it? Update your trunk/common directory. Under common/aspell there is a README.txt. You can also use this link: https://forgesvn1.novell.com/svn/lfl/trunk/common/aspell/README.txt Bye, Tom -- -- SUSE LINUX Products GmbH o) Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Please provide LfL in HTML format, online browseble
Hi Alexey, On Montag, 16. April 2007, Alexey Eremenko wrote: To Novell: Please provide LfL in HTML format, online browseble. There is a link on the page below to HTML version, but it doesn't works. :( http://developer.novell.com/wiki/index.php/Lessons_for_Lizards Thanks to Frank, it's now working. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] [STYLE] Terminology for Sources from which Packages Are Installed
Hi, On Montag, 16. April 2007, Benji Weber wrote: [...] I would suggest: Software Repository Isn't it confused with a Subversion/CVS repository? I am not sure if there is already this connotation. Software Catalogue. I imagine a description merely *about* software with this phrase but not a collection of installable RPM packages. Maybe it's only me. :) What about this: * Software depot * Software depository * Software reservoir * Software deposit * Software/Package storage (site) * Software loft ;) Ok, I admit some may sound very strange for a native speaker. :) Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Lack of LfL in the latest Alpha !?
Hi, On Freitag, 16. März 2007, Alexey Eremenko wrote: As I understand there is a lack of LfL in the latest Alpha of openSUSE 10.3 ! Yes, that's true. Why is this? I would prefer to see it on the SUSE start menu. We were busy with other things, but we will integrate it into one of the next alphas/betas. I think, we should consider how we can improve the text basis. Someone (we, others?) should read it carefully and remove any strange sentences, typos, make it more consistent, etc. What do you think? Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Changing ENV and Makefile?
Hi, On Mittwoch, 7. März 2007, Thomas Schraitle wrote: any objections changing the ENV and Makefile? I am asking, because the modification will not work with older versions of susedoc. I hope most people updated to the latest version. :) If nobody objects I will commit the changes in the next few days. Ok, I updated ENV-lessons4lizards and Makefile. Please report any errors. Thanks, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Updated article of VirtualBox + openSUSE
Hi Alexey, On Mittwoch, 7. März 2007, Alexey Eremenko wrote: I have just updated my article (part of LfL, SUSE documentation) - that explains step-by-step about configuring VirtualBox on openSUSE system. HTTP link: http://download.yousendit.com/62543C517313426E The new, updated article also includes information about 2 Hot Topics: Host Networking and USB. (thanks Pablo!), plus it has extended database for troubleshooting tips and a lot of useful external links. What do you think of this article? Thanks for the update! :-) I have some suggestions, maybe you find it useful: 1. Section Terminology: ... this is *what* you are trying to emulate. use emphasiswhat/emphasis instead of *what* 2. You used an orderedlis in section Basic Configuration Procedure. That's possible but I would say a procedure fits semantically better, because you describe a task here. Another issue are the 17 steps. I would suggest to group them into smaller units with substeps. This helps your reader to skim through the task and it is much more readable. For example, a procedure with substeps looks like this: procedure step paraDownloading VirtualBox/para substeps step paraDownload VirtualBox from .../para /step step paraChoose .../para /step /substeps /step step paraInstalling VirtualBox/para substeps step para.../para /step /substeps !-- ... -- /step step paraConfiguring VirtualBox/para substeps step para.../para /step /substeps !-- ... -- /step /procedure 2. Step 4 is IMHO too simple. :) You group guimenus into menuchoice (which is fine) but acutally some content is not a guimenu at all. I would separate them. For example: Setup your user(s) to be part of “vboxusers” group. Start YaST and select Security and Users+Group Management. Create a new group with ... Maybe you can even separate this step into two individual steps? 3. In step 11 a verb (select?) is missing. 4. Step 13 contains a kaskade of guimenus, but without a menuchoice. Wrap a menuchoice around them and remove the -. 5. Section Setting up Guest VM Additions: You can put your NOTE: That linux-sources... into a real note like the warning in the same section. 6. Section Advanced Topic: Networking via Host Bridging: ... user “tux”. Better use this: systemitem class=usernametux/systemitem (Search in your article if there are other occurances of users and replace them with systemitem.) 7. Use a procedure for the orderelist As we said earlier,... 8. Section Advanced Topic: HOWTO USB + openSUSE 10.2 + VirtualBox 1.3.6: You used kind of subsections (Slower bootup of VM, Preconditions) which I would transform into a sect3. Another point is: I would move the acknowledgments into your respective Thanks section. 9. Section Troubleshooting and Tips: ... press Right “Ctrl+F” Better use keycap and keycombo. :) 10. Section Thanks, Article first released on ... If you want a revision history for your article, there is the tag revhistory for this purpose. Insert it inside your sect1info. For more information, see http://www.docbook.org/tdg/en/html/revhistory.html Best wishes, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Update notification / XSLT questions
Hi Christian, On Donnerstag, 8. März 2007, Christian Boltz wrote: [...] I want to mail some documentation about available updates to root ;-) and hope that this makes this mail less off-topic here *g* - I need a bit help from XML/XSLT experts which I expect to be in the doc team ;-) In short: I have written a xsl file that filters the output of zypp-checkpatches-wrapper to send an update notification mail to root. It basically works, however I have some problems with the whitespace. Basically, it is a good idea to use xsl:text and xsl:strip-space and/or xsl:preserve-space. Especially if you want exact control of your whitespace. It can be a bit tricky to find the correct combination though. :) [...] I'd like to have - no empty at the very beginning - *** ERROR ***, Update sources and === ... === without leading whitespace - an empty line after the patch summary - less empty lines before Total updates Can someone help me with these issues? See the attached XSLT file. It gives me the following output: $ xsltproc patch2mail.xsl zypp.xml *** ERROR *** Some error during calculation happened *** ERROR *** Another error Update sources: ftp.gwdg.de (http://ftp.gwdg.de/pub/suse/update/10.1) irgendwo (http://ftp.irgendwo.de) === java-1_5_0-sun- Patch 1438-0(security) === SUN Java packages prior 1.5.0 update 7 allow DOS. Sun Java Runtime Environment (JRE) 1.5.0_6 and earlier, JDK 1.5.0_6 and earlier, and SDK 1.5.0_6 and earlier allows remote attackers to cause a denial of service (disk consumption) by using the Font.createFont function to create temporary files of arbitrary size in the %temp% directory (CVE-2006-2426). === java-1_5_0-sun- Patch 1438-0(security) === SUN Java packages prior 1.5.0 update 7 allow DOS. Sun Java Runtime Environment (JRE) 1.5.0_6 and earlier, JDK 1.5.0_6 and earlier, and SDK 1.5.0_6 and earlier allows remote attackers to cause a denial of service (disk consumption) by using the Font.createFont function to create temporary files of arbitrary size in the %temp% directory (CVE-2006-2426). Total updates: 2 (2 security) __TOTAL__22__ Bye, Tom -- -- SUSE LINUX Products GmbH o) Documentation Team Maxfeldstrasse 5 /\\ Technical Editor 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team ?xml version=1.0 encoding=ISO-8859-15? !-- Copyright (c)2007 Christian Boltz - www.cboltz.de License: GPL v2 or any later version -- xsl:stylesheet version=1.1 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; !-- xsl:output method=text encoding=ISO-8859-15 media-type=text/plain / -- xsl:strip-space elements=*/ xsl:template match=/xsl:apply-templates //xsl:template xsl:template match=update-status xsl:document href=- method=text xsl:apply-templates / /xsl:document/xsl:template !-- errors -- xsl:template match=errorsxsl:apply-templates //xsl:template xsl:template match=errors/error xsl:text*** ERROR ***#10;/xsl:text xsl:apply-templates / xsl:text#10;/xsl:text /xsl:template !-- update sources -- xsl:template match=update-sources xsl:textUpdate sources:#10;/xsl:text xsl:apply-templates / xsl:text#10;/xsl:text /xsl:template xsl:template match=update-sources/source xsl:value-of select=@alias / (xsl:value-of select=@url /) /xsl:template !-- updates -- xsl:template match=update-list xsl:apply-templates / /xsl:template xsl:template match=update-list/update xsl:text=== /xsl:text xsl:value-of select=@name / xsl:text- Patch /xsl:text xsl:value-of select=@edition / xsl:text(/xsl:text xsl:value-of select=@category / xsl:text) ===#10;/xsl:text xsl:apply-templates / xsl:text#10;/xsl:text /xsl:template xsl:template match=update-list/update/summary xsl:apply-templates / /xsl:template xsl:template match=update-list/update/description xsl:text#10;/xsl:text xsl:apply-templates / /xsl:template !-- xsl:template match=update-list/update/sourceUpdate source: xsl:value-of select=@alias / (xsl:value-of select=@url /)/xsl:template -- !-- summary -- xsl:template match=update-summary xsl:textTotal updates: /xsl:text xsl:value-of select=@total / xsl:text (/xsl:text xsl:value-of select=@security / xsl:text security)#10;#10;__TOTAL__/xsl:text xsl:value-of select=@total /xsl:value-of select=@security / xsl:text__#10;/xsl:text /xsl:template !-- end -- /xsl:stylesheet
[opensuse-doc] Changing ENV and Makefile?
Hi, any objections changing the ENV and Makefile? I am asking, because the modification will not work with older versions of susedoc. I hope most people updated to the latest version. :) If nobody objects I will commit the changes in the next few days. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Changing ENV and Makefile?
Hi, On Mittwoch, 7. März 2007, Thomas R. Jones wrote: On Wed, 7 Mar 2007, Thomas Schraitle wrote: Hi, any objections changing the ENV and Makefile? I am asking, because the modification will not work with older versions of susedoc. I hope most people updated to the latest version. :) If nobody objects I will commit the changes in the next few days. Bye, Tom Curiously, what type of changes are you referencing? Right, I should have better explained it. The changes affect tree files: 1. .env-profile This is already in our SVN but it is not used at the moment. It contains mainly echo statements and incorporates the system-profile from /usr/share/susedoc/etc/ 2. ENV-lessons4lizards The design of how we detect the respective stylesheets for a book has been changed. For this reason we introduced the LAYOUT variable, deleted some obsolete variables and incorporate the .env-profile. 3. Makefile This file can search in different directories for susedoc now. The DTDROOT variable is build from the result of this search. Of course the overall targets have not changed. It's just to iron out some outstanding issues that we had (bugfixing, simplification, ...). Nothing serious, but you can get in trouble if you have the wrong version of susedoc. Hope you get a feeling about these changes now. :) Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Help
Hello Greg, On Montag, 19. Februar 2007, Greg Smith wrote: [...] So. Is there a resource out there that can explain Linux's ins and outs in layman's terms? I have no problems with trying to learn the ins and outs, but most sources I can find are either TOO basic, or way over my head. Can anyone recommend a good starting point for my education? I am certainly willing to learn, even if it takes a few years, to get up to speed on Linux. I am just looking for a course of action, and am lost.Any guidance would be appreciated!Thanks for your time and consideration! Have you looked already in our openSUSE documentation? There are several manuals: * Start /usr/share/doc/manual/opensuse-manual_en/manual/book.opensuse.startup.html As the name implies, it's a more basic manual, explaining the installation, shell basics, directory structure of Linux, etc. * Novell AppArmor /usr/share/doc/manual/opensuse-manual_en/manual/book.apparmor.admin.html Explains the AppArmor security suite * KDE User Guide /usr/share/doc/manual/opensuse-manual_en/manual/book.opensuse.kdeuser.html Exploit the features of your desktop * Reference /usr/share/doc/manual/opensuse-manual_en/manual/book.opensuse.reference.html For the more advanced user. This is a really BIG manual containing 42 chapters(!) about your system, administration, network, services, etc. to name only a few. You can access it from the SUSE Help Center or directly by entering the above URLs. PDFs are available in the RPM package opensuse-manual_en-pdf. Have fun, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Translation of the Offcial Novell Documentation
Hi Nikolay, On Samstag, 17. Februar 2007, Nikolay Derkach wrote: Russian openSUSE community would like to translate Novell documentation stored at http://www.novell.com/documentation/opensuse102. Here is the project site: http://svn.team.org.ru:8000/trac Thanks a lot for your translation effort! We've already done a KDE Quick Start translation (as test), but experienced some problems with building pdf. First, the customization layer included in susedoc works currently for XEP only, not FOP. That's a pity, but when my time permits I will make it more compatible with FOP. [...] Building using xep went almost smoothly but xep is unacceptable due to license issues. Yeah, that's pity. Did you know that RenderX offers also a Personal edition? As far as I know, it contains a stamp on each page and it's free for noncommercial personal use. http://www.renderx.net/Content/download/getbuy.cgi (Use Personal, *not* Trial) This might not solve the licensing issue but be useful for the time being until our stylesheets are ready for FOP. Fop couldn't find necessary fonts: [ERROR] unknown font ZapfDingbats,italic,normal so defaulted font to any [ERROR] unknown font sansserif,normal,bold so defaulted font to any It's mainly a (font) configuration issue from XEP. Complete log: http://svn.team.org.ru:8000/trac/browser/test/build.log (some other annoying errors there). The errors come from unsupported attributes in FOP. There is one issue that is related to our stylesheets: At the moment we don't support Russian localization but we will include it in the near future. If you want, you can translate the English text under /usr/share/susedoc/xslt/common/l10n/en.xml and send it directly to me. I can include it in the next update of susedoc. At least this error will disappear. :) Finally, I want to ask about legality of such stuff. Doesn't it violate in any way licences if we leave all the copyrights and trademarks in our translations? Andreas covered that already. :) Hope that helps, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-doc] New version of susedoc -- Please update
Hi, there is a new version of our susedoc RPM packages. I would encourage you to install it and test it. Major improvements are mainly under the hat but to name a few: * Separated layout from ENV file * Get rid of unnecessary environment variables * Fallback behavior for missing profiling stylesheets fixed * Profiling is done only when it is necessary * Several improvements for our internal stylesheets of creating openSUSE manuals (see xslt/ChangeLog for details) * Improved CSS handling * Support for multiple entity files 1. Installation and Update Please update the susedoc RPM with your favorite installation tool (YaST, smart, rug, ...). In case you use YaST and haven't added the respective repository, read [1] to add it. If you want to download the RPM package manually, find it under [2]. Choose your distribution and select noarch. Look for susedoc-4.2_*.noarch.rpm. 2. Future Changes in ENV and Makefile The new susedoc RPM package introduces also a new, cleaner design of building our books. It affects mainly the ENV and Makefile. For the time being we support both ways, but in the future the old method will not be available anymore. Therefor we will adapat the ENV and Makefile in the future to reflect these changes. Please report any errors or other strange issues. (The openSUSE Build Server is building the packages at the moment. It takes some time. Stay tuned. ;) ) Have fun! Tom [1] http://developer.novell.com/wiki/index.php/Lfl/Lessons_for_Lizards_Quick_Start#Getting_and_Installing_the_Software [2] http://software.opensuse.org/download/home:/thomas-schraitle/ -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Good News: new VirtualBox setup article for openSUSE project (LfL)
Hi Alexey, On Dienstag, 13. Februar 2007, Alexey Eremenko wrote: I have decided that this is good time for a new article to come into SUSE documentation (Lessons for Lizards), that aims to integrate better between the two products and communities. That's great! This article introduces VirtualBox to SUSErs (SUSE users) and explains step-by-step how-to install this product on openSUSE, how to run and troubleshoot and where to get help. VirtualBox is a full x86 virtualizer, like VMware, to me it's revolutionary, because it's the world's first user-friendly open-source solution in this class. I believe that people, who use VMware or VirtualPC should try this. Yes, it's very promising. I tried it over the weekend, but had only two problems: My DVD drive wasn't recognised so I had to create an ISO image to boot. The second issue had something to do with fullscreen. After I switched to fullscreen mode I couldn't go back. That was strange, but maybe it was my fault. [...] Hope it will help people getting started. What do you think of it? Great lesson! I thought of an article about VirtualBox too, but you was faster than me. :) I have only some suggestions for you, mainly technical stuff. Hope you find it useful: 1. I would replace the content of the two screen elements with an itemizedlist element. It seems to me this has nothing to do with computer generated input or output, isn't it? :) 2. A minor issue: What do you think about putting your terminology into a variablelist? 3. Mark up in section Procedure, step 2 the text ~/vm with filename~/vm/filename 4. Also a minor issue: I would recommend to mark up menu items with menuchoice like this (see section Procedure, step 3): menuchoice guimenuSecurity and Users/guimenu guimenuGroup Management/guimenu guimenuvboxusers/guimenu /menuchoice 5. More important: If you have a warning for your readers, use the element warning. The stylesheets render this with or without nice little graphics, depending on the setup (see section Procedure, step 3): warning titleBe Careful With Your Setup/title!-- Optional title -- paraThis step is critical, one mistake and VirtualBox will not work !/para /warning 6. If you have a solution to the fullscreen problem above, maybe you can add it to your Troubleshooting and Tips section. :) 7. Someone created RPM packages[1] of VirtualBox. What do you think of inserting this information into your article too? Thanks Alexey! If something is unclear from my list, don't hesitate to ask again. I hope Frank or I can synchronise the new book today, available on the usual URL[2]. Bye, Tom [1] http://software.opensuse.org/download/virtualization/ [2] http://forgeftp.novell.com/lfl/.html/ -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] How about including some books with openSUSE ?
Hi, On Thursday 25 January 2007 06:26, Rajko M. wrote: On Wednesday 24 January 2007 13:43, Alexey Eremenko wrote: hi Susers ! There are some great free books lying around, included with some OSS distributions: Those are technical books, such as Rute Linux tutorial, and philosophical books such as The cathedral and the bazaar. I think it would be smart to include those two as RPMs in main repository. (or on the media itself) What do you think? -Alexey Eremenko. It would be good idea. Yes, that's a good idea. You can find already three packages (OpenOffice Essential, Producing OSS, RELAX NG) in my repository: http://software.opensuse.org/download/home:/thomas-schraitle/openSUSE_10.2/repodata/repoview/Documentation.Other.group.html Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Please include contributors page with LFL
Hi, On Monday 15 January 2007 08:38, Rebecca Walter wrote: [...] http://developer.novell.com/wiki/index.php/Lfl/Statistics I know, only users are listed with commit rights. I think he means an authors list in the book. Would that be possible? Sure. :) If you think this is useful, go ahead. :-) Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Please include contributors page with LFL
Hi Alexey, On Saturday 13 January 2007 04:17, Alexey Eremenko wrote: Please include Contributors page with Lessons for Lizards. Do you want me to create one? What do you think of the Statistics page? There is a list of users who contributed: http://developer.novell.com/wiki/index.php/Lfl/Statistics I know, only users are listed with commit rights. Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Information re 10.2 files needed
Hi, On Friday 05 January 2007 20:20, Dennis J. Tuchler wrote: I just received my boxed set of 10.2 (ordered at the end of last week! what service!) with which came a start-up manual with references in it to a more detailed work (e.g. Chapter 36, Wireless Communication) Where is this document stored after installation? See file:///usr/share/doc/manual/opensuse-manual_en/manual/cha.wireless.html (package opensuse-manual_en) Bye, Tom -- -- SUSE LINUX Products GmbH o) Documentation Team Maxfeldstrasse 5 /\\ Technical Editor 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL: HTML Version Available
Hi, On Saturday 30 December 2006 19:42, jdd wrote: [...] I don't know how wikibooks handle the thing: http://en.wikibooks.org/wiki/Main_Page From my perspective, the problems are still the same, be it with Wiki or with DocBook XML. again, not about writing the core text, but about interaction with the reader. Ok, jdd, what do you think about this page: http://developer.novell.com/wiki/index.php/Lfl/Feedback With this page everybody can leave comments, wishes or general feedback. It's even linked from the main page. :) [...Similar LDP problems...] the problem is similar, there are no really satisfactory solution. Right. Of course, we all would like to see people contributing with text, corrections, etc. in DocBook-XML but I fear that's a bit unrealistic for simple typos. It's seems that we don't solve the problem this year. If nobody has a good solution I fear we will have to live with that, at least for the moment. using this very mailing-list and eventually a wiki page is pretty good :-) Yes, see the above page. happy new year, it's very late to work :-)) jdd Yes, very true. Happy new year! :-)) Bye, Tom -- -- SUSE LINUX Products GmbH o) Documentation Team Maxfeldstrasse 5 /\\ Technical Editor 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-doc] LfL: HTML Version Available
Hi, as the subject says: There is now a HTML version of Lessons for Lizards available: http://forgeftp.novell.com/lfl/.html/ I don't consider the contents nor the layout as finished. See the Jobs description page how *you* can contribute: http://developer.novell.com/wiki/index.php/Lfl/Jobs Have fun and happy new year, :-) Tom -- -- SUSE LINUX Products GmbH o) Documentation Team Maxfeldstrasse 5 /\\ Technical Editor 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL RFC
Hi Alexey, On Thursday 21 December 2006 15:54, Alexey Eremenko wrote: [...] Unfortunately I dunno how-to open this format. It seems OO2 can't open that. How do you open it? Any texteditor wil do: Emacs, vi, Kate..whatever you want! yes, but text-editor opens that without formatting it properly. It's like opening HTML with text-editor. Is there any software that opens it correctly ? (need user-friendly editor) Well, there is Emacs but some people don't like it. ;) Apart from Emacs there is also jEdit. I think I saw a XML plugin that can use DTDs too (I have to look at it first.) KDE's Kate is also a good editor although it might not be the primary target for XML. It can use a precompiled kind-of DocBook DTD. See here more details: http://wiki.docbook.org/topic/DocBookAuthoringTools Best wishes, Tom -- -- SUSE LINUX Products GmbH o) Documentation Team Maxfeldstrasse 5 /\\ Technical Editor 90409 Nuernberg, Germany _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] LfL RFC
Hi Alexey, On Wednesday 20 December 2006 17:03, Alexey Eremenko wrote: On 12/20/06, Rebecca Walter [EMAIL PROTECTED] wrote: [...] In order to comment, I need to see your docs. Plz give me link. The DocBook XML source is here: https://forgesvn1.novell.com/svn/lfl/trunk/books/en/xml/homenetwork.xml Bye, Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: [opensuse-announce] openSUSE 10.2 is done
Hi, On Thursday 07 December 2006 16:56, Stelian Iancu wrote: On Thursday 07 December 2006 16:51, Geir A. Myrestrand wrote: I miss the printed Admin guide too, although my PDF collection of books is probably 100 times bigger than my collection of printed books... By the way, do you know of any print-at-request web site (preferably in Germany or Switzerland) that will let you upload a PDF and will send you a printed book? [...] Maybe the following is useful for you: http://www.bod.de Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: [opensuse-announce] openSUSE 10.2 is done
Hi, On Thursday 07 December 2006 18:00, jdd wrote: Lake-Wind a écrit : I feel that Novell should publish the manual and sell it separately, we could enphasize on the fact that the admin manual can be largely disconnected from the distribution itself. I still use the 9.0 I have just on the shelf behind me. I mean, Novell don't have to make a new manual for each distro, may be just an addon to make print cheaper :-) Actually we did this some time ago, if I remember correctly. We had the Update Manual. It was mainly a collection of changes and additions not an addon as you think of. However, don't underestimate the amount of work just to create this piece. :) By the way: If everbody seem to be interested in documentation we have also the mailinglist opensuse-doc@opensuse.org for this purpose. :) Tom -- Thomas Schraitle -- SUSE LINUX GmbH o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: [suse-beta-e] openSUSE user documentation
Hi Anders, On Monday 29 May 2006 10:51, Anders Norrbring wrote: Thanks Adrian, This message is sent to opensuse-doc@opensuse.org as well, I'll continue to search Google to see if I can find something useful. Anders. Adrian Schröter skrev: Am Monday 29 May 2006 10:03 schrieb Anders Norrbring: I'm looking at posting a how-to at opensuse.org, but I'm kindof confused by the site.. I can't find any way to upload my DocBook XML files, just a web based section editing function.. Do I have to copy-and-paste all of it into that web based editor? Or can I somehow use my XML files? The wiki remains to be a wiki ;) But we did plan to support also handbook style writings via doc.opensuse.org. You should get in contact via our doc writers, via opensuse-doc@opensuse.org bye adrian Currently, we have similiar problems with our docs. I developed XSLT stylesheets to transform Novdoc or DocBook XML into Wiki syntax. Check it out from [1]. It's in a preliminary alpha state, but it creates more or less useful outputs. Maybe the output must be manually corrected. And of course, not all elements are supported. You transform your XML document into wiki with: xsltproc --output DOC.wiki db2mediawiki/docbook.xsl DOC.xml You should keep in mind that transforming your rich marked up DocBook document into Wiki syntax is semantic degradation: It's always possible to transform from DocBook into Wiki but not back. :) Hope this helps, Tom --- [1] https://forgesvn1.novell.com/svn/novdoc/trunk/xslt/db2mediawiki -- Thomas Schraitle -- SUSE LINUX Products GmbH o)Technical Editor Maxfeldstrasse 5 /\\Documentation Team 90409 Nuernberg, Germany_\_vhttp://www.suse.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] Re: [suse-beta-e] openSUSE user documentation
Hi Anders, On Monday 29 May 2006 12:54, Anders Norrbring wrote: Thomas Schraitle skrev: [...] Replace the CHAPTER_ID with the id of your corresponding chapter. Roughly speaking lists, figures and some inline elements should be supported, probably not all DocBook features. If the stylesheets encounter an unknown element it will print the above message to inform the user. I'll give it another shot.. I prefer working in oXygen on my Windows box, but I'll do some testing on both platforms. Sure. It's very handy to create a transformation scenario with oXygen but you need to connect the XSLT stylesheet with the XML file. I'll send you the pack of xml files for inspection, they're currently drafts since most id elements are missing. But I thought maybe you can find the time to give some pointers? That would be very helpful. I am not sure if I find time today but I will look at it as time permits. Thanks, Tom -- Thomas Schraitle -- SUSE LINUX Products GmbH o)Technical Editor Maxfeldstrasse 5 /\\Documentation Team 90409 Nuernberg, Germany_\_vhttp://www.opensuse.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-doc] merging community Novell docs tutorials
Hi, On Tuesday 09 May 2006 18:58, jdd wrote: Thomas Schraitle wrote: Thanks! I tried it with the documentation page of the openSUSE wiki. But ... the problem is still the same. :-( It is just a nice wrapper around the original text filled with some metainformation. No semantics. what I said is that xml is nor the problem nor the solution. nowaday anybody do xml. however xml is a very good thing as langage is :-) Ok, I see your point. However to make it clearer: XML becomes only useful, if the *contents* in your document are also marked up reasonably. We have an XSLT stylesheet that prints out all links. With another script it checks if these links are still accessible. So it's a kind of qualitfy check. It would be not possible, if we (as writers) don't markup it accordingly. And this is the crucial point: XML is (only?) useful, if you investigate some time in your markup. To write documents in XML can be sometimes awkward for unexperienced users. But if you get used to it it is pretty easy. ;) [...] on the contrary it's easy to go from any docbook/novbook/ structured form to html. The result will certainly lose part of the markup though. Yes, that's the nature of this approach. :) anyway, all this is _text_ and scripts can be made like sgmltools and linuxdoc to have some kind of compatibility. Yes, it is text but without /meaningful/ semantics. It is nearly impossible to convert some plain text into some meaningful DocBook XML document automatically. (Ok, with some fancy regex hackery you *could* try to find URLs in your text and convert them to ulinks. But the problem still persists.) The truth is that we badly need a wysiwyg xml editor. there are some, but none really satisfactory (neither emacs), so write one should be really a good thing, even for a single dtd Look at [1]. There are lots of good XML editors -- either commercial or free. Tom - [1] http://wiki.docbook.org/topic/DocBookAuthoringTools -- Thomas Schraitle -- SUSE LINUX Products GmbH o)Technical Editor Maxfeldstrasse 5 /\\Documentation Team 90409 Nuernberg, Germany_\_vhttp://www.suse.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Eval version of Suse Linux 10.0
Hi, On Tuesday, 11. October 2005 09:59, Marcel Hilzinger wrote: [...] With this new manual, that's true. I'have never seen so much bugs in the german manual. Was it partly translated in the USA?? No, in Dublin. We switched from German to English, so the original German text is not under our control anymore. If you want to discuss things around documenation, I would like to suggest to go to the opensuse-doc mailinglist. :) Tom -- Thomas Schraitle -- SUSE LINUX Products GmbH o)Technical Editor Maxfeldstrasse 5 /\\Documentation Team 90409 Nuernberg, Germany_\_vhttp://www.suse.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
