You are not logged in.
I am gonna ask the one stupidest question on these forums, but what is TeX, teTeX, TeXLive????
You should search the web before asking such a question... LaTeX is a typesetting application focused mainly on scientific papers and books. TeXLive is a distribution of LaTeX. A good introduction document: The not so short introduction to LaTeX2e.
Last edited by Ramses de Norre (2007-12-18 10:26:18)
Offline
I did search, right after I asked. My curiosity got the best of me. I wish I hadn't of asked, I really have no use for such a program.
Offline
Wrong attitude. Right answer: You really have lots of use for such a program, you just don't know it yet. :-)
Offline
Wrong attitude. Right answer: You really have lots of use for such a program, you just don't know it yet. :-)
purrfect
Offline
I really have no use for such a program.
When you've written a few papers with LaTeX, you'll discover how terrible WYSIWYG word processors really are... I never even consider making a document or a presentation with such an application anymore. I have to admit that it'll take you some learning to write those beautiful documents with LaTeX, but it is certainly worth it.
BTW: the number one argument people have against trying out linux, is that they have no use for it and they think windows fits their needs perfectly fine. Those who find the courage to step into the new thing mostly find out (after a while) that they just didn't see the use.
Offline
Well I do not write papers or present any sort of documents that need that type of formatting. I just tinker with anything I can get my hands on, most importantly, anything that other people find interesting. Its a good way of getting your hands dirty when learning a 'new' language.
Offline
I have been trying to use these packages for awhile but keep encountering a string of warnings like the following
kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/(2*4000) --dpi 8000 cmr8
mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode.
Even though my documents compile through such warnings, compile times are extremely long (I have a few documents that contain many tex figures in addition to being several hundered pages in their own right). Doing a texlive install from the dvd doesn't have the above issue at all. This problem has been reported as a bug with the debian texlive distro; and has subsequently been resolved (although I am not sure what they did). I am currently looking into seeing what exactly is causing this issue; but if someone else knows how to resolve it, it should be patched into the main packages.
Last edited by PDExperiment626 (2008-04-15 09:40:48)
... and for a time, it was good...
Offline
First, your system tries to compile the fonts via metafont. If you you use pdftex, you should prohibit this by a \usepackage{lmodern} or the like.
Do you have a file /opt/texlive/texmf-var/fonts/map/pdftex/updmap/pdftex.map? If so, delete it. Seems to be a bug.
The other question is why the system tries to generate fonts in that high resolution. Normally it should generate fonts for ljfour in 600 dpi resolution. What printer do you have?
Last edited by Stefan Husmann (2008-04-16 15:13:24)
Offline
Do you have a vile /opt/texlive/texmf-var/fonts/map/pdftex/updmap/pdftex.map? If so, delete it. Seems to be a bug.
Hm? That file should contain info on for which fonts and how should pdftex use postscript binary fonts. It's true that if pdftex tries to use bitmap fonts instead of type1/postscript ones, then there's probably something wrong with the mappings in that file, but delete? It gets regenerated every time you run 'updmap-sys' as root (which should be run after installing any fonts).
Offline
Another thought comes to mind: check your /opt/texlive/texmf-{*}/web2c/mktex.cnf. (That {*} is most probably 'var'. EDIT: Anyway, if you will be changing it, you should really edit the one in 'var', since that shouldn't get overwritten on updates.) That config file has some impact on how the bitmap fonts are generated.
: ${MT_FEATURES=appendonlydir:varfonts}
: ${MODE=ljfour}
: ${BDPI=600}
Last edited by bender02 (2008-04-16 15:20:51)
Offline
Yes, delete! I encountered that after every updmap-sys this file has to be deleted (or renamed, but its is useless anyway). Otherwise some of the fonts that are avaiable in typ1-format won't be found and the mktexpk mechanism tries to do its job. I think it is a bug, but I do not have any idea where to search for it.
That is weird, indeed.
Offline
Another thought comes to mind: check your /opt/texlive/texmf-{*}/web2c/mktex.cnf. (That {*} is most probably 'var'. EDIT: Anyway, if you will be changing it, you should really edit the one in 'var', since that shouldn't get overwritten on updates.) That config file has some impact on how the bitmap fonts are generated.
: ${MT_FEATURES=appendonlydir:varfonts} : ${MODE=ljfour} : ${BDPI=600}
This is exactly the content of my /opt/texlive/texmf-var/web2c/mktex.cnf
PDExperiment626, is this different on your site?
Last edited by Stefan Husmann (2008-04-16 15:28:21)
Offline
Well, on my system it's just a symlink:
lrwxrwxrwx 1 root root 15 2008-04-16 10:07 pdftex.map -> pdftex_dl14.map
-rw-r--r-- 1 root root 124712 2008-04-16 10:07 pdftex_dl14.map
-rw-r--r-- 1 root root 123162 2008-04-16 10:07 pdftex_ndl14.map
That makes me wonder...
Offline
Yes, delete! I encountered that after every updmap-sys this file has to be deleted (or renamed, but its is useless anyway).
Perhaps you have another pdftex.map in one of the texmf-{*} trees. Because pdftex really needs a pdftex.map file.
Offline
We should really get a bugtracker instead of solving it in this thread...
Offline
Surely I have Under /opt/texlive/texmf/fonts/map/pdftex
Maybe I should delete that?
Last edited by Stefan Husmann (2008-04-16 15:43:38)
Offline
I don't have it in -dist tree. Yes, I think you should delete it - these dynamically generated files should not be present in the -dist tree.
Offline
I don't have it in -dist tree. Yes, I think you should delete it - these dynamically generated files should not be present in the -dist tree.
Sorry I was wrong, I edited my former post (you are very quick, guys )
Offline
I can reproduce this issue now. If the file pdftex.map in the -var tree is present, pdftex uses pk-fonts, if I delete it, it uses the correct type-1 fonts.
Offline
$ pacman -Qo /opt/texlive/texmf/fonts/map/pdftex/updmap/pdftex.map
/opt/texlive/texmf/fonts/map/pdftex/updmap/pdftex.map is owned by texlive-bin 2007.2-2.1
Now looking in, I have lines like
<snip>
cmr10 CMR10 <cmr10.pfb
cmr12 CMR12 <cmr12.pfb
cmr17 CMR17 <cmr17.pfb
cmr5 CMR5 <cmr5.pfb
cmr6 CMR6 <cmr6.pfb
cmr7 CMR7 <cmr7.pfb
cmr8 CMR8 <cmr8.pfb
cmr9 CMR9 <cmr9.pfb
<snip>
Those are responsible for replacing cm* fonts by type1 alternatives when running pdftex. I have them in both .../texmf-var/.../pdftex.map and .../texmf/.../pdftex.map. If they're not there, then pdftex probably tries to use bitmap fonts.
Now I'm not totally sure how does pdftex select the file which it uses, but I think that if the file is that ~/.texmf-{*} overrides /opt/texlive/texmf-var, which overrides /opt/texlive/texmf{-dist,}.
Offline
I think you are right, but on my machine the new generated pdftex.map in -var-tree i significantly smaller. The issue we discuss here apllys not for Computer-modern fonts, but e.g. for yfrak an kpfonts. The -var-tree seems to be searched first, and if the pdftex.map there does not include the fonts, they are generated.
If the file does not exist, the texmf-tree witout any -extension is searched, the fonts are found and need not to be regenerated with metafont.
Offline
I guess then what you want to look at is 'updmap-sys --edit' (or 'updmap --edit' as user). You get to edit the file which tells updmap which map files it should include in newly generated *.map files. For instance to get yfrak type1 work properly, you should add the line 'Map yfrak.map' to that file (actually, it's just ~/.texmf-var/web2c/updmap.cfg file EDIT: in the user case; system-wide is /opt/texlive/texmf{,-config}/web2c/updmap.cfg), and similarly for kpfonts.map. Apparently even though yfrak is distributed with texlive, its .map file is not enabled by default. If you installed kpfonts manually, then updating updmap is one of the steps (I don't have them installed, so I'm guessing here.) Any AUR packages that install new tex type1 fonts should add themselves to updmap.cnf automatically in .install scripts.
On the other hand, the pdftex.map shipped with texlive-bin contains *everything*. While this is OK, the moment you install fonts not shipped with texlive (like kpfonts), the .map files should be regenerated, and correctly.
We should explain the updmap stuff to arch/texlive users (probably on the wiki?).
Last edited by bender02 (2008-04-16 16:27:17)
Offline
That was it! You were perfectly right. (Though kpfonts come with TeXlive, at least with the svn-version.) Thank you!
Offline
I guess I'll try to put some info about updmap to wiki, when I have some time.
I still think it would be useful to have a bugtracker and/or forum for texlive issues to make testing/updating texlive to 2008 version smoother for the end user. I know, we can post here, and use flyspray, but still. Resolving updmap issue was fun, but it shouldn't really belong to this thread.
Offline
Alright, I posted more-less the above solution to the wiki as TeXLive FAQ. Now that's quite aspiring name for a wiki page, so go ahead and fix my errors, and more importantly, contribute, please!
Offline