Project home page > Main help page
It is assumed that very few types of text markup are needed for a fictional text:
When importing from yw7 format, the converter replaces these formattings as follows:
"> "
in yWriter, are formatted as Quote.When exporting to yw7 format, the reverse is the case.
ODF documents are generally assigned a language that determines spell checking and country-specific character substitutions. In addition, Office Writer lets you assign text passages to languages other than the document language to mark foreign language usage or to suspend spell checking.
If a document language (Language code acc. to ISO 639-1 and country code acc. to ISO 3166-2) is detected in the source document during conversion to yw7 format, these codes are set as yWriter project variables.
If language code and country code exist as project variables during conversion from yw7 format, they are inserted into the generated ODF document.
If no language and country code exist as project variables when converting from yw7 format, language and country code from the operating system settings are entered into the generated ODF document.
The language and country codes are checked superficially. If they obviously do not comply with the ISO standards, they are replaced by the values for "No language". These are:
If text markups for other languages are detected during conversion to the yw7 format, they are converted and transferred to the yWriter scene.
This then looks like this, for example:
xxx xxxx [lang=en-AU]yyy yyyy yyyy[/lang=en-AU] xxx xxx
To prevent these text markups from interfering with yWriter, they are automatically set as project variables in such a way that yWriter interprets them as HTML instructions during document export.
For the example shown above, the project variable definition for the opening tag looks like this:
lang=en-AU
<HTM <SPAN LANG="en-AU"> /HTM>
The point of this is that such language assignments are preserved even after multiple conversions in both directions, so they are always effective for spell checking in the ODT document.
It is recommended not to modify such markups in yWriter to avoid unwanted nesting and broken enclosing.
A work in progress has no third level heading.
* * *
→ Scene divider (not needed for the first scenes in a chapter).An outline has at least one third level heading.
This writes back the document's content to the yWriter project file.
This will write yWriter 7 chapters and scenes into a new OpenDocument text document (odt).
<yW project name>.odt
.<HTML>
or <TEX>
are not imported./* this is a comment */
) are converted to author's comments.* * *
. The first line is not indented. You can replace the scene separators by blank lines with the menu command Format > Replace scene dividers with blank lines.>
are formatted as quotations.This will write yWriter 7 chapters and scenes into a new OpenDocument text document (odt) with visible scene markers. File name suffix is _proof
.
<HTML>
or <TEX>
are not exported.[ScID:x]
markers. Do not touch lines containing the markers if you want to be able to write the document back to yw7 format.|
.|
.###
→ Scene divider. Optionally, you can append the scene title to the scene divider. You can also add a description, separated by |
.You can write back the scene contents to the yWriter 7 project file with the Export to yWriter command.
This will write a brief synopsis with chapter and scenes titles into a new OpenDocument text document. File name suffix is _brf_synopsis
.
<HTML>
or <TEX>
are not imported.This will generate a new OpenDocument spreadsheet (ods) containing a character list that can be edited in Office Calc and written back to yWriter format. File name suffix is _charlist
.
You may change the sort order of the rows. You may also add or remove rows. New entities must get a unique ID.
You can write back the edited table to the yWriter 7 project file with the Export to yWriter command.
This will generate a new OpenDocument spreadsheet (ods) containing a location list that can be edited in Office Calc and written back to yWriter format. File name suffix is _loclist
.
You may change the sort order of the rows. You may also add or remove rows. New entities must get a unique ID.
You can write back the edited table to the yWriter 7 project file with the Export to yWriter command.
This will generate a new OpenDocument spreadsheet (ods) containing an item list that can be edited in Office Calc and written back to yWriter format. File name suffix is _itemlist
.
You may change the sort order of the rows. You may also add or remove rows. New entities must get a unique ID.
You can write back the edited table to the yWriter 7 project file with the Export to yWriter command.
This will generate a new OpenDocument text document (odt) containing navigable cross references. File name suffix is _xref
. The cross references are:
This will replace the three-line "* * *" scene dividers with single blank lines. The style of the scene-dividing lines will be changed from Heading 4 to Heading 5.
This will select all paragraphs that start with "> " and change their paragraph style to Quotations.
Note: When exporting to yWriter, Quotations style paragraphs will automatically marked with "> " at the beginning.
This will select all paragraphs that start with "- " and apply a list paragraph style.
Note: When exporting to yWriter, Lists will automatically marked with "- " list strokes.