Hello Branden!

On Sun, 10 Nov 2024, G. Branden Robinson wrote:

Lest anyone get apprehensive about disruptive changes in groff 1.23.0,
this is isn't a change in groff 1.23.0.

I wasn't assuming or implying that. I was just mentioning my version.

You're not looking in the right places, unfortunately.

1.  groff does not use glib in any way.
2.  Within groff, only preconv(1) uses iconv(3).

Third, grotty(1) isn't doing it either.  What you're probably looking
for is this:

https://git.savannah.gnu.org/cgit/groff.git/tree/src/libs/libgroff/uniuni.cpp?h=1.23.

I knew that groff isn't using glib. That's what I am using and would probably use to compose the characters instead of hardcoding translation tables.

My guess is that you will need to write a device description file for
your output device.  This should not be a major task; the files tend to
be brief and while groff_out(5) still badly needs heavy editorial
revision, I've done some sanding and polishing on groff_font(5), and it
should be clear enough for you to undertake writing a "DESC" file for a
"font/devsciteco" directory you create.  If anything in that man page is
unclear, I definitely want your feedback on the subject.

Well, I don't think it's worth it. I cannot really support multiple fonts or font sizes, so reusing the "utf8" device is probably sufficient. grosciteco is for rendering documents into Scintilla buffers and while they do support all sorts of font styles, you need to assign a single 8-bit number to every combination of styles you could possibly use in your document.
And it's really only used for rendering manpages anyway.
I was trying to abuse it for rendering a presentation about SciTECO into SciTECO itself - but that would have really been more of a gimmick... As far as I see, I cannot prevent the unicode decomposition in a custom DESC file. However It seems I could consult the devutf8 font description files instead of using a library to compose the characters.

Sooner or later, I might have non-English documentation to render into buffers with grosciteco, so supporting diacritics might be necessary sooner or later. For the time being, it's not urgent.

Cheers,
Robin

Reply via email to