Alfredo Braunstein wrote:
>> Actually, I think that prepare_for_export could check whether the
>> converted image has been generated and if not add some lines to an
>> ostream that is eventually dumped as a shell script. That way we would
>> need to monitor only one process and wouldn't run into s
Angus Leeming wrote:
>>> That is, we need a 'prepare_for_export(LaTexFlavour const &)' member
>>> function in the insets or somesuch. The actual 'latex' member function
>>> will do no more than dump the appropriate text to the ostream.
>>
>> But why the prepare_for_export must be latex-specific?
Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
>> Step one: perform all the necessary conversions of (eg) images.
>> Preferably asynchronously. When finished, emit a signal to begin
>> Step two: the main conversion from latex to xyz. I guess that this still
>> needs to be synchronous for the
Angus Leeming wrote:
> Step one: perform all the necessary conversions of (eg) images. Preferably
> asynchronously. When finished, emit a signal to begin
> Step two: the main conversion from latex to xyz. I guess that this still
> needs to be synchronous for the time being but longer term it would
Alfredo Braunstein wrote:
> Agreed. What do you think about the above?
>
> Regards, Alfredo
Actually, since you are thinking about the conversion stuff, I think that we
need a two-phase export scheme (two-phase is the in-thing at the moment
after all).
Step one: perform all the necessary conve
Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
> Thanks, Angus. I though that the flavour thing was coupled with the
> harcoded guessing.
>
>> I think that that makes a lot of sense. However, I think that flavour is
>> your friend here. You just need a mechanism to link the latex output
>> f
Angus Leeming wrote:
Thanks, Angus. I though that the flavour thing was coupled with the harcoded
guessing.
> I think that that makes a lot of sense. However, I think that flavour is
> your friend here. You just need a mechanism to link the latex output
> format (latex-for-pdf) to the flavour (PD
Alfredo Braunstein wrote:
> I don't like the flavor thing, because it seems to hardcode part of the
> conversion based on the name of some converter in the path(?).
> Can we have different buffer backends (i.e. different formats), one for
> each flavour (latex-for-pdf, latex-for-ps, etc), and let
