Re: Considering High Level Interlinear Text Requirements

Hi Sean,

I'm very pleased to meet you and to learn about the interlinear challenges
you've faced and the solutions you have arrived at.  Its eye opening and a
little more daunting a challenge than I had anticipated, but exciting at
the same time.  In your pas (and any present) work with interlinear text,
have you used xml or a markup language?

Brainstorming on how best to approach an eventual common markup language
for interlinear text, I think collecting text samples that represent use
cases, under the high level requirements, would be a good thing.  Text
sample would be images, with a citation, that demonstrate a target
rendering for e-media.  We would also transcribe the text from the images
and develop markup to encapsulate and describe the relevant parts.

Would you have any time to capture some sample use cases?  The ITLCG group
has a both a wiki page and web page available.  If your time is very
limited, you could direct me to some samples with links I could take a pass
and documenting them.

cheers,

-Daniel


On Tue, Jan 29, 2019 at 1:37 PM Sean Harrison <sah@bookgenesis.com> wrote:

> I would add
>
>
>
> 3) Multiple anchored start and end: The interlinear text is bound to two
> or more non-contiguous ranges of text.
>
>    - This is true in many cases in the relationship between the New
>    Living Translation and the Greek NT, where a particular Greek word or
>    phrase is matched by a phrase or clause that is not contiguous in English.
>    For example: http://nltinterlinear.com/Rom.1.1-32/matchup and select
>    “promised” in v. 2.
>    - In addition a particular Greek phrase may itself be non-contiguous,
>    since word order is less important in Greek and other inflected languages.
>    I don’t have a ready example of this.
>
>
>
> 4) 1 or more alignment “types”: A particular alignment relationship is of
> some particular type, and there may be different types of relationships in
> an alignment. (This is true in many cases in the relationship between the
> New Living Translation and the Greek NT, though I don’t have access to the
> data at the moment to give you details about this.)
>
>
>
> In answer to your question at the end: Yes, there are situations where the
> interlinear text was not created for the interlinear context. Example:
> http://nltinterlinear.com/Rom.1.1-32/interlinear, in which the English
> text is the NLT itself rearranged in the order of the Greek.
>
>
>
> FD + Disclaimer: I wrote the software the powers http://nltinterlinear.com
> nearly 10 years ago, but I am no longer its maintainer (and it has been
> largely unmaintained).
>
>
>
> –Sean
>
>
>
> [image: image001.png]
>
> *Sean Harrison*
>
>
>
> sah@bookgenesis.com
>
>
>
>
>
>
>
> *From: *Daniel Yacob <yacob@geez.org>
> *Date: *Sunday, January 27, 2019 at 10:02
> *To: *"public-itlcg@w3.org" <public-itlcg@w3.org>
> *Subject: *Considering High Level Interlinear Text Requirements
> *Resent-From: *<sah@bookgenesis.com>
> *Resent-Date: *Sunday, January 27, 2019 at 10:02
>
>
>
> Greetings All,
>
>
>
> At this point there may be only two of on the mail list.  Though more have
> expressed interest in enhancing interlinear text support in w3c standards,
> there is likely a lack of awareness that the group has formed -so get the
> word out :-)
>
>
>
> I thought I would start a conversation on very high level requirements for
> interlinear text as it relates to base text.  From observation, interlinear
> text has at least two alignment associations:
>
>
>
> 1) Anchored start:  The interlinear text is "anchored" or "bound" to one
> or more contiguous letters in the base text.  The interlinear text aligns
> at the anchor point and continues to its end, which may span one or more
> base lines.
>
>
>
> 2) Anchored start and end: The start and end points of interlinear text
> are each anchored to one or more contiguous letters in the base text. The
> "margins" of the IL text are within the start and end anchors.  Alignment
> (left, right, center) and letter distribution of the IL text is also
> specified (e.g. CSS ruby-align attribute values).
>
>
>
> These definitions should be valid for both RTL and LTR text.  Ruby and
> Zaima interlinear text would fall under the "Anchored start and end"
> category.  Ruby, and even more so Zaima, annotation practices are what I am
> most familiar with -and little else.  The "Anchored start" (1), with no
> fixed end point I gather is essential to other interlinear use cases.
>
>
>
> Thoughts? Is there another high level requirement?  Is interlinear text
> ever fully independent of the content of the base text?
>
>
>
> cheers,
>
>
>
> -Daniel
>
>
>