Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

At 2023-04-26T19:33:48+0200, Oliver Corff wrote: > On 26/04/2023 15:16, G. Branden Robinson wrote: > > Be sure you review my earlier messages to Oliver in detail. The > > hyphenation code isn't "broken", it's simply limited to the C/C++ > > char type for character code points and hyphenation

Re: Warn on semantic newlines

On Fri, Jun 10, 2022 at 11:52:30AM +0200, Alejandro Colomar wrote: > Hi, Ingo and Branden! > > As far as I know, there's currently no tool that warns on "foo. bar" in > filled test. Not `mandoc -Tlint`, and not `groff -ww`, and not `groff > -rCHECKSTYLE=999`. I know that CHECKSTYLE is not

Re: proctological linter warnings on groff's man pages (was: mdoc(7): CHECKSTYLE)

On 4/26/23 11:44, Alejandro Colomar wrote: > Hi Branden, > > On 4/26/23 11:06, G. Branden Robinson wrote: >> Hi Alex, >> >> At 2023-04-24T19:11:58+0200, Alex Colomar wrote: At 2023-04-23T16:17:06+0200, Alejandro Colomar wrote: > I got some errors from mdoc(7), which were probably due

Re: mdoc(7): CHECKSTYLE

Hi Branden, On 4/24/23 19:11, Alex Colomar wrote: > $ make check -k > TROFF .tmp/man/man1/gpinyin.1.cat.set > troff: man1/gpinyin.1:316: warning: macro 'AD' not defined > make: *** [share/mk/build/catman.mk:47: .tmp/man/man1/gpinyin.1.cat.set] > Error 1 > make: *** Deleting file

Re: mdoc(7): CHECKSTYLE

Hi Branden, On 4/24/23 19:11, Alex Colomar wrote: > $ make check -k > TROFF .tmp/man/man1/gpinyin.1.cat.set > troff: man1/gpinyin.1:316: warning: macro 'AD' not defined > make: *** [share/mk/build/catman.mk:47: .tmp/man/man1/gpinyin.1.cat.set] > Error 1 > make: *** Deleting file

Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

Hi Robin and Branden, On 26/04/2023 15:16, G. Branden Robinson wrote: At 2023-04-26T15:16:55+0300, Robin Haberkorn wrote: For future texts I therefore wanted to return to Groff (where we also have the excellent MOM macros). Not being able to hyphenate UTF-8 Cyrillic text is a major limitation

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #11, bug #62776 (project groff): That exceeds the bounds of what I would deem "easy." :) A groff warning category can be disabled from within the document source with the .warn request. Your method not only takes control away from the document itself, it also realistically

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #10, bug #62776 (project groff): [comment #9 comment #9:] > comment #8 comment #8:] > > Disabling a warning if you don't care is easy. > > I would love for that to be true of groff warnings. Unfortunately, you can only enable and disable warnings by category, the existing

Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

At 2023-04-26T15:16:55+0300, Robin Haberkorn wrote: > For future texts I therefore wanted to return to Groff (where we also > have the excellent MOM macros). Not being able to hyphenate UTF-8 > Cyrillic text is a major limitation for me. I might get away with > converting it to KOI8 first, but

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #9, bug #62776 (project groff): comment #8 comment #8:] > Disabling a warning if you don't care is easy. I would love for that to be true of groff warnings. Unfortunately, you can only enable and disable warnings by category, the existing categories range in scope from

Re: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian

25.04.23 19:51, G. Branden Robinson пишет: While I'm pontificating I'll opine that I'm not a huge fan of C++ as a language, but I have found with groff that, given discipline, and by maintaining a clear view of its roots in C (_also_ not my favorite language--but one

Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

Hello! I can confirm that Neatroff (and Heirloom Troff) works well for typesetting Russian texts including hyphenation. BUT, I found them unsuitable for complex scientific texts as their ms macros are buggy and tbl is somewhat limited. Regarding Neatroff, I found that its hyperlinking

Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

Hi Ralph, I could not resist the temptation to procrastinate from my current work and had a look at neatroff. Really neat! Out-of-the-box, my test file russ.ms and TeX utf8 hyphenation patterns taken straight from my TeX installation produced the attached very satisfying result. Best regards,

Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

Hi Ralph, thank you very much for mentioning neatroff. In principle, I am aware that there are other implementations, all with their particular unique features, but I never dived into anything other than groff so far (also due to the fruitful and friendly exchange on this mailing list), and

neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

Hi Oliver, Are you aware there are other troff implementations than GNU's groff? Neatroff is one. Ali Gholami Rudi wrote it because he wanted better Unicode support for foreign languages, including right-to-left text. He seems very much of your mould in needs. A good summary of its features is

[bug #64114] [pdfpic] when falling back to EPS, should create file in temporary directory, but doesn't

URL: Summary: [pdfpic] when falling back to EPS, should create file in temporary directory, but doesn't Group: GNU roff Submitter: gbranden Submitted: Wed 26 Apr 2023 10:51:18 AM UTC

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #8, bug #62776 (project groff): [comment #6 comment #6:] > Also I think the technique you describe, which I have not seen in the wild, might be too clever by half. Better to say in English in a comment, "This macro is intended to cause no breaks.", no? I tend to prefer actual

Re: proctological linter warnings on groff's man pages (was: mdoc(7): CHECKSTYLE)

Hi Branden, On 4/26/23 11:06, G. Branden Robinson wrote: > Hi Alex, > > At 2023-04-24T19:11:58+0200, Alex Colomar wrote: >>> At 2023-04-23T16:17:06+0200, Alejandro Colomar wrote: I got some errors from mdoc(7), which were probably due to the LANDMINE

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #7, bug #62776 (project groff): [comment #6 comment #6:] > the technique you describe, which I have not seen in the wild, I haven't either, just thinking out loud (or the virtual version thereof). ___ Reply to this item

proctological linter warnings on groff's man pages (was: mdoc(7): CHECKSTYLE)

Hi Alex, At 2023-04-24T19:11:58+0200, Alex Colomar wrote: > > At 2023-04-23T16:17:06+0200, Alejandro Colomar wrote: > > > I got some errors from mdoc(7), which were probably due to the > > > LANDMINE > > >

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #6, bug #62776 (project groff): [comment #5 comment #5:] > One may not be saying something meaningful to groff, but may be to a human reader. For example, if a user-defined macro should not cause a break, and that macro invokes five requests, two of which cause a break, then

Re: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian

Hi Branden, I'll take the route you suggest, i.e. install a 1.23.0 version where I'll place the macros; but I'll have to postpone this until Saturday --- so no earlier feedback possible. Best regards, Oliver. On 26/04/2023 10:18, G. Branden Robinson wrote: Hi Oliver, At

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #5, bug #62776 (project groff): [comment #4 comment #4:] > 2. Invoking a non-breaking request with the no-break control > character; the user will think they're saying something > meaningful, but they are not. One may not be saying something meaningful to groff, but may be to a

Re: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian

Hi Oliver, At 2023-04-26T09:19:41+0200, Oliver Corff wrote: > thank you very much for the sharing your insight regarding groff > internals. I wish they were deeper! There is still plenty I have to learn. > I tried your demonstration, replacing the text file with my own file > (utf8-encoded

Re: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian

Hi Branden, thank you very much for the sharing your insight regarding groff internals. I tried your demonstration, replacing the text file with my own file (utf8-encoded Cyrillic), and I did not succeed to reproduce your results. I copied all Russian-related macros (ru.tmac, hyphen.ru and