October 2010 - openSUSE Documentation - openSUSE Mailing Lists

[opensuse-doc] questions for susedoc (Japanese fonts in susedoc)
by Yasuhiko Kamata 13 Dec '10

13 Dec '10

Hello all, We're now trying to translate the opensuse_manual to Japanese in beriOS.de (http://developer.berlios.de/projects/opensuse-man-ja/) This translation effort is about 25 percent completed. So I've planned to generate a PDF file from them. Before making, I've modified /usr/share/susedoc/xslt/common/l10n/ja.xml as follows for IPA fonts.  <l:gentext key="fop1.body.font.family" text="IPAPMincho,FreeSerif"/> <l:gentext key="fop1.sans.font.family" text="IPAPGothic,FreeSans"/> <l:gentext key="fop1.monospace.font.family" text="IPAGothic,FreeMono"/> <l:gentext key="fop1.symbol.font.family" text="IPAPGothic,Symbol"/> <l:gentext key="fop1.callout.unicode.font" text="IPAPGothic"/> ("fop1.pocket.*", "xep.*", and "xep.pocket.*" was also modified like above) After modification, run as follows. $ cd trunk/opensuse-html $ source ENV-opensuse-html $ make validate $ make pdf Validation (make validate) and PDF creation (make pdf) finished with no error. But some sorts of tagged texts in PDF were displayed with blank. These are "guimenu", "replaceable", and "xref" (referenced text). In addition, some characters of these texts can be displayed normally if the character is ASCII (alphabets, numbers, etc.). So I think this problem was caused by some font setting. However, no font settings seems to be exist in susedoc except above. How do I fix it? Cheers, -- Yasuhiko Kamata E-mail: belphegor(a)belbel.or.jp -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

4 11

[opensuse-doc] doc.opensuse.org title
by Manu Gupta 26 Oct '10

26 Oct '10

Hi all doc.opensuse.org still remains rtfm.opensuse.org at the website please correct that Regards Manu -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 3

[opensuse-doc] [ANN] Documentation Sources Going Public (opensuse-doc)
by Thomas Schraitle 24 Oct '10

24 Oct '10

Hi, after some blood, sweat, and tears (actually it was only the middle, but hey, that statement sounds more dramatic! ;) our documentation sources are publicly available on BerliOS! :-) The opensuse-doc project[1] contains now all the sources for openSUSE including our business products released under the GFDL. It's possible to anonymously check it out; go to the SVN page[2] on our project page for more details. Alternativly, for a more visually attractive version of our SVN, use the WebSVN page[3]. The opensuse-doc SVN is the result of the merge of three different, independant SVN repositories. It has been merged before and during the openSUSE conference. 1. Want to contribute? Find more information in the openSUSE Wiki[4]. We are happy to discuss your contributions on our opensuse-doc mailinglist. 2. Want to know more about us? Find our team page on the openSUSE Wiki[5]. 3. Want an overview about what's inside our SVN? Find more information about our SVN structure here[6] There will be some fine tuning over the week -- expect still some changes, but not dramatically. Hope you like it! :) Tom ----- References: [1] http://developer.berlios.de/projects/opensuse-doc/ [2] http://developer.berlios.de/svn/?group_id=11522 [3] http://svn.berlios.de/wsvn/opensuse-doc/trunk/ [4] http://en.opensuse.org/openSUSE:Documentation_Contribute [5] http://en.opensuse.org/openSUSE:Documentation_team [6] http://en.opensuse.org/openSUSE:Documentation_Contribute#SVN_Structure -- 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+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

1 0

[opensuse-doc] New (i hope so) Member of the Team
by Sascha 'saigkill' Manns 24 Oct '10

24 Oct '10

Hi Mates, as i talked with Jürgen Weigert and Thomas Schraitle i have interest to join the Team. I know the new Place of the Sources in Berlios, and i can use Serna and XML Mind (depends on that what i would like to do) and now the process to create the needed Output. So if you're meaning, that i can help out, just drop me a note :-) -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) Open-SLX : Linux convenient, simple, secure and complete

2 1

[opensuse-doc] Re: [opensuse-project] How to contribute: openSUSE Documentation
by Juergen Weigert 20 Oct '10

