Carlos E. R. wrote:

The Wednesday 2008-02-06 at 08:33 -0500, Aaron Kulkis wrote:

...

...

I want a GUI to write man pages. Rather, to translate them to Spanish, so the choice of using "man" is not mine.

I'm not willing to learn trof/roff whatever. I wish something like openoffice, or at least, LyX.

I have found a program in python, wyneken, that says it can edit/create man pages. I haven't tried it yet. [...]

Hey, when I commented about the great html man pages in tcl/tk distributions, one of the developers commented that they were actually written in a different format, then run through utilities to convert them to html, man, docbook, etc. Why not subscribe to comp.lang.tcl and ask them about it? John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

cannotsorry becausescams pecked at the keyboard and wrote:

Dear opensuse@opensuse.org

please put a stop to these emails i am recieving that are supposed to be going to opensuse@opensuse.org not my email address noscammers@live.com.au have already asked you once and if i get anymore i will be contacting the communications ombudsman there is a mistake on your part deal with now

from retired JP

They ARE from the mailing list YOU subscribed to. The only way to get them to the list is to send them to the list server address which is what you see. If YOU do not want these messages sent to you then YOU need to unsubscribe from the list by sending an email to opensuse+unsubscribe@opensuse.org No one else on the list can/will do it for you. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Wednesday 2008-02-06 at 08:33 -0500, Aaron Kulkis wrote:

...

...

I want a GUI to write man pages. Rather, to translate them to Spanish, so the choice of using "man" is not mine.

I'm not willing to learn trof/roff whatever. I wish something like openoffice, or at least, LyX.

troff/nroff isn't hard to learn.

The simplest thing to do is just copy the source code from another man page or pages, then cut and replace.

I have done that in the past, for small files, but it is tricky for larger ones. I would have thought that after so many thousand years we would have something more... up to the times.

nroff/troff is available on ALL *nix systems, therefore, *roff man-pages are readable on all *nix systems.

I have found a program in python, wyneken, that says it can edit/create man pages. I haven't tried it yet.

Give it a shot.

