expanding glosssary doesn't always work

This forum is for all Flare issues related to the HTML5, WebHelp, WebHelp Plus, and Adobe Air Targets
Post Reply
lacastle
Propellus Maximus
Posts: 1028
Joined: Thu Apr 12, 2007 7:28 am
Location: Wilmington, DE
Contact:

expanding glosssary doesn't always work

Post by lacastle »

Some of my words in my glossary do not expand like they should in the output. The term is definitely in the glossary file and it works in some topics, but not all of them. For a few topics, I was able to delete the word and re-type it and it worked. But sometimes I run out of ways to delete and re-type (in the xml viewer, in the internal text editor, with tags visible) and it still doesn't work.

All the words were entered in the glossary at the same time and all the words in my list of terms in the topic were typed at the same time too.
invisible terms1.jpg
Here's what the source code looks like for this section of working/non-working terms:

Code: Select all

        <ul>
            <li class="QBulletedList" value="1">Evaluation Date</li>
            <li class="QBulletedList" value="2"><span class="MCExpanding"><a href="javascript:void(0);" class="MCExpandingHead" onclick="FMCExpand( this ); return false;">Evaluation Basis<img style="border: none;margin-left: 5px;" src="../../SkinSupport/book_closed.png" MadCap:altsrc="../../SkinSupport/book_open2.png" class="MCExpandingIcon" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( '../../SkinSupport/book_open2.png' ); }" /></a><span class="MCExpandingBody" style="display: none;">Test definition</span></span>
            </li>
            <li class="QBulletedList" value="3"><span class="MCExpanding"><a href="javascript:void(0);" class="MCExpandingHead" onclick="FMCExpand( this ); return false;">Use alternate pricing<img style="border: none;margin-left: 5px;" src="../../SkinSupport/book_closed.png" MadCap:altsrc="../../SkinSupport/book_open2.png" class="MCExpandingIcon" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( '../../SkinSupport/book_open2.png' ); }" /></a><span class="MCExpandingBody" style="display: none;"></span></span>

            </li>
            <li class="QBulletedList" value="4"><span class="MCExpanding"><a href="javascript:void(0);" class="MCExpandingHead" onclick="FMCExpand( this ); return false;">Pricing Vendor<img style="border: none;margin-left: 5px;" src="../../SkinSupport/book_closed.png" MadCap:altsrc="../../SkinSupport/book_open2.png" class="MCExpandingIcon" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( '../../SkinSupport/book_open2.png' ); }" /></a><span class="MCExpandingBody" style="display: none;"></span></span>
            </li>
            <li class="QBulletedList" value="5">Book Value Basis</li>
            <li class="QBulletedList" value="6"><span class="MCExpanding"><a href="javascript:void(0);" class="MCExpandingHead" onclick="FMCExpand( this ); return false;">Amortize To/Thru?<img style="border: none;margin-left: 5px;" src="../../SkinSupport/book_closed.png" MadCap:altsrc="../../SkinSupport/book_open2.png" class="MCExpandingIcon" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( '../../SkinSupport/book_open2.png' ); }" /></a><span class="MCExpandingBody" style="display: none;"></span></span>
            </li>
            <li class="QBulletedList" value="7">Subtotal Items?</li>

            <li class="QBulletedList" value="8"><span class="MCExpanding"><a href="javascript:void(0);" class="MCExpandingHead" onclick="FMCExpand( this ); return false;">Cash/DDA Positions<img style="border: none;margin-left: 5px;" src="../../SkinSupport/book_closed.png" MadCap:altsrc="../../SkinSupport/book_open2.png" class="MCExpandingIcon" onload="if ( typeof( FMCPreloadImage ) == 'function' ) { FMCPreloadImage( '../../SkinSupport/book_open2.png' ); }" /></a><span class="MCExpandingBody" style="display: none;"></span></span>
            </li>
And here are the words in the glossary:
glossary1.jpg
glossary2.jpg
Has anyone else ever seen this problem?
You do not have the required permissions to view the files attached to this post.
lacastle
Propellus Maximus
Posts: 1028
Joined: Thu Apr 12, 2007 7:28 am
Location: Wilmington, DE
Contact:

