From rdt at cs.queensu.ca Sun Dec 1 18:07:35 2013 From: rdt at cs.queensu.ca (Bob Tennent) Date: Sun, 1 Dec 2013 12:07:35 -0500 Subject: [tex-live] dvipdfmx warnings Message-ID: <529b6cd7.g7x1RIpE2W+rjNLt%rdt@cs.queensu.ca> When processing a file with document options [dvipdfmx,legalpaper,landscape] using latex -> dvipdfmx, I'm getting warning messages from dvipdfmx as follows ** WARNING ** Unparsed material at end of special ignored. Current input buffer is -->! /landplus90 true store<-- The PDF output is fine but the messages are annoying. How can I turn them off (without losing the rest of the console output)? There are -v and -vv options for increasing the verbosity, but no option that I can see for reducing it. And I suspect that they shouldn't be output at all. Bob T. From rdt at cs.queensu.ca Sun Dec 1 21:15:46 2013 From: rdt at cs.queensu.ca (Bob Tennent) Date: Sun, 1 Dec 2013 15:15:46 -0500 Subject: [tex-live] dvipdfmx warnings Message-ID: <529b98f2.FO02+KehmUgdKVn+%rdt@cs.queensu.ca> > When processing a file with document options > [dvipdfmx,legalpaper,landscape] using latex -> dvipdfmx, I'm getting > warning messages ... It seems the solution is to use \usepackage[driver=dvipdfm]{geometry} Bob T. From jfbu at free.fr Sun Dec 1 22:55:04 2013 From: jfbu at free.fr (jfbu) Date: Sun, 1 Dec 2013 22:55:04 +0100 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <529b98f2.FO02+KehmUgdKVn+%rdt@cs.queensu.ca> References: <529b98f2.FO02+KehmUgdKVn+%rdt@cs.queensu.ca> Message-ID: <76CCB598-9C0B-4EB9-B36E-8967F78975D7@free.fr> Le 1 d?c. 2013 ? 21:15, Bob Tennent a ?crit : >> When processing a file with document options >> [dvipdfmx,legalpaper,landscape] using latex -> dvipdfmx, I'm getting >> warning messages ... > > It seems the solution is to use > > \usepackage[driver=dvipdfm]{geometry} > > Bob T. I used this kind of set-up when I wanted to have both dvipdfmx and pdflatex routes for a given source, where \ifwithdvipdfmx is a document boolean (or rather something set in a driver file) \makeatletter \ifwithdvipdfmx \@for\@tempa:=hyperref,bookmark,graphicx,xcolor\do {\PassOptionsToPackage{dvipdfmx}\@tempa} % \PassOptionsToPackage{dvipdfm}{geometry} \PassOptionsToPackage{bookmarks=true}{hyperref} \PassOptionsToPackage{dvipdfmx-outline-open}{hyperref} \PassOptionsToPackage{dvipdfmx-outline-open}{bookmark} % \def\pgfsysdriver{pgfsys-dvipdfm.def} \else \PassOptionsToPackage{bookmarks=true}{hyperref} \fi \makeatother this is before the loading of the packages Regards Jean-Francois From rdt at cs.queensu.ca Sun Dec 1 23:09:57 2013 From: rdt at cs.queensu.ca (Bob Tennent) Date: Sun, 1 Dec 2013 17:09:57 -0500 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <049DCF46-B851-48AD-8FDA-933A97696F2D@wideopenwest.com> References: <529b98f2.FO02+KehmUgdKVn+%rdt@cs.queensu.ca> <049DCF46-B851-48AD-8FDA-933A97696F2D@wideopenwest.com> Message-ID: <529bb3b5.GtOkrJ86QJUw4e9+%rdt@cs.queensu.ca> >|> It seems the solution is to use >|> >|> \usepackage[driver=dvipdfm]{geometry} >|> >|The geometry package can test for latex, pdflatex, xelatex (and >|lualatex?) but if you are using latex it has no way of ``knowing'' what >|backend processing is going to be used to go from dvi->pdf; the default >|it uses is dvips->... since that is the most common path. So for any other >|backend processing you have to explicitely tell geometry what to use. Hi Herb. Other packages (hyperref, graphicx) seem to be able to figure it out witthout an explicit option, presumably from the global option. Also, it is somewhat confusing that sometimes one must use dvipdfmx and sometimes one must use dvipdfm and sometimes either will do. It doesn't help that there is not even a man page for dvipdfmx. I sent my complaint here because there seemed to be no other suitable venue. Best, Bob T. From zdenek.wagner at gmail.com Sun Dec 1 23:39:04 2013 From: zdenek.wagner at gmail.com (Zdenek Wagner) Date: Sun, 1 Dec 2013 23:39:04 +0100 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <529bb3b5.GtOkrJ86QJUw4e9+%rdt@cs.queensu.ca> References: <529b98f2.FO02+KehmUgdKVn+%rdt@cs.queensu.ca> <049DCF46-B851-48AD-8FDA-933A97696F2D@wideopenwest.com> <529bb3b5.GtOkrJ86QJUw4e9+%rdt@cs.queensu.ca> Message-ID: 2013/12/1 Bob Tennent : > >|> It seems the solution is to use > >|> > >|> \usepackage[driver=dvipdfm]{geometry} > >|> > >|The geometry package can test for latex, pdflatex, xelatex (and > >|lualatex?) but if you are using latex it has no way of ``knowing'' what > >|backend processing is going to be used to go from dvi->pdf; the default > >|it uses is dvips->... since that is the most common path. So for any other > >|backend processing you have to explicitely tell geometry what to use. > > Hi Herb. Other packages (hyperref, graphicx) seem to be able to > figure it out witthout an explicit option, presumably from the > global option. Also, it is somewhat confusing that sometimes one > must use dvipdfmx and sometimes one must use dvipdfm and sometimes > either will do. It doesn't help that there is not even a man page > for dvipdfmx. I sent my complaint here because there seemed to be no > other suitable venue. > The packages can reliably recognize XeTeX, pdftex, luatex and can recognize whether PDF or DVI is being created. It cannot be recognized how you will process the DVI file later. (x)dvipdfm(x) understands some (but not all) postscript specials and some (but not all) pdftex specials. If the package assumes that DVI will be processed by dvips and emits only such specials that are understood by (x)dvipdfm(x), you get no error (my zwpagelayout does that). If the package may use a special that is understood by one DVI driver and not understood by another DVI driver, you have to specify which DVI driver you intend to use. > Best, > Bob T. -- Zden?k Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz From karl at freefriends.org Sun Dec 1 23:39:50 2013 From: karl at freefriends.org (Karl Berry) Date: Sun, 1 Dec 2013 22:39:50 +0000 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <529bb3b5.GtOkrJ86QJUw4e9+%rdt@cs.queensu.ca> Message-ID: <201312012239.rB1MdoT6032524@freefriends.org> It doesn't help that there is not even a man page for dvipdfmx. dvipdfm.1 is for both dvipdfm and dvipdfmx. I'll make the dvipdfmx.1 .so reference for next time. (And also update the bug mailing address, which is indeed the tex-live list now. ChoF et al. no longer had time to maintain it as of a couple years ago, so we have been babysitting it.) I can't solve the package problems. dvipdfm has been a symlink to dvipdfmx for years now, although (as I recall) there are a couple of small argv[0]-based behavior differences for the sake of compatibility. Unfortunately I don't remember what they are. Maybe someone else would like to look at the source (Build/source/texk/dvipdfm-x) and document it, the way it should have happened in the first place. The new directory name in the source is because Peter B and Khaled have merged dvipdfmx and xdvipdfmx for next year, so that is more documentation updates that should happen. Patches welcome ... Best, karl From roy.nico at free.fr Mon Dec 2 10:19:35 2013 From: roy.nico at free.fr (roy.nico) Date: Mon, 2 Dec 2013 10:19:35 +0100 Subject: [tex-live] Please tell me how to unsubscribe In-Reply-To: <201312012239.rB1MdoT6032524@freefriends.org> References: <201312012239.rB1MdoT6032524@freefriends.org> Message-ID: <529C50A7.7010506@free.fr> Thanks in advance From P.Taylor at Rhul.Ac.Uk Mon Dec 2 10:38:24 2013 From: P.Taylor at Rhul.Ac.Uk (Philip Taylor) Date: Mon, 2 Dec 2013 09:38:24 +0000 Subject: [tex-live] Please tell me how to unsubscribe In-Reply-To: <529C50A7.7010506@free.fr> References: <201312012239.rB1MdoT6032524@freefriends.org> <529C50A7.7010506@free.fr> Message-ID: <529C5510.8040909@Rhul.Ac.Uk> roy.nico wrote: > Thanks in advance You're welcome. 1) Press Ctrl-U or otherwise View Headers / View Source 2) Observe the line that reads : "List-Unsubscribe: , " 3) Follow one of the two suggested routes. Philip Taylor From preining at logic.at Mon Dec 2 13:06:24 2013 From: preining at logic.at (Norbert Preining) Date: Mon, 2 Dec 2013 21:06:24 +0900 Subject: [tex-live] [PATCH] tlmgr perltk gui: change order of filtering In-Reply-To: References: Message-ID: <20131202120624.GA4106@gamma.logic.tuwien.ac.at> Hi Ahmad, > Currently in tlmgr perltk gui, the selection filter doesn't have any > effect, because the text match does not pass through when the filter text > is empty (it has return 1 instead). > I've attached the patch for fixing the bug. Great, thanks. I will look into your patch as soon as possible and include it in the code after review. Great to hear that someone else but me is looking into the code of this mosnter ;-) Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From rdt at cs.queensu.ca Mon Dec 2 14:08:02 2013 From: rdt at cs.queensu.ca (Bob Tennent) Date: Mon, 2 Dec 2013 08:08:02 -0500 Subject: [tex-live] dvipdfmx warnings Message-ID: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> Jean-Francois: "\ifwithdvipdfmx is a document boolean" It seems using dvipdfmx as a document option doesn't create/set that conditional. But your post does list all (?) the packages affected by using dvipdfm(x) and thanks for that. This information should be in the dvipdfm documentation; otherwise how is a user to know that using dvipdfm may require an explicit option to those packages? Zdenek: "It cannot be recognized how you will process the DVI file later" Yes, but if the user provides dvipdfmx as a document option, the geometry package should be aware of the user's intention to use that processor. The hyperref package does. It seems dvipdfmx does the right thing when legalpaper,landscape are used. Wouldn't it be possible for it to suppress the frenetic but useless 3-line ** WARNING ** message it currently produces when the user forgets to add a driver option to the geometry package? Or even replace it by a hint to the user about what to do to prevent it? BTW, the reason I'm using dvipdfm is because it embeds type 2 (aka type 1C) fonts into the pdfs it generates, which significantly reduces the size compared to embedding type 1 fonts. Ideally pdftex and dvips would do the same, though I've been told pdftex is "frozen"; what about dvips? Bob T. From jfbu at free.fr Mon Dec 2 14:35:50 2013 From: jfbu at free.fr (jfbu) Date: Mon, 2 Dec 2013 14:35:50 +0100 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> References: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> Message-ID: <151512B9-AA96-4CA6-A48B-FECAA23951EB@free.fr> Le 2 d?c. 2013 ? 14:08, Bob Tennent a ?crit : > > Jean-Francois: "\ifwithdvipdfmx is a document boolean" > > It seems using dvipdfmx as a document option doesn't create/set that > conditional. But your post does list all (?) the packages affected Bob, I apologize for not having clearly stated that this \ifwithdvipdfmx was a user (me) created boolean; actually I create this boolean in another file, and then load the main file (which contains all the \PassOptionsToPackage things after the \documentclass) via an \input. I can then keep the main file unchanged and decide to compile it via latex+dvipdfmx or pdflatex Also: the packages listed in my message are the ones I experimentally figured to be in need to be properly set-up for dvipdfmx use, there may be others, the list proved sufficient for my use cases, perhaps some other packages I don't know about or not needed in my documents do need proper attention. Whenever I can, I use dvipdfmx as it produce systematically smaller pdf's, for some fonts the pdf size can be drastically improved, I have experienced going down from 700K to 200K, mostly I observe from 10% to 30% gain. One font which I cannot use with dvipdfmx is T1/txtt, when the document uses letters like ? or ? outside the 32-127 range. regards, Jean-Francois > by using dvipdfm(x) and thanks for that. This information should be > in the dvipdfm documentation; otherwise how is a user to know that > using dvipdfm may require an explicit option to those packages? > > Zdenek: "It cannot be recognized how you will process the DVI file > later" > > Yes, but if the user provides dvipdfmx as a document option, the > geometry package should be aware of the user's intention to use that > processor. The hyperref package does. > > It seems dvipdfmx does the right thing when legalpaper,landscape are > used. Wouldn't it be possible for it to suppress the frenetic but > useless 3-line > > ** WARNING ** > > message it currently produces when the user forgets to add a driver > option to the geometry package? Or even replace it by a hint to the > user about what to do to prevent it? > > BTW, the reason I'm using dvipdfm is because it embeds type 2 (aka > type 1C) fonts into the pdfs it generates, which significantly > reduces the size compared to embedding type 1 fonts. Ideally pdftex > and dvips would do the same, though I've been told pdftex is > "frozen"; what about dvips? > > Bob T. From zdenek.wagner at gmail.com Mon Dec 2 14:54:16 2013 From: zdenek.wagner at gmail.com (Zdenek Wagner) Date: Mon, 2 Dec 2013 14:54:16 +0100 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> References: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> Message-ID: 2013/12/2 Bob Tennent : > > Jean-Francois: "\ifwithdvipdfmx is a document boolean" > > It seems using dvipdfmx as a document option doesn't create/set that > conditional. But your post does list all (?) the packages affected > by using dvipdfm(x) and thanks for that. This information should be > in the dvipdfm documentation; otherwise how is a user to know that > using dvipdfm may require an explicit option to those packages? > > Zdenek: "It cannot be recognized how you will process the DVI file > later" > > Yes, but if the user provides dvipdfmx as a document option, the > geometry package should be aware of the user's intention to use that > processor. The hyperref package does. > The option name for geometry is dvipdfm, not dvipdfmx. You can ask the author to implement aliases. > It seems dvipdfmx does the right thing when legalpaper,landscape are > used. Wouldn't it be possible for it to suppress the frenetic but > useless 3-line > > ** WARNING ** > > message it currently produces when the user forgets to add a driver > option to the geometry package? Or even replace it by a hint to the > user about what to do to prevent it? > > BTW, the reason I'm using dvipdfm is because it embeds type 2 (aka > type 1C) fonts into the pdfs it generates, which significantly > reduces the size compared to embedding type 1 fonts. Ideally pdftex > and dvips would do the same, though I've been told pdftex is > "frozen"; what about dvips? > > Bob T. -- Zden?k Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz From rdt at cs.queensu.ca Mon Dec 2 15:09:25 2013 From: rdt at cs.queensu.ca (Bob Tennent) Date: Mon, 2 Dec 2013 09:09:25 -0500 Subject: [tex-live] dvipdfmx warnings In-Reply-To: References: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> Message-ID: <529c9495.VPXYaS1yFGx02pZz%rdt@cs.queensu.ca> >|> Yes, but if the user provides dvipdfmx as a document option, the >|> geometry package should be aware of the user's intention to use that >|> processor. The hyperref package does. >|> >|The option name for geometry is dvipdfm, not dvipdfmx. You can ask the >|author to implement aliases. I tried using dvipdfm as a document option and that was rejected because dvipdfm.def wasn't available. But I've just now tried using *both* dvipdfm *and* dvipdfmx as document options and that does work! Sigh. Bob T. From semen at trygub.com Mon Dec 2 14:55:11 2013 From: semen at trygub.com (Semen Trygubenko / =?utf-8?B?0KHQtdC80LXQvSDQotGA0LjQs9GD0LHQtdC9?= =?utf-8?B?0LrQvg==?=) Date: Mon, 2 Dec 2013 13:55:11 +0000 Subject: [tex-live] =?utf-8?q?enquiry_regarding_Ukrainian_=22=D1=96=22_enc?= =?utf-8?q?oded_as_Latin_=22i=22_in_Latex?= Message-ID: <20131202135511.GI90883@inanna.trygub.com> Dear Members of tex-live at tug.org, I'm having the following problem with inputenc package: Ukrainian letter "?" is substituted with Latin "i" during compilation. Letters look identical so it is not a problem for displaying text, but it makes it hard to search inside the generated pdf using conventional means. Here's the illustration: test.tex : -- \documentclass{article} \usepackage[utf8]{inputenc} \usepackage[T2A]{fontenc} \begin{document} ????(?)? \end{document} -- latex test.tex produces test.dvi . Inspection of test.dvi will reveal that the word is encoded correctly but the letter that I parenthesised appears as "(i)", i.e. it is incorrectly encoded. Could you please help me fix it or point me to someone who could help further? Many thanks in advance, Semen Trygubenko -- ????? ?????????? http://trygub.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: From d.p.carlisle at gmail.com Mon Dec 2 18:03:44 2013 From: d.p.carlisle at gmail.com (David Carlisle) Date: Mon, 2 Dec 2013 17:03:44 +0000 Subject: [tex-live] =?koi8-u?q?enquiry_regarding_Ukrainian_=22=A6=22_encod?= =?koi8-u?q?ed_as_Latin_=22i=22_in_Latex?= In-Reply-To: <20131202135511.GI90883@inanna.trygub.com> References: <20131202135511.GI90883@inanna.trygub.com> Message-ID: On 2 December 2013 13:55, Semen Trygubenko / ????? ?????????? < semen at trygub.com> wrote: > Dear Members of tex-live at tug.org, > > I'm having the following problem with inputenc package: > Ukrainian letter "?" is substituted with Latin "i" during compilation. > Letters look identical so it is not a problem for displaying text, but > it makes it hard to search inside the generated pdf using conventional > means. > > Here's the illustration: > > test.tex : > -- > \documentclass{article} > \usepackage[utf8]{inputenc} > \usepackage[T2A]{fontenc} > > \begin{document} > > ????(?)? > > \end{document} > -- > > latex test.tex > > produces test.dvi . Inspection of test.dvi will reveal that the word is > encoded correctly but the letter that I parenthesised > appears as "(i)", i.e. it is incorrectly encoded. > > Could you please help me fix it or point me to someone who could help > further? > > Many thanks in advance, > Semen Trygubenko > > > > -- > ????? ?????????? http://trygub.com > Hi, the texlive team can only distribute what is in the LaTeX distribution, so the place to report problems with inputenc is the latex bug database at http://latex-project.org/bugs.html However looking at the T2A encoding that you are using texdoc encguide page 23 I only see one i character. Perhaps I missed something? Is there a character representing i in T2A ? Classic TeX has to make compromises to fit everything into 256-character fonts, you can get more natural unicode encodings in the generated file by using xelatex or lualatex. David -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robin.Fairbairns at cl.cam.ac.uk Mon Dec 2 18:29:12 2013 From: Robin.Fairbairns at cl.cam.ac.uk (Robin Fairbairns) Date: Mon, 2 Dec 2013 17:29:12 +0000 Subject: [tex-live] enquiry regarding Ukrainian "i" In-Reply-To: Your message of Mon, 02 Dec 2013 13:55:11 +0000. <20131202135511.GI90883@inanna.trygub.com> Message-ID: <9084.1386005352@cl.cam.ac.uk> Semen Trygubenko / ?????????? ???????????????????? wrote: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > I'm having the following problem with inputenc package: > Ukrainian letter "i" is substituted with Latin "i" during compilation. > Letters look identical so it is not a problem for displaying text, but > it makes it hard to search inside the generated pdf using conventional > means. the inputenc mechanism provides glyphs to represent the incoming character stream. given that the t2a fonts don't have an "i" in the cyrillic half of their glyph table, they use the "i" in the latin half of the table. (my guess is that the cmap package doesn't help here, but i can't convince myself...) if i am right, you need to go with xetex or luatex, and a font that covers cyrillic as unicode to get the "correct" output. robin From zdenek.wagner at gmail.com Mon Dec 2 21:55:21 2013 From: zdenek.wagner at gmail.com (Zdenek Wagner) Date: Mon, 2 Dec 2013 21:55:21 +0100 Subject: [tex-live] enquiry regarding Ukrainian "i" In-Reply-To: <9084.1386005352@cl.cam.ac.uk> References: <20131202135511.GI90883@inanna.trygub.com> <9084.1386005352@cl.cam.ac.uk> Message-ID: 2013/12/2 Robin Fairbairns : > Semen Trygubenko / ????? ?????????? wrote: > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: quoted-printable > MIME-Version: 1.0 > >> I'm having the following problem with inputenc package: >> Ukrainian letter "i" is substituted with Latin "i" during compilation. >> Letters look identical so it is not a problem for displaying text, but >> it makes it hard to search inside the generated pdf using conventional >> means. > > the inputenc mechanism provides glyphs to represent the incoming > character stream. given that the t2a fonts don't have an "i" in the > cyrillic half of their glyph table, they use the "i" in the latin > half of the table. > > (my guess is that the cmap package doesn't help here, but i can't > convince myself...) > The cmap package could help, it depends whether it contains toUnicode map for the T2A encoding. > if i am right, you need to go with xetex or luatex, and a font that > covers cyrillic as unicode to get the "correct" output. > > robin -- Zden?k Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz From karl at freefriends.org Tue Dec 3 00:04:33 2013 From: karl at freefriends.org (Karl Berry) Date: Mon, 2 Dec 2013 23:04:33 +0000 Subject: [tex-live] dvipdfmx warnings In-Reply-To: <529c8632.XotLPMtlQNRNMRKS%rdt@cs.queensu.ca> Message-ID: <201312022304.rB2N4XVL032495@freefriends.org> Hi Bob, This information should be in the dvipdfm documentation; otherwise how is a user to know that using dvipdfm may require an explicit option to those packages? And equally, how can the dvipdfm maintainers (us) possibly know what packages need an option, let alone what that option's name should be? Answer: we can't. It's a matter for package authors, and presumably changes over time. On the other front, clearly it would be better for all package authors to handle dvipdfm and dvipdfmx as synonyms. We can't control any of this. Just have to report bugs to the package authors and hope they are responsive, as far as I can see. However, we could add a note about "known packages needing