Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Zdeněk Wagner wrote: >> [PT] What are "the normalisation rules", Zdeněk ? ** Phil. > A path can be specified by many equivalent ways, for instance a/./b > is the same as a/b, a/c/../b is again a/b (it need not be true in > unix systems). Doble slashes are ignored too, a//b is again a/b. The >

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

2017-01-15 21:05 GMT+01:00 Philip Taylor : > > > Zdenek Wagner wrote: > > > No, ./ is not a path specification, the normalization rules will > > remove it, ./foo.tex is the same as foo.tex. If you want to specify > > the path, ../Welcome/foo.tex will help because such a file

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Zdenek Wagner wrote: If you want to specify the path, ../Welcome/foo.tex will help because such a file is not below dynamic-content. That would indeed appear to be the case, Zdeněk : > E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content > ../welcome/foo.tex > This is

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Zdenek Wagner wrote: > No, ./ is not a path specification, the normalization rules will > remove it, ./foo.tex is the same as foo.tex. If you want to specify > the path, ../Welcome/foo.tex will help because such a file is not > below dynamic-content. What are "the normalisation rules", Zdeněk

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

No, ./ is not a path specification, the normalization rules will remove it, ./foo.tex is the same as foo.tex. If you want to specify the path, ../Welcome/foo.tex will help because such a file is not below dynamic-content. Zdeněk Wagner http://ttsm.icpf.cas.cz/team/wagner.shtml

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Philip Taylor wrote: > But the defined behaviour for : > > o xetex --output-directory=../dynamic-content > E:/TeX/Projects/WBH/Welcome/foo.tex > > must /surely/ be to process E:/TeX/Projects/WBH/Welcome/foo.tex, not > E:/TeX/Projects/WBH/Dynamic-content/foo.tex, which is what it does;

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

On Sun, 15 Jan 2017, David Carlisle wrote: >    Specify the directory dirname to which output files are > written. Also look for >    input files in dirname first, before looking along the normal > search path. See >    Section 3.4 [Output file location], page

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Ulrike Fischer wrote: > The output-directory is not only for output-files. XeTeX must also be > able to read from this folder, e.g. a toc-file or an aux-file. And if > there is (in a latex compilation) an (older) foo.aux in the current > folder and a new foo.aux in /dynamic-content you would

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

On 15 January 2017 at 09:20, Philip Taylor wrote: > > > But all of this is besides the point : surely > > o XeTeX --output-directory=../dynamic-content foo (or foo.tex) > > should compile foo.tex, not ../dynamic-content/foo.tex > > ** Phil. > No I think not, if

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Am Sun, 15 Jan 2017 09:20:13 + schrieb Philip Taylor: > But all of this is besides the point : surely > > o XeTeX --output-directory=../dynamic-content foo (or foo.tex) > > should compile foo.tex, not ../dynamic-content/foo.tex The output-directory is not only for output-files.

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

2017-01-15 16:00 GMT+01:00 Philip Taylor : > > > Zdeněk Wagner wrote: > > > The same on Linux but with the full (absolute) path it works as > > expected: > > > > [zw@. tmp]$ xetex --output-directory=./dynamic-content /tmp/foo.tex > > But from "/tmp", does

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Zdeněk Wagner wrote: > The same on Linux but with the full (absolute) path it works as > expected: > > [zw@. tmp]$ xetex --output-directory=./dynamic-content /tmp/foo.tex But from "/tmp", does "./dynamic-content" exist, and if so, does it contain an instance of "foo.tex" ? ** Phil.

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

The same on Linux but with the full (absolute) path it works as expected: [zw@. tmp]$ xetex --output-directory=./dynamic-content /tmp/foo.tex This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded format=xetex) entering extended mode (/tmp/foo.tex [1] ) Output written on

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Philip Taylor wrote: > But all of this is besides the point : surely > > o XeTeX --output-directory=../dynamic-content foo (or foo.tex) > > should compile foo.tex, not ../dynamic-content/foo.tex Note that this occurs even if a specific path to "foo.tex" is given : >

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Dominik Wujastyk wrote: > ​I routinely work on tex projects in my Dropbox file area. I mean > every day, all the time. I've never noticed a problem with Dropbox > mirroring my ephemeral files, even the synctex one. I have > moderately fast wifi at home and fast ethernet at work; it might be >

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

On 14 January 2017 at 10:39, Philip Taylor wrote: > ​...​ > > If (as I do) one uses Dropbox to mirror one's work for security, the last > thing one needs is for Dropbox to continually synch one's ephemeral files > (.aux, .log, .ind/idx, .pdf, etc), whence my unvarying use of

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

David Carlisle wrote: > try a file without \end[document} (\end for you:-) and type \end to the * > prompt > you will see that the text such as > --output-directory=... > after the filename is just typeset True -- I had not considered that possibility. > The problem is that if you configure

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Phil, > E:\TeX\Projects\WBH\Welcome>xetex foo --output-directory=../dynamic- content > (./foo.tex This is the intended foo.tex ) isn't that just because the flags after the filename are ignored? Personally I'd just add it to the end of the list of reasons never to use --output-directory,

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

Zdeněk Wagner napsal : > I have just tried on Linux and found that it depends on the way how > the file name is specified, namely whether foo.tex is given including > the extension or only foo: Under Windows (7, Ultimate, 64-bit) what appears to matter is the order of parameter v. qualifier;

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

I have just tried on Linux and found that it depends on the way how the file name is specified, namely whether foo.tex is given including the extension or only foo: $ xetex --output-directory=./dynamic-content foo This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded