- dev-context - NTG Mailing Lists

pdfetex 1.30.4 binaries for linux-64
by Taco Hoekwater 17 Nov '05

17 Nov '05

I compiled 1.30.4 this morning on our amd64 machine: http://tex.aanhet.net/temp/pdfetex-linux-64.zip Cheers, Taco

1 0

\sqrt in expansions bug
by Taco Hoekwater 16 Nov '05

16 Nov '05

Hi, Macros that use \doifnextcharelse should all be defined as \unexpanded, to prevent errors like: \expanded{$\sqrt 2$} Also affected are: \decrement \increment maybe there are others, but these were easy to spot because they were single-line \def's. The \sqrt is painful, because it is likely to appear in \write-s Cheers, Taco

2 1

Re: [NTG-context] font problems again
by Adam Lindsay 15 Nov '05

15 Nov '05

[changed to dev-context] Hans Hagen said this at Mon, 14 Nov 2005 00:07:44 +0100: >lucida is a special case -) > >because i used lucida a lot, those definitions ended up in the core, but >when i bought more and more fonts, i finally decided to move the lucida >defs to the type-buy.tex typescript because that;s where they belong > >you can add the line: > > \usetypescriptfile[type-buy] > >to the cont-sys.tex file, but best is (because it's a document property) >to say in you document (or style): > >\usetypescriptfile[type-buy] % loads commercial font definitions >\usetypescript[lucida][texnansi] % defines a lucida typeface >\setupbodyfont[lucida,12pt] % enables the typeface defined as >'lucida' That reminds me, Hans. The PCTeX edition of Lucida are floating around. I've done some preliminary typescripts, and they seem to fit in well. I need to track down some issues with obscure math characters (making them match CM math), figuring out if the discrepancy is in the current math- lbr definitions, or in changes with the new fonts. Other than that, what should the definitions be called? \starttypescript[lucidanew]? doing an override in type-dis? Cheers, adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

3 4

\belowdisplayshortskip
by Taco Hoekwater 14 Nov '05

14 Nov '05

Hi, ConTeXt initializes the \belowdisplayshortskip to zero point. I believe this is wrong, it should be equal to \belowdisplayskip: the fact that the line above the display is short shouldnt affect the typesetting that follows the display. For the moment, I've fixed it by: \everydisplay {\belowdisplayshortskip=\belowdisplayskip } Taco

2 5

\uncompressedlist macro
by Taco Hoekwater 14 Nov '05

14 Nov '05

Hi Hans, Can you perhaps put this macro in the core somewhere? It is the inverse of \compresslist. Cheers, Taco (In the collector, this is item #21) % ----------------------------------------------------------- %D \macros {uncompresslist} %D %D When given a list like \type{1,4-7,9} as argument, this macro %D will store the expanded commalist in \type{\uncompressedlist}. %D %D \startbuffer %D \def\MojcaHasToDoTheTasks[#1]#2% %D {{\uncompresslist[#1]% %D \def\processitem##1{I have to do ##1 #2\par}% %D \processcommacommand[\uncompressedlist]\processitem}} %D %D \MojcaHasToDoTheTasks[1-4,7,9-11]{until tomorrow} %D \stopbuffer %D %D Here is an example of how to use \type{\uncompresslist}: %D \typebuffer %D %D The output of this is: %D %D \getbuffer \def\uncompresslist[#1]% {\let\uncompressedlist\empty \def\docompressedlistitem##1-##2-% {\@EA\dorecurse\@EA {\the\numexpr 1+##2-##1\relax}% {\@EA\appendtocommalist\@EA {\the\numexpr ##1-1+####1\relax}\uncompressedlist }}% \def\douncompresslist##1% {\doifinstringelse{-}{##1} {\docompressedlistitem##1-} {\appendtocommalist{##1}\uncompressedlist}}% \processcommalist[#1]\douncompresslist } % -----------------------------------------------------------

2 2

Re: announce list (licenses)
by Taco Hoekwater 11 Nov '05

11 Nov '05

Hi Guys, As keeps on happening whenever this licensing stuff comes up, I've been reading licenses again. After a lot of browsing, there are two license types I personally really like: * BSD(-style) license (mostly because of their amazing shortness, but that also has a downside) * Artistic(-perl) license (because the text is rather readable and at least it makes an attempt at quality control/maintaining reliability) What follows is one example of each (because tiny variations do occur), maybe one of them is acceptable or perhaps, if not, usable as a starting point for a "do it yourself" license? Cheers, Taco BSD Style: ======================= Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ========================= Artistic License: ========================== The "Artistic License" Preamble The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications. Definitions: * "Package" refers to the collection of files distributed by the Copyright Holder, and derivatives of that collection of files created through textual modification. * "Standard Version" refers to such a Package if it has not been modified, or has been modified in accordance with the wishes of the Copyright Holder. * "Copyright Holder" is whoever is named in the copyright or copyrights for the package. * "You" is you, if you're thinking about copying or distributing this Package. * "Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.) * "Freely Available" means that no fee is charged for the item itself, though there may be fees involved in handling the item. It also means that recipients of the item may redistribute it under the same conditions they received it. 1. You may make and give away verbatim copies of the source form of the Standard Version of this Package without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers. 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domain or from the Copyright Holder. A Package modified in such a way shall still be considered the Standard Version. 3. You may otherwise modify your copy of this Package in any way, provided that you insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following: a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as ftp.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package. b) use the modified Package only within your corporation or organization. c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version. d) make other distribution arrangements with the Copyright Holder. 4. You may distribute the programs of this Package in object code or executable form, provided that you do at least ONE of the following: a) distribute a Standard Version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get the Standard Version. b) accompany the distribution with the machine-readable source of the Package with your modifications. c) accompany any non-standard executables with their corresponding Standard Version executables, giving the non-standard executables non-standard names, and clearly documenting the differences in manual pages (or equivalent), together with instructions on where to get the Standard Version. d) make other distribution arrangements with the Copyright Holder. 5. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. 6. The scripts and library files supplied as input to or produced as output from the programs of this Package do not automatically fall under the copyright of this Package, but belong to whomever generated them, and may be sold commercially, and may be aggregated with this Package. 7. C or perl subroutines supplied by you and linked into this Package shall not be considered part of this Package. 8. The name of the Copyright Holder may not be used to endorse or promote products derived from this software without specific prior written permission. 9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. The End ===========

1 0

Re: [NTG-context] bib module: \setupcite macro
by Taco Hoekwater 09 Nov '05

09 Nov '05

Hi Hans, Can you please give me some info on this? (resent from a mail I sent last two weeks ago) Cheers, Taco _________________________________ Idris Samawi Hamid wrote: > Another issue: > > My definition for \citeyear crashes. This used to work-) First: this problem is caused by the fact that year citations are by default uncompressed. if year compression is turned on, then different code is used, and the problem never happens. ------- I've made a change to the representation of authors (there is now one or two extra sets of braces around each author), and this causes the crash. It turns out to be a problem with the core macro \addtocommalist, that I don't know how to fix. Minimal demonstration of problem/bug: \def\acommalist{} \addtocommalist{{stuff with braces}}\acommalist Q for Hans: The way my data representation is written now, I need to be able to add the following three types of elements as well as stuff without braces: {author} % stands for one author {authora},{authorb} % stands for two authors {authora},{} % stands for author et. al. is that doable eventually, or should I implement another presentation altogether? Cheers, Taco

2 3

bug in the new release (typo) and question
by Taco Hoekwater 01 Nov '05

01 Nov '05

Hi Hans, There is an extra 'j' left in this line: ========================================= diff -r scripts/context/ruby/base/tex.rb 1125c1139 < system("xdv2pdf #{File.suffixed(jobname,'xdv')}") --- > system("xdv2pdf #{File.suffixed(jrawname,'xdv')}") ========================================== And is this right? It looks like you removed a bugfix or feature: =========================================== diff -r tex/context/base/core-not.tex 712,717c729,730 < \ifx\lastnotesymbol\relax < \unskip < \gotobox{\dodonotesymbol\currenttextreference}[#2]% < \else < \lastnotesymbol < \fi --- > \unskip > \gotobox{\dodonotesymbol\currenttextreference}[#2]% =========================================== Taco

2 2

[Fwd: [tex-live] mptopdf bug?]
by Taco Hoekwater 30 Oct '05

30 Oct '05

-------- Original Message -------- Subject: [tex-live] mptopdf bug? Date: Sat, 29 Oct 2005 09:38:19 +0800 From: Chunyu Wang <chunyu(a)db.cs.hit.edu.cn> To: tex-live(a)tug.org When I run the command 'mptopdf xx.mp', it'll complain 'can't find context.fmt'. The parameters of pdfetex in line 104 should be changed, place -fmt ahead of -progname. diff -c "c:/free_ware/texlive2005/texmf-dist/scripts/context/perl/mptopdf.pl-orig" "c:/free_ware/texlive2005/texmf-dist/scripts/context/perl/mptopdf.pl" *** c:/free_ware/texlive2005/texmf-dist/scripts/context/perl/mptopdf.pl-orig Sat Oct 29 09:32:17 2005 --- c:/free_ware/texlive2005/texmf-dist/scripts/context/perl/mptopdf.pl Sat Oct 29 09:32:32 2005 *************** *** 101,107 **** { if ($miktex) { $command = "pdfetex -fmt=mptopdf" } else ! { $command = "pdfetex -progname=context -fmt=mptopdf" } if ($dosish) { $command = "$command \\relax $file" } else --- 101,107 ---- { if ($miktex) { $command = "pdfetex -fmt=mptopdf" } else ! { $command = "pdfetex -fmt=mptopdf -progname=context" } if ($dosish) { $command = "$command \\relax $file" } else Diff finished. Sat Oct 29 09:32:47 2005 -- Harbin Institute of Technology, China. Wang Chunyu. _______________________________________________ TeX Live mailing list http://tug.org/mailman/listinfo/tex-live

3 2

Options that will work for blocking this spammer.
by Brooks Moses 26 Oct '05

26 Oct '05

Hello, all: Clearly, fixing the damage and waiting for the spammer to go away just isn't working. The following things, in my opinion, will most likely work. I don't know which of them are possible within the MediaWiki software, however, so I'm listing everything I can think of that seems plausible. Most of them only fix this one spammer, though, not the problem in general -- but it seems that we've only had this one really problematic spammer in two years, so maybe it's enough. * Block all edits that contain "<div ...>" tags. All of these do -- they're all using a "<div ...>"-tag block to hide links invisibly on the page. (Many of them have left out the links, but nearly all of them have included the tag.) * Set things so that all of Musa8's edits (as tracked by username) get ignored rather than actually applied. * Block the five dozen or so IP addresses that he's using. (This is a temporary solution.) * Protect the two dozen Wiki pages that he's changing -- he keeps changing the same ones, not randomly-chosen ones. (This, again, is a temporary solution.) * Put in an "are you human?" test for all anonymous users, and for all logged-in users who haven't been approved by the site admins. (Something like one of the "type in the numbers in this warped image" things that some sites have.) * Change the edit page urls from "&action=edit" to "&action=editpage". My guess is that this person is using an automatic script that's aimed at bunches of MediaWiki sites, and changing the url will break his script, and he's unlikely to change it just for one site. (This trick works pretty well for weblog spam, apparently.) Meanwhile, is there a community of MediaWiki users somewhere that we can talk to about this? I'd guess that this spammer has been hitting other sites pretty hard too, and there are probably lots of other people working on figuring out good solutions to this.... - Brooks P.S. Someone came through and put in a couple of "real" edits to the "Russian" page. I've made backups of the updated page so it can be re-updated after Patrick reverts things to an old backup of the site.

3 3