Re: [Groff] Groff, Grohtml and Encodings

2010-11-11 Thread Werner LEMBERG
> Attached is the patch for groff.texinfo. Compared to the > corresonding man patch with Werner's corrections, I've only added > one clause to the end. Thanks, applied! Werner

Re: [Groff] Groff, Grohtml and Encodings

2010-11-07 Thread Anton Shepelev
Werner Lemberg: Thanks! I've applied it, with slight modifications. Attached is the patch for groff.texinfo. Compared to the corresonding man patch with Werner's correc- tions, I've only added one clause to the end. Anton groff.texinfo.diff Description: Binary data

Re: [Groff] Groff, Grohtml and Encodings

2010-11-02 Thread Werner LEMBERG
>> This looks fine. Are you going to send a real patch? > > Attached is the patch for grohtml.man. Thanks! I've applied it, with slight modifications. Werner

Re: [Groff] Groff, Grohtml and Encodings

2010-10-30 Thread Anton Shepelev
> This looks fine. Are you going to send a real patch? Attached is the patch for grohtml.man. Anton --- grohtml_cur.man 2010-10-30 23:15:36.0 +0400 +++ grohtml_a.man 2010-10-30 23:29:22.0 +0400 @@ -99,6 +99,23 @@ .B \-P option. . +.PP +.B grohtml +invokes +.B groff +

Re: [Groff] Groff, Grohtml and Encodings

2010-10-30 Thread Anton Shepelev
Werner Lemberg, > This looks fine. Are you going to send a real > patch? Yes. I posted this for review, because otherwise reviewing would require applying the patch... Sorry for the long delay, but even when making small patches a newbie finds it necessary to learn a lot about the th

Re: [Groff] Groff, Grohtml and Encodings

2010-10-30 Thread Werner LEMBERG
> Below is what I've added to the Description section of grohtml man > page. This looks fine. Are you going to send a real patch? > The second paragraph is also to go in the grohtml info manual, > although it is a violation of the "Once and Only Once" principle -- > I don't know why the documen

Re: [Groff] Groff, Grohtml and Encodings

2010-10-28 Thread Anton Shepelev
Werner Lemberg: > These warning messages are harmless. Reason is > that grohtml processes the input twice: One time > with -Thtml for text and a second time with -Tps > for everything which grohtml can't handle. This > second run causes the warning messages. > [...] > Admittedly, this i

Re: [Groff] Groff, Grohtml and Encodings

2010-10-18 Thread Anton Shepelev
Werber Lemberg: > BTW, does my suggestion w.r.t. Cyrillic PS fonts > work? Yes. Anton

Re: [Groff] Groff, Grohtml and Encodings

2010-10-17 Thread Werner LEMBERG
>> Admittedly, this is badly documented if at all. I would be glad if >> you could provide patches to improve that. > > The two-pass method is described in the info file, but not in the > man page, so I will add it to the man page and modify both man and > info by: Thanks in advance! > a. add

Re: [Groff] Groff, Grohtml and Encodings

2010-10-17 Thread Anton Shepelev
Werner, > For me it works [...] Sorry, I checked it again and it had the expected effect. Must have been doing something wrong. > ??? I have this line in font/devlatin1/R: > > `A 24 0 0300 I already got it and wrote about it, but the post probably made it to the list too late. > These

Re: [Groff] Groff, Grohtml and Encodings

2010-10-17 Thread Werner LEMBERG
> [...] When I process this file using the following MSDOS batch > script > >type %1 | groff -mkoi8-r -t -Thtml > %2 > > groff outputs six (one per each symbol) warning messages of the > form: > >stdin:1: warning: can't find special character '', These warning messages are harmless.

[Groff] Groff, Grohtml and Encodings

2010-10-14 Thread Anton Shepelev
Hello all, I thought I had solved all encoding problems until I tried to export my documetns into the HTML format. It seems that my understanding of how groff maps input charactes into its internal charactes and then into output glyphs is incomplete. Below I have described what I was d