Mailing List Archive

Bernhard Reiter wrote:
> [patch in attachment]

I suggest striking "what was" and revising, leaving "can be changed to
the previous default value, which" to make the text flow less awkwardly.


-- Jacob

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

> I suggest striking "what was" and revising, leaving "can be changed to
> the previous default value, which" to make the text flow less awkwardly.

Thanks, new patch version attached.

Bernhard Reiter wrote:
>> I suggest striking "what was" and revising, leaving "can be changed to
>> the previous default value, which" to make the text flow less awkwardly.
>>
>
> Thanks, new patch version attached.
>

The problem for me is "the value of what was the previous default" is
awkward; I suggest instead saying "the previous default value" there.
Is this an awkward phrasing to optimize TeX typesetting?


-- Jacob

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

> The problem for me is "the value of what was the previous default" is
> awkward; I suggest instead saying "the previous default value" there.

New patch attached, thanks.

> Is this an awkward phrasing to optimize TeX typesetting?

I don't know as I somehow kept the structure of the original sentence.

Feel free to improve the phrasing as the important part is that the chance
in default is reflected here. (A potential additional improvement could be
that it is generated into that place of the documentation, so it is not
forgotten next time the default is changed.)

Regards,
Bernhard