April 13. 2006 09:58

I think that I may have a problem with the MiKTeX Data directory.
I maintain a MiKTeX installation at my wordk.
We have MiKTeX installed on a fileserver. We have a main additional TeX root for our LaTeX classes for a house style.
Each user has a LocalTeXmf on the fileserver.

Each user can work from any PC but also from home.
Everything on the fileserver is always accessible from any PC.

With the new system as documented in "MiKTeX 2.5 Preview" our current configuration will no longer work.

There is even talk of clearing up ....\Local Settings\username every time the computer is shutdown. I have been told that this is practice in (many,some) enterprise situations. This would imply having to regenerate format files every time a computer is started.

Will it be possible to put the MiKTeX data directory somewhere else?
What should we do?

Berend

Berend Hasselman

April 13. 2006 10:22

The installation is installed as

k:\tex\tex holds MiKTeX total
k:\tex\cpbtex holds all house style things
g:\private\appdata\localtexmf is for all user stuff and generated things

A paths.ini file in the appropriate subdirectory of the MiKTeX root contains the TeX roots.

K: and G: are located on a fileserver accessible from a normal PC and from an application server so that people can work from home. Some users put private stuff in their LocalTeXmf. Those users know how to update filename databases.


I install and update everything on my PC with special permissions. Before I do that I clean my LocalTeXmf.
I then copy the appropriate contents of my LocalTexMf to the fileserver. The system administrators then copy the stuff to each user's localtexmf.

Sometimes I have to change things in the house style root. I generate a new filename database. Then there are two options: either the new filename database is copied to each user's localtexmf or we use initexmf -u.... to update the appropriate filename database for each user (this is done silently in the background).

Every user can now run MiKTeX stuff regardless of the PC he/she is using and regardless of working remotely or not.
A user doesn't have to do anything.

Hopefully this is clear enough.

Berend

Berend Hasselman

April 13. 2006 10:56

Christian,

A different question: is shifting the local user data directory to /Documents and Settings/Local Settings/... intended to increase some sort of integration with WinXP and thereafter? In MiKTeX 2.4, the installation instructions highly encourage the user to not install the files in directories with spaces in the directory names. Well, /Documents and Settings/ and /Local Settings/ etc. contain white space.

Kwang

April 14. 2006 04:50

Looks good.
This should provide me wth all the configuration options I need.
Thanks very much.


Berend

Berend Hasselman

May 1. 2006 07:18

Dear Christian:

I usually put all my .tex and .eps files under d:\tex.
In MiKTeX 2.4, I can easily revised miktex.ini to search for all
the files in d:\tex.

