What happened to the Glossary?

[rickliveops]

I started entering glossary items via the Admin interface. But I can't find a way to view them in the user interface. What am I missing?

[Thorsten]

Hi,

they are added automatically in the frontend. For example if you have a glossary item like "PHP" with the description "PHP: Hypertext Preprocessor" all occurrences of the string "PHP" will be converted to

Code: Select all

<acronym title="PHP: Hypertext Preprocessor">PHP</acronym>

bye
Thorsten

[rickliveops]

Ah, I see. Very nice!

However, there are a few issues with this feature:

1) If the term is followed by any punctuation, it is not seen as a glossary term. E.g. "PHP" would work as you state above but not "PHP." So you can't put your term at the end of a sentence, or quote it in your text, etc. unless you put a space after. Not a huge problem, but a little inconvenient.

2) On Firefox Mac, the rollover text is limited to about 78 characters. So a longer glossary entry gets truncated. I have not found a workaround for that.

3) It would nice if the glossary entry could be linked to an FAQ. That way, you could put longer definitions in a FAQ (bypassing the issue in #2) and make a pretty powerful cross referenced document.

(I hope I'm not giving you too much feedback. I used to be a software QA engineer and old habits die hard. )

[Thorsten]

Hi Rick,

1) If the term is followed by any punctuation, it is not seen as a glossary term. E.g. "PHP" would work as you state above but not "PHP." So you can't put your term at the end of a sentence, or quote it in your text, etc. unless you put a space after. Not a huge problem, but a little inconvenient.

Okay, I'll try to fix this until the final release... maybe the fix will last until 2.0.1...

2) On Firefox Mac, the rollover text is limited to about 78 characters. So a longer glossary entry gets truncated. I have not found a workaround for that.

This is the same behaviour in all Firefox versions before 3.

3) It would nice if the glossary entry could be linked to an FAQ. That way, you could put longer definitions in a FAQ (bypassing the issue in #2) and make a pretty powerful cross referenced document.

We plan to extend the Glossary feature in 2.1 if enough users are asking for that.

(I hope I'm not giving you too much feedback. I used to be a software QA engineer and old habits die hard. )

No, I want as much feedback as I can get to make phpMyFAQ better. Thanks for your really good testings and bug reports!

bye
Thorsten

[Dirk67]

We plan to extend the Glossary feature in 2.1 if enough users are asking for that.

I would like to ask for this feature* too...
*(extend the Glossary feature)

First of all:
I think it should be multilingual as well
since PMF is a multilingual application

The <title> attribut works not very well in some browsers
(cut off after x chars)
maybe one can implement some kind of simple "java hover window" (?)

Also sorting the Glossary terms alphabetic would be helpful in the admin backend...

[matteo]

Hi,

1) If the term is followed by any punctuation, it is not seen as a glossary term. E.g. "PHP" would work as you state above but not "PHP." So you can't put your term at the end of a sentence, or quote it in your text, etc. unless you put a space after. Not a huge problem, but a little inconvenient.

FYI: you can track the working progress about this minor issue in:
https://thinkforge.org/tracker/index.ph ... 2&atid=169

Ciao,
Matteo

[Dirk67]

The <title> attribut works not very well in some browsers
(cut off after x chars)
maybe one can implement some kind of simple "java hover window" (?)

I meant something like this:
http://webmatze.de/webdesign/javascript/tooltips.htm (in german)