Atlantis Word Processor - ePub creation tool

[awp]

It would be nice though for search and replace to be able to copy from the text and paste into the search line.

I do not know if it is a good idea. The "View | Special Symbols" mode is not always on (actually it is off by default). Many users would not even know that a document selection contains any special symbols, and they might be confused by "special" stuff in the edit boxes of the "Find / Replace" dialog.

Have you tried running the "Tools | AutoCorrect..." command in your document? It can automatically remove extra spaces from document text.

[mrmikel]

What I need is removal of unnecessary paragraph marks at the end of every line. I guess I will just have to do it manually.

[awp]

There is a "Join paragraphs" command in Atlantis. It can remove unwanted paragraph end marks (in OCR-ed documents, for example).

Just select a text fragment that should be converted into one paragraph, and press Ctrl+Shift+U.

If text fragments representing logical paragraphs, are separated with blank paragraphs (see attached "Join pars (before).rtf"), you can select entire document (press Ctrl+A), then execute the "Join paragraphs" command (press Ctrl+Shift+U). You would get something like the attached "Join pars (after).rtf".

[mrmikel]

It does the job exactly as needed. Thanks again.

[mrmikel]

One thing that might be added to ebook help is that if you want to generate epub sections, you need to insert next page section breaks between the parts you want to be sections of the epub. Continuous won't do. Might also suggest making these breaks at each chapter, since this is good practice in making easily useable epubs.

Otherwise quite pleased with how it works with the test I made of creating simple epub from plain text. Really didn't need to do much in Sigil at all.

[awp]

There are no sections in EPUB or XHTML. As I understand, you mean "flow breaks".

Flow breaks are created by dividing the eBook contents into separate HTML files. If you have 10 HTMLs in your EPUB package, there will be 9 flow breaks (or hard page breaks) in your eBook (when viewed in eReaders).

The rule is very simple: Atlantis creates as many flow breaks in EPUB as hard page breaks in the source document.

Continuous section breaks do not create page breaks, otherwise they would not be named "continuous".

There are multiple ways to create hard page breaks in a source document:

1. (Hard/manual) page breaks can be created by pressing Ctrl+Enter (inserts a manual page break symbol), or by inserting non-continuous section breaks (the "Insert | Break | Section Break" menu).

2. When you have a "zoomed to fit page" image in your document, Atlantis also implicitly adds page breaks before and/or after it. Double-click a picture in your document to toggle the "zoom to fit page" option for this picture.

3. You can also create a page break before a paragraph by enabling the "Page break before" attribute on the "Line & Page Breaks" tab of the "Format | Paragraph..." dialog for this paragraph. Quite often this attribute is enabled in the "Heading 1" style. In this way, each chapter automatically starts at a new page.
By the way, this method is preferable over the "Ctrl+Enter" method – please click the below links for details:

http://atlantiswordprocessor.blogspo...racefully.html
http://atlantiswordprocessor.blogspo...cefully-2.html

[awp]

The rule is very simple: Atlantis creates as many flow breaks in EPUB as hard page breaks in the source document.

Two notes regarding this rule:

1. If your source document contains chapters larger than 300 KB (when saved as XHTML), Atlantis automatically creates additional page breaks within such chapters in order to produce smaller XHTMLs.

2. If your source document contains footnotes and/or endnotes, Atlantis puts them into a separate HTML file. As a result, there is a page break before notes when viewed in eReaders.

[awp]

Otherwise quite pleased with how it works with the test I made of creating simple epub from plain text. Really didn't need to do much in Sigil at all.

Could you please be more specific: what exactly do you need to modify (tweak) in EPUB files generated by Atlantis Word Processor?

[DaleDe]

Originally Posted by awp

Could you please be more specific: what exactly do you need to modify (tweak) in EPUB files generated by Atlantis Word Processor?

I have found a few things. Generation of the ePub is not WYSIWYG. For example if I define a space between paragraphs in my style settings it is not transferred to the ePub. Much of the style does transfer over but not this information.

Dale

[mrmikel]

There is a name sort as metadata in Sigil that is not in AWP.

Some things AWP does, like seeming to add a carriage return when I apply a heading, may be matters of configuration. AWP sees it as yet another paragraph, I think. For Sigil, it is just a tag...a different in point of view I may need to get used to.

[DaleDe]

Another thing I could not get to transfer from the style to the ePub is keeping two paragraphs together so that a heading wouldn't be left at the end of a page all by itself.

Dale

[awp]

if I define a space between paragraphs in my style settings it is not transferred to the ePub.

I cannot reproduce this. When a paragraph in an Atlantis document has "space before" and/or "space after" it, this "space" is supposed to be saved to EPUB.

If you can reproduce this, please email your sample document to support@AtlantisWordProcessor.com, or attach it to your forum post.

[awp]

Some things AWP does, like seeming to add a carriage return when I apply a heading, may be matters of configuration.

Atlantis never creates extra paragraphs when you apply styles. Possibly what you think is a new paragraph, is just a "space after" the heading. In many cases, the "Heading 1" style includes "space before" and "space after" within its paragraph format.

Please enable the "View | Special Symbols" mode. When this mode is on, you could see paragraph end marks (pilcrow symbols) terminating each paragraph in your document.

There is a name sort as metadata in Sigil that is not in AWP.

I am not sure that understand what you mean. You can specify "metadata" directly in the "Save as eBook" dialog of Atlantis:

[awp]

Another thing I could not get to transfer from the style to the ePub is keeping two paragraphs together so that a heading wouldn't be left at the end of a page all by itself.

The "avoid" value of the "page-break-after" CSS property does not seem to be widely supported by the HTML rendering software. If it is "overused" in an HTML document, it can lead to display problems.

Are you sure that all major eReaders support the "avoid" value of the "page-break-after" CSS property?

[DaleDe]

Originally Posted by awp

I cannot reproduce this. When a paragraph in an Atlantis document has "space before" and/or "space after" it, this "space" is supposed to be saved to EPUB.

If you can reproduce this, please email your sample document to support@AtlantisWordProcessor.com, or attach it to your forum post.

Sorry, I did not mean a space like the character. I meant space as in distance. I do not double space between paragraphs. I set the margin around the paragraph to be what I want. I create space by setting the margin. If you changed the margin in the style for the paragraph and then it stayed in the ePub (transferred to the CSS) then I would like to see that.

Dale