Not logged in. · Lost password · Register
Page:  1  2  3 ... 17  18  19  next 

All posts by rgleason (272)

topic: Media Manager no longer works as it did  in the forum: General Help and Support Features and Functionality
Avatar
rgleason #1
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
Subject: Media Manager no longer works as it did
I have found that Media Manager no longer permits me to create a new sub - namespace in the url.
That field is locked out and not editable for some reason.
I used to be able to create a new namespace, then upload a file into the namespace (which acts as a placeholder to keep the new directory in place) and to insert that image into a page.  All through the media manager.
I can no longer do this.
I have also checked the namespaces with Move Manager and they all appear to be there, but I did not try to move anything yet, as I cannot create a new subnamespace for new media files.

Additionally my editors are finding that they do not have access to normal media manager folders as they used to.
I have checked all the permissions and they appear to be unchanged and correct.

One of the managers is trying to upload photos for his new version of an OpenCPN plugin and he is having difficulty. I quote his report below:

Hi Rick,
   The issue I am having is that the Media Manager and the 'Insert Image/Browse Server" locations are different. In the media manager the OD images are in:
[root]/opencpn/manual/plugins/odraw
but the insert image/browse server only lets me get to:
/opencpn/opencpn_user_manual/plugins/safety

I have already uploaded the new images to a subdirectory of odraw via the media manager, but I cannot get to this location by the browse server process. It would appear that the browse server is not seeing all of the directories available. The media manager does not even see the opencpn_user_manual directory.

Perhaps there is a permissions issue.

Regards
   Jon

Does anyone have some suggestions regarding this problem?
Has the way that Media Manager works been changed recently?

IPOF  The way Media Manager has worked in the past, with regard to creating new namespaces has always been byzantine and obscure, in my opinion, and I had hoped that it would have been improved. I have always had to handle these kinds oof tasks for my manager/editors as they do not use these tools regularly.  An improvement would be very welcome.
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #2
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 65942
Now I am finding when I bring the 20mb epub result of this code:

<epub:User Manual-2>
:opencpn:opencpn_user_manual:*

direct into Sigil and I am prompted for fixing html which I did.
Then I used the epub fix tools and went to the first page, and the links all work properly.

Why are the links not working properly when each page is listed fully?
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #3
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 65939
Okay after recreating my earlier listing of each namespace with its title

[[opencpn:opencpn_user_manual|OpenCPN User Manual]]

[[opencpn:opencpn_user_manual:toc|Table of Contents]]
   [[opencpn:opencpn_user_manual:getting_started|Getting Started]]
       [[opencpn:opencpn_user_manual:getting_started:opencpn_installation|OpenCPN Installaton]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:windows|Windows]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:ubuntu_ppa|Ubuntu PPA]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:linux|Linux]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:fedora|Fedora]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:mac_os_x|MacOSx]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:orange_pi|Orange Pi]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:dedicated_marine_os|Dedicated Marine OS]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:raspberrypi_rpi2|RaspberryPi]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:android|Android]]
          [[opencpn:opencpn_user_manual:getting_started:opencpn_installation:release_history|Release Directory]]
       [[opencpn:opencpn_user_manual:getting_started:opencpn_first_use|OpenCPN First Use]]
       [[opencpn:opencpn_user_manual:getting_started:gps_setup|GPS Setup]]
       [[opencpn:opencpn_user_manual:getting_started:chart_installation|Chart Installation]]
       [[opencpn:opencpn_user_manual:getting_started:setting_option|Setting Options]]
       [[opencpn:opencpn_user_manual:getting_started:marks_and_routes|Marks and Routes]]
       [[opencpn:opencpn_user_manual:getting_started:touch_screen_tablets|Touch Screen Tablets]]
       [[opencpn:opencpn_user_manual:getting_started:help_fix_bugs|Help fix Bugs]]
   [[opencpn:opencpn_user_manual:getting_around|Getting Around]]
 and so on for pages, done completely manuallly

I tried this at the top, after reading the manual.

<epub:User Manual-2>
:opencpn:opencpn_user_manual:*

With this result


Directory: /home/szlhykiz/public_html/wiki/dokuwiki/data/pages/opencpn/opencpn_user_manual
Found following pages in :opencpn:opencpn_user_manual:* namespace:
Array
(
    [0] => :opencpn:opencpn_user_manual:toolbar_buttons
    [1] => :opencpn:opencpn_user_manual:toc_offline_user_manual_charts
    [2] => :opencpn:opencpn_user_manual:toc_offline_user_manual
    [3] => :opencpn:opencpn_user_manual:toc_offline_plugins_manual
    [4] => :opencpn:opencpn_user_manual:toc_offline_advanced_features
    [5] => :opencpn:opencpn_user_manual:toc
    [6] => :opencpn:opencpn_user_manual:terminology
    [7] => :opencpn:opencpn_user_manual:plugins
    [8] => :opencpn:opencpn_user_manual:options_setting
    [9] => :opencpn:opencpn_user_manual:menubar
    [10] => :opencpn:opencpn_user_manual:license_and_authors
    [11] => :opencpn:opencpn_user_manual:getting_started
    [12] => :opencpn:opencpn_user_manual:getting_around
    [13] => :opencpn:opencpn_user_manual:faq
    [14] => :opencpn:opencpn_user_manual:epub
    [15] => :opencpn:opencpn_user_manual:editors
    [16] => :opencpn:opencpn_user_manual:charts
    [17] => :opencpn:opencpn_user_manual:advanced_features
)
Saving namespace pages
Created following titles:
Array
(
    [0] => Toolbar Buttons
    [1] => Toc Offline User Manual Charts
    [2] => Toc Offline User Manual
    [3] => Toc Offline Plugins Manual
    [4] => Toc Offline Advanced Features
    [5] => Toc
    [6] => Terminology
    [7] => Plugins
    [8] => Options Setting
    [9] => Menubar
    [10] => License And Authors
    [11] => Getting Started
    [12] => Getting Around
    [13] => Faq
    [14] => Epub
    [15] => Editors
    [16] => Charts
    [17] => Advanced Features
)
processed: :opencpn:opencpn_user_manual:advanced_features
processed: :opencpn:opencpn_user_manual:charts
processed: :opencpn:opencpn_user_manual:editors
processed: :opencpn:opencpn_user_manual:epub
processed: :opencpn:opencpn_user_manual:faq


Which is great, but it does not seem to be going down to lower levels.

When I download the file and use Calibre I notice that internal links are still shown as  Name [174] for example. The link goes to a reference to an "internal page" which it should not as far as I understand. This used to work properly.

When I download the file and use Sigil, I notice that the internal links are still shown as Name [174] for example. Link goes to a reference to an internal page similar to these in the footnotes:

opencpn_opencpn_user_manual.html

[1] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:getting_started
[2] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:getting_around
[3] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:charts
[4] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:options_setting
[5] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:toolbar_buttons
[6] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:menubar
[7] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:plugins
[8] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:advanced_features
[9] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:terminology
[10] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:faq
[11] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:license_and_authors
[12] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:editors
[13] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:getting_started
[14] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:getting_around
[15] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:toolbar_buttons
[16] https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:menubar

I am wondering what I am doing wrong here.
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #4
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 65938
With epub, I need to have each page that I want to export in this fashion

[[opencpn:opencpn_user_manual:getting_started|Getting Started]]

one page after another. 

I consider that "hard coded", as compared to what indexmenu does, which uses the file structure and some specific directions to create a "dynamic on the fly" TOC.

Maybe I am thick. ..Say I just wanted it to export all pages from this namespace down to the bottom, even including [blank] pages?

[[opencpn:opencpn_user_manual|User Manual]]

Is there a command for a way to do that?
Is there a command to not include a namespace and namespaces below that?
Thinking about this situation, is there a command to exclude [blank] pages?
This post was edited on 2019-05-09, 22:52 by rgleason.
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #5
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 65936
Subject: epub for OpenCPN documentation
Myron, Thankyou.  As you know we are now using epub for OpenCPN documentation, having found it much easier to work with.

I am trying to find an easy way to create the hard coded pages that epub requires. Perhaps you have some suggestions.

From this TOC User Manual namespacee  https://opencpn.org/wiki/dokuwiki/d…?id=opencpn:toc&…
if I look at the page source we have all the information needed  (plus the excess html)

This has been generated by Indexmenu and we are using this format

%%{{indexmenu>:opencpn#4|msort nsort nojs skipns=/(^opencpn:developer_manual$|^opencpn:supplementary_software$|^opencpn:supplementary_hardware$|^opencpn:user_corner$|^opencpn:opencpn_user_manual:charts:advanced_chart_work$|^opencpn:opencpn_user_manual:charts:pilot_charts$|^opencpn:opencpn_user_manual:editors$|^opencpn:opencpn_user_manual:edit_user_manual$|^opencpn:opencpn_user_manual:gallery_boats$)/}}%%

The relevant part of the page source looks like this:

<li class="open"><div class="li"><a href="/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:getting_started" class="indexmenu_idx_head">Getting Started</a></div>

Do you know of an easy way to get it formatted like this for epub?

[[opencpn:opencpn_user_manual:getting_started|Getting Started]]

Maybe IndexMenu would be able do that in it's output, by having a trigger that would show the path & title in that format?  Then I could just highlight and copy the screen output and a special epub file would not have to be maintained through all the documentation changes. This list of pages could be made when we are going to publish.

What I actually need is something like to old dos "dir > filename.txt"

Who would I talk to about this possibility?  It would dovetail nicely with epub.

BTW we have just released OpenCPN version 5.0 and everyone is hard a work answering user questions and fixing bugs,  but the Dokuwiki documentation is still for v4.8.8. When the dust settles we are going to have to update the manual and hopefully package it differently.

One of the goals is to package separate smaller epub modules for documentation, and the second goal is to have a very stripped down "Basic Manual" that will ship with the software. To do this we need to place html on a github page (it will just be one, for the purpose of packaging). Is there a reasonable way to accomplish that from the Dokuwiki?  IE convert it to html and then publish to github?

Thank you for all your help and advice. It has always been right on the mark!

PS I've been using Sigil, but I understand the best process is to use Calibre and clean up the html and then bring it into Sigil and use their tools for html and epub, including the Table of Contents feature.  I've found what I think are recent Calibre changes to be more confusing but perhaps that will go away as I get back into it.
This post was edited 2 times, last on 2019-05-09, 22:29 by rgleason.
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #6
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62795
Dear Myron,

I am back at it with epub. I mistakenly deleted my epub text file on my local drive, so I am recreating it, and using epub to create and download an epub, that I load into Sigil and then use tools to fix and clean up Html, then clean up Epub, and then I check the links and I am finding many of the internal links showing as  Title[some number] for an external reference.
Why is the transition process treating these links as external when they should be internal?
   
Do you by any chance know why would this be happening? 
Is there a quick way to get these internal links to work properly?

Wish I could upload an image.
topic: Internationalization of Wiki's using Dokuwiki (OpenCPN needs to translate the User Manual to multiple languages)  in the forum: General Help and Support General Stuff
Avatar
rgleason #7
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 63208

Is Dokuwiki set up so that users of OpenCPN who want to read the Opencpn User Manual (dokuwiki) can easily select which language files to be using?


It appears that thehttps://www.dokuwiki.org/plugin:translation Translation Plugin will allow the user to select a language, but the way it is described, that appears to be a per page selection.  IE go to the page and then select the language. We would need something more comprehensive for the entire User Manual. We need to find out more about this.


Is Dokuwiki itself and the Plugins (that we use for OpenCPN) translated to multiple languages?


1. Yes, it appears that Dokuwiki and a number of it's plugins have been translated and the selection of the language is made in the Config file.  See Localization of Dokuwiki https://www.dokuwiki.org/localization

2. Directions for consistent translations: https://www.dokuwiki.org/teams:i18n:consistenttranslations

3. See the list of languages available at this point where you can download the various versions https://download.dokuwiki.org/ These versions will need to be hosted on the opencpn.org website, along with the versions of the plugins.

4. See the list of plugin translations available here https://translate.dokuwiki.org/
Upgrade Plugin, Wrap, Gallery, Captcha, Indexmenu, Move, Translation, Dw2PDF, Ckgedit, Multiorphan, etc.
Looks pretty good, but some translations will be needed.

We next need to determine which languages and implement that on the opencpn.org website.

There may be some translation needed for Dokuwiki and plugins to get this completed.
Then the next task would be to build the crowdsource files and test out the OpenCPN translation process.

Are there some public dokuwiki websites with multiple languages that can be looked at for examples?
In looking for this I found an old plugin called Mutilingual https://www.dokuwiki.org/plugin:multilingual
and instructions are here https://www.inmotionhosting.com/support/edu/dokuwiki/chang… however I believe Adreas Gohr's plugin Translation is far advanced https://www.dokuwiki.org/start?id=plugin:translation

Here is a spanish help version of the Translation plugin
https://www.dokuwiki.org/es:plugin:translation#translation…

Here is French (no translation yet)
https://www.dokuwiki.org/start?id=fr:plugin:translation

Here is Japanese
https://www.dokuwiki.org/start?id=ja:plugin:translation

And Russian
https://www.dokuwiki.org/start?id=ru:plugin:translation

Note the Namespace standard:   Language [two characters?]:plugin:[plugin name]

I expect that there is a similar standard for various language files for dokuwiki itself.

Yes, this is the page for French Translation  https://www.dokuwiki.org/start?id=fr:dokuwiki
from the left dropdown, German https://www.dokuwiki.org/start?id=de:dokuwiki
Italian https://www.dokuwiki.org/start?id=it:dokuwiki
https://www.dokuwiki.org/start?id=nl:dokuwiki

So the namespace structure for multiple language versions of Dokuwiki is
[Language two characters]:dokuwiki


Another question related to translation of the  OpenCPN User Manual is will the IndexMenu Sidebar feature work, such that the Titles of each page in the translated version be used to create the sidebar navigation?

I believe the answer is yes, I believe it will work this way, but we will have to try it.

See this github issue however...
https://github.com/splitbrain/dokuwiki-plugin-translation/…
He is using Sidebar in a different way than we are however.  We are using IndexMenu and the Page/Namespace titles to create the Sidebar navigation.
This post was edited 3 times, last on 2018-10-20, 19:44 by rgleason.
topic: Internationalization of Wiki's using Dokuwiki (OpenCPN needs to translate the User Manual to multiple languages)  in the forum: General Help and Support General Stuff
Avatar
rgleason #8
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
Subject: Internationalization of Wiki's using Dokuwiki
We have a crowd sourced method to engage and manage internationalization for the program OpenCPN which is associated with github.

This is a link to a description of the process  (needs some updates)
https://opencpn.org/wiki/dokuwiki/doku.…?id=opencpn:deve…

We would like to use the same crowd sourced methods and github to manage translation of the User Manual for OpenCPN.

This will result in different data text files for each language.

Is Dokuwiki set up so that users can easily select which language files to be using?

I expect that the dokuwiki help files for the various plugins in a number of languages will be available, but some of the languages will be swedish etc. which will be needed too. Perhaps these can be done by our translators too?

I would like to know how "ready" Dokuwiki is for this type of use.

Are there any example websites I could look at?

Thanks.
This post was edited on 2018-10-17, 17:08 by rgleason.
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #9
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62746
Myron,

I am going to do some tests locally, to determine exactly what happens, and will report back here, ok. I should have done that myself, but I was pressed at the time I wrote too. Sorry.
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #10
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62483
Subject: Links to Titles - both on the same page and to another page
Myron, Note:I have not tried the most recent Epub extension, that I just updated.
I have been using the results of the previous version and learning how to correct it using Calibre.
There are a number of important links to "Titles" in the text that are not working very well, perhaps partially because we are not using the appropriate namepace#Title link configurations in the original dokuwiki to achieve a successful result and partially because Epub may not be recognizing the links properly and outputting them.

Here is what I have been doing for about a week, changing all links in the EPUB book to conform to the following.

Hyperlinks to Titles within namespace/pages:

    For the Hyperlink:  <a href "#create_a_mark">Create a Mark</a>
    For the Heading: <h2 id="create_a_mark"> Create a Mark</h2>

Hyperlinks to Titles in other namespaces/pages:
    For the Hyperlink:  <a href="opencpn_opencpn_user_manual_options_setting_display.html#the_display">The Display</a>
    For the Heading: <h1 id="the_display" class="calibre5">The Display</h1> 

Which works in EPUB.



Please advise what the correct format should be for links to work properly when converted to EPUB by Epub Extension,
for
Hyperlinks to Titles within internal namespace/pages
Hyperlinks to Titles in other namespaces/pages

In the case of internal links to Titles is it preferred to just use 
 <a href "#create_a_mark">Create a Mark</a>  ?

In the case of external links to Titles in other namespace/pages is it preferred to use the full namespace?
<a href="opencpn_opencpn_user_manual_options_setting_display.html#the_display">The Display</a>

Will both of these translate properly with the Current Epub?

I'd like to go through the entire original online document and correct all of these so they will work when translated to Epub.
Thanks,
topic: Local server-Bitnami Dokuwiki - php - max_execution_time  in the forum: General Help and Support Installation and Configuration
Avatar
rgleason #11
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62456
The problem was being created by SiteExport plugin which always runs out of execution time when running large jobs. The SiteExport problem was not solved.

I finally gave up on it after two + years and moved to Myron's Epub Extension which is working much much better. Thanks for your help.
topic: Pipe dynamically created Indexmenu to a text file for use with Myron's Epub Extension  in the forum: General Help and Support Features and Functionality
Avatar
rgleason #12
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62368
Subject: Thank you!  Nice Table of Contents!!!
Dear Myron,
It has been awhile since I was on the forum. This suggestion to use Sigil to generate the TOC is going to save hours!
It also has links to all Titles and an great TOC search. I really appreciate the Playground example above.
This will save hours of manual TOC editing.

I think this will solve my request "Pipe dynamically created Indexmenu to a text file for use with Myron's epub extension"  very nicely.
Thank you!

I've been busy, cleaning up the epub, learning how to use the tools in Calibre to fix everything that is wrong. I did eventually remove unused CSS, etc. and started trying to fix broken links. More on that in another post.

Thanks Again!
Rick
topic: ePub Extension  Link/Bookmarks to Titles (Links/Bookmarks to titles)  in the forum: General Help and Support Plugins
Avatar
rgleason #13
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
Subject: ePub Extension  Link/Bookmarks to Titles
First of all, I would like to report that this ePub Extension is superb. We now have a very useful ePub User Manual for OpenCPN with a fully operational Table of Contents which matches the  IndexMenu "sidebar"  (I had to recreate this manually in Calibre, but it was not very difficult to do.  Sometime it would be nice if it could be made automatically.) This manual is 23mb and can be converted to PDF as well and then optimized for the web to be compressed to 23mb as well.  Epub Extension is the first time we have been able to create good documentation from Dokuwiki without a huge headaches and excessive time laboriously editing html.  Thank you Myron and the rest of the Team!

There several aspects that need some improvement IMHO:
1. Automatic generation of TOC either with the use of a special TOC page, or by using the Indexmenu sidekick page.
2. Handling of # Link/Bookmarks to Titles  (for #title links to within a namespace and #title links to other namespaces.

I am finding that these types of Dokuwiki links do not translate properly.
I had over 500 error/warnings on a recent conversion and the majority of the problems were related to the use of "#" in either the relative or absolute path form.

Referencing other pages, and including a Title

as in https://opencpn.org/wiki/dokuwiki/doku.…?id=opencpn:open…
**__[[opencpn:opencpn_user_manual:options_setting:display|The Display]]__ ** \\
 //[[opencpn:opencpn_user_manual:options_setting:display#general|General]]\\
 [[opencpn:opencpn_user_manual:options_setting:display#units|Units]]\\
 [[opencpn:opencpn_user_manual:options_setting:display#advanced|Advanced]]//\\
It seems to me that the ePub Extension when converting to epub, should inserting bookmarks at the proper location to make these links work properly.  Please see the quote and reference below about the use of # and bookmarks in epub.  Thanks. Rick


Referencing the same page and including a Title

As in https://opencpn.org/wiki/dokuwiki/doku.…?id=opencpn:open… Scroll down to Links for the example.
  - [[#hardware_installation|Hardware installation]]
  - [[#software_requirements|Software installation]]
  - [[#basic_operation|Basic operation]]
  - [[#view_menu|Target trails]]
  - [[#ebl_vrm|Cursor, EBL and VRM]]
  - [[#guard_zone|Guard zones]]
  - [[#timed_transmit|Timed transmit]]
In this case, where the link is from within the same page, in order to get it to work I must change the code to use the full pages pathname.  For example:

  - [[opencpn:opencpn_user_manual:plugins:ais_radar:br24_radar#hardware_installation|Hardware installation]]

(This may be changing in epub, as there was a fix noted for calibre to this effect, but it does not seem to be working and I have had to use the full pathname.) I have updated to the most current Calibre 3.31 [07 Sep, 2018]  actually I think it is 3.39 now.)
This is from an ePub tutorial 
http://www.jedisaber.com/eBooks/formatsource.shtml

Making Links to a specific part of a fie:

What if you want to want to link to a specific part of a file? Taking our example above, let's say chap01.xhtml has a reference to apple trees. Let's say chap02.xhtml has details on different kinds of fruit trees, each in it's own section, but all in the same XHTML file. Let's also say we want to provide a link in Chapter 1 that will jump straight to the section on apple trees in Chapter Two. If we just put a link in using the information in the above section, it will just take us to the beginning of Chapter 2, not to the specific section we want. How do we do that?

We have to do two things:

    add a bookmark to the code in chap02.xhtml where we want to link too.
    modify our link to point to not only the page, but the bookmark

Adding a bookmark:

A bookmark in HTML is just what it sounds like. A small hunk of code that we can use to make a hyperlink jump to the exact part of an HTML file that we want it to. In our example, we would add the following code to chap02.xhtml just above where we want the link to go to:

<a name="AppleTrees"></a>

You'll note that a HTML bookmark uses the same markup tag as the hyperlink, but with a different identifier and missing all the linky bits. Note that the link text ("AppleTrees", in this case, can be anything you want.)

To make our link jump right to the section on Apple Trees, make the link in chap01.xhtml look like this:

<a href="chap02.xhtml#AppleTrees">Link Text</a>

Basically, you add #LinkName to the the URL in your hyperlink. The part after the # sign has to match the text you have in the Name attribute of your bookmark. Now when you click (or tap) the link in Chapter 1, it will not only link you to Chapter 2, but to the right spot in Chapter 2.

Note: If you want to link to a bookmark in the same file (for example, if you want a link in Chapter 1 to go to another section in Chapter 1) put a bookmark where you want the link to go to, and make the link look like this:

<a href="#BookmarkName">Link Text</a>

We leave out the filename because we're just going to a different place in the same file, so all that's required is the bookmark name.

This post was edited on 2018-09-10, 19:12 by rgleason.
topic: Pipe dynamically created Indexmenu to a text file for use with Myron's Epub Extension  in the forum: General Help and Support Features and Functionality
Avatar
rgleason #14
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62347
There is now a 20mb Epub Book for OpenCPN 4.8.6 here partway down the page.
https://opencpn.org/wiki/dokuwiki/doku.…?id=opencpn:open…

Thank you Myron.
topic: Pipe dynamically created Indexmenu to a text file for use with Myron's Epub Extension  in the forum: General Help and Support Features and Functionality
Avatar
rgleason #15
Member since Sep 2016 · 272 posts
Group memberships: Members
Show profile · Link to this post
In reply to post ID 62289
Yes, after using it several times getting used to the format, it does work.  I misunderstood. I was hoping to be able to make a hierarchical Table of Contents.
Close Smaller – Larger + Reply to this post:
Special characters:
Page:  1  2  3 ... 17  18  19  next 
Special queries
Go to forum
Imprint
This board is powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2015 by Yves Goergen
Current time: 2019-08-22, 03:02:15 (UTC +02:00)