From: Carlos E. R. <car...@us...> - 2008-02-08 14:03:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm reviewing the translation to Spanish of your man pages, and I found a tool for the task, manedit: <http://www.battlefieldlinux.com/wolfpack/ManEdit/> <http://www.unixreview.com/documents/s=9513/ur0501k/ur0501k.html> but unfortunately doesn't even support my UTF keyboard: I have to use it in latin1 mode (ISO-8859-1). I wonder if that is an issue for you? I mean, I don't know if your man pages should be utf or latin. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHrGE9tTMYHG2NR9URAlBTAJ4o0iGZXP4tEY2RmbJdjC+D8cD1OQCfUv47 c3dHLosb1Ehl8y9aWRNjqQ8= =RbMt -----END PGP SIGNATURE----- |
From: Brian J. T. <bj...@co...> - 2008-02-08 18:17:14
|
Carlos E. R. wrote: > I'm reviewing the translation to Spanish of your man pages, and I found a > tool for the task, manedit: > > <http://www.battlefieldlinux.com/wolfpack/ManEdit/> > <http://www.unixreview.com/documents/s=9513/ur0501k/ur0501k.html> > > but unfortunately doesn't even support my UTF keyboard: I have to use it > in latin1 mode (ISO-8859-1). Assuming your language is covered by latin1, you can always use iconv afterwards to convert your work to utf8: iconv -f ISO-8859-1 -t UTF-8 latin1file > utf8file -brian |
From: Carlos E. R. <car...@us...> - 2008-02-08 19:11:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-02-08 at 10:17 -0800, Brian J. Tarricone wrote: > Assuming your language is covered by latin1, you can always use iconv > afterwards to convert your work to utf8: > > iconv -f ISO-8859-1 -t UTF-8 latin1file > utf8file Yes, I thought of that, even though it is an extra complication. But the main question remains: what locale should I use for the xine project. My guess is that it should be utf. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHrKlNtTMYHG2NR9URAlnCAJwNsPoYxdOhdMsi+J82CBdqi5v1nwCgjgvc ml4uKsqmBNP5eyTv2WqYrmw= =23x3 -----END PGP SIGNATURE----- |
From: Darren S. <li...@yo...> - 2008-02-09 00:55:06
|
I demand that Brian J. Tarricone may or may not have written... > Carlos E. R. wrote: >> I'm reviewing the translation to Spanish of your man pages, and I found a >> tool for the task, manedit: >> <http://www.battlefieldlinux.com/wolfpack/ManEdit/> >> <http://www.unixreview.com/documents/s=9513/ur0501k/ur0501k.html> >> but unfortunately doesn't even support my UTF keyboard: I have to use it >> in latin1 mode (ISO-8859-1). > Assuming your language is covered by latin1, you can always use iconv > afterwards to convert your work to utf8: > iconv -f ISO-8859-1 -t UTF-8 latin1file > utf8file That would work, yes, but it's not suitable - I've seen misdisplayed man pages using each encoding and displayed in an environment using the other. Characters outside the ASCII printable range must be encoded; see groff_char(7) (but note that we use "\('e" rather than "\['e]"). -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. Get out the Crisco. |
From: Carlos E. R. <car...@us...> - 2008-02-09 01:43:59
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-02-09 at 00:35 -0000, Darren Salt wrote: >> Assuming your language is covered by latin1, you can always use iconv >> afterwards to convert your work to utf8: > >> iconv -f ISO-8859-1 -t UTF-8 latin1file > utf8file > > That would work, yes, but it's not suitable - I've seen misdisplayed man > pages using each encoding and displayed in an environment using the other. > Characters outside the ASCII printable range must be encoded; see > groff_char(7) (but note that we use "\('e" rather than "\['e]"). Oh damm. Oh damm :-( I have no way of handling that. This is terribly unfortunate. :-( I can not write groff whatever unless some other thing translates from my human language to whatever thing 'man' wants. I'm not prepared to learn trof/groff. I write, not program. Sorry. I've been searching hard for a program allowing me to write man pages comfortably. I tried LyX, and failed: nobody knows how to produce man pages using LyX, and it is not the first time I try (and I googled for it a lot). My installation fails to produce workable docbook/linuxdoc from LyX and apparently nobody knows how to solve it to produce man pages; it is above my skills, as I know nothing about latex, docbook, linuxdoc, xml or even html. I was told about "manedit", and I was happy: it is reasonably comfortable, but I found it only supports latin1. Now you tell me that man pages have a special way of supporting special chars. I try and you are correct: the page displays either in latin1 or utf, but not both, correctly. That's a blocker for me. An absolute blocker. I can no way create man pages using the coding you describe. :-/ Currently I can only write them in latin1, and perhaps (not tested) convert to utf. :-(( I'm off to bed. Dunno how to continue. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHrQVbtTMYHG2NR9URAv1RAJ9aQGFytFxU6jXu5119deWhv/uHywCgjzkB MKYdh/WmvSNgYUzBoYxJicw= =CWQb -----END PGP SIGNATURE----- |
From: Jim P. <ji...@jt...> - 2008-02-09 02:03:40
|
Carlos E. R. wrote: > > That would work, yes, but it's not suitable - I've seen misdisplayed man > > pages using each encoding and displayed in an environment using the other. > > Characters outside the ASCII printable range must be encoded; see > > groff_char(7) (but note that we use "\('e" rather than "\['e]"). > > Oh damm. Oh damm :-( > > I have no way of handling that. This is terribly unfortunate. :-( > > I can not write groff whatever unless some other thing translates from my > human language to whatever thing 'man' wants. I'm not prepared to learn > trof/groff. I write, not program. Sorry. .. > That's a blocker for me. An absolute blocker. > > I can no way create man pages using the coding you describe. :-/ All you need to do is type "\('e" into manedit whenever you want "é" to show up in the manpage. An inconvenience but I don't think it should be a blocker. If you'd rather type é directly, you could just do that and use a script to transform the output file after you're done. If you tell me which non-ascii characters you intend to use I can create such a script for you. -jim |
From: Carlos E. R. <car...@us...> - 2008-02-09 12:03:46
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ??he Friday 2008-02-08 at 21:03 -0500, Jim Paris wrote: > All you need to do is type "\('e" into manedit whenever you want "é" > to show up in the manpage. An inconvenience but I don't think it > should be a blocker. If you'd rather type é directly, you could just > do that and use a script to transform the output file after you're > done. If you tell me which non-ascii characters you intend to use I > can create such a script for you. It may be just an inconvenience for a coder, but it is a big rock on the road for a writer. I can not use a spell checker, for instance. I can not see at a glance the text and check my grammatical/ syntax/ orthographical/ translation errors, which are already difficult to track because of the tokens. Yes, I did think about the search and replace. The only way would be to have my version in latin1 and some "converter" doing those changes before submission. I have been told a list of other editors I should check. I'll see. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHrZaMtTMYHG2NR9URAsN7AJ9nJ8BYtDrJPxYEZIp4UsEVzPNHIgCgh+Rq jWjqHCz90HLPl0NPLiqZmsY= =1yp4 -----END PGP SIGNATURE----- |