Skip to main content

diigo

Add to browser

Tags with embedded "-" characters no longer work. ( characters embedded tags) Join Group To Post

You are here: Diigo Home > Groups > Diigo Community > Forum > Tags with embedded "-" characters no longer work.

  • #1Hans Wobbe said ...(on 07-25-2007)

    Hans Wobbe
    In an effort to work around some of the tag formating issues and to achieve compatibility with other systems I use, I've been embedding "-" characters in my tags (for quite some time). They are particularly useful in date strings such as "2007-07"...

    As of today, none of these tags work. They all report "You have no tags..." in spite of the fact that these tags appear in the Cloud box.

    Should I wait for a fix or start converting the tags? Can you provide any hints regarding the acceptability of other characters that can be keyed, as embedded tag characters?

    Thanks.
  • #2Joel Liu said ...(on 07-27-2007, replying to Hans Wobbe on #1)

    Joel Liu
    I am sorry to miss your question. We fixed the bug.
    Regarding to the acceptable tags, ideally,
    1)you can insert any embedded tag characters, including some special characters such as $ # in the tag.
    2) When you do a tag search, for example $investments, the search engine only search investments.
    3) So if you only input $, it's not searchable.

    We are looking for some better solution for tag search.
    Thanks.
  • #3Hans Wobbe said ...(on 07-27-2007, replying to Joel Liu on #2)

    Hans Wobbe
    Thank you very much Joel. I really appreciate the fix.

    Also, thanks for taking the time to explain a bit more about the special characters. I had already inferred some of the behaviors, and started migrating the early instances of tags that I created while testing the limits within DiiGo, as well as the treatment of those tags in some of my other Pre- and Post- DiiGo processes that communicate via your RssFeed(s).

    I'm quite looking forward to watching where you take the software in the next Release and perhaps even being able to contribute a bit to your future directions.

    Thanks, again.

    joel wrote:
    > I am sorry to miss your question. We fixed the bug.