Hallo ConTeXters, I filally prepared first version of Storm fonts support. For now next 10 families are included: Lido, Aichel, Dynamo RE, Biblon, Libcziowes, Preissig (text+antikva), Preissig1918, Solpera, Serapion, Tyfa (text). Lido is free for non-commertioal use, so you can play with. Since now OpenType and TrueType versions of Lido are available from www.stormtype.com but unfortunately no Type1 version, I included Type1 to this distrib (see its licence). There is a catalog: http://typokvitek.com/stormcontext/stocat-prj.pdf Files: stormcontext.zip support itself stormcontext-lido.zip support only for Lido font stormcontext-cat.zip catalog and its sources storm-lido.zip Type1 Lido: read the licence before installing! http://typokvitek.com/stormcontext/index.html I would like to incorporate the distr to the garden, but I believe it needs some file/dir name changes. Suggestions are welcomed. vit
Hello Vit,
I filally prepared first version of Storm fonts support. For now next 10 families are included: Lido, Aichel, Dynamo RE, Biblon, Libcziowes, Preissig (text+antikva), Preissig1918, Solpera, Serapion, Tyfa (text).
Great! The pdf is pretty impressive. Thank you very much.
I would like to incorporate the distr to the garden, but I believe it needs some file/dir name changes. Suggestions are welcomed.
If you think of a clever way, please tell me where/how to put your typescripts + .. on garden. I could even add a new section: fonts.contextgarden.net if this sounds appropriate for collecting stuff like yours. Patrick -- ConTeXt wiki and more: http://contextgarden.net
Vit Zyka said this at Sun, 10 Apr 2005 23:17:39 +0200:
I filally prepared first version of Storm fonts support. For now next 10 families are included:
Vit, Fantastic stuff! I love the presentation (PDF), and the usage of the \variant[] mechanism in order to get the extended characters looks really clever. Sounds like it could be a way of supporting an encoding like TS1, if people really still cared about that. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Vit Zyka said this at Sun, 10 Apr 2005 23:17:39 +0200:
stormcontext-lido.zip support only for Lido font
Small comment: this package seems to be missing the type-sto.tex file. Otherwise, it's really nice. A general suggestion--you might experiment with the [special] typescripts in type-spe as a way of loading the mathcollections. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Vit Zyka said this at Tue, 12 Apr 2005 14:27:24 +0200:
Next (t-type-***.tex) at the evening.
Okay, I noticed a second thing, in the [serif][cond][size] and other [size] typescripts: you define things like \tfc with the intention of "typeface-condensed". This will interfere with people who rely on the conventional interpretation of "typeface-at-size-C". That's one of the things that make this tricky territory. I'm not satisfied with most of the solutions I find, most of the time. I'd like an orderly way of dealing with extra weights and shapes that 1) fit in the "ConTeXt Way," 2) work well with other peoples' setups 3) is rational and 4) extensible. Fontvariants were one step in that direction, but I recognise that it's not a complete solution by any means. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Adam Lindsay wrote:
Vit Zyka said this at Tue, 12 Apr 2005 14:27:24 +0200:
Next (t-type-***.tex) at the evening.
Okay, I noticed a second thing, in the [serif][cond][size] and other [size] typescripts: you define things like \tfc with the intention of "typeface-condensed". This will interfere with people who rely on the conventional interpretation of "typeface-at-size-C".
That's one of the things that make this tricky territory. I'm not satisfied with most of the solutions I find, most of the time. I'd like an orderly way of dealing with extra weights and shapes that 1) fit in the "ConTeXt Way," 2) work well with other peoples' setups 3) is rational and 4) extensible. Fontvariants were one step in that direction, but I recognise that it's not a complete solution by any means.
when i have to deal with that i just define another typeface: \definetypeface[blabla-normal] ... \definetypeface[blabla-condensed] ... \definetypeface[blabla-whatever] ... Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi fonTeXters, I have incorporated your suggestions to storm-font-support: A) --------------- Adam Lindsay wrote:
Okay, I noticed a second thing, in the [serif][cond][size] and other [size] typescripts: you define things like \tfc with the intention of "typeface-condensed". This will interfere with people who rely on the
and Hans Hagen wrote:
when i have to deal with that i just define another typeface:
\definetypeface[blabla-normal] ... \definetypeface[blabla-condensed] ...
I split Lido font to 1) Lido 2) Lido-Condensed B) ---------------- Adam Lindsay wrote:
A general suggestion--you might experiment with the [special] typescripts in type-spe as a way of loading the mathcollections.
Incorporated, so \input t-math-sto.tex \usemathcollection[storm] is no more needed; just e.g. \useencoding[st1] \useencoding[st3] \usetypescriptfile[t-type-slido] \usetypescript[Lido][st2] \setupbodyfont[Lido,10pt,rm] C) -------------------- Hans Hagen wrote:
Taco Hoekwater wrote:
Patrick, my vote is against a separate interface for this. Perhaps split the stuff at modules.cg.net into modules/fonts/docs/packages subtrees, but I really like the 'central repository' idea.
the only thing about user typescripts and modules is that we need to make sure that names don't clash; so for instance, a user typescript can be something
t-type-xxx.txx
OK, I changed all typescripts in this way. But still there are some files that do not fit this concept: a) redistributed files (storm.map, slido.map, stormex.enc) b) enco-*.tex files since \useencodings has not enabled loading t-enco-*.tex yet (something like \useencoding[t][st1]). D) ----------------------- Adam Lindsay wrote:
it could be a way of supporting an encoding like TS1, if people really still cared about that.
TS1 is texnansi??? Why ec (=st1) is not sufficient? You can setup regime... If you persuade me I will prepare some enco-st4.tex(??) = texnansi for storm fonts. Patrick Gundlach wrote:
If you think of a clever way, please tell me where/how to put your typescripts + .. on garden. I could even add a new section: fonts.contextgarden.net if this sounds appropriate for collecting stuff like yours.
I think it is a good idea. So please... After that I will write some words or two about the package and upload you the files. Is it OK? G) ------------------------- Examples of mathbold (where bold font is available) were added to the catalog. F) ------------------------- Some bug fixes namely in t-type-slido.tex and t-type-sbiblon.tex. Upgraded version is available from http://typokvitek.com/stormcontext/index.html Vit
Vit Zyka said this at Wed, 20 Apr 2005 17:59:37 +0200:
D) ----------------------- Adam Lindsay wrote:
it could be a way of supporting an encoding like TS1, if people really still cared about that.
TS1 is texnansi??? Why ec (=st1) is not sufficient? You can setup regime... If you persuade me I will prepare some enco-st4.tex(??) = texnansi for storm fonts.
Sorry, that was actually an under-specified suggestion to take your clever solution to the ConTeXt group at large. TS1 is the LaTeX-driven TeX Companion encoding, designed to live beside EC, to handle glyphs and punctuation missing in the EC encoding. For those trying to follow along, Vit came up with a clever application of the \Var[] construct to be able to switch over to an expert font/ alternative encoding. I saw a more general application in the TS1 encoding, if there was a demand for it. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
participants (4)
-
Adam Lindsay -
Hans Hagen -
Patrick Gundlach -
Vit Zyka