- dev-context - NTG Mailing Lists

cont-xx.xml translating
by Ark Shraer 26 Jul '06

26 Jul '06

Hello, I'd like to start translate cont-en.xml and keys-en.xml into russian. I looked at other translations and in the mailing list archives but it still unclear for me what to translate in these files? I have a several questions (if it's isn't annoying :) 1. Is there a common rule of what tags to translate? 2. What the meaning of cont-xx.xml and keys-xx.xml? 3. Some terms are unclear. How can I know the meaning of them (e.g. "quote" and "quotation", "intermezzo", "hfactor") in ConTeXt context :) ? 4. "setupbodyfont" -- spaces in translation must be omitted also? 5. How can I test my translation in my environment first? Thats all. Excuse me for that storm of questions :) Cheers, Arkady

5 7

wrong paper orientation with pstopdf
by Mojca Miklavec 24 Jul '06

24 Jul '06

Hello, Hans, Do you remember some strange 90 degrees rotation in the gnuplot module? I thougt that gnuplot did a strange job, but now I found out that it was indeed pstopdf's fault. The option -dAutoRotatePages=/None should be either removed or changed somehow, otherwise landscape figures rotate for 90 degrees, which is wrong. Mojca

3 11

My way on matharrows
by Aditya Mahajan 21 Jul '06

21 Jul '06

Hi, I am attaching myway on using matharrow. Are there any suggestions before I release it to public? I found some surprises while making this my way. 1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons. 2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to \definematharrow [xmapsto] [3599] [\mapstofill] Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar. Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts? I could not correct leftrightharpoons. Why does this not work? \definematharrow [xleftrightharpoons] [3395,3359] [\leftharpoonupfill,\rightharpoondownfill] \starttext \math{\xleftrightharpoons} \stoptext Aditya

4 30

Re: [dev-context] My way on matharrows
by Mojca Miklavec 21 Jul '06

21 Jul '06