20 Oct '10

On Oct 18, 10 18:00:39 +0200, Freek de Kruijf wrote: > Op maandag 18 oktober 2010 17:07:47 schreef Juergen Weigert: > > This information should be in the wiki in separate pages, but with links to it > from Portal:Documentation and Portal:How_to_participate and Portal:Teams Right you are! Thanks for those pointers. I've taken the liberty and added my team to the portals. (And chopped the contents into 3 parts.) cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw(a)suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "You are trying to use packages from project 'openSUSE:11.3'. Note that malicious packages can compromise your system." -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 1

[opensuse-doc] How to contribute: openSUSE Documentation
by Juergen Weigert 18 Oct '10

18 Oct '10

Hi there! Last week a discussion started on opensuse-marketing about creating an openSUSE manual: http://lists.opensuse.org/opensuse-marketing/2010-09/msg00259.html While this is a cool idea, it turned out that many people are unaware of the existing openSUSE documentation or do not know how to contribute. Being responsible for the openSUSE documentation, I would like to shine a light on this ;-) : Table of contents (beware, lengthy posting): 1. Contributing 1.1 Getting in touch with the SUSE Documentation Team 1.2 Reporting Documentation Bugs or Suggesting Adjustments 1.3 Translating Manuals 1.4 Contributing new Chapters or Books 1.5 Contributing to the Build Environment (susedoc) 2. Outlook: What's in the Pipeline 2.1 Publishing the Book Sources 2.2 Re-writing the Build Environment 2.3 openSUSE BookBuilder 3. List of openSUSE Manuals ################### # 1. Contributing # ################### Currently the openSUSE documentation (listed below under 3.) is maintained mostly within Novell by the SUSE Documentation Team (http://en.opensuse.org/openSUSE:Documentation_team) The discussion on opensuse-marketing has shown that people are interested in contributing to this documentation--a fact that we really welcome! Our manuals are written in NovDoc XML, a simplified subset of DocBook (http://www.docbook.org/) The XML sources for the manuals are hosted on an SVN server. Generating books from the XML sources is done with the susedoc build environment, which is developed and maintained by the team as well. This build environment includes _everything_ to build books from DocBook or NovDoc and is shipped with openSUSE (package: susedoc, license: GPL). You may also want to point us to ommissions, corrections, or even to ready articles (wiki, txt, pdf, whatever) that could be merged or referenced. Let us not get into a struggle about correct or wrong tools. I really like the original idea of creating a commuity driven openSUSE book. We are already looking into ways how to interconnect wiki and/or openoffice with docbook. Ideas welcome! 1.1 Getting in touch with the SUSE Documentation Team ----------------------------------------------------- Reaching out to us is pretty easy - either subscribe to the opensuse-doc mailinglist (http://en.opensuse.org/Mailing_lists#Subscribing) or join the #opensuse-doc IRC channel on freenode. If you have typos, questions, suggestions or simply want to say hello, these are the places to go. You can also meet us in person at the openSUSE conference in Nuremberg this week. There will be a talk about one of our latest doc projects, the openSUSE Book Builder (see 2.3 below or refer to http://conference.opensuse.org/indico//contributionDisplay.py?contribId=71&…) We would be glad to see you there! 1.2 Reporting Documentation Bugs or Suggesting Adjustments ---------------------------------------------------------- Currently, two feedback channels are available if you have corrections or enhancements for us: - File a bug report (or an enhancement request) against the Documentation component for the respective product. Or, much easier: - Use the doc comment system: Go to http://www.novell.com/documentation/opensuse113/ where the openSUSE 11.3 documentation is hosted. Click on a manual title and navigate to the page where you have spotted an error/would like to suggest adjustments. Scroll to the bottom of that page and click on "Add comment". Insert your comment. If you are interested in getting feedback, provide your name and email address. Your comment is directly routed to our team, so we can take care of it. 1.3 Translating Manuals ----------------------- If you are interested in translating our manuals, we can provide the necessary infrastructure for you. Currently the Russian translation team already uses our SVN repository on berliOS to translate the openSUSE 11.3 manuals. 1.4 Contributing new Chapters or Books -------------------------------------- If you would like to contribute larger amounts of contents (chapters, sections, etc.), please get in touch with us (see above), and let us know what you like to contribute. Don't worry, you _DON'T_ have to know XML, susedoc, or the likes - that is something we can take care of ;-). 1.5 Contributing to the Build Environment (susedoc) --------------------------------------------------- susedoc is publicly hosted at https://developer.berlios.de/projects/opensuse-docmaker/ and can be checked out anonymously. Patches are welcome! If you are interested in contributing more than an occasional patch, you can get full access to the project. ###################################### # 2. Outlook: What's in the Pipeline # ###################################### The SUSE documentation has a few more projects in the pipeline. First and foremost we are working on making it easier for you to contribute. Second we have have planned two major software projects. 2.1 Publishing the Book Sources ------------------------------- The XML sources for our manuals are hosted on a Novell internal SVN server. We are currently in the process of moving them to a public SVN at berliOS, where they will be available for anonymous checkout. Document maintainers will get write access. As a first step, the SUSE Studio documentation and the openSUSE Documentation Style Guide are hosted at https://developer.berlios.de/projects/opensuse-doc/ More is to come very soon. We can also provide an infrastructure for manual translations on that server - in fact our Russian translators already make use of it. 2.2 Re-writing the Build Environment ------------------------------------ Our build environment (susedoc) currently is a mixture of tools using make, bash, python and perl. Although this tool collections works very well, we would like to consolidate it in order to make future enhancements easier. We have started to write a central docmaker library in perl and python which should provide everything that is needed to manage, monitor and build books from XML sources. Development of this library is in a very early state - if you are interested in helping us to develop it, get in contact with us. The sources are available from http://svn.berlios.de/wsvn/opensuse-docmaker/trunk/lib/ 2.3 openSUSE BookBuilder ------------------------ In short, the openSUSE BookBuilder is a library utilizing susedoc to automatically build books from XML sources. Added is a web application that serves as a virtual library. See http://conference.opensuse.org/indico//contributionDisplay.py?contribId=71&… for a more detailed description. If you are interested in that project, come to the talk at the openSUSE conference or contact me directly. ############################### # 3. List of openSUSE Manuals # ############################### openSUSE comes with with a lot of manuals in HTML and PDF format with a current page count of almost 2000 pages. Not all of them are shipped in the box. The HTML version of all manuals can be installed with the package opensuse-manuals_en. http://en.opensuse.org/openSUSE:Documentation_team#List_of_Manuals http://en.opensuse.org/SDB:Official_documentation ePUB versions can be downloaded from http://community.opensuse.org/ebooks/ebooks113/ 3.1 Startup Guide ----------------- Guides you through the installation and basic configuration of your system. For newcomers, the manual also introduces basic Linux concepts such as the file system, the user concept and access permissions and gives an overview of the features openSUSE offers to support mobile computing. Provides help and advice in troubleshooting. The Startup Guide is ca. 200 pages and is found in the openSUSE box. 3.2 Reference Guide ------------------- Gives you a general understanding of openSUSE and covers advanced system administration tasks. It is intended mainly for system administrators and home users with basic system administration knowledge. It provides detailed information about advanced deployment scenarios, administration of your system, the interaction of key system components and the set-up of various network and file services openSUSE offers. 3.3 GNOME User Guide -------------------- Introduces the GNOME desktop of openSUSE. It guides you through using and configuring the desktop and helps you perform key tasks. It is intended mainly for end users who want to make efficient use of GNOME desktop as their default desktop. 3.4 GNOME Quick Start --------------------- Gives a short introduction to the GNOME desktop and some key applications running on it. 3.5 KDE User Guide ------------------ Introduces the KDE desktop of openSUSE. It guides you through using and configuring the desktop and helps you perform key tasks. It is intended mainly for users who want to make efficient use of KDE as their default desktop. 3.6 KDE Quick Start ------------------- Gives a short introduction to the KDE desktop and some key applications running on it. 3.7 Application Guide --------------------- Learn how to use and configure key desktop applications on openSUSE. This guide introduces browsers and e-mail clients as well as office applications and collaboration tools. It also covers graphics and multimedia applications. 3.8 Security Guide ------------------ Introduces basic concepts of system security, covering both local and network security aspects. Shows how to make use of the product inherent security software like AppArmor (which lets you specify per program which files the program may read, write, and execute) or the auditing system that reliably collects information about any security-relevant events. 3.9 Installation Quick Start ---------------------------- Lists the system requirements and guides you step-by-step through the installation of openSUSE from DVD. 3.10 AppArmor QUick Start ------------------------- Helps you understand the main concepts behind AppArmor. Thanks to Frank, Tanja, Tom for compiling this writeup, (shame on me for messing it up). cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw(a)suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "You are trying to use packages from project 'openSUSE:11.3'. Note that malicious packages can compromise your system." -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 1

