Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
Hey guys. There have been so many calls for a web export in Ulysses. Doing HTML and blogs and stuff right from the app. But till now ... theres about zero feedback. What's up? Did we confuse you? Is there no interest? Did you miss to read about it? No time? etc. We'd really like to know!
Got it. We'll take care of the problem :)
This "property list error 0" message is pretty strange, since I haven't encountered it yet while working with the Web Export. We would appreciate it if you could send the crash log to support@the-soulmen.com, it might help us in finding the root of the problem.
If you want your paragraphs to be separated by <br /> instead of enclosed in <p> and </p>, you can simply change the format of the default Style (the Paragraph Style Action with the description "Paragraph" and the type "default") from "<p>{{}}</p>" to "{{}}<br />". This way, a "<br />" is inserted after every paragraph. Currently, you cannot simply enter "<br />" in the Editor, since some characters such as <, > or & are automatically converted to their respective HTML entities (< >, &).
Aren't the empty lines outside the <p></p> tags? For me, these empty lines helped reading the source code. We'll think about such an option, but right now it doesn't really seem too useful to me.
You can actually change this setting by yourself by editing the Info.plist file of the Snippet Template. There's a whole section on how to edit to Templates called "Creating Custom Templates" in the documentation of the Web Export. Once you opened the Info.plist file, navigate to multiFiles > Item 0 and set the property "name" to {{document.index}} - {{ENC document.name}}.html (the only thing which is changed is the extension). We're currently working on a Template Editor, which will greatly simplify changing settings like these.
The easiest thing would be to add a Paragraph Style with "- " or "1. " as tag and apply the Style Action "List (Unordered)" to that Paragraph Style. That's actually what I do when working with lists.
What other tags would like to have included in the default Templates? The selection of tags in the Templates is only a subset of all HTML tags but we felt those were the most important ones for exporting Ulysses Projects. If you want, you can also add your own Actions to the Templates (using the instructions provided in the Web Export Documentation).
I hope that helps.
Götz
Maggot: Adventures and discoveries.
Wow, I was really impressed by how much you played around with the Web Export and made use of its capabilities!
Here are a few remarks to your adventures:
"Note I didn't change the tag "tableofcontents" - seemed to be asking for trouble - but if you do, remember to change it in pages.html as well. I say leave it alone; illogical, but I think the less you change, the better."
The Localizable.strings files inside the en.lproj folder always have the same format: first the identifier in quotes, then an = and then the localized string in quotes. The identifier is the same for all localizations, the localized string is not. For instance, the string with the identifier "tableOfContents" has the localized string "Table of Contents" in the English localization (which can be found in en.lproj), while the German localization (located in de.lproj) has "Inhaltsverzeichnis"" as localized string. One of the commands for the placeholders in the Web Export is LOC. Whenever you use it, you put LOC first and then the identifier, e.g. {{LOC tableOfContents}}. During export, this placeholder will be replaced with "Table of Contents" if you run Ulysses (and Mac OS X) in English. If you run Mac OS X in German, the placeholder will be replaced with "Inhaltsverzeichnis". Therefore, you shouldn't change the tag, but the localized string. If you change the tag, you will need to change the tag inside the LOC placeholder as well. The Web Export has a built-in validator that checks for those things.
"Couldn't work out how to put a carriage return inside those strings, though - Götz?"
You should be able to insert a carriage return by putting \n at the position where you want the line break.
"5) I wanted a copy of pages separate from the main list of pages. I knew their names and had fixed them so that they were top and second top in the export. First add a couple of new lines to the localisable file: "Home" = "Home"; "About" = "About"; Restart U. In pages.html, add the following inside the ul toc list, but before the FOR loop: <li><a href="1 - {{LOC Home}}.html">{{LOC Home}}</a></li> <li><a href="2 - {{LOC About}}.html">{{LOC About}}</a></li> <hr /> But the pages need to be taken out of the FOR loop as well; I thought using the index count was easiest. Add {{IF document.index != '2' AND document.index != '1'}} ... {{END}} around the li element. You need the quotes around the 2 and the 1 - otherwise they evaluate as an integer, I think. But as it is there might be a problem if you have more than 9 pages... it might decide (say) 11 is between 1 and 2. Ah well - I'll cross that bridge when I come to it."
First off, you don't necessarily need to use the LOC placeholder. It's useful if you want to write a multi-language Template. Otherwise, you can simply put the following code before the FOR loop:
<li><a href="1 - Home.html">Home</a></li>
<li><a href="2 - About.html">About</a></li>
The IF condition is a bit tougher. The problem is, once you have more than 10 documents, the document index will be '01' and '02' since they are numbers < 10 are padded with zeroes. document.index is a string, that's why you need to add single quotes around them. Maybe we'll find a better for your problem. (oh and '11' and '12' should work just fine.)
Again, it's great to see people playing around with the Web Export :)
Götz