On 7/21/06, Aditya Mahajan wrote: > On Thu, 20 Jul 2006, Hans Hagen wrote: > > > Aditya Mahajan wrote: > >> On Wed, 19 Jul 2006, Taco Hoekwater wrote: > >> > >>> Aditya Mahajan wrote: > >>>> None of the extensible arrows work with antykwa-torunska as \relbar is > >>>> not of fixed width in that font. Are there any other free math fonts that > >>>> I should check? > >>> > >>> iwona and kurier have math nowadays, don't they? > >> > >> Tested for iwona and it works fine. I do not know how to get kurier to work > >> (I was looking at typescripts defined in type-exa and kurier is not there). > >> > > \usetypescript[iwona] [texnansi] > > \usetypescript[kurier][texnansi] > > Kurier typeface is not defined anywhere! The following definition should be > part of type-exa.tex Hans also had some fancy definitions some time ago to define a whole large family of typescripts (designed esp. for Iwona). I don't know where they are now (might be part of distribution, but I didn't look closely enough), but it might be that I forgot to insist enough to add kurier definitions as well. The fonts improve constantly, so some definitions tend to be forgotten in typescripts. > --------------------------------------%<-------------------------------------- > \starttypescript [kurier-light,kurier,kurier-medium] [texnansi,ec,8r,uc,t2a] > > % todo: rscale > > \definetypeface[\typescriptone][ss][sans] [\typescriptone] [default][encoding=\typescripttwo] > \definetypeface[\typescriptone][rm][serif][modern] [default][encoding=\typescripttwo] > \definetypeface[\typescriptone][tt][mono] [modern] [default][encoding=\typescripttwo] > \definetypeface[\typescriptone][mm][math] [\typescriptone] [default][encoding=\typescripttwo,text=ss] > \stoptypescript > --------------------------------------%<-------------------------------------- > > Also, why not add all iwona variants to \starttypescript for iwona. I agree. > --------------------------------------%<-------------------------------------- > \starttypescript [iwona-light,iwona,iwona-medium,iwona-heavy,iwona-light-cond,iwona-cond,iwona-medium-cond,iwona-heavy-cond] [texansi,ec,8r,uc,t2a] > --------------------------------------%<-------------------------------------- Mojca

1 0

messages
by Vit Zyka 21 Jul '06

21 Jul '06

Hi, I have done some corrections of the Czech section of messages in x-set-11.tex. Coding is UTF-8. Please can you incorporate it to distro? Then I have some related questions: 1. ma-cb-en uses \shortsetup{placeblock} but AFAICS 'placeblock' (and for ma-cb more interesting 'placetable' too) is not defined somewhere. Will the definition be added or we will not use it in the manual? 2. What is the origin of interface/cont-??.xml ? It is prepared manually or somewhat generated? Thank you Vit

1 0

Re: [NTG-context] What about dynamic documentation?
by Taco Hoekwater 20 Jul '06

20 Jul '06

Hi Jérôme, > However, this seems rather far from the pdf manuals and does not really > help a newbie as I am. Definately it could be improved. In IT, almost everything is suboptimal starting the second after it's birth. Perhaps we should continue this discussion on the developers list, dev-context(a)ntg.nl? It is likely we will spend some other mails on this subject, and perhaps it is better not to clutter the general list. Anybody willing to discuss/help out can easily subscribe to that list (even if just for a while). Is that OK? > More precisely: > > 0 - Category search is missing. It is well known that searching by > contents or by command name won't give the proper result if the search > request is not well formed a priori. > Each command should have a list of associated key words, allowing smart > navigation and filtering > For example, the sectionning commands (including toc, headers and so on) > could be gathered in one big category. That could be as simple as allowing users / viewers to attach one or two key words/categories to the current commands, I think. There can be a predefined set of those, and there will not be all that many. It could also easily be backported to the XML data. Patrick? > 1 - The examples oftenly need output to let the user really understand > the effect. > Moreover, the information available in the graphical output is more > obvious thus more efficient. Perhaps the examples could be fed through the Live ConTeXt, just like the wiki examples? > 2 - Missing code template(s) to paste into the source, copy/paste does > noot help when really needed. Of course, I can grab them from > contextgarden but it is there both hidden and not well formatted. I am not sure what you mean. > 3 - The description only concerns the command. > Each key should also have its own description. Yes. > Each predefined value should also have its own description. Also yes. (both have been discussed before but never implemented due to lack of manpower). > Then the user interface can provide a layout a la headerdoc or some kind > of rollup tooltips. > > 4 - The data storage model for a size range seems weird. The range 5pt > ... 12pt is coded with an ordered list of 3 values "5pt" '..." and > "12pt" whereas it means an unordered list of 8 values: "5pt", "6pt", > ..., "12pt". This latter data model obviously turns into a pop up button > with a list of sizes. It is even a bit weirder. "5pt ... 12pt" usually stands for "any font size that is already defined using \definebodyfont". Except on the command itself, of course. There it means: "any font size you wish to define for use in the other commands that use 5pt ... 12pt". I'm smiling as I write this :-) It really should be an abstract type, like "cd:dimension" instead of those three values. > 5 - The command variants might need specials (eg \setupinterlinespace). Yes, the current solution for that command is not very nice. But there are more than a few commands with such variant calling conventions, and it is hard to come up with a nice-looking solution. Suggestions for solutions are welcome. > 6 - Sometimes the acceptable values depend on the context (eg arguments > of \ref), it means that all the relevant information is not static and > the data model should provide some entry points. But at first glance > this is a very advanced feature which cost might be unaffordable. You mean crossover functionality with reftex/auctex style programs? Would be nice to have I assume, but hard to do portably, and not really worth the effort if it cannot be done in a portable manner. (always speaking from my point of view, of course. YMMV) > Finally, it seems that the underlying data model needs more entropy. Thermodynaics says it will probably move in the right direction, once it starts moving ;-) Cheers, Taco

3 8

CSV, alpha 2 ;)
by Mojca Miklavec 19 Jul '06

19 Jul '06

