[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #12, bug #66103 (group groff): At 2024-09-14T13:17:52-0400, Helge Kreutzmann wrote: > regarding po4a macros - I'm also sometimes learning by Martin Quinson > (maintainer of po4a) reply to my bug reports there.The best source I know of > is Locale::Po4a::Man(1). Ah, thanks--I ha

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #11, bug #66103 (group groff): Hello Branden, regarding po4a macros - I'm also sometimes learning by Martin Quinson (maintainer of po4a) reply to my bug reports there.The best source I know of is Locale::Po4a::Man(1). Thanks for handling the ISO/IEC reference. As you reopend t

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #10, bug #66103 (group groff): Hi Helge, At 2024-09-14T12:35:35-0400, Helge Kreutzmann wrote: > thanks for handling the report. I'll note down where you are not in > agreement with the report, so it won't be reported again in the > future. Okay. I won't get upset if they are.

[bug #66103] manpage-10n project: issues in man pages

Update of bug #66103 (group groff): Status: Fixed => None Assigned to:gbranden => None Open/Closed: Closed => Open Planned Release:

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #8, bug #66103 (group groff): Hello Branden, thanks for handling the report. I'll note down where you are not in agreement with the report, so it won't be reported again in the future. Regarding the questions raised, here is my reply. It's a bit tough in this form, so please acc

[bug #66103] manpage-10n project: issues in man pages

Update of bug #66103 (group groff): Status:None => Fixed Assigned to:None => gbranden Open/Closed:Open => Closed Planned Release:

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #5, bug #66103 (group groff): ___ Reply to this item at: ___ Message sent via Savannah https://savannah.nongnu.org/ signature.as

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #4, bug #66103 (group groff): >> Man page: soelim.1 >> Issue 1: I<\\%soelim> → B<\\%soelim> >> Issue 2: I<\\%troff> → .MR \\%troff 1 >> >> "I<\\%soelim> is I required for I<\\%troff> to source files." > As this is the very next sentence, another cross reference here would be

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #3, bug #66103 (group groff): Looks like Savane got angry with me. Here's what I *tried* to reply with via email: Subject: Re: [bug #66103] manpage-10n project: issues in man pages [self-follow-up] I had a wordo here. At 2024-09-11T04:33:41-0400, G. Branden Robinson

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #2, bug #66103 (group groff): ___ Reply to this item at: ___ Message sent via Savannah https://savannah.gnu.org/ signature.asc Desc

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #1, bug #66103 (group groff): At 2024-08-18T13:53:13-0400, Helge Kreutzmann wrote: > Please note: I know you are not following traditional man rules any > more, I dispute that. I think groff's man pages are as faithful to the format and conventions established in the Seventh Ed

[bug #66103] manpage-10n project: issues in man pages

Update of bug #66103 (group groff): Summary: Issues in man pages => manpage-10n project: issues in man pages ___ Reply to this item at: ___