Follow-up Comment #1, bug #68022 (group groff):

On Friday, 6 February 2026 09:59:33 GMT G. Branden Robinson wrote:
> URL:
> <https://savannah.gnu.org/bugs/?68022>
>
> Summary: [gropdf] flip sense of bit 3 of new `--opt`
> command-line option
> Group: GNU roff
> Submitter: gbranden
> Submitted: Fri 06 Feb 2026 09:59:30 AM UTC
> Category: Driver gropdf
> Severity: 3 - Normal
> Item Group: Feature change
> Status: Need Info
> Privacy: Public
> Assigned to: deri
> Open/Closed: Open
> Discussion Lock: Unlocked
> Planned Release: None
>
>
> _______________________________________________________
>
> Follow-up Comments:
>
>
> -------------------------------------------------------
> Date: Fri 06 Feb 2026 09:59:30 AM UTC By: G. Branden Robinson <gbranden>
> Spawned off of comment 18 to bug #66342.
>
> I wrote:
>> I would [...] like to see the meaning of bit 3 of `--opt` inverted.
>>
>> I'd like to see this done before 1.24.0 is out, to avoid the necessity of
>> changing the meaning of bit 3 of gropdf's `--opt` [later, from that in a
>> shipped release].
>>
>> Unless of course you disagree with that proposal, in which case further
>> discussion is warranted.
>>
>> If you agree, I'm happy to help develop the change[].
>
> Setting Item Group to "Feature change" because that seems most accurate,
> however this would not (of itself) require a "NEWS" entry, because it would
> be a change to a feature that hasn't yet shipped in a _groff_ release.
>
> Assigning to Deri for his feedback.
>

I'm not to keen on this, although I may be persuaded. Let me explain my
logic:-

Bits
====

1. = subset
1 = compact by using space glyph (if available)
2 = compress streams
3 = remove font data (may create non-standard pdf)

Setting value to 1 = do it, to zero = don't do it.

The first 3 are things which you definitely want to do, the last is definitely

dodgy, so the default value is 7.

Since bit 3 is "dangerous" I think it is "safer" to conciously add 8 to the
value to cause it to happen.

Please explain your logic similarly.

Cheers

Deri






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?68022>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to