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

ePub files with table tr td #46

Closed
jagadeesanb opened this issue Jul 19, 2011 · 5 comments
Closed

ePub files with table tr td #46

jagadeesanb opened this issue Jul 19, 2011 · 5 comments

Comments

@jagadeesanb
Copy link

We have problems customizing monocle to suit for ePub files with TABLE, TR, TD tags.. Then we found that none of monocle ePub sample files has those tags, could someone explain why? Thanks!

@joseph
Copy link
Owner

joseph commented Jul 19, 2011

No reason, I just don't work with many books with tables. I can investigate if you describe these problems.

@jagadeesanb
Copy link
Author

We have been trying to customize to implement features like bookmarks, highlights and search... We face two problems when the books have tables:

  1. When (custom) searching, we cannot navigate to the precise search result location when the searched item is available within a table in a paragraph or within a paragraph in a table.

  2. When adding a note or bookmark, we attach it to a unique html tag and treat this as ID. This way, we could reload them when the book is reloaded. Now, we have problem locating the unique html tags.

Please advise.

@joseph
Copy link
Owner

joseph commented Aug 4, 2011

From the description, it sounds like the problems you're having relate to a layer of functionality you're implementing above Monocle. It's not clear where Monocle can assist with this. Perhaps you could isolate the simplest possible test-case demonstrating the problem, either in a gist or in a commit to the test/bugs directory.

@jagadeesanb
Copy link
Author

Joseph,

Thank you for your reply. You are right, we are trying to customize Monocle
to add some more features and the layer could most probably obstruct the
expected behavior. We will come up with the simplified version and
demonstrate the problem, or will let you know if we found a fix.

Regards,
Jagadeesh

On Wed, Aug 3, 2011 at 7:01 PM, joseph <
reply@reply.github.com>wrote:

From the description, it sounds like the problems you're having relate to a
layer of functionality you're implementing above Monocle. It's not clear
where Monocle can assist with this. Perhaps you could isolate the simplest
possible test-case demonstrating the problem, either in a gist or in a
commit to the test/bugs directory.

Reply to this email directly or view it on GitHub:
#46 (comment)

@joseph
Copy link
Owner

joseph commented Feb 7, 2012

I'm closing this as 'answered'. But please re-open if you do come up with that simplified version or fix.

@joseph joseph closed this as completed Feb 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants