I am working on a collaboratively translated document (a comic book) with many irregularly distributed text frames with different styles (think of descriptions, callouts, etc); the style is set per-frame. I export plain-text of text frames into google document, let people improve the translation, then load it back (it is a bit more complicated to match frames with pages and such, but that's is not important now).

for page in range(1,scribus.pageCount()+1): for frame in scribus.getPageItems(): if frame[1]!=4: continue # not a text frame newText=... # grab new text value scribus.setText(newText,frame)but what happens is that styles of processed frames are reset.

Is there a way to set text while preserving the style information? Note that even in (rare) cases of multi-paragraph frames, they still all have the same style which I applied to the frame itself.

it still looks a bit wild but i'm close to get a prototype that could be used for building a new scripter.and, with a bit of luck, that repository will transform in a nice manual on how to embed a python interpreter inside of a c++ application.(imo, this is something that is not well documented, and every project is creating its own solution)

combined with the issue 3 linked above -- which states that the technology used by the scripter created by henning is not supported anymore (and have never really been supported) -- i prefer restarting from scratch, get much inspiration from the wonderful previous new scripter (really, it looks like a very clever solution... even if i could not understand everything!), and produce a new scripter with a very similar API as the so called scripter 2.

i hope to have my tentatives finished by the end of next week and then i could need work with defining the API and porting the code from the scripter 1 and 2 to the scripter 3

ah, please, forget as soon as possible the name scripter 3... if it gets into scribus, it should simply be the new scripter or the pybind11 scripter : - )

Wow, very happy you chose pybind11. I have a LOT of experience with boost::python and have liked pybind11 from the very beginning (still know only from docs), it is solving a lot of boost::python's issues, plus is much more lightweight. I will look at it. Good luck and thanks for the thorough information! vaclav