Re: [docbook-apps] acronym and small caps

[Tony Graham]

On 12/06/2021 20:54, Kevin Dunn wrote:
...

This accomplishes nothing with fop or xep, but axf does the right
thing: it uses the small cap glyph in the font I am using.


With AH Formatter, you also have the option of
'font-variant="all-small-caps"' so that capital letters also come out as
small caps.  (Useful if, e.g., you want 'XML' [1] in small caps.) See
https://www.antenna.co.jp/AHF/help/en/ahf-ext.html#axf.font-variant

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp

[1] But is 'XML' really an acronym?

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] acronym and small caps

[Bob Stayton]

Hi Kevin,

Looks like you did it right, congratulations!


When using FOP and something does not work as expected, it is good to 
bookmark the FOP Compliance Page 



which shows the limitations of FOP for each XSL-FO feature.  In this 
case, you will see that font-variant is not supported yet.



XEP may require some addtional configuration in the XEP configuration 
file to trigger the selection of a small caps font.   Check the XEP 
documentation.


Bob Stayton
b...@sagehill.net

On 6/12/2021 12:54 PM, Kevin Dunn wrote:
Apologies for the newbie question, but I'm reading the 1.79.1 xsl 
stylesheets using eyes that are accustomed to reading dsl. I found the 
fo/inline.xsl file where acronym is processed. It looks like it just 
passes its contents through unchanged (which is how it looks in pdf 
produced by fop, xep and axf). It seems like at a minimum it should 
render all caps in the next smaller font. At a premium, it should use 
small caps if the font has them available.


So...I tackled my first xsl customization, and I'm pretty pleased with 
myself:



  
    
  


This accomplishes nothing with fop or xep, but axf does the right 
thing: it uses the small cap glyph in the font I am using. And if I 
set small-caps-emulation-always="true" in the Antenna House options 
file, axf scales the normal caps instead of using the small caps from 
the font. The scaled caps look similar to the small caps, but they are 
different enough that I can tell that axf is using the small cap when 
it is allowed to.


I'm pretty happy with this. My only real question is whether I 
reinvented the wheel.

[docbook-apps] acronym and small caps

[Kevin Dunn]

Apologies for the newbie question, but I'm reading the 1.79.1 xsl stylesheets 
using eyes that are accustomed to reading dsl. I found the fo/inline.xsl file 
where acronym is processed. It looks like it just passes its contents through 
unchanged (which is how it looks in pdf produced by fop, xep and axf). It seems 
like at a minimum it should render all caps in the next smaller font. At a 
premium, it should use small caps if the font has them available.

So...I tackled my first xsl customization, and I'm pretty pleased with myself:


  

  


This accomplishes nothing with fop or xep, but axf does the right thing: it 
uses the small cap glyph in the font I am using. And if I set 
small-caps-emulation-always="true" in the Antenna House options file, axf 
scales the normal caps instead of using the small caps from the font. The 
scaled caps look similar to the small caps, but they are different enough that 
I can tell that axf is using the small cap when it is allowed to.

I'm pretty happy with this. My only real question is whether I reinvented the 
wheel.

Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 2019

[Dave Pawson]

On Fri, 11 Jun 2021 at 23:05, Kevin Dunn  wrote:
>
> I spent the day playing with the demo versions of XEP and Antenna House 
> Formatter. I got both of them up and running using xsltproc and the default 
> xsl stylesheet, with the SelfDocBook as a source xml file. Pdf from both 
> looks good.
>
> Following DocBook XSL TCG, I was able to add a new font and enable ligatures 
> by editing xep.xml. So XEP seems like I could make it work.
>
> Antenna House Formatter was not too bad to install, but the documentation is 
> huge, and I have yet to figure out how to add a font or enable ligatures. I 
> found the font-config.xml file and added a font to it, but I can't figure out 
> how to tell the formatter to use that font.

That's where you need to read up on xsl-fo. Called up from xsl-fo, AH
then uses font-config to locate the file.

There also seems to be extensions required to enable ligatures, but I
haven't figured out how to use them, either on the command line or in
a configuration file. Is the AH Formatter much more complicated to use
than XEP? Any kind of "newbie guide" for it?

Simple things easy, more complex things you have to work at. No
dummies book that I know of.


>
> As much as I hate to flush all my dsssl-jadetex customizations, it seems like 
> xsl-fo is going to be the way to go.


I think so.
How much work went into learning DSSSL and \tex?

regards


>
>
>  From: Norm Tovey-Walsh
> Sent: Friday, June 11, 2021 11:00 AM
> To: Kevin Dunn
> Cc: docbook-apps@lists.oasis-open.org
> Subject: Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 
> 2019
>
> Kevin Dunn  writes:
> > Thanks, Dave. You were helpful to me 10 years ago. The XEP PDF output
> > looks pretty nice with the default xsl stylesheet. There are some
> > fancy things I achieved with dsssl and jadetex, and I'm not sure how
>
> There’s a blast from the past!
>
> I’ve been chatting, off and on, with Peter Flynn about working on a way
> to use TeX as a formatting back end in the modern era. But it’s not in
> the top couple of reams of the todo list, at the moment.
>
> I expect the future is XML+CSS and that’s what I have in mind for the
> xslTNG stylesheets. It would be entirely possible, of course, to
> generate XSL-FO, but it feels like custom-HTML output and custom-CSS fed
> through Antennahouse would be the shortest path to victory.
>
> PrinceXML would also work that way.
>
> AFAIK, there are no free formatters that take HTML+CSS and produce
> results comparable with FOP, which surprises me. (Not that the FOP level
> of output would satisfy your requirements; but the lack of reasonable
> open source print formatters is one of the things that leads me to
> ponder generating LaTeX. You know, like we did in the 90’s when we were
> young! :-))
>
> Be seeing you,
>   norm
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
> > Linux. Because rebooting is for hardware upgrades.



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 2019

[Kevin Dunn]

Thanks, everyone. I figured out fonts in the Antenna House formatter. I'm 
closer to satisfactory PDFs after two days of exploring xsl-fo than I was after 
two weeks of trying to troubleshoot my old custom dsssl stylesheets on a new 
computer. I'm sure I'll have more questions, but they won't be about 
docbook2pdf.

Get Outlook for Android


From: Kevin Dunn 
Sent: Friday, June 11, 2021, 6:06 PM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 
2019

I spent the day playing with the demo versions of XEP and Antenna House 
Formatter. I got both of them up and running using xsltproc and the default xsl 
stylesheet, with the SelfDocBook as a source xml file. Pdf from both looks good.

Following DocBook XSL TCG, I was able to add a new font and enable ligatures by 
editing xep.xml. So XEP seems like I could make it work.

Antenna House Formatter was not too bad to install, but the documentation is 
huge, and I have yet to figure out how to add a font or enable ligatures. I 
found the font-config.xml file and added a font to it, but I can't figure out 
how to tell the formatter to use that font. There also seems to be extensions 
required to enable ligatures, but I haven't figured out how to use them, either 
on the command line or in a configuration file. Is the AH Formatter much more 
complicated to use than XEP? Any kind of "newbie guide" for it?

As much as I hate to flush all my dsssl-jadetex customizations, it seems like 
xsl-fo is going to be the way to go.



From: Norm Tovey-Walsh
Sent: Friday, June 11, 2021 11:00 AM
To: Kevin Dunn
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 
2019

Kevin Dunn  writes:
> Thanks, Dave. You were helpful to me 10 years ago. The XEP PDF output
> looks pretty nice with the default xsl stylesheet. There are some
> fancy things I achieved with dsssl and jadetex, and I'm not sure how

There’s a blast from the past!

I’ve been chatting, off and on, with Peter Flynn about working on a way
to use TeX as a formatting back end in the modern era. But it’s not in
the top couple of reams of the todo list, at the moment.

I expect the future is XML+CSS and that’s what I have in mind for the
xslTNG stylesheets. It would be entirely possible, of course, to
generate XSL-FO, but it feels like custom-HTML output and custom-CSS fed
through Antennahouse would be the shortest path to victory.

PrinceXML would also work that way.

AFAIK, there are no free formatters that take HTML+CSS and produce
results comparable with FOP, which surprises me. (Not that the FOP level
of output would satisfy your requirements; but the lack of reasonable
open source print formatters is one of the things that leads me to
ponder generating LaTeX. You know, like we did in the 90’s when we were
young! :-))

Be seeing you,
  norm

--
Norman Tovey-Walsh 
https://nwalsh.com/

> Linux. Because rebooting is for hardware upgrades.