- dev-context - NTG Mailing Lists

encodings
by Hans Hagen 08 Sep '05

08 Sep '05

Hi, I added a new command \showpatterns which produces a table of loaded patterns; btw, czech and polish need testing since we move to latin modern exclusively (pl0 an il2 are only used for plr and csr fonts so we may as well drop loading patterns for these encodings; user can use regimes which will then map onto qx and ec) 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 -----------------------------------------------------------------

1 0

[Fwd: Re: [dev-context] Re: [NTG-context] new beta]
by Hans Hagen 08 Sep '05

08 Sep '05

1 0

Wiki Text Problems.
by Brooks Moses 07 Sep '05

07 Sep '05

(Taking Taco's suggestion, and mentioning this here rather than trying to converse on the Wiki's talk pages.) Patrick, Mojca, Taco, and other Wiki-people: The rendered text on the Wiki has suddenly become ugly -- letters are thinner (too thin!), and the edges of the text are a bit ragged. My guess is that this is a result of the interaction between anti-aliasing and setting the transparency to true -- everything that was anti-aliased to gray is now also set transparent, and thus becomes white when displayed. I don't know if this is browser-dependent or not, but it's repeatable in both Opera and Firefox, on my (Windows) computer. Given this problem, I would recommend reverting to the non-transparent version. - Brooks

4 12

Re: [NTG-context] Some concerns about the ConTeXt license.
by Taco Hoekwater 06 Sep '05

06 Sep '05

Hi Brooks, Are you on the dev-context(a)ntg.nl list? If not, would you please subscribe? It would make communication about the contextgarden stuff easier ('talking' through the wiki's Talk pages is not optimal), and also the user mailing list is quite large and most people on it are beginners who should probably not be bothered with technical / development things too much. Is that ok? On the license: I believe the context license should essentially be the LPPL, and the two reasons why it is not currently are: 1) there was no usable LPPL when context first became public 2) Hans and I are unhappy with the word "LaTeX" in the name. Cheers, Taco

3 3

[Fwd: Re: LMs 0.99.0, i.e., 0.99.1]
by Hans Hagen 01 Sep '05

01 Sep '05

Hi, The latest latin modern ... shouldn't we make tfm's for our new dense encodings? 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 -----------------------------------------------------------------

3 3

Re: [NTG-context] Suitable mechanism for Theorems and Definitions
by Taco Hoekwater 30 Aug '05

30 Aug '05

Hans, Be careful. This hack makes the command parse for yet another set of brackets, and that might break existing documents when implemented as default. Taco Hans Hagen Outside wrote: > Taco Hoekwater wrote: > >> >> Hi David, >> >> Not sure if you are still interested, but here is my "optional title" >> hack, revamped for a modern context distro. It creates a second >> extra optional argument for the enumeration, nothing too fancy. >> The example also shows a way in which you can access the number. >> >> This does not solve the list generation, sorry. > .... > ok, i can cook up something along these lines > Hans

2 1

Re: kannadaTeX
by Hans Hagen Outside 29 Aug '05

29 Aug '05

shiva shankar shankar wrote: > Dear sir, > > We have kannadaTeX/LaTeX for kannada language. Please tell me > how to enable the kannada language in conTeX. > > For this language we have for different shapes of fonts "regular", > "slant", "bold" and "bold and slant". > We have hyphenation patterns for kannada language. > > How can i make kannada as default in ConTeX and it should also use > kannada hyphenation patterns. > - what fonts are used? - what name does the hyphenation file have? take a look at the lang-*.tex files (e.g. lang-ger.tex) it's probably rather easy to do 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 -----------------------------------------------------------------

3 3

verb-xml.tex patch
by Taco Hoekwater 28 Aug '05

28 Aug '05

Hi Hans (and others), First, here is a small patch for verb-xml that fixes some wrong highlighting within attribute values, for the equals sign and the semicolon. Spotted by Mojca. Second, it would be nice if you could extend the \setuptyping command in such a way that the special handlers can receive options themselves (see the thread about namespaces). Something like this would be cool: \setuptyping[XML][option=namespaces] % doesn't work This does not work, because it is an 'unknown' option, and therefore it is treated as a pretty handler. And an undefined pretty handler at that, so the highlighting reverts to TEX style. In fact, \setuptyping[XML][option=JS] makes \startXML behave like \startJS, which is cute but somewhat silly ;-) I know I could easily create a verb-namespaces.tex, but it would be much nicer to have these really small options in-lined (also for things like visible spaces etc.). Is that doable? Cheers, Taco

1 0

Re: [NTG-context] ec encoding and tcaron
by Mojca Miklavec 24 Aug '05

24 Aug '05

Adam Lindsay wrote: > Am I right in thinking the > main array in pdfr-ec maps from slots in the encoding to the unicode > code point? Is there anything else I need to be mindful of? According to the Adobe specification <http://partners.adobe.com/public/developer/en/acrobat/5411.ToUnicode.pdf> both existing pdfr-* files already violate at least one of the following two requirements: /CMapType 2 def ... 1 begincodespacerange <0000> <FFFF> endcodespacerange You can either define a range (for example for A-Z, 0-9, ...) or single characters. Mojca

2 2

Euro-letter encoding (was: Dense Encoding)
by Adam Lindsay 22 Aug '05

22 Aug '05

Hans Hagen said this at Sun, 21 Aug 2005 18:36:21 +0200: >so the advised font encodings will be: texnansi, qx, t5, dense Okay, thinking about it, dense isn't a great name, either. Just about all the 8-bit encodings are dense--they're just dense with different stuff. So with that in mind, I present euro-letters: <http://homepage.mac.com/atl/tex/euro-letter.pdf> <http://homepage.mac.com/atl/tex/euro-letter.zip> In the course of things, I found that for whatever reason, the unic-030 (VN) vector was off by two slots. I added [ST]commaaccent to enco-uc (should be in enco-def, too) and unic-002. The key files, however, are enco-el.tex and eurolett.enc. The tester file was brought to life simply by installing: texfont --ma --in --ve=public --co=lm --so=auto --en=eurolett \ --pat="lmvtt*" Please run with normal text--anything you can get your hands on. I am nearly a monoglot, and don't have a lot of stuff lying around that would actually put this stuff to the test. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

4 8