Richard Heck wrote:
How do I get at these highly precise times? The boost file_write_time()
function returns a time_t, which seems to be in seconds. (As you say,
this may not work anyway.)
On BSD-like systems you could use
int utimes(const char *filename, const struct timeval tv[2]);
but as
Richard Heck wrote:
> How do I get at these highly precise times? The boost file_write_time()
> function returns a time_t, which seems to be in seconds. (As you say,
> this may not work anyway.)
On BSD-like systems you could use
int utimes(const char *filename, const struct timeval tv[2]);
but
Richard Heck wrote:
Georg Baum wrote:
Richard Heck wrote:
This is the result of a problem that Uwe noticed the other day with the
MikTeX implementation of the htlatex scripts: The scripts will not run
properly unless they are run in the same directory as the original file.
Georg Baum wrote:
I didn't. I meant it should copy it to the NEW temporary directory, e.g.:
/tmp/lyx_098weras/lyx_tmpbuf0/file.html.conversion/
which is where the converted files will be dumped.
Why not do that in LyX (with the copier to fix paths of included files) and
call the
Richard Heck wrote:
That's the approach I'm now taking, more or less, as Enrico found yet
further problems. He also suggested a simpler way, namely: note the time
when we start the conversion; then look at the modification times of the
files after the conversion to see which ones got
Georg Baum wrote:
Richard Heck wrote:
That's the approach I'm now taking, more or less, as Enrico found yet
further problems. He also suggested a simpler way, namely: note the time
when we start the conversion; then look at the modification times of the
files after the conversion to see
On Thu, May 24, 2007 at 11:55:35AM -0400, Richard Heck wrote:
Georg Baum wrote:
Richard Heck wrote:
That's the approach I'm now taking, more or less, as Enrico found yet
further problems. He also suggested a simpler way, namely: note the time
when we start the conversion; then look
Enrico Forestieri wrote:
I don't think so as you would copy back all the graphics files (maybe
converted to postscript from some bitmap format and thus huge) and all
sort of things that gets copied to the tempdir.
Why not implementing what I really proposed, i.e.,
1) make a list of all file
On Thu, May 24, 2007 at 11:55:35AM -0400, Richard Heck wrote:
Georg Baum wrote:
Richard Heck wrote:
That's the approach I'm now taking, more or less, as Enrico found yet
further problems. He also suggested a simpler way, namely: note the time
when we start the conversion; then look
Richard Heck wrote:
> Georg Baum wrote:
>> Richard Heck wrote:
>>
>>
>>> This is the result of a problem that Uwe noticed the other day with the
>>> MikTeX implementation of the htlatex scripts: The scripts will not run
>>> properly unless they are run in the same directory as the original
Georg Baum wrote:
>> I didn't. I meant it should copy it to the NEW temporary directory, e.g.:
>> /tmp/lyx_098weras/lyx_tmpbuf0/file.html.conversion/
>> which is where the converted files will be dumped.
>>
> Why not do that in LyX (with the copier to fix paths of included files) and
> call
Richard Heck wrote:
> That's the approach I'm now taking, more or less, as Enrico found yet
> further problems. He also suggested a simpler way, namely: note the time
> when we start the conversion; then look at the modification times of the
> files after the conversion to see which ones got
Georg Baum wrote:
> Richard Heck wrote:
>
>
>> That's the approach I'm now taking, more or less, as Enrico found yet
>> further problems. He also suggested a simpler way, namely: note the time
>> when we start the conversion; then look at the modification times of the
>> files after the
On Thu, May 24, 2007 at 11:55:35AM -0400, Richard Heck wrote:
> Georg Baum wrote:
> > Richard Heck wrote:
> >
> >
> >> That's the approach I'm now taking, more or less, as Enrico found yet
> >> further problems. He also suggested a simpler way, namely: note the time
> >> when we start the
Enrico Forestieri wrote:
> I don't think so as you would copy back all the graphics files (maybe
> converted to postscript from some bitmap format and thus huge) and all
> sort of things that gets copied to the tempdir.
>
> Why not implementing what I really proposed, i.e.,
> 1) make a list of all
On Thu, May 24, 2007 at 11:55:35AM -0400, Richard Heck wrote:
> Georg Baum wrote:
> > Richard Heck wrote:
> >
> >
> >> That's the approach I'm now taking, more or less, as Enrico found yet
> >> further problems. He also suggested a simpler way, namely: note the time
> >> when we start the
Richard Heck wrote:
This is the result of a problem that Uwe noticed the other day with the
MikTeX implementation of the htlatex scripts: The scripts will not run
properly unless they are run in the same directory as the original file.
Several other converters (e.g. lilypond) have the same
Georg Baum wrote:
Richard Heck wrote:
This is the result of a problem that Uwe noticed the other day with the
MikTeX implementation of the htlatex scripts: The scripts will not run
properly unless they are run in the same directory as the original file.
Several other converters
Richard Heck wrote:
>
> This is the result of a problem that Uwe noticed the other day with the
> MikTeX implementation of the htlatex scripts: The scripts will not run
> properly unless they are run in the same directory as the original file.
Several other converters (e.g. lilypond) have the
Georg Baum wrote:
> Richard Heck wrote:
>
>
>> This is the result of a problem that Uwe noticed the other day with the
>> MikTeX implementation of the htlatex scripts: The scripts will not run
>> properly unless they are run in the same directory as the original file.
>>
> Several other
This patch has been to the list previously and been more or less
approved. I'm sending it again, however, as I've made some additional
changes and it should be tested by at least one other person, I think,
before I commit. If you do test, please test: (i) ViewHTML; (ii)
FileExportHTML; (iii)
Richard Heck wrote:
This patch has been to the list previously and been more or less
approved. I'm sending it again, however, as I've made some additional
changes and it should be tested by at least one other person, I think,
before I commit. If you do test, please test: (i) ViewHTML; (ii)
Herbert Voss wrote:
contains(buffer-filePath(), ' ')) {
Alert::error(_(File name error),
- _(The directory path to the document cannot contain
spaces.));
+ _(The directory path to the document cannot contain
spaces,
i get:
1..\..\trunk\src\Exporter.cpp(275) : error C4101: 'e' : unreferenced local
variable
i get
An error occurred whilst running htlatex C:/tmp/lyx_tmpdir2696a00632/lyx_tmpbuf
1/t
more here:
pplatex: Process input file teachers.dvi
pplatex: Copy data to teachers.dvi
pplatex: Process input file teachers.dvi
pplatex: Copy data to teachers.dvi
This is the result of a problem that Uwe noticed the other day with the
MikTeX implementation of the htlatex scripts: The scripts will not run
properly unless they are run in the same directory as the original file.
So you can't run e.g. htlatex C:/path/to/file.tex. You can only run
htlatex
This patch has been to the list previously and been more or less
approved. I'm sending it again, however, as I've made some additional
changes and it should be tested by at least one other person, I think,
before I commit. If you do test, please test: (i) View>HTML; (ii)
File>Export>HTML; (iii)
Richard Heck wrote:
> This patch has been to the list previously and been more or less
> approved. I'm sending it again, however, as I've made some additional
> changes and it should be tested by at least one other person, I think,
> before I commit. If you do test, please test: (i) View>HTML;
Herbert Voss wrote:
>> && contains(buffer->filePath(), ' ')) {
>> Alert::error(_("File name error"),
>> - _("The directory path to the document cannot contain
>> spaces."));
>> + _("The directory path to the document cannot
i get:
1>..\..\trunk\src\Exporter.cpp(275) : error C4101: 'e' : unreferenced local
variable
i get
An error occurred whilst running htlatex "C:/tmp/lyx_tmpdir2696a00632/lyx_tmpbuf
1/t
more here:
pplatex: Process input file teachers.dvi
pplatex: Copy data to teachers.dvi
pplatex: Process input file teachers.dvi
pplatex: Copy data to teachers.dvi
This is the result of a problem that Uwe noticed the other day with the
MikTeX implementation of the htlatex scripts: The scripts will not run
properly unless they are run in the same directory as the original file.
So you can't run e.g. htlatex C:/path/to/file.tex. You can only run
htlatex
32 matches
Mail list logo
