CTAN Comprehensive TeX Archive Network

CTAN up­date: px­u­font

Date: March 13, 2019 9:41:54 AM CET
Takayuki Yato sub­mit­ted an up­date to the px­u­font pack­age. Ver­sion num­ber: 0.5 Li­cense type: mit Sum­mary de­scrip­tion: Emu­late non-Uni­code Ja­panese fonts us­ing Uni­code fonts An­nounce­ment text:
New fea­tures: - Sup­port for the fonts of ruby no­ta­tion forms. - Sup­port for the fonts of 'min10' se­ries.
This pack­age is lo­cated at http://mir­ror.ctan.org/lan­guage/japanese/px­u­font More in­for­ma­tion is at https://www.ctan.org/pkg/px­u­font
Thanks for the up­load. For the CTAN Team Erik Braun
We are sup­ported by the TeX users groups. Please join a users group; see http://www.tug.org/user­groups.html .

px­u­font – Emu­late non-Uni­code Ja­panese fonts us­ing Uni­code fonts

The set of the Ja­panese log­i­cal fonts (JFMs) that are used as stan­dard fonts in p and up con­tains both Uni­code JFMs and non-Uni­code JFMs. This bun­dle pro­vides an al­ter­na­tive set of non-Uni­code JFMs that are tied to the vir­tual fonts (VFs) that re­fer to the glyphs in the Uni­code JFMs. More­over it pro­vides a pack­age that re­de­fines the NFSS set­tings of the Ja­panese fonts of (u)p so that the new set of non-Uni­code JFMs will be em­ployed. As a whole, this bun­dle al­lows users to dis­pense with the map­ping setup on non-Uni­code JFMs.

Such a setup is use­ful in par­tic­u­lar when users want to use OpenType fonts (such as Source Han Serif) that have a glyph en­cod­ing dif­fer­ent from Adobe-Ja­pan1, be­cause map­ping se­tups from non-Uni­code JFMs to such phys­i­cal fonts are dif­fi­cult to pre­pare.

Copy­right2017 Takayuki YATO
Main­tainerTakayuki Yato



Guest Book Sitemap Contact Contact Author