Re: expanding glosssary doesn't always work

Post by lacastle »

In case anyone was wondering, i think i may have figured out what my problem.

I think that sometimes i am a lazy typer so the Shift key is down with the Spacebar, so I get a   non-breaking space in between my words. If the glossary does not have this type of space, it won't pick up the terms automatically like it's supposed to since they are not *exactly* alike. This also is a problem if the glossary has the non-breaking space and the word in the topic doesn't.

Either way, this is annoying, especially since the only way to know if you have a non-breaking space is to look at the source code.
KevinDAmery
Propellus Maximus
Posts: 1985
Joined: Tue Jan 23, 2007 8:18 am
Location: Darn, I knew I was around here somewhere...

Re: expanding glosssary doesn't always work

Post by KevinDAmery »

lacastle wrote:Either way, this is annoying, especially since the only way to know if you have a non-breaking space is to look at the source code.
... or to turn on the paragraph marks in the topic view. If you do, the non-breaking spaces show in red rather than blue. Although I find I have to look very closely to see it (I run my monitor at 1600x1200).
Until next time....
Image
Kevin Amery
Certified MAD for Flare
lacastle
Propellus Maximus
Posts: 1028
Joined: Thu Apr 12, 2007 7:28 am
Location: Wilmington, DE
Contact:

Re: expanding glosssary doesn't always work

Post by lacastle »

Well, I have to do about 500 more topics like this (with about 10 glossary terms in each one), so I'll try the paragraph marks. Thanks!
KevinDAmery
Propellus Maximus
Posts: 1985
Joined: Tue Jan 23, 2007 8:18 am
Location: Darn, I knew I was around here somewhere...

Re: expanding glosssary doesn't always work

Post by KevinDAmery »

Why not just do a find and replace in source code for &160 ?
Until next time....
Image
Kevin Amery
Certified MAD for Flare
lacastle
Propellus Maximus
Posts: 1028
Joined: Thu Apr 12, 2007 7:28 am
Location: Wilmington, DE
Contact:

Re: expanding glosssary doesn't always work

Post by lacastle »

KevinDAmery wrote:Why not just do a find and replace in source code for   ?
Could that hurt anything? Looking in a few of my topics, I also have some lines like this:

Code: Select all

<p style="text-align: center;"> </p>
I guess I can just make a copy of my project and see what happens. I noticed that there are non-breaking spaces in a few of my glossary terms too, which is a problem when i type the word in the topic correctly :(
lacastle
Propellus Maximus
Posts: 1028
Joined: Thu Apr 12, 2007 7:28 am
Location: Wilmington, DE
Contact:

Re: expanding glosssary doesn't always work

Post by lacastle »

Ok. The find/replace worked in the topics, but can i do it for the glossary too?
KevinDAmery
Propellus Maximus
Posts: 1985
Joined: Tue Jan 23, 2007 8:18 am
Location: Darn, I knew I was around here somewhere...

Re: expanding glosssary doesn't always work

Post by KevinDAmery »

You may have to open the glossary manually into the internal text editor to get it to work, but as long as you do that it can do a find and replace.
Until next time....
Image
Kevin Amery
Certified MAD for Flare
lacastle
Propellus Maximus
Posts: 1028
Joined: Thu Apr 12, 2007 7:28 am
Location: Wilmington, DE
Contact:

Re: expanding glosssary doesn't always work

Post by lacastle »

The Internal text editor (and notepad) doesn't show me the same code as the actual glossary.

Here's the internal text editor/notepad code for the glossary term:

Code: Select all

  <GlossaryEntry TermClass="Expanding">
    <Terms>
      <Term>Cash/DDA Positions</Term>
    </Terms>
    <Definition
      Link=""></Definition>
  </GlossaryEntry>
Here's the Source Code for the word in the generated glossary:

Code: Select all

<a href="javascript:void(0);" class="GlossaryPageTerm" id="MCDropDownHotSpot_2626670449_36" onclick="FMCDropDown( this ); FMCScrollToVisible( window, this.parentNode.parentNode ); return false;">Cash/DDA Positions</a>

Oh well. I just have to locate the issues in the source and change them in the text editor for the glossary.
Post Reply