Re: removing the .IX macro from the ms package in 1.23 breaks old documents

2024-10-13 Thread joerg van den hoff
tadziu, I missed your mail/suggestion regarding reinsertion of the `.ll -8n' request in .XA and only today became aware of it due to the reverted commit (so too late to confirm that indeed this fixes the main issue perfectly -- you know that already ;)). thanks a whole lot for pointing this o

Re: removing the .IX macro from the ms package in 1.23 breaks old documents

2024-10-13 Thread G. Branden Robinson
[replying only to the lists since you're clearly subscribed, or otherwise following them] Hi Joerg, At 2024-10-13T12:36:23+0200, joerg van den hoff wrote: > On 13.10.24 11:24, G. Branden Robinson wrote: > it seems it would probably be best to just agree to disagree and move > on, but ... Where w

Re: removing the .IX macro from the ms package in 1.23 breaks old documents

2024-10-13 Thread joerg van den hoff
On 13.10.24 11:24, G. Branden Robinson wrote: Hi Joerg, hi branden, it seems it would probably be best to just agree to disagree and move on, but ... At 2024-10-13T11:03:52+0200, joerg van den hoff wrote: but I really believe the line should never have been deleted in the first place (

Re: removing the .IX macro from the ms package in 1.23 breaks old documents

2024-10-13 Thread G. Branden Robinson
Hi Joerg, At 2024-10-13T11:03:52+0200, joerg van den hoff wrote: > but I really believe the line should never have been deleted in the > first place (I think the working hypothesis should better be "even if > I do not see why it is there and even if it seems superfluous to me, > it is there for a

Can or rather is a macro package be licensed?

2024-10-13 Thread Matthew Polk
I want to in the future sometime, submit a nice macro package I'm creating to savannah. However, can the macro package itself be licensed and if yes, you must also use the same license like other types of programs say python (Where if you import a GPL licensed script, that too must be GPL)? It c

Re: removing the .IX macro from the ms package in 1.23 breaks old documents

2024-10-13 Thread Dave Kemper
On Sun, Oct 13, 2024 at 8:31 AM G. Branden Robinson wrote: > It isn't, yet. What you have seen is a Savannah bug report about it.[2] > It was filed anonymously. ("Who _was_ that masked man?" Dave Kemper, I > reckon.) Guilty. I (sometimes) anonymously file tickets in which I have no personal i

Re: Can or rather is a macro package be licensed?

2024-10-13 Thread G. Branden Robinson
Hi Matthew, At 2024-10-13T12:11:24+, Matthew Polk wrote: > I want to in the future sometime, submit a nice macro package I'm > creating to savannah. Good to hear! I'm curious--do you mean for distribution with groff or as an independent Savannah project? > However, can the macro package its

Re: removing the .IX macro from the ms package in 1.23 breaks old documents

2024-10-13 Thread joerg van den hoff
On 13.10.24 15:31, G. Branden Robinson wrote: [replying only to the lists since you're clearly subscribed, or otherwise following them] Hi Joerg, hi branden, At 2024-10-13T12:36:23+0200, joerg van den hoff wrote: On 13.10.24 11:24, G. Branden Robinson wrote: it seems it would probably b

Re: Can or rather is a macro package be licensed?

2024-10-13 Thread Matthew Polk
Hi, thanks for the very swift and verbose response. :) I figured previously that it probably wouldn't be included in groff upstream at the time of this writing, but if there is a possibly of inclusion I am more than delighted to hand over copyright to maintainers (Which I believe is the FSF). I