Francesc Serra Graells

@jcwinkler Sorry, I did not mean to replace the Preamble File but combining it with my proposal. The GUI would only require an "Import" button besides the existing "Clear" one,...

I see the following dis/advantages of each preamble embedidng approach: **Per node basis** :heavy_check_mark: Copying one TexText node from document to document keeps preamble info. :heavy_check_mark: Possibility to customize preamble...

Your are welcome @jcwinkler. No user feedback can pay for such an excellent tool! :smiley: I agree that adding too many options may distract the average user. Maybe the first...

@sizmailov, if I understood correctly, _Mode 1_ uses something like preamble **profiles**. The TeX code of each profile is stored in an external file, while the name/id mapping of all...

@sizmailov, I understand that when copying one TexText node from document to document, the preamble profile will be copied from the external file to the SVG root of the destination...

@sizmailov, I see your point. Then I would propose to store a copy of the preamble profile into every TexText node to ensure it is propagated when copying the node...

@sizmailov Fully agree, but still preserving your idea of preamble manager. In this way, user can manage a large number of TexText nodes with little effort because preambles are grouped...

@jcwinkler, if I had to choose one single feature, then I would still vote fro **portability** (as in my original post). Portability when I am sharing the SVG files with...

It looks like this enhancement request has languished... Maybe my initial proposal could be reconsidered, as it requires a minimal modification and it is fully retrocompatible. I am assuming here...