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

On 4/26/23, G. Branden Robinson wrote: > It would probably be a good idea to represent Unicode strings internally > using char32_t as a base type anyway, but groff's design under the Unix > filter model described above makes the choice less dramatic in terms of > increased space consumption than

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

On 4/29/23, Oliver Corff wrote: > Would it be a feasible option to use UTF-8 throughout the inner workings > of a future groff, This is the topic of http://savannah.gnu.org/bugs/?40720 (though most of the interesting discussion has taken place in http://savannah.gnu.org/bugs/?58796). But in my

Re: Count number of spaces at beginning of line?

On 4/29/23, Oliver Corff wrote: > Is there any possibility to count leading spaces in groff? See the documentation for the \n[lsn] register. I've never used it, but its description sounds like what you're looking for.

[bug #46914] breaking behavior inconsistent within a .ce block

Update of bug #46914 (project groff): Summary: .ce sometimes ignores right margin => breaking behavior inconsistent within a .ce block ___ Follow-up Comment #13: [comment #11 comment #11:] > Similar "subject" is also

Re: Warn on mid-input line sentence endings

Hi Branden, On 4/30/23 02:05, G. Branden Robinson wrote: > I should clarify a couple of points here since I was feeling grumpy when > I wrote the following, and that made me forget things. > > At 2023-04-27T09:45:40-0500, G. Branden Robinson wrote: >> We're re-covering some familiar ground here.

Re: Multi-columns in ms

On Sat, Apr 29, 2023, G. Branden Robinson wrote: > > After ending the two-column mode, I want to contine on the same > > page. > > I don't think any of the "classical" macro packages address this > scenario. Maybe mom(7) does. Mom doesn't support this, either. > > Also, how do I force a column

Re: Warn on mid-input line sentence endings

I should clarify a couple of points here since I was feeling grumpy when I wrote the following, and that made me forget things. At 2023-04-27T09:45:40-0500, G. Branden Robinson wrote: > We're re-covering some familiar ground here. > > I have a few points I'd like to make. > > 1. "Semantic

Re: Multi-columns in ms

On Saturday, 29 April 2023 23:07:05 BST G. Branden Robinson wrote: > The latter approach in particular presents challenges; footnote text is > formatted at the time the footnote mark occurs, but in a diversion. > When the page bottom is reached, a trap is sprung that causes the > footnote text's

Re: Behaviour of .so differs between mandoc and groff

Ping. Does anyone have any thoughts on this? It's a small but persistent irritation on my system. :-) Alexis writes: [1. text/plain] Hi all, On my Gentoo system, awk.1 simply contains an .so request whose argument is the man page for the actual awk implementation in use, i.e. just:

Re: Multi-columns in ms

Hi Oliver, At 2023-04-29T23:02:44+0200, Oliver Corff wrote: > groff_ms(7) states that "All of them (i.e. .1C, .2C and .MC) force a > page break if a multi-column mode is already set. However, if the > current mode is single-column, starting a multi-column mode does _not_ > force a page break. >

Multi-columns in ms

Dear all, groff_ms(7) states that "All of them (i.e. .1C, .2C and .MC) force a page break if a multi-column mode is already set. However, if the current mode is single-column, starting a multi-column mode does _not_ force a page break. So, .2C Does not force a page break here, assuming that

Re: Count number of spaces at beginning of line?

Hi Ralph, You nailed the provenance of my way of thinking: Unlike TeX, where everything is written in TeX, troff favours using a preprocessor which produces troff, e.g. pic(1) and tbl(1). These can be quite simple, say an awk script which processes what it recognises and passes through the

Re: Count number of spaces at beginning of line?

Hi Oliver, > .\" Start of example text > > Learning Language X \"should return 0 > > [] Prerequisites \" should return 1 > > [][] Tools \" should return 2 ... > \n[Text_of_my_line] would contain the level of indentation, like > \n[Tools] and \n[Documentation] whould both return 2 which could be >

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

Hi Branden, On 27/04/2023 05:07, G. Branden Robinson wrote: At 2023-04-26T19:33:48+0200, Oliver Corff wrote: I am not familiar with modern incarnations of C/C++. Is there really no char data type that is Unicode-compliant? There is. But "Unicode" is a _family_ of standards. There are

Count number of spaces at beginning of line?

Dear all, the weekend is there, and drives me to try silly things (which is a good way to learn a language). Is there any possibility to count leading spaces in groff? I use [] to express spaces in the following mock-up of an outline: .\" Start of example text Learning Language X \"should

Re: Inter-paragraph separation modified by HP

Hi Branden, On 4/29/23 21:18, G. Branden Robinson wrote: > At 2023-04-29T21:05:36+0200, Alejandro Colomar wrote: >> BTW, I didn't ask explicitly, but I also would like to know why I >> don't notice any effects of HP (apart from the reported regression) >> Is it safe if I replace it with PP, or is

[bug #46914] .ce sometimes ignores right margin

Follow-up Comment #12, bug #46914 (project groff): [comment #11 comment #11:] > Similar "subject" is also discussed in bug #60731 > > It is the job of '.ce' to ignore the right margin, This is an absurd claim. The request has to know where the "right margin" is (what the line length is)

Re: Inter-paragraph separation modified by HP

At 2023-04-29T21:05:36+0200, Alejandro Colomar wrote: > BTW, I didn't ask explicitly, but I also would like to know why I > don't notice any effects of HP (apart from the reported regression) > Is it safe if I replace it with PP, or is there some special > formatting that my eyes aren't seeing?

Re: Inter-paragraph separation modified by HP

Hi Alex, At 2023-04-29T21:02:52+0200, Alejandro Colomar wrote: > I was checking some warning about using HP. It happens in uri.7. > > I'm not sure I understand the macro. From visual inspection, it's > creating inter-paragraph spacing, but from the documentation I'd > say it should only affect

[bug #46914] .ce sometimes ignores right margin

Follow-up Comment #11, bug #46914 (project groff): Similar "subject" is also discussed in bug #60731 It is the job of '.ce' to ignore the right margin, that is, _not_ to break the input line in two pieces for the output line. The example in groff.texi ("info groff") is misleading in two

Re: Inter-paragraph separation modified by HP

BTW, I didn't ask explicitly, but I also would like to know why I don't notice any effects of HP (apart from the reported regression) Is it safe if I replace it with PP, or is there some special formatting that my eyes aren't seeing? Cheers, Alex -- GPG key

Savannah administrivia: fixes to our Git repository

Following up on two issues from this month: "no repository found" errors when browsing our with cgit, and the unbuildability of archives generated by cgit. At 2023-04-21T04:15:35-0500, G. Branden Robinson wrote: > Maybe our intrepid Savannah admins can catch the beast anyway. They can, and they

[bug #64105] [eqn] off-by-one error in line numbering

Update of bug #64105 (project groff): Status: Confirmed => In Progress Assigned to:None => gbranden ___ Reply to this item at:

Re: [tbl] Line wrapping (Was: Setting the widths of the columns)

At 2023-04-29T16:04:28+0200, Frederic Chartier wrote: > On 2023-04-28 16:39 -0500, G. Branden Robinson wrote: > > > Per tbl(1) from groff 1.23.0: > > [...] > > Ordinarily, a table entry is typeset rigidly. It is not filled, > > broken, hyphenated, adjusted, or populated with additional

[tbl] Line wrapping (Was: Setting the widths of the columns)

On 2023-04-28 16:39 -0500, G. Branden Robinson wrote: > Per tbl(1) from groff 1.23.0: > [...] > Ordinarily, a table entry is typeset rigidly. It is not filled, > broken, hyphenated, adjusted, or populated with additional inter??? > sentence space. This sentence was added in version

Re: [tbl] Setting the widths of the columns

On 2023-04-28 16:39 -0500, G. Branden Robinson wrote: > At 2023-04-28T23:18:34+0200, Frederic Chartier wrote: > > Specifically, I want column 1 to be exactly as wide as its > > contents requires, columns 3 and 4 to have specific (and > > different) widths and column 2 to take up the remaining > >

Re: [tbl] Setting the widths of the columns

Hi Branden, > Per tbl(1) from groff 1.23.0: > > Column modifiers > Any number of modifiers can follow a column classifier. > Arguments to modifiers, where accepted, are case‐sensitive. > If the same modifier is applied to a column specifier more than once, > or if conflicting