make-or-break #2 (priority: gap critical)

[atomrab]

For students to use this effectively, they have to be able to see where they are in the book, not just from the timeline. There should be some indication with each chunk of text that the reader is at 5.14 or whatever. There also needs to be a way to jump to a chunk of text -- this seems to be possible in the navigation field at the bottom, so maybe when the book issue is fixed that will solve that problem.

[atomrab]

A corollary of this is that it would be really helpful to have some indication of book divisions in the frequency graphs, even a faint dividing line. Students will almost invariably be guided through Herodotus by book, as are professional scholars (we talk about stuff from "book 4" as shorthand).

[enridaga]

@ekansa @atomrab (it may be silly to ask) but I have in the hestia book data the following (thanks @ekansa):

Sections:
0: {section:1, firstPage:1}
1: {section:2, firstPage:217}
2: {section:3, firstPage:405}
3: {section:4, firstPage:565}
4: {section:5, firstPage:770}
5: {section:6, firstPage:903}
6: {section:7, firstPage:1047}
7: {section:8, firstPage:1304}
8: {section:9, firstPage:1455}

how this relate to the examples of @atomrab when he says "There should be some indication with each chunk of text that the reader is at 5.14 or whatever" ?

Does X.YY map to Section.Page ?

[ekansa]

Yes! I think that is the way it goes.

[atomrab]

Hi, guys,
So the "section" element in what you have is actually the book in
Herodotus (the Histories are divided into 9 books). And the firstPage
element should actually start again at 1 for each section/book -- so that
instead of 9.1455, you have 9.1 (see, for example, here:

http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.0126%3Abook%3D9%3Achapter%3D1%3Asection%3D1

but ignore the second decimal point; this indicates a subdivision
(book.chapter.section) that we're not using for Hestia).

For students to be able to navigate in a familiar way, they have to be able
to jump to, say, book 4, chapter 10 (4.10) -- not book 4, chapter 780
(which doesn't exist in the text), or "page 780" (which also doesn't exist
in the text). The reason the work is divided in this way, rather than by
page number, is that an infinite number of editions and translations of
Herodotus have been produced, all with different pagination -- so the only
way you can find your way from one version to the next is by the canonical
text divisions (book.chapter) that they all share. Is that clearer?

Thanks!

Adam

On Fri, Dec 6, 2013 at 4:38 PM, Eric Kansa notifications@github.com wrote:

Yes! I think that is the way it goes.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-30035791
.

[enridaga]

It is, thank you!

[enridaga]

This have been implemented.
When sections are available, GapVis uses this information to display the page number as section.page .
It is now possible to jump to a page using the section.page reference or as usual using the serial page number.
Note the changes are fully backward compatible, in other words for books not providing sections info the behaviour remains the same as before.

See http://enridaga.github.io/gapvis/gap2 for the version with sections

See http://enridaga.github.io/gapvis/gap for the version without sections

[atomrab]

Hey, Enrico,
Two bugs (post here or on github?).

1. There should never be a page zero (every book starts 3.1, not 3.0).

2. When I jump to a section by typing 2.1 into the navigation field, the
   text jumps, but the timeline/map does not synchronize (it does so only when
   I hit previous/next).

On Tue, Dec 10, 2013 at 5:23 PM, Enrico Daga notifications@github.comwrote:

This have been implemented.
When sections are available, GapVis uses this information to display the
page number as section.page .
It is now possible to jump to a page using the section.page reference or
as usual using the serial page number.
Note the changes are fully backward compatible, in other words for books
not providing sections info the behaviour remains the same as before.

See http://enridaga.github.io/gapvis/gap2 for the version with sections

See http://enridaga.github.io/gapvis/gap for the version without sections

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-30279046
.

[atomrab]

Oops, and 3) the timeline needs to show the book/chapter divisions as
well... since these numbers aren't pages in any real sense, showing them as
an uninterrupted sequence counting up from 1 to 1XXX is at best not useful
and at worst very confusing.

On Tue, Dec 10, 2013 at 5:48 PM, Adam Rabinowitz
adam.rabinowitz@gmail.comwrote:

Hey, Enrico,
Two bugs (post here or on github?).

1. There should never be a page zero (every book starts 3.1, not 3.0).

2. When I jump to a section by typing 2.1 into the navigation field, the
   text jumps, but the timeline/map does not synchronize (it does so only when
   I hit previous/next).

On Tue, Dec 10, 2013 at 5:23 PM, Enrico Daga notifications@github.comwrote:

This have been implemented.
When sections are available, GapVis uses this information to display the
page number as section.page .
It is now possible to jump to a page using the section.page reference or
as usual using the serial page number.
Note the changes are fully backward compatible, in other words for books
not providing sections info the behaviour remains the same as before.

See http://enridaga.github.io/gapvis/gap2 for the version with sections

See http://enridaga.github.io/gapvis/gap for the version without sections

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-30279046
.

[enridaga]

Ok, 1 and 2 are solved. 3 is not easy, need some time.

[atomrab]

Is the original Hestia code (interface here:
http://hestia.open.ac.uk/herodotus/basic.html) useful for this?

On Tue, Dec 10, 2013 at 7:52 PM, Enrico Daga notifications@github.comwrote:

Ok, 1 and 2 are solved. 3 is not easy, need some time.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-30287349
.

[enridaga]

Apparently I saw the light right after my last comment.
3 should be fixed now :)

(and thank you @atomrab for the notice)

On 11 December 2013 01:58, atomrab notifications@github.com wrote:

Is the original Hestia code (interface here:
http://hestia.open.ac.uk/herodotus/basic.html) useful for this?

On Tue, Dec 10, 2013 at 7:52 PM, Enrico Daga notifications@github.comwrote:

Ok, 1 and 2 are solved. 3 is not easy, need some time.

—
Reply to this email directly or view it on GitHub<
https://github.com/ekansa/gap2/issues/2#issuecomment-30287349>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-30287635
.

Enrico Daga

http://www.enridaga.net
skype: enri-pan

[enridaga]

This is fixed, FWIW. Feel free to reopen if needed (or create another issue for emerging bugs in this area...)