Follow-up Comment #5, bug#65232 (group groff):
[comment #4 комментарий №4:]
>
> [comment #3 comment #3:]
> > After switching from pdfroff (-Tps) to pdfmom (-Tpdf), hyphenation
suddenly works fine.
>
> Glad to hear it.
>
I forgot to mention, I also had to install a new version of the
LiberationSerif fonts as the previous ones I was using, apparently weren't
fully compatible with gropdf. There were for instance some space characters
that were not displayed correctly.
> > Moreover, it will even work with UTF8 input (-Kutf-8), even though that
causes other glitches.
>
> What glitches are you seeing?
>
With -Kutf-8, link texts generated by .pdfhref were sometimes missing -
seemingly random - characters.
> The input is coverted from UTF-8 to KOI8-R. The hyphenation patters are
defined in terms of KOI8-R code points. The formatter (GNU _troff_) decides
where the hyphens should go and performs the breaks. The formatter converts
the input characters into internal data structures called "nodes" that do not
use an externally visible encoding. Then, when generating device-independent
output, each glyph nodes is converted to a device-independent special
character command _if_ the output device supports its code point. (If it
doesn't, you get a warning like "special character 'u0413' not defined".)
>
Are you telling me that pdfmom is actually internally converting my text to
KOI8-R after noticing I did -mru?
This is obviously not the case as I tried to print some Cyrillic using .tm and
it comes out as Unicode escapes as would be expected after the sources are ran
through preconv.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65232>
_______________________________________________
Сообщение отправлено по Savannah
https://savannah.gnu.org/