Hello, Hans and Taco (once you're back), http://pub.mojca.org/tex/csv/ has the new version of the documentation for the database module, but it's still a bit buggy. Please forget about "feature requests" at the end of the document, they're there just for the guidelines about what could also be useful. There are still some bugs appearing (problems with UTF were introduced recently); a funny thing is also that if I redefine the font encoding to be EC instead of texnansi (I don't understand why texnansi is used by deafault, but I don't really mind), the resulting characters in "Taco's mode" are different (wrong in both cases anyway). "Hans's mode" doesn't compile if utf-8 characters are present. The following definition has to be fixed: \def\setupseparatedlist {\dodoubleempty\dosetupseparatedlist} \def\dosetupseparatedlist[#1][#2]% {\getparameters[\??ls#1][#2]} And if you manage to figure out what's going wrong with \showsetups{startseparatedlistname} \showsetups{processseparatedfile} and with the very last example with TSV, I would be very grateful as well. These are probably my mistakes somewhere, but I don't know where I did a (probably stupid little) mistake. What's the default behaviour with \inmargin inside \placefloat? I guess that that is or should be forbidden, but how can I place something "marginal" next to the float? (I have some other "\marginal" questions, but that's a topic for another mail.) Mojca

4 10

alpha release
by Hans Hagen 19 Jul '06

19 Jul '06

I uploaded an alpha with the discussed patches - math - module - font fix (we need to figure out a name scheme for the additional setup files, maybe math-ext-en.xml and alike) 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 -----------------------------------------------------------------

2 2

Re: [dev-context] [NTG-context] strange font switching (bug?)
by Taco Hoekwater 18 Jul '06

18 Jul '06

Hi, Mojca Miklavec wrote: > Hello, > > can anyone explain this weird behaviour? The accents on the second Just for debug information, this helps: --- \def\xxdododefinefont#1#2#3#4% \autofontsizetrue is set by calling routine {\edef\lastfontidentifier{#3}% - \ifcsname\newfontidentifier\endcsname\else + \iftrue \def\localrelativefontsize{#1}% \def\localabsolutefontsize{#2}% \parsefontspec{#4}\newfontidentifier \let\localrelativefontsize\defaultrelativefontsize % not needed \fi \csname\newfontidentifier\endcsname \autofontsizefalse \ifskipfontcharacteristics \else \setfontcharacteristics \the\everyfontswitch \fi} --- > page are broken (setting bodyfont to 7pt at the beginning works OK and > using other sizes works as well.). > > \setupbodyfont[8pt] > > \startsetups{img} > \switchtobodyfont[7pt] > \stopsetups > > \starttext > \ccaron\scaron\zcaron > \page \setups{img} > \ccaron\scaron\zcaron > \stoptext > > Thank you very much, > Mojca > _______________________________________________ > ntg-context mailing list > ntg-context(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-context

2 1

Re: [dev-context] [NTG-context] align question
by Aditya Mahajan 18 Jul '06

18 Jul '06

On Mon, 17 Jul 2006, Hans Hagen wrote: > Bruce H. Wagner wrote: >> >> >> Incidentally, the reason I am using the LaTeX syntax is that we are >> translating LaTeX code into Context automatically using a perl script, and >> it's therefore much easier to stick to whatever LaTeX code works. >> Basically, I just want something comparable to the array environment in >> LaTeX, which works very nicely. >> > Aditya is in more or less charge of the specification/tryout part of the math > extensions and taco/myself implement things based on that input, so i suggest > that the two of you come up with specs Hans and Taco, I have been using Taco's mathfix for some time now and have not encountered any problem. Taco had implemented two of my requests i) style=\textstyle or \displaystyle for matrix and ii) location=top|bottom for matrix. I think that these can be added to the core. However, I am not sure about the notation. I had requested for location=top|bottom (thinking in Latex terms) but I now think that the Context way to name it is low|high. Taco had also provided a bugfix for breaking multiline formula across pages. There are some minor glitches with it. Taco, do you have time to look into those? Aditya

2 1