[opensuse-doc] FW: [opensuse-marketing] The openSUSE Handbook proposal
by Bryant, Christian 06 Oct '10

06 Oct '10

Think this should actually have been sent to this list :) - Christian Bryant -----Original Message----- From: Bryant, Christian [mailto:CABryant@mednet.ucla.edu] Sent: Wednesday, October 06, 2010 8:57 AM To: opensuse-marketing(a)opensuse.org Cc: 'Klaas Freitag' Subject: RE: [opensuse-marketing] The openSUSE Handbook proposal Just as a proof-of-concept for document writing community success, see http://flossmanuals.net - easy to use, produces nice output, has a great community of contributors. In terms of wiki-to-book, Wikipedia has had that for some time, and there are some nice examples out there: http://en.wikipedia.org/wiki/Help:Books I'm sure there is a way to build on that model for openSUSE. I have both the "good-writer-skill" and "I-like-to-fiddle-with-tools-which-produce-great-outcome", as Klaas puts it. But I also have to recognize which one of these others are as well, as a project manager or in a community leader roll. It's the users that should define what is pursued here, I believe. I think the wiki-to-book functionality should definitely be added to the openSUSE wiki as an option, and if it matured to a point where all the other features discussed in this thread could be produced, then all the better. For now, I am still using Emacs to edit my openSUSE documents - but the older I get, the simpler I like things to be :) I wouldn't turn away from a nice wiki that would squirt out a publish-ready document! Cheers, Christian Bryant >Couldn't we find people for these two groups instead: >- Editors: People who work on content and deliver in which format they ever > want (nearly ;-) to >- Book Builders: People who get the content from the Editors and work on > building a book with the best suited tool for that? >Maybe it makes more sense to devide the "good-writer-skill" from the "I-like- >to-fiddle-with-tools-which-produce-great-outcome" role? >regards, >Klaas IMPORTANT WARNING: This email (and any attachments) is only intended for the use of the person or entity to which it is addressed, and may contain information that is privileged and confidential. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. Unauthorized redisclosure or failure to maintain confidentiality may subject you to federal and state penalties. If you are not the intended recipient, please immediately notify us by return email, and delete this message from your computer. -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-marketing+help(a)opensuse.org IMPORTANT WARNING: This email (and any attachments) is only intended for the use of the person or entity to which it is addressed, and may contain information that is privileged and confidential. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. Unauthorized redisclosure or failure to maintain confidentiality may subject you to federal and state penalties. If you are not the intended recipient, please immediately notify us by return email, and delete this message from your computer. -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

