fchauvel / flap

Flattening LaTeX projects
https://fchauvel.github.io/flap
GNU General Public License v3.0
17 stars 2 forks source link

`\def`are stripped out #28

Closed fchauvel closed 7 years ago

fchauvel commented 7 years ago

From @gro1729, Issue 22:

In combination with the package "wrapfigure" I had to define some variables:

\newcounter{figure} 
\makeatletter 
\def\ext@figure{} 
\makeatother 
\newcounter{table} 
\makeatletter 
\def\ext@table{} 
\makeatother 

FLaP translates this to :

\newcounter{figure} 
\makeatletter 
\makeatother 
\newcounter{table} 
\makeatletter 
\makeatother

in the file "merged.tex"

fchauvel commented 7 years ago

Hopefully, Commit 357022c should fix this issue. @gro1729, could you give it a try and let me know?

gro1729 commented 7 years ago

I get:

\makeatletter
   \def\ext@figure{}
\makeatother
\newcounter{table}
\makeatletter
   \def\ext@table{}
\makeatother

in the file "merged.tex". Thanks.

Are there still any other issues I could try?

Best Regards Andreas

P.S.: Is it possible to define via commandline option the name of the output-file?

Am 12.01.2017 15:07, schrieb Franck Chauvel:

Hopefully, Commit 357022c https://github.com/fchauvel/flap/commit/357022ca8c785203b58e62068ce7923ae0575305 should fix this issue. @gro1729 https://github.com/gro1729, could you give it a try and let me know?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fchauvel/flap/issues/28#issuecomment-272171431, or mute the thread https://github.com/notifications/unsubscribe-auth/AEjJqyL8yCQ1oKFhYgXCfnZSWPylSA-Zks5rRjOagaJpZM4LhCAl.

gro1729 commented 7 years ago

Sorry, I have another question.

I have several commands re-defined that use the same interface like the original command. May be, you remember my "\includesvgdf". It would be great to have a "customer"-needs section, where I can define "behaves like" and flap handles these command automagically automatically.

What do you think?

Regards from Andreas

Am 12.01.2017 15:07, schrieb Franck Chauvel:

Hopefully, Commit 357022c https://github.com/fchauvel/flap/commit/357022ca8c785203b58e62068ce7923ae0575305 should fix this issue. @gro1729 https://github.com/gro1729, could you give it a try and let me know?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fchauvel/flap/issues/28#issuecomment-272171431, or mute the thread https://github.com/notifications/unsubscribe-auth/AEjJqyL8yCQ1oKFhYgXCfnZSWPylSA-Zks5rRjOagaJpZM4LhCAl.

fchauvel commented 7 years ago

Thanks for the feedback. I'll close this very issue then.

I am not sure I understand what you would like to do with \includesvgdf. Could this be the idea as in Issue #16?

gro1729 commented 7 years ago

/I do not think, that it is the same issue./

What I would like to have is an interface for my personal LaTeX-macros in FLaP. For instance: "adjincludegraphics" is not implemented in the "graphicx"-package. But this official TeXLive- package implements "adjincludegraphics" with the same 'signature' like 'includegraphics'. As I have understood, you would implement the use of "adjincludegraphics" as an enhancement in the 'kernel'-implementation of FLaP.

You will not do this each time a new package (like my personal includesvgpdf- package) is implemented? And that's not necessary, I think.

What is my daily (\LaTeX) business? For some of my colleagues I have to write German, Slovenian, Polisch, .... macros that are mimicing the behaviour of the English counterpart. "includegraphics" has the counterpart "fuegeGraphikEin". The German Macro is nothing else than a textual replacement of the English macro. The interface is the same, but the ,,implementation'' is different.

What I would like to have is a FLaP-customizing area, where I can 'register' "fuegeGraphikEin" as my own macro, that has to be handled in the kernel-implementation like "includegraphics", independent of my local (La-)TeX-implementation.

Writing this...

/Yes. "includetikz" has more or less the same signature like "includegraphics", "includesvgpdf", "fuegeGraphikEin"./

Local declaration-files are already (more or less) copied into the "merged"-directory. The local use of a user-defined macro like "fuegeGraphikEin" should also work, provided the referenced image-file would be copied into the merged-directory, which should work for all macros that are inheriting from, say "includegraphics".

Best regards Andreas

P.S.: It is very difficult to describe an abstract idea in a foreign language. Germans have too complex structures of their sentences. I hope, you will understand my lousy DENglish.

Am 12.01.2017 19:22, schrieb Franck Chauvel:

Thanks for the feedback. I'll close this very issue then.

I am not sure I understand what you would like to do with |\includesvgdf|. Could this be the idea as in Issue #16 https://github.com/fchauvel/flap/issues/16?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fchauvel/flap/issues/28#issuecomment-272240882, or mute the thread https://github.com/notifications/unsubscribe-auth/AEjJq41iJrGB81Z0pLnMSyE141lGfKniks5rRm9-gaJpZM4LhCAl.