Escript supports this item


34 comments found.

Looks very useful. Could you please confirm that it is possible to embed the glossary within a SCORM 2004 module for use within a LMS.

Hi, it really depends on the framework you’re trying to embed it in. If your authoring framework will allow you to import/embed a html page which reads in javascript/css/xml files, then yes.

Hi, is there a Wordpress version of this script? Alternatively, is it possible to embed this script and the fully populated glossary in a Wordpress page?

The script is not a WordPress plugin. You can however include any custom HTML page in a WordPress site. Check the WordPress Help/Forums for details on this.

Is it possible to define / limit a page length and create multiple navigable pages with this script / plugin? Even if it is embedded in, say, Wordpress?

I don’t understand your question, sorry.

does the data have to be in a xml file like in the demo, or can it come from somewhere else, like markup

Hi, it works with XML format.

Wow. After days of searching and trying every other plugin out there, this one seems to be exactly what we have been looking for. Hopefully it will play nice with our chosen theme. If it does, we’ll be very enthusiastic customers!

We do have a question however:

Can we have multiple glossaries on a single site (but appearing on different pages)? For example, a glossary page for ‘fruit’ terms and a second glossary page for ‘vegetables’ ?

Hi, yes but you would need to purchase a separate license for each Glossary instance.

How do you link from an external html page to a word in the glossary using the “id”?

No I have not, but as someone mentioned earlier that you are using xml format, I know in html I can use IDs to link sections, but If you are using xml how will this work?

It’s covered in the documentation that you will receive if you purchase the item.

This is an excellent script well documented.

How can I make the search box longer? Extend the width…

Hi, you can add a css style to styles.css, e.g. #searchInput{width:300px;}

How can I just print the definition only. Presently when printing, the output looks clustered with the definition and word holders.

You could add a button which opens a PDF of your Glossary.

How do I go about getting that done?

Hi, the documentation has examples of setting up buttons and events. If you need further support please could you send an email to the support email address. Many thanks.

Can this script work well with large dictionary file with 200.000 records?

I’ve never tried it but I wouldn’t recommend storing this number of definitions in a single xml file.

Question: In a previous comment you said that multiple purchases will need to be made so that the buyer can use it multiple times on the same website in different pages? I have eLearning project that will need to link to this. There are 17 modules, does this mean that I will have to buy it 17 times even if its the same project?

Hi there. The license applies to a single end product, i.e. one Glossary. You can then copy that one Glossary as many times as you like. If you need to create different Glossaries, i.e. a different Glossary for each eLeaning module you are producing, that would mean purchasing a license for each unique Glossary. The CodeCanyon license terms are at: The FAQs on single-end applications are at:

Hello, this support special characters in the search engine?

Yes. Type any character into the search field it will find any matching characters in all of the words.

Hi. Can you show me Manager page? I want to know how to add words to site. I have 80000 words.

There’s no manager page. You add words and definitions to an xml file using the editor of your choice.

I would like to display just the content and not the listing of items or category. Is that possible? For instance when your click on N and you get all those pictures for Nasa there is a side column that contains the word “Nasa”. I would like the gallery to take up the full width under the letters. Is that possible?

Hi there. Please use the support email address for questions rather than the comments section : )

You could try hiding the wordHolder container (using anim=”hide”). You might want to also change the width of the definitionHolder accordingly.

Thank you for such a quick reply and yes I will use the support email from now on. Your answer was perfect regarding my question.

Hey there, it really looks nice, I think you already know that as everyone is saying so. I wanted to make a simple dictionary with around 5,000 words in it. From some comments I came to know that this access all the definitions from an XML file. And again in one reply you said not to use big xml; and in another you said “I wouldn’t recommend storing this number of definitions in a single xml file”. So, that means we can use more than one xml file?

I need this for an Arabic to English; English to Arabic; Arabic to Bangla; Bangla to Arabic dictionary. So, you think it can contain special characters from other languages (I hope it does)?

And, do I need to buy multiple licence? Please let me know. Can’t wait….

Hi there, the comment you mention was for storing 200,000 definitions. 5,000 should be fine. The consideration is file size – the time is takes the browser to initially read in the xml file. Once the file is loaded, the engine can handle thousands of definitions very quickly.

Special characters are supported – just paste in whichever language you choose, the xml file is utf-8 encoded. For RTL languages you can optionally add a css style to right-align the text.

The license applies to a single end product, i.e. one Glossary. You can then copy and translate that one Glossary as many times as you like. If you require versions that vary (other than just a direct translation of language), i.e. a different set of words and/or definitions, each variant would require a separate license.

If you intend to charge users to use the Glossary, or it be part of a wider package that you charge users to use, you would need an extended license for each variant.

The CodeCanyon license terms are at: The FAQs on single-end applications are at:

Kind regards.