Follow-up Comment #4, bug #68216 (group groff):

[comment #3 comentario nº3:]
> [comment #2 comment #2:]
>> given the lack of additional feedback, and in order to close the issue, I
>> believe you may do the following.
>> 
>> 1. keep the current hyphenation patterns, if they don't clog groff's memory
>> (i don't know if there is a test suite to run a benchmark test).
> 
> No, but an ad hoc test suggests that any difference from loading, say,
> English hyphenation patterns is negligible.
> 
> 

ok: that means that there may not be penalty for the large hpf, so hyphen.es
may stay as it is...

> 
>> 2. keep the approved changes by Eloi, and push the patch to close the
>> issue.
>> 
>> I may fix the patch to keep Eloi's approved changes, if required.
> 
> I don't have much feedback as I'm not a native Spanish speaker.
> 
> However I'm aware of this issue and my intention is to address it for the
> _groff_ 1.25.0 release, planned for early July.  For the moment my focus is
> on the formatter, as I want to get my fingers *out* of it before chilling the
> development temperature as release time gets closer.

I'll do the following: I'll make the corrections approved by Eloi in the other
thread and remove my suggestions, and provide a diff file correcting only the
clear misspellings to have it ready for the next bugfix or main release, to
let you decide when to release.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
Mensaje enviado vía Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to