openlp-core team mailing list archive

[Meinert Jordan <876211@xxxxxxxxxxxxxxxxxx>]

Hmm,
so <lines break="optional">...</lines> means, that there is a optional break after the lines block?

In the end we need to have theese kinds of page brakes:
- hard page break (will be implemented as parte e.g. v1a, v1b)
- preferred page break ([---], or call it optional)
- prohibited break

The prohibited break is necessary to make shure, that diffenent parts
which are sung at the same time appear on the same slide. It has the
similar effect like adding a preferred page break at all other positions
(but you might want to use both kinds in the same song).

Samuel, would you please explain the exact semantic of the break
attribute?

** Changed in: openlp
     Assignee: (unassigned) => Meinert Jordan (m2j)

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/876211

Title:
  OpenLyrics export non-compliant for split verses

Status in OpenLP - Worship Presentation Software:
  Confirmed

Bug description:
  OpenLP 1.9.7

  When exporting to OpenLyrics there is a case where the file created is non-compliant to the OpenLyrics standard.
  In OpenLP, the only way to obtain a 'hard break' (split verse across two or more slides) is to create separate consecutive 'verses' but number them the same:
  ---[Verse:1]---
  Amazing grace! How sweet the sound
  That saved a wretch like me;
  ---[Verse:1]---
  I once was lost, but now am found,
  Was blind, but now I see.

  When exported to OpenLyics, this results in two verses both with name="v1". However, the OpenLyrics spec says "There shouldn’t be two or more verses the same name." The correct way to indicate split verses in OpenLyrics is with name="v1a", name="v1b", etc.
  <http://openlyrics.info/dataformat.html#verse-name>

  While on this topic, should we talk about better ways to specify 'hard
  breaks' within OpenLP?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/876211/+subscriptions