I have been trying to get the MOSTL implementation in office 2003 to work -
but without luck. 8 hours of digging forums, groups, blogs without the right
hit.
Is there anybody who uses the MOSTL implementation (and it works) ? Peter
Jamieson, maybee ?
Regards
Aage Nielsen
I haven't been visiting for a while but will try to help you out. (I'm a bit
busy though!)
Where are you getting stuck?
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:75986C7C-5AC6-451B...@microsoft.com...
Thanks :-)
I have downloaded the Smart SDK - tried the (Excel) MOSTL generator - and
ended with a simple example:
<?xml version="1.0" encoding="UTF-8"?>
<FL:smartTagList xmlns:FL="urn:schemas-microsoft-com:smarttags:list">
<FL:name>KUNO</FL:name>
<FL:description>Kuno app stuff </FL:description>
<FL:moreInfoURL>http://portal.nrgifibernet.dk</FL:moreInfoURL>
<FL:smartTag type="urn:schemas-microsoft-com:office:smarttags#nrgitags">
<FL:caption>Customernumber</FL:caption>
<FL:re>
<FL:exp>700[0-9]*</FL:exp>
</FL:re>
<FL:actions>
<FL:action id="kuno">
<FL:caption>Finding customer in KUNO...</FL:caption>
<FL:url>http://portal.nrgifibernet.dk/kuno/pages/overview.seam?customerId={TEXT}</FL:url>
</FL:action>
</FL:actions>
</FL:smartTag>
</FL:smartTagList>
and placed the xml file in C:\Program Files\Common Files\Microsoft
Shared\Smart Tag\LISTS directory with other MOSTL examples.
But no matter what I try neither of the examples show up in word or excel.
I have also downloaded the "Smart tag explorer" but keep getting an
"Unspecified error" exception.
- Aage
2. You should probably close all your Office applications, or at least Word
3. Did you go into Word Tools|Autocorrect Options...|Smart Tags and look for
your tag?
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:8538B6B2-2B93-4F99...@microsoft.com...
<FL:smarttaglist
xmlns:FL="http://schemas.microsoft.com/office/smarttags/2003/mostl">
However,
a. In Word 2003, it does not appear to make any difference
b. In Word 2003, the capitalistion of the element names is also ignored,
i.e. you can use smarttaglist when the schema specifies smartTagList
c. the examples in Lists also suggest that you must save the files as
Unicode files. This does not actually seem to be necessary, and if you use
the standard XML header with the UTF-8 specification, I guess you should
really save them as UTF-8.
I was very focussed on Word 2003 when I looked at this stuff. It is possible
that other office 2003 applications are more fussy. In theory I would assume
that Office 2007 is more fussy because it is using XML a lot more. However,
since it is the MOSTL DLL that actually reads these lists, it is actually
more likely that the same rules (or lack of them) apply to all apps and all
versions.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Peter Jamieson" <p...@KillmapSpjjnet.demon.co.uk> wrote in message
news:Oh9s5tu1...@TK2MSFTNGP03.phx.gbl...
I have tried the other URI - checked that the xml file is UTF-8 - closed all
office apps - tried the SmartTagInstall.exe - reopened word and check the
Auto Correct | Smart tags tab - no MOSTL implementations !!
Any other clues?
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:00CA374A-20B0-405A...@microsoft.com...
1030 is the Danish LCID - there is content in both the 1030 and 1033
directory, ex.
the phone.xml examples from Microsoft. The MOFL.dll is registered as an
InprocServer32 and the Smart tag GUID matches eg.
HKEY_CLASSES_ROOT\CLSID\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}
???
Not at the moment.
Other than version dates and numbers (on my Word 2003 system my DLLs are
dated 19/04/2007 which I would guess is related to the SP3 update) which I
doubt are significant, use of the Danish LCID is the only visible difference
between your system and mine.
I have looked in my registry and find that the CLSID
{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6} that you mention should be listed
under
HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Actions
and
HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Recognizers
and that under Recognizers, the CLSID {64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}
should be listed. Under that, there should be a list of recognizers,
possibly including e.g.
HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart
Tag\Recognizers\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}\urn:schemas-microsoft-com:office:smarttags#nrgitags
(The urnschemas URI is used even if you use the
http://schemas.microsoft.com/office/smarttags/2003/mostl URI in your MOSTL
.xml file.
If you want, you can try
a. saving the registry tree under
HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag by exporting it
b. saving the following to a .reg file and importing it
Proceed with caution as always!
-----.start after this line
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag]
"migratedBitValues"=hex:01,00,00,00
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Actions]
@=""
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart
Tag\Actions\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}]
@=""
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Applications]
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart
Tag\Applications\OpusApp]
"FriendlyName"="Microsoft Word 11.0"
"LabelText"=hex:01,00,00,00
"Save"=hex:01,00,00,00
"ShowButtons"=hex:01,00,00,00
"ShowIndicators"=hex:01,00,00,00
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Recognizers]
@=""
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart
Tag\Recognizers\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}]
@=""
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart
Tag\Recognizers\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}\urn:schemas-microsoft-com:office:smarttags#nrgitags]
"OpusApp"=dword:00000001
----- finish before this line
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:EA6A11BD-7583-4E7B...@microsoft.com...
I have tried your regístry changes without any luck. My word app is SP3 but
the mofl.dll is 12.0.4518.1014 from oktober 2006 - could this be an issue ?
any clues to where I find an update ?
I am a bit puzzled - I implemented the exactly same smart tag MOSTL example
in Open office - and it worked in less than 1 hour... include downloads and
installation ...
Still, I really appreciate you help :-)
"Peter Jamieson" wrote:
> >> > Any other clues?
>
> Not at the moment.
>
> Other than version dates and numbers (on my Word 2003 system my DLLs are
> dated 19/04/2007 which I would guess is related to the SP3 update) which I
> doubt are significant, use of the Danish LCID is the only visible difference
> between your system and mine.
>
> I have looked in my registry and find that the CLSID
> {64AB6C69-B40E-40AF-9B7F-F5687B48E2B6} that you mention should be listed
> under
>
> HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Actions
> and
> HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart Tag\Recognizers
> and that under Recognizers, the CLSID {64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}
> should be listed. Under that, there should be a list of recognizers,
> possibly including e.g.
> HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Smart
> Tag\Recognizers\{64AB6C69-B40E-40AF-9B7F-F5687B48E2B6}\urn:schemas-microsoft-com:office:smarttags#nrgitags
>
> (The urnschemas URI is used even if you use the
> http://schemas.microsoft.com/office/smarttags/2003/mostl URI in your MOSTL
> ..xml file.
> I have tried your regístry changes without any luck. My word app is SP3
> but
> the mofl.dll is 12.0.4518.1014 from oktober 2006 - could this be an issue
> ?
> any clues to where I find an update ?
It could be an issue, because that is the current MOFL.DLL for Office 2007.
Here, I keep different versions of Word on completely different virtual
machines to avoid potential version-related problems such as this. But I'll
do some tests at some point but I cannot do them right now.
If you want to "go back" to Office 2003 MOFL etc., An Office Detect and
Repair /might/ do it. But it's also possible that installation of the Office
2007 converters for Office 2003 introduces the new versions - at the moment
I just don't know.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:58CFF34F-3A0D-4249...@microsoft.com...
--
So I guess that's the cause of the problem on your system. If you already
have a Word 2003 MOFL.DLL somewhere, maybe you could try the same thing (in
reverse). otherwise, why not despam my email p...@KillMapSpjjnet.demon.co.uk
and contact me that way?
The same problem may obviously also apply to the other Word 2007 Smart Tag
DLLs you have.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:DE1C80EF-77E9-431B...@microsoft.com...
Not sure what you mean about despam - but you can reach me at
aagen...@live.com :-))
Regards
Aage Nielsen
I've just replied to your email.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:C359CAD7-B77F-458B...@microsoft.com...
I just copied all your 2003 DLL's to the .../Smart Tag/ directory and now
everything works :-) like it should.
So the Office update something has messed it all up ! Do you think it
possible to contact Microsoft and get somebody to work on it - or maybe the
MOSTL implementation is being removed...
Thanks for you help :-))
Best regards
Well, I am not so sure - my Office 2003 system uses automatic updates and
does not have these Office 2007 DLLs.
So I wonder whether or not your system has ever had any Office 2007
(trialware? beta versions) installed.
But in any case, there may still be an issue for anyone who has Office 2003
and Office 2007 software on the same system. I'll see if I can find out
anything about that.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Aage" <Aa...@discussions.microsoft.com> wrote in message
news:C0D92A8B-BCDA-480C...@microsoft.com...
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Peter Jamieson" <p...@KillmapSpjjnet.demon.co.uk> wrote in message
news:uXDxsQq2...@TK2MSFTNGP05.phx.gbl...