In MiKTeX 2.5, is there an easy way to do this?
(In fact, I don't know how to ask latex to search for my .eps files.)
It seems that I have to revise latex.ini, dvips.ini, bibtex.ini and so on
(in the c:\Document and Settings\ ...) to get the result.

Thanks!

Tsong-Min Wu

Tsong-Min Wu

May 1. 2006 15:02

I thought that, but do not know how to do it.

In MiKTeX 2.5, "MiKTeX Options => Roots", there is
a "New" button, but no "add" button. I tries "New",
but it does not seem to work.

Maybe I have done something wrong?

Tsong-Min Wu

May 2. 2006 12:57

Regarding whitespace in file names: paths with spaces work fine, but a space in the filename causes compilation errors:

compiling "the main file.tex" results in a file the.tex being created and the following in the log:
This is e-TeX, Version 3.141592-2.2 (MiKTeX 2.5 Beta 5) (preloaded format=latex 2006.4.30) 30 APR 2006 22:23
entering extended mode
**the*main*file.tex
(the main file.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, dumylang, nohyphenation, ge
rman, ngerman, french, loaded.
(C:\apps\MiKTeX25\tex\latex\base\minimal.cls
Document Class: minimal 2001/05/25 Standard LaTeX minimal class
)

! LaTeX Error: Missing \begin{document}.

Ervin

May 5. 2006 23:44

Thanks, Beta 6 can set TEXMF root directory.

I am writing a install to add a Chinese TeX preprocessor and fonts to MiKTeX.
I wonder if mo.exe can be used in command line? What I want to do is, e.g.,
to let the install program to add "c:\Program Files\cwtex" as a root directory.
(If you let the users to set it up by themselves, they sometimes make mistakes.)

The other issue is with the directory for the user's files.
If I set "D:\" as a root directory, MiKTeX will search for .tex and .eps files under D:\tex//; and .bib files under D:\bibtex//. MiKTeX 2.5 searches for files according to TDS. In other words, if my .bib file is with .tex and .eps files, MiKTeX will not able to find it. (In MiKTeX 2.4, this is possible by revising miktex.ini.)

I wonder if it is a good idea that I can ask MiKTeX to search for all the user's files (including .tex, .eps, and .bib) at some specific directory?

Tsong-Min Wu

May 6. 2006 23:48

Yes, a new file is created.
"the.tex" contains one line: "\relax"
beta6 does the same.

Ervin

May 7. 2006 12:48

dvips 5.95b in MiKTeX 2.5 beta 6

I typeset a Chinese book of about 300 pages.
In MiKTeX 2.4, the .ps file (dvips 5.94) is about 25mb.
In MiKTeX 2.5 beta 6, .ps file size is about 38.9mb.
The reason for the much bigger file size seems to be that
some Chinese fonts are reloaded several times.

For example, looking into the .ps file, I find that

BeginFont: CWTEX-M0

occurs several times. (M0 is one of the Chinese fonts used.)

YAP works nicely, except that there are conflicts of font names.
For example, Chinese font names, M0, M1, ..., F0, RB1, ...,
conflict with the following packages: levy, lfb, lh, lhcyr.
When encounter the Chinese fonts, YAP will try to install
the above packages. So I have to rename, e.g., levy.tpm to
levy_bak.tpm, and then YAP will generate the Chinese PK fonts.

This is not an elegant way at all, but it seems to work.
What puzzle me is that dvips will use the Chinese fonts
directly without any troubles.

Tsong-Min Wu

May 8. 2006 01:26

Christian:

I think I can reproduce pretty much the same problem Ervin described. I created a minimal test file with white space in filename called "white space.tex.":

\documentclass{article}

\begin{document} blah \end{document}

Then I switch to the command line and try to compile the file using latex.exe from current MiKTeX 2.4 and beta 2.6, respectively. I paste the output from the command line below.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Temp>latex "white space.tex"
This is e-TeX, Version 3.141592-2.2 (MiKTeX 2.4)
entering extended mode
(white space.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, dumylang, nohyphenation, ge
rman, ngerman, french, loaded.
(C:\texmf\tex\latex\base\article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
(C:\texmf\tex\latex\base\size10.clo))
No file "white space".aux.
[1] (white space.aux) )
Output written on "white space.dvi" (1 page, 216 bytes).
Transcript written on "white space.log".

C:\Temp>C:\MiKTeX25\miktex\bin\latex "white space.tex"
This is e-TeX, Version 3.141592-2.2 (MiKTeX 2.5 Beta 6)
entering extended mode
(white space.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, dumylang, nohyphenation, ge
rman, ngerman, french, loaded.
(C:\MiKTeX25\tex\latex\base\article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
(C:\MiKTeX25\tex\latex\base\size10.clo))

! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type H for immediate help.
...

l.3 \begin{document}
blah \end{document}
?

Kwang

May 22. 2006 22:29

beta7 fixed the issue with whitespace in the filenames.
the fix seems to have been in the code that creates the .aux file

Ervin

May 24. 2006 02:01

There are still some issues with spaces in filenames, this time with job-name option.

to reproduce:
create a minimal valid latex document, call it "name with spaces.tex"
\documentclass{minimal}
\begin{document}
Hello world!
\end{document}


The straightforward usage:
pdflatex "name with spaces"
works fine in beta7

However, if the job-name option is used with a string containg a space, like
pdflatex -job-name="name with spaces" "name with spaces"
has the same issues as before, i.e. a "LaTeX Error: Missing \begin{document}." is thrown and a file "name.tex" is created (containing \relax)

At first I tried "test spaces.tex", but I kept getting a dialog box saying:
The required file 'tex\plain\vertex\test.tex' is missing
Name: vertex
Title: Styles for economics working papers and journals

Ervin

June 7. 2006 01:25

Indeed, you fixed it.

Ervin

June 7. 2006 18:46

I'm just counting the days till MikTex 2.5 will be finished.
I hope that you are not a to big soccer fan, so you can keep on working while FIFA WM2006 is running.

Greetings,
Jean

Jean

July 26. 2006 10:26

I am using MiKTeX 2.5 Beta 10 and have still problems with adding additional texmf directories as root. There is an "ADD" button but I get the error message
"Windows API error 5: Access is denied. Data: Software\MiKTeX.org\MiKTeX\2.5\Core".

cheers

Kai

Kai

July 29. 2006 07:12

a n00b question:

1. what ist the main different among Miktex 2.4 & Miktex 2.5?

2. does existist an table, where the different or changelog are listed?

ali

September 2. 2006 19:34

In case it helps anyone, I discovered accidentally that the following bibtex.ini works:

[ft.bib]

path=.
path;=%R/bib//

It would nice if this were more clearly documented for those upgrading...

Ken Turner

September 2. 2006 20:28

Having just upgraded to MikTeX 2.5, there doesn't seem to be a bibtex.ini file in the installation as a model. I guessedthe following:

[bibtex]

extensions=
extensions;=.tex
extensions;=.src
extensions;=.ltx

path=.
path;=%R/bib//

but that doesn't work. What's the right format?

Ken Turner

September 29. 2006 20:45

MiKTeX 2.5 is OK for English. It is almost impossible to use with the Korean characters.

With MiKTeX 2.4, Korean TeX users had sevral options, HLaTeX, Hangul-ucs, etc. (see http://faq.ktug.or.kr/faq/HPack#s-2.1 ). It works fine.

I have upgraded it from Version 2.4, it does not make new pk font files. Hence Yap dosen't show many Korean characters.

Young H. Choe

October 2. 2006 23:41

I found the reason why Yap doesn’t show many Korean characters.
The reason is that MiKTeX 2.5 doesn’t recognize ttf2pk folders.
Hence it cannot make new pk font files.
So, I moved all files of ttf2pk folders to ttf2tpm folders.
I also reinstalled MiKTeX 2.5 instead of upgrading it from Version 2.4.
Now I can use both HLaTeX and Hangul-ucs packages freely.

Greetings,
Young

Young H. Choe

July 14. 2009 03:38

Pingback from answerspluto.com

list of urls - 5 « Answers Pluto

answerspluto.com