) into Scribus text frame(s) (as one example of a pipeline). But the general idea is to use Scribus in a "tool chain" such as importing markdown content from an Editor such as atom.io (or Scrivener or Sublime. If I get around to writing one I will post it here.
However Mac has its own family of automation tools.
#Scribus for mac edit text plus#
I have one which covers Linux (my desktop) plus Windows, but not Mac. The biggest obstacle is finding an automation "power tool" which is truly cross platform. We do have the benefit of Scripter but my approach would be to "drive" the Scribus GUI to apply various processes. This would allow meta commands to drive more complex operations using Scribus built in methods. However I have an idea to develop a "power tool" to which refers above.īasically using UI automation scripts the Scribus GUI (including properties windows) can be controlled using external helper scripts (macros). I confess that I am a casual visitor to this forum dropping in from time to time to read trends. Perhaps something to consider for Scribus 2.0? Maybe someone can explain the logic of the two dialog windows? Further, why not have the option to dock font menus as text and attendant styling is pretty important in desktop publishing. Having two separate menus for what should be the same task is awkward. You may also select (highlight) text and change the highlighted text features in Properties > Text. When you click inside the frame, you will see a blinking vertical cursor where you may add or edit text.
It seems a better workflow would be to have a one-stop-shop for text styling/editing by merging 'story editor' and 'text properties'. Click the Edit Contents of Frame icon on the toolbar (keyboard: E). Handling fonts in 'Story Editor' tends to be awkward as it keeps reverting to default font. 'Text Properties' does, however, have a font weight menu. Whereas 'text properties' does live preview the text, but you cannot style parts of the text within the body or be selective about alignment. It seems that 'Story Editor' is for styling the body of the text, such as italics, but it lacks a live preview.
#Scribus for mac edit text windows#
Two dialog windows for what should be the same task seem redundant, especially since you can control font selections from both. I was working with text in Scribus and noticed the 'Story Editor' and 'Text Properties' and wonder why the two must be kept separate.
0 kommentar(er)
