Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xml:id's #21

Open
JoernT opened this issue May 2, 2016 · 1 comment
Open

xml:id's #21

JoernT opened this issue May 2, 2016 · 1 comment

Comments

@JoernT
Copy link
Member

JoernT commented May 2, 2016

Some texts (e.g. Nyāyabinduṭīkā and Dharmottarapradīpa) have now a TOC in the linking to the verses of the base-text. The xml:id's still have to be processed so that the links work in html.

@JoernT
Copy link
Member Author

JoernT commented May 2, 2016

copied from original ticket:

#1 - 09/23/2015 05:07 PM - Claudius Teodorescu - Status changed from New to In Progress
#2 - 09/23/2015 06:02 PM - Claudius Teodorescu
Hi,
The links in the TOC are working now, but they point to the document itself. Can you give me a link to what the first one for Nyāyabinduṭīkā should point to? I mean what user should see in the browser?
#3 - 09/23/2015 08:44 PM - Liudmila Olalde

  • File dharmottarapradipa.html added
    Dear Claudius,
    I have attached an html generated by oXygen. The links there work, so you can check there where they are supposed to point to.
    adapt new site css to old site css #4 - 09/24/2015 08:54 AM - Claudius Teodorescu
    Thanks, this is exactly as I thought, as it is the behaviour for the HTML pages, etc.
    But what would be the behaviour in the context of sarit, as the TOC is on a separate page, and an user is seeing parts of the work, on a page by page basis?
    I would be very glad if you can provide me a "visually" description of such behaviour.
    Document list should be output as table #5 - 10/20/2015 01:15 PM - Birgit Kellner
    The user should see the element of the target reference plus a few paragraphs, I suppose, no?
    I think it would be ideal to have (a) a TOC on the left side and (b) when navigating through the TOC items, the target element (plus a few paragraphs) shows up on the right side. The TOC might be toggled away if the user chooses to then just browse the text further, and the text itself should have "previous" and "next" links that operate as in other texts. -- That would be my idea for navigation.
    It appears from http://sarit.indology.info/exist/apps/sarit/works/pramanavarttikavrtti.xml_1.5.3.2.html#div_pvv.1.1 that the TOC feature is already "live", but it does not work as expected (clicking on the links in the TOC does not open the verse(s)) in question.
    04/13/2016 1/2
    Link from search results doesn't work #6 - 10/28/2015 03:50 PM - Liudmila Olalde
  • Assignee changed from Claudius Teodorescu to Wolfgang Meier
    Cut sarit-pm dependency from old sarit project #7 - 10/28/2015 04:11 PM - Liudmila Olalde
  • Duplicated by Feature #761: New website: browsing added
    Todo: CSS fix headline for mobile view #8 - 11/15/2015 10:27 PM - Liudmila Olalde
    Dear Wolfgang,
    We had agreed in July that I would add a verse-TOC to some of the documents in the database because looking for a certain verse within these texts is much more useful than looking for a chapter. As you suggested, I used ref-elements that link to the verses:
    The problem is that the app does not process the xml:id's properly (I think). So clicking on the links in the TOC leads you to the beginning of the whole document and not to the beginning of the block-element that has the corresponding xml:id. Could you please take care of this? The documents that have a verse-TOC are (the older versions currently in the Showcase don't have the TOC!):
  • Nyāyabinduṭīkā and Dharmottarapradīpa 2. Pramāṇavārttika
  • Tattvasaṅgrahapañjikā

    nb.1.1

    CSS: Add color scheme #9 - 11/15/2015 10:29 PM - Liudmila Olalde
  • Subject changed from Table of contents to Verse-TOC
    Markup for document-list links are generated as muli-line <h1> headings #10 - 11/15/2015 10:45 PM - Liudmila Olalde
  • Tracker changed from Feature to Bug
    Enable code highlighting or wrap preformatted markup with pre and code in documents #11 - 11/15/2015 11:06 PM - Liudmila Olalde
  • Duplicated by deleted (Feature #761: New website: browsing)
    Empty href attributes in document links #12 - 04/13/2016 04:53 PM - Liudmila Olalde
  • Subject changed from Verse-TOC to xml:id's
    Although I've deleted the TOCs, we still have cross-references in the files (@target, @sameas, @corresp, @next, @Prev) that point to xml:id's within the database . These xml:id's have to processed in order for the HTML-links to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant