 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 04.02.2016 um 02:17 schrieb Mike Horvath:
> If I have the time I may look at the docs and see why the indices are
> all messed up. It should be a simple but maybe tedious task, since I've
> worked on HTML Help documents in the past.
If you do, don't forget that the docs are auto-generated from the Wiki
content.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/3/2016 8:48 PM, clipka wrote:
> Am 04.02.2016 um 02:17 schrieb Mike Horvath:
>
>> If I have the time I may look at the docs and see why the indices are
>> all messed up. It should be a simple but maybe tedious task, since I've
>> worked on HTML Help documents in the past.
>
> If you do, don't forget that the docs are auto-generated from the Wiki
> content.
>
Where in the wiki are the indices stored?
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/3/2016 8:17 PM, Mike Horvath wrote:
> On 2/3/2016 8:16 PM, Mike Horvath wrote:
>> On 2/3/2016 5:33 PM, Alain wrote:
>>> Le 16-02-03 13:30, clipka a écrit :
>>>> Am 03.02.2016 um 05:30 schrieb Mike Horvath:
>>>>> It is still a PITA to scroll up and down that page though. It's
>>>>> hard to
>>>>> grab the scrollbar handle, and when you do grab it you can't move
>>>>> it in
>>>>> small increments. This is easily solvable by just splitting the page
>>>>> into a few smaller portions.
>>>>>
>>>>> Mike
>>>>
>>>> Still using a mouse without a scroll wheel?
>>>>
>>>
>>> If you have a few hours available to invest into scrolling through that
>>> page... Beter use the Page Up and page Down keys to navigate here.
>>
>> I think I've also noticed the page not loading 100% before the program
>> tries to resolve a link or index. I.e. the navigation falls short of the
>> target anchor because the page hasn't fully loaded yet. Which shouldn't
>> happen in document stored on the local hard drive.
>>
>>
>> Mike
>
> If I have the time I may look at the docs and see why the indices are
> all messed up. It should be a simple but maybe tedious task, since I've
> worked on HTML Help documents in the past.
>
the reason that (for windows help) the indices are messed up has nothing
to do with the wiki files or the code written to pull the docs from the
wiki ... it's the post processing that formats it into a windows help
file. the former i have control over, the later i do not
>
> Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/8/2016 9:32 AM, Jim Holsenback wrote:
> the reason that (for windows help) the indices are messed up has nothing
> to do with the wiki files or the code written to pull the docs from the
> wiki ... it's the post processing that formats it into a windows help
> file. the former i have control over, the later i do not
just recalled another reason that's also contributing to the busted
indices issue ... there are a fair number of indexentry tags that did
NOT get converted to the new tag style (a last minute change) i did SOME
of them but obviously not ALL ... there's an office politics reason why
and i don't think getting into that is appropriate in this forum.
windows help is the ONLY flavor of docs that even cares about this, the
mac and nix flavors have them stripped out.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/8/2016 2:32 PM, Jim Holsenback wrote:
> the reason that (for windows help) the indices are messed up has nothing
> to do with the wiki files or the code written to pull the docs from the
> wiki ... it's the post processing that formats it into a windows help
> file. the former i have control over, the later i do not
Welcome back. Long time no see.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/8/2016 11:08 AM, Stephen wrote:
> On 2/8/2016 2:32 PM, Jim Holsenback wrote:
>> the reason that (for windows help) the indices are messed up has nothing
>> to do with the wiki files or the code written to pull the docs from the
>> wiki ... it's the post processing that formats it into a windows help
>> file. the former i have control over, the later i do not
>
>
> Welcome back. Long time no see.
Thanks ... back wouldn't be entirely correct. Not much time for tracing
ray's lately. Just an occasional touch-n-go.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/8/2016 4:45 PM, Jim Holsenback wrote:
>
> Thanks ... back wouldn't be entirely correct. Not much time for tracing
> ray's lately. Just an occasional touch-n-go.
I've not been Poving much myself. I've been poorly but getting over it
now. :-)
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 08.02.2016 um 13:15 schrieb Mike Horvath:
> On 2/3/2016 8:48 PM, clipka wrote:
>> Am 04.02.2016 um 02:17 schrieb Mike Horvath:
>>
>>> If I have the time I may look at the docs and see why the indices are
>>> all messed up. It should be a simple but maybe tedious task, since I've
>>> worked on HTML Help documents in the past.
>>
>> If you do, don't forget that the docs are auto-generated from the Wiki
>> content.
>>
>
> Where in the wiki are the indices stored?
The magic is in the "{{#indexentry:...}}" tags.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Holsenback <spa### [at] nothanks net> wrote:
> the reason that (for windows help) the indices are messed up has nothing
> to do with the wiki files or the code written to pull the docs from the
> wiki ... it's the post processing that formats it into a windows help
> file. the former i have control over, the later i do not
You know, given no other Wiki editors ever materialised in years, one might
considert backporting to the 3.6 docs format that worked flawlessly, even though
it wasn't a well documented process. Still having broken docs all over the place
is hardly going to help new users getting started...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/1/2016 8:52 AM, Stephen wrote:
> There has been some talk about how the search function in the Help
> file is broken.
> I had forgotten about this workaround until I used it without thinking.
> When you search for a keyword and Help takes you to the top of a large
> page. Left click on the right hand pane and press Ctrl + F to bring up a
> search box. There you can search for your keyword.
>
Just to be clear about this I'm responding to the head of this thread so
as to not have it taken that I'm commenting to anyone in particular.
I'm absolutely certain the problem is all the indexentry tags that DID
NOT get converted to the new format imposed at the last minute.
I'm going to go ahead and step back from this.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
