Re: [Semediawiki-user] [SG] Testing SMW 1.6, Semantic Glossary (r88968)

[James H. K. <jam...@gm...>]

Hi Stephan,

>> not contain spaces or punctuation characters

As for testing purposes, we did define (no spaces but it would be hard
since most terms have more than just a single word)

[[Glossary-Definition::Encyclopedia testing]]
[[Glossary-Link::Encyclopedia_Category]]
[[Glossary-Term::Encyclopedia]]

and went on a page where we know that the term Encyclopedia is used
but suddenly the page would stop half the way to process and only show
the title of the page.

The Apache error log for the page would show something like - "" is
not a valid magic thingie for "clear_external_data".

>> not recognize UTF-8 characters

Meaning it would not work for our Japanese and Chinese entries.

MediaWiki	1.16.5
PHP	5.2.13 (apache2handler)
MySQL	5.1.44-community

Semantic MediaWiki (Version 1.6 alpha)	(r88977)
Semantic Glossary (Version 0.1 alpha)	(r88977)

Cheers,

MWJames

On Sat, May 28, 2011 at 1:13 AM, Stephan Gambke <f....@gm...> wrote:
> Hi James,
>
> Am 27.05.2011 14:34, schrieb James Hong Kong:
>> but on the pages that include the term nothing happens. While when
>> using the term we defined via Special:Glossary it shows as expected.
>
> Yes, that is one of the shortcomings, the extension has: Glossary
> entries must not contain spaces or punctuation characters (\.(),;:?!). I
> do have an idea to improve this. However, parsing the article is very
> time consuming so every addition to the inner loop needs to be
> considered very carefully.
>
>
>> When using {{#ask: [[Glossary-Term::+]], the only results coming back
>> are Acquisition Strategy but not term that we defined via
>> Special:Glossary (in this case Random).
>
> Hmm, strange. This should definitely work. Could this be a caching
> issue? Please try refreshing (action=purge) the page.
>
>
>> Further investigation of  {{#ask: [[Glossary-Term::+]] ... and an
>> entry called GlossaryTerm#0 showed up within the list (which was not
>> defined by us).
>
> This is the SMW internal page generated by the special page. Hence the
> mainlabel=- I put into the query.
>
> Another major problem is, that currently UTF-8 is not supported. In
> fact, the extension does not only not recognize UTF-8 characters, it
> damages the article wherever those characters appear.
>
> Stephan
>