[...] Does not run. :-(

Oh, that sucks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Wednesday 2008-02-06 at 08:33 -0500, Aaron Kulkis wrote:

...

...

I want a GUI to write man pages. Rather, to translate them to Spanish, so the choice of using "man" is not mine.

I'm not willing to learn trof/roff whatever. I wish something like openoffice, or at least, LyX.

troff/nroff isn't hard to learn.

The simplest thing to do is just copy the source code from another man page or pages, then cut and replace.

I have done that in the past, for small files, but it is tricky for larger ones. I would have thought that after so many thousand years we would have something more... up to the times.

have you read the *roff tutorials? The old Programmer's Workbench (PWB) Unix manuals have them, and I believe the version 7 manuals, too. You want to look in Volume 2. http://wolfram.schneider.org/bsd/7thEdManVol2/ http://wolfram.schneider.org/bsd/7thEdManVol2/trofftut/trofftut.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

hello but sorry to bother you but i have got about 50 emails that are addressed to opensuse@opensuse.org must be some mistake i will not delete anymore as i can see there is a mistake as my email address is noscammers@live.com.au not opensuse@opensuse.org i do not work at opensuse@opensuse.org i only subcribed to you to lear about opensuse ----------------------------------------

From: thomas.schraitle@suse.de To: opensuse@opensuse.org Subject: Re: [opensuse] How can I write man pages? Linuxdoc/Docbook anyone? Date: Wed, 6 Feb 2008 15:20:22 +0100

Hi Carlos,

On Mittwoch 06 Februar 2008, Carlos E. R. wrote:

...

I want a GUI to write man pages. Rather, to translate them to Spanish, so the choice of using "man" is not mine.

I'm not willing to learn trof/roff whatever. I wish something like openoffice, or at least, LyX.

I have tried LyX, with no luck. After exporting to sgml, I can not create the man because it either is not generated, or the converter balks out, or I get absurd errors by the ton I have no idea howto solve:

cer@nimrodel:~/lyx> sgml2txt -man testing_manpage.sgml [... Removed errors... ]

I would consider this process as outdated. The preferred way of getting a manpage is to use the XSLT stylesheets thesedays.

Try to use this:

$ DB=/usr/share/xml/docbook/stylesheet/nwalsh/current/ $ # Maybe skip the following command: $ xmllint --valid --noout testing_manpage.sgml $ xsltproc $DB/manpages/docbook.xsl testing_manpage.sgml

Maybe you have to convert your SGML file into XML first, depends on your file.

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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

_________________________________________________________________ What are you waiting for? Join Lavalife FREE http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30288&_t=764581033&_r=email_taglines_Join_free_OCT07&_m=EXT-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-02-06 at 15:20 +0100, Thomas Schraitle wrote:

...

cer@nimrodel:~/lyx> sgml2txt -man testing_manpage.sgml [... Removed errors... ]

I would consider this process as outdated. The preferred way of getting a manpage is to use the XSLT stylesheets thesedays.

I tried that because that is what I found googling. If you know of a document explaining how to create a manpage with LyX, I'd appreciate it.

Try to use this:

$ DB=/usr/share/xml/docbook/stylesheet/nwalsh/current/ $ # Maybe skip the following command: $ xmllint --valid --noout testing_manpage.sgml $ xsltproc $DB/manpages/docbook.xsl testing_manpage.sgml

cer@nimrodel:~/lyx> DB=/usr/share/xml/docbook/stylesheet/nwalsh/current/ cer@nimrodel:~/lyx> xmllint --valid --noout testing_manpage.sgml testing_manpage.sgml:2: parser error : SystemLiteral " or ' expected [ <!ENTITY % output.print.png "IGNORE"> ^ testing_manpage.sgml:2: parser error : SYSTEM or PUBLIC, the URI is missing [ <!ENTITY % output.print.png "IGNORE"> ^ cer@nimrodel:~/lyx> xsltproc $DB/manpages/docbook.xsl testing_manpage.sgml testing_manpage.sgml:2: parser error : SystemLiteral " or ' expected [ <!ENTITY % output.print.png "IGNORE"> ^ testing_manpage.sgml:2: parser error : SYSTEM or PUBLIC, the URI is missing [ <!ENTITY % output.print.png "IGNORE"> ^ unable to parse testing_manpage.sgml

Maybe you have to convert your SGML file into XML first, depends on your file.

Lyx can generate docbook as sgml or xml. But the error is similar :-( cer@nimrodel:~/lyx> xmllint --valid --noout testing_manpage.xml testing_manpage.xml:6: element book: validity error : No declaration for attribute title of element book <book lang="en_US" title="LyX" sectnum="1"> ^ testing_manpage.xml:6: element book: validity error : No declaration for attribute sectnum of element book <book lang="en_US" title="LyX" sectnum="1"> ^ testing_manpage.xml:19: element book: validity error : Element book content does not follow the DTD, expecting ((title , subtitle? , titleabbrev?)? , bookinfo? , (dedication | toc | lot | glossary | bibliography | preface | chapter | reference | part | article | appendix | index | setindex | colophon)*), got (sect1 sect1 sect1 sect1) table file name. </para></listitem></varlistentry></variablelist></sect1></book> ^ cer@nimrodel:~/lyx> xsltproc $DB/manpages/docbook.xsl testing_manpage.xml Erro: no refentry: No refentry elements found in "Title". Title I change the .lyx, retry cer@nimrodel:~/lyx> xsltproc $DB/manpages/docbook.xsl testing_manpage.xml Erro: no refentry: No refentry elements found in "lyx - A Docume lyx - A Document Processor No use. :-( - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHqdjNtTMYHG2NR9URAhzNAJ9XfWN1tVvE1uKtW2SH8Ohd/2mSWQCdHqkI 5JKM8VAj3OfIPxXWRGzkx5c= =y1dy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-02-07 at 08:00 +0100, Thomas Schraitle wrote: ...

Well, as I wrote, you have to convert your SGML file into XML first,

I did. I said I did. I'm doing the test both with XML and SGML, and both fail. Look again: cer@nimrodel:~/lyx> file testing_manpage.xml testing_manpage.xml: XML <======= cer@nimrodel:~/lyx> DB=/usr/share/xml/docbook/stylesheet/nwalsh/current/ cer@nimrodel:~/lyx> xsltproc $DB/manpages/docbook.xsl testing_manpage.xml Erro: no refentry: No refentry elements found in "lyx - A Docume lyx - A Document Processor cer@nimrodel:~/lyx>

otherwise the method doesn't work. You can install the "opensp" package and run the osx command (or sgml2xml). This should convert your DocBook SGML file into DocBook XML. Well, at least in theory, I didn't try it. ;)

SGML is still in use, but new methods and tools are implemented mostly for XML, not SGML. I tried LyX some year ago, so I can't say for sure. However, in my perspective, I would better recommend a "real" *XML editor*, like Emacs, jEdit, ...

Never. The whole point is to produce the output not having to look at a single line of "code". XML is like code to me. That would be as bad as learning troff and generating the man page there. I want a GUI to translate man pages to Spanish: I'm not the coder, just the translator. And I want to avoid working with text looking like code. I would use OpenOffice if I could. I want to mark something as "tittle" and see it display in bold. Not to write <bold> and having to decipher what it means. That's fine for you coders, but not for plain people. :-P

Show us the code, please! :)

