Hi, I'm new to work with Ulysses.
In general i had a round tript to explore the functionalities and i was very surprised to find the functionality to work with own templates for exports.

For me it is intesting, because i use for technical description the docbook format. And i have a vision to use Ulysses as writer tool, but i need as final export a valid XML-file.

The template functionality is the right one for me to create nearly an XSLT, to transform my text to an docbook xml file. But i have the first stones on my way.

It is important to nestle content like that:

<sec1 xml:id="id_test1>

<title>Section 1</title>
<para>Blindtext.</para>

</sec1>

My first try is to create chapters with Ulysses like that:

#Section 1
Blindtext.

Blindtext.

#Section 2
Again a Blindtext.

My export result is:

<sec1 xml:id="id_try>
<title>Section1</title>
</sec1>
<para>Blindtext.</para>

<para>Blindtext.</para>

<sec1 xml:id="id_versuch>
<title>Section 2</title>
</sec1>
<para>Again a Blindtext.</para>

So, how work Ulysses to identify a grouped text? And how can i create the actions for this logic?

Thank you and

regards

oelauge

Exporting to DocBook with Ulysses can be achieved using the WebExport. This exporter includes a few templates, which are mostly HTML and Markdown templates. However, you can create custom templates, either be starting one from scratch or by duplicating an existing Template. In your case, it would make sense to start a new one. The WebExport documentation provides extensive coverage of how to create and edit templates.

The main problem I see with creating a DocBook template are the end tags of the sections. Usually, the WebExport puts start and end tags before and after a paragraph (such as in the title tag or the para tag -- you can realize these without problems). If the start and end tags should span multiple paragraphs, you would need to set the paragraph style before every paragraph it should span (this is intended for lists, which are enclosed by <ul>...</ul> and each line has a <li>...</li> tag). But this doesn't really help you for the DocBook sections. What you could do instead is to create a Paragraph Style for the start of a section (which you then assign to a WebExport Style action containing the start tag <sec1 ...>) and a Paragraph Style for the end of a section (which you assign to a different WebExport Style action containing just the end tag </sec1>) and put the first Style at the beginning of a section and the second at the end of a paragraph.
You can create these actions in the Template Editor (which is described in detail in the WebExport documentation). If you want, you can also duplicate an existing template and then click on "Edit template…" in the popup menu to see how they are structured. If you need any further help with creating Templates, you can contact us here in the forums or directly at support@the-soulmen.com.

Götz

I've just tried it with a small set of Paragraph Styles and it seems to work nicely. First, I created two Paragraph Styles in the Ulysses Preferences (Cmd-,): one for the start of a section and one for the end of a section (the tags are "## ", "#--", respectively, but that shouldn't matter). Then I went to the Exporters, created a new WebExport Template, set up a template file (in the second tab) to include the text of a document ({{document.text}}) and added two Paragraph Style Actions (I called them "Section start" and "Section end") in the Actions tab. I set the result text field of the first one to
<sec1 xml:id="id_try"> <title>{{}}</title (you can insert line breaks by pressing Alt+Return). Then I set the result text field of the second one to
</sec1>
Finally, I changed the result text field of the Default Paragraph Style to <para>{{}}</para> so that all lines which don't have a Paragraph Style assigned to them are enclosed by the para tag. Close the Template Editor sheet and set the Paragraph Style of the start of a section to "Section start" and do the same for the end of a section.

If you now type in Ulysses

## Section 1   
Blindtext.   

Blindtext.   
##-   

## Section 2   
Blindtext.   

##-    

the text should be converted accordingly.

I hope that helps,
Götz

Hello oelauge,

sorry for taking so long for answering your request. I thought about how to include labels in the section and haven't really come up with a solution that could fit your needs. What you would need is something like the Formatted Inline Style Actions, where you can give your text inside Inline Style tags a certain formatting (e.g., for links linkName-URL). However, we haven't added these capabilities for Paragraph Style actions yet. I'm afraid we've hit a wall here where the WebExport can't really help you in this matter.

Götz