Taglocity General Discussion Forum

I use Taglocity with a German version of Outlook 2003. Each tagged item has "unknown Tags" which contain fragments of my tags. Example: I have the tags "LBK" and "Project" assigned to a message and the unknown tags dialogue shows "lbk];[Project".
Q1: Is there a way to remove those tags? (I would prefer a batch-solution)
Q2: How can I avoid this problem?

I've read in one of the older messages that this problem might occur in non English versions because those use semicolons instead of commas. Is that the reason?

Hello,

Yes, I would suspect the issue is due to the German version of Outlook, as the 'Unknown Tags' feature does scan the Categories field looking for comma delimited tagnames ([inbrackets]).

It seems quite odd that the delimiter character for Outlook Categories (where the tags are held) is ';' and not ',' as that doesn't seem particularly 'locale' useful to anyone, but I'll investigate some more from Microsoft.

One interim fix for the next update I will look into is if we can 'detect' a non-US language and try to change the delimiter character to be user configurable (perhaps in a file setting), as that would at least allow Taglocity to function correctly.

One factor to decide this will be how many languages have different delimiters (and why!) and if there is any consistency.

Unfortunately I can't think of any batch way to remove these, other that some VBA, and the poor 'workaround' at the moment is just to have one tag on each item - which isn't very good.

Does anyone know if French, Dutch or Italian (the other languages that have been asked for) uses a semi-colon rather than a comma? Is there any reason why that people can think of?

Hello David,
thanks for your prompt answer. I expected that since I've read the question of the French user in the archived files. Now there is another problem showing up:
When I try to search for tagged items (tools->tag search) the result window remains empty. The program allows me to mark tags in the cloud or to enter search terms but there seems to be no action.
Windows desktop search works properly and its database has been indexed several times since I've installed Taglocity. Can this also be a result of the seperator (comma vs. semicolon) mismatch?

With a working search function Taglocity would be a milestone in getting my work organised. Keep on running!! There seems to be a big market. Get your share before Microsoft picks up that idea!

Ingo

This may be the case of the comma/semi-colon as part of the German locale breaks the query.

Taglocity builds up a query for the desktop search that has based on the tags being seperated by a comma (the Outlook default for US-EN). The use of a semi-colon when the tags are put on may have 'mangled' the data as far as the index is concerned.

If you type into Windows Desktop Search search textbox (the one when you double-click the systray magnifing glass icon) the following query then does it work?

'Category:[tag1]'

...with the assumption that you replace that 'tag1' example with a tag you have already put on a message?

Incidently, what version of Windows Desktop Search are you using?

Strange: When entering 'Category:[BauProjekt]' the instantly appearing window shows two Results which contain that searchstring even though I've never tagged them. But none of the tagged items is displayed.
After clicking the button with the start symbol the "big" Desktop Search window opens without any result. "no results were found..." Not even the two objects mentioned before.
When hovering over the "BauProjekt" tag in the tag cloud window the "tip-text" shows correctly the number of tagged items.
I use WDS 2.6 an this might be the problem. Do you plan an update which supports 2.6 or shall I downgrade WDS?

WDS 2.6 is supported on the current Taglocity version - the next update will support WDS 3.0 too.

I think it's related to the comma vs semi-colon.

Let me place in a config setting for an updatable 'separator character' and we can see if that is a solution.

Could you contact me at [email protected] please and I can set you up with a test build to try? If it works ok then I'll include it in the next 1.0.X update.