Ok, I redid the man to a few lines. The file converts in LyX perfectly to a .dvi or .ps (not pdf(latex)), but the xml is bad - and I have tried many combinations. Remember I know nothing about latex, sgml, xml, or even trof. Here goes the LyX text: +++ #LyX 1.5.1 created this file. For more info see http://www.lyx.org/ \lyxformat 276 \begin_document \begin_header \textclass docbook-book \options title="LyX" sectnum="1" \language english \inputencoding default \font_roman default \font_sans default \font_typewriter default \font_default_family default \font_sc false \font_osf false \font_sf_scale 100 \font_tt_scale 100 \graphics default \paperfontsize 10 \spacing single \papersize default \use_geometry false \use_amsmath 1 \use_esint 0 \cite_engine basic \use_bibtopic false \paperorientation portrait \secnumdepth -1 \tocdepth -1 \paragraph_separation indent \defskip medskip \quotes_language english \papercolumns 1 \papersides 1 \paperpagestyle default \tracking_changes false \output_changes false \author "" \end_header \begin_body \begin_layout Section Name \end_layout \begin_layout Standard manu - A man page test \end_layout \begin_layout Section Synopsis \end_layout \begin_layout Standard manu [ command-line switches] [name.lyx ... ] \end_layout \begin_layout Section Description \end_layout \begin_layout Standard \emph on manu \emph default is too simple to write about. \end_layout \begin_layout Section Options \end_layout \begin_layout Standard \emph on manu \emph default supports the following command-line switches: \end_layout \begin_layout Description - -help summarizes manu usage \end_layout \end_body \end_document ++- And converted by LyX to XML: +++ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <!-- XML file was created by LyX 1.5.1 See http://www.lyx.org/ for more information --> <book lang="en_US" title="LyX" sectnum="1"> <sect1> <title>Name</title> <para>manu - A man page test</para></sect1><sect1> <title>Synopsis</title> <para>manu [ command-line switches] [name.lyx ... ] </para></sect1><sect1> <title>Description</title> <para><emphasis>manu</emphasis> is too simple to write about.</para></sect1><sect1> <title>Options</title> <para><emphasis>manu </emphasis>supports the following command-line switches: </para><variablelist> <varlistentry><term>-help</term><listitem><para>summarizes manu usage</para></listitem></varlistentry></variablelist></sect1></book> ++- The original LyX example I used was named "linuxdoc_manpage.lyx" (came with lyx-1.3.4). There is no such example in current LyX. #LyX 1.3 created this file. For more info see http://www.lyx.org/ \lyxformat 221 \textclass manpage \options title="LyX" sectnum="1" ... And the first problem is that class "manpage" does not exists, so I had to tell it to use "textclass docbook" instead, which I don't know if it is correct, nor do I know if the resulting layout is correct. I have no howto, book, guide, whatever, to guide me. I'm going blind. And believe me, I googled. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHqvAmtTMYHG2NR9URAtR7AJ9iBAX3rsRb+HCJVBTnlVywIVbGKgCfbwde Cmn6dwNNrM2IpiFhrJI1/Ik= =sAOC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 06 February 2008 9:23:28 pm Dog Walker wrote:

Have you seen this: http://wolfpack.twu.net/ManEdit/

That's an outdated page -- this is the most current, I think: http://www.battlefieldlinux.com/wolfpack/ManEdit/ (at least according to Freshmeat...) I wrote an article on using ManEdit a long time ago, it's pretty easy to use. (http://www.unixreview.com/documents/s=9513/ur0501k/ur0501k.html) It's very old -- still uses GTK 1.2.10 according to the page. However, the SUSE RPM did install and run OK just now for me on 10.3, so maybe it'll still do the job. Maybe someone will pick it up and run with the program, since it doesn't seem to be actively developed anymore. Best, Zonker -- Joe 'Zonker' Brockmeier openSUSE Community Manager jzb@zonker.net | zonker@opensuse.org http://zonker.opensuse.org/ | http://www.dissociatedpress.net/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, Feb 7, 2008 at 10:45 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:

I compiled, run it, create a sample page in a minute. ¡YEPEEE! :-))

That's great!

Thankyou both :-)

...

Maybe someone will pick it up and run with the program, since it doesn't seem to be actively developed anymore.

Yes, it is mantained - see changelog:

Oh, oops. I'm happy I'm wrong there, then. Good luck with it, please let us know how it goes. Best, Zonker -- Joe 'Zonker' Brockmeier openSUSE Community Manager jzb@zonker.net http://zonker.opensuse.org/ http://www.dissociatedpress.net/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. schreef:

I haven't finished yet, but I found a blocker.

The program does it job fairly well, but the locale encoding turns out to be a problem.

I asked the people of the project for whom I'm translating their pages, whether they wanted the pages in latin1 or utf8, and the answer is "neither":

] Characters outside the ASCII printable range must be encoded; see ] groff_char(7) (but note that we use "\('e" rather than "\['e]").

This is a problem too with manual pages in the suse distro: they either display well in latin 1 or in utf 8, but not both. And using the encoding described in groff_char(7) they display correctly in both. The blocker is that manedit does not support that encoding.

I would have to write "ol\('e" instead of "olé", which may be just a nuisance for a coder, but it is a big inconvenience for a writer: I can not spell check the file, and my sight doesn't see "olé" but gibberish, so I can't proofread the text.

:-/

But wait, you're almost there! The only thing you need is a sed script to convert the utf-8 symbols to groff_char(7) gibberish, right? Something like utf2groff #!/bin/sed -f # # Convert utf 8 to groff_char(7) s/é/\\('e/g s/è/\\(`e/g . . . # etc You'd have to throw that script together only once and then you can write, proofread and spell check to your heart's content and when it's ok convert it to gibberish. Maybe it even exists already. :-) Regards, -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org