1 0

[opensuse-doc] Re: [opensuse-marketing] The openSUSE Handbook proposal
by Thomas Schraitle 06 Oct '10

06 Oct '10

Hi, (CC'ed opensuse-doc so doc people can read that too.) On Monday 04 October 2010 Christian Boltz wrote: > [...] > > I'm not sure about that. I don't say that it will be very easy, but it > should be possible, and it won't be too hard. You are underestimate the efforts. > 90% of the formatting can be done with plain wikitext, and for the > remaining 10% templates can be used (which can, but don't have to have a > visible effect in the wiki). A "visible" template might be something > like "text printed on screen", an "invisible" template might contain a > keyword for the book index. We use a feature in DocBook/Novdoc what is called "profiling". We label one paragraph for business related products and another one for openSUSE products. When we process the manual, the paragraphs are being "filtered" so only the requested product is visible in the end format. Maybe this belongs to the remaining 10%... > I think we could even develop a "XML skin" for mediawiki so that the > wiki can generate valid docbook/novdoc XML out of wiki pages (with > <para> instead of <p> etc.). > The alternative solution would be to post-process the wikitext or the > HTML to convert it to XML. Depending on the HTML this sounds scaring. > Basically the two methods don't differ too > much, the main difference/question is if you want XML output integrated > in the wiki or not. > > > I would propose XML hosted on SVN. Although the learning curve would > > be a bit stepper than with e.g. wiki markup it would give us the > > maximum flexibilty and a guaranteed future. > > I'm afraid that the learning curve is too high - lessons for lizards > unfortunately gave you/us that lesson... Sorry, but I never understood the "XML is too difficult" rant. People are *not* afraid to learn LaTeX or Wiki, dig into HTML, or even migrate from Windows to Linux because of "the learning curve is too high". Why they are not afraid? Because they are _interested_ and want to _learn_ something new. Why should it be difficult to learn DocBook/Novdoc? It's just a format as HTML, WikiText, ASCIIDoc, or anything else. Maybe it's a bit more verbose, but if you can write HTML and design your webpage, you can also write documentation in DocBook or Novdoc. It's just a matter of your XML editor. Of course, Lessons for Lizards was not as successful as we wished it would be. However, it's a bit too easy to blame only XML for the demise. Maybe it had an effect, maybe not. The biggest problem IMHO was time and marketing. > I don't know if the learning curve was the only problem there, but at > least it's "I have to learn another thing before I can contribute". I'm afraid, I have to disagree here. "To learn another thing before I can contribute" is the case for _every_ open source project. If you want to contribute, you usually use what's there. If you are interested enough then you are willing to take that "extra step". If not, you simply don't contribute. Just think of this example: People were not afraid to learn CVS. After some time, it was more or less replaced by Subversion. Although it was not that different, people were willing to learn the differences. Now it seems Git will be the sucessor for Subversion. And *that* is really different from CVS/Subversion! And what's the opinion? "Git is soo coool!" is what can I heare a lot. ;) > > Whatsmore, the existing documentation (speaking of almost > > 2000 pages!!) already uses XML. > > OK, _that_ is an argument. But as you already wrote, it shouldn't be > hard to convert it to wikitext. Indeed, there are stylesheets (I've wrote it), but I wouldn't want to transform a complete book. The two systems are too different in some aspects. > And it would be a good testbed for the > wikitext to XML converter - ideally there should be no difference after > converting it forth and back again ;-) (and that would make us better > than google translator *g*) > > [...] Let me suggest another idea: In my opinion, most people have problems with XML because it's (a) too verbose, (b) it's too "complicated", and (c) you don't see the result. At least that's what I hear a lot. As most of the functionality thesedays goes through the Web, why not have a XML editor in, let's say, Firefox? Of course, it should offer the usual features but would hide the XML syntax and display just the rendered text. I know, this is day-dreaming and the idea is not new. However, I think, this would lower the entrance. We could use the existing XML source without converting it to Wiki while embracing Web usability. I think, this should solve the above problems. Maybe we could use Bitflux, see http://bitfluxeditor.org/. > [...] > I see the public SVN as a fast solution so that people have a chance to > dig into the manual's source. It might even be read-only in the > beginning - having to upload patches to bugzilla or send them to the > -doc mailinglist is still easier than reporting "on page 123 in section > 'foo', there's a typo in 'baar'". A page number is a bad choice 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,d&r* 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+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

5 5

[opensuse-doc] NovDoc Usage
by Bryant, Christian 01 Oct '10

01 Oct '10

I'm going to be working on some custom appliances using SUSE Studio. I love the susedoc style sheets 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? Thank you. Cheers, Christian Bryant, UCLA Health System Project Manager, IT Operations Medical Information Technology Services (MITS) IMPORTANT WARNING: This email (and any attachments) is only intended for the use of the person or entity to which it is addressed, and may contain information that is privileged and confidential. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. Unauthorized redisclosure or failure to maintain confidentiality may subject you to federal and state penalties. If you are not the intended recipient, please immediately notify us by return email, and delete this message from your computer. -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

3 3