Hey Jonathan,
I just committed my updates to your search_plugin, here's what I did:
* renamed Browser2.0 to Search
* renamed "Keyword Search" title to "Search by Tag". The "keyword" part didn't seem to make sense once doing the translation, since the keywords won't be translated, or they won't work. So it seem to me they are really more "tags" than keywords".
* rearranged some code to get [_ ""] everywhere, some lists needed more than trivial rearrangedments (i.e. [list foo bar] instead of {foo bar})
Hope these all work for you.
.hc
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: pd-dev List pd-dev@iem.at Cc: Sent: Friday, December 21, 2012 10:30 PM Subject: [PD-dev] updates to search_plugin for translation support
Hey Jonathan,
I just committed my updates to your search_plugin, here's what I did:
renamed Browser2.0 to Search
renamed "Keyword Search" title to "Search by Tag". The
"keyword" part didn't seem to make sense once doing the translation, since the keywords won't be translated, or they won't work. So it seem to me they are really more "tags" than keywords".
That will cause confusion.
The pd META subpatch consists of various comments with the form "TAG value1 value2 etc.". One of those tags happens to be "KEYWORDS". All the blue links listed under the heading "Keyword Search" are possible values that I've used after the tag "KEYWORDS" in help patches. Therefore, it is a "Keyword Search"-- a search for values from a specific type of tag named "KEYWORDS"-- and not a "Search by Tag", which implies values matched from various tags like KEYWORDS, DESCRIPTION, OUTLET_1, etc.
The fact that you can't translate the keywords is simply a limitation of pd's implementation which has no way to sensibly translate content inside patches. (At least none that I know of.)
-Jonathan
- rearranged some code to get [_ ""] everywhere, some lists needed
more than trivial rearrangedments (i.e. [list foo bar] instead of {foo bar})
Hope these all work for you.
.hc _______________________________________________ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
On Dec 22, 2012, at 7:47 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: pd-dev List pd-dev@iem.at Cc: Sent: Friday, December 21, 2012 10:30 PM Subject: [PD-dev] updates to search_plugin for translation support
Hey Jonathan,
I just committed my updates to your search_plugin, here's what I did:
renamed Browser2.0 to Search
renamed "Keyword Search" title to "Search by Tag". The
"keyword" part didn't seem to make sense once doing the translation, since the keywords won't be translated, or they won't work. So it seem to me they are really more "tags" than keywords".
That will cause confusion.
The pd META subpatch consists of various comments with the form "TAG value1 value2 etc.". One of those tags happens to be "KEYWORDS". All the blue links listed under the heading "Keyword Search" are possible values that I've used after the tag "KEYWORDS" in help patches. Therefore, it is a "Keyword Search"-- a search for values from a specific type of tag named "KEYWORDS"-- and not a "Search by Tag", which implies values matched from various tags like KEYWORDS, DESCRIPTION, OUTLET_1, etc.
The fact that you can't translate the keywords is simply a limitation of pd's implementation which has no way to sensibly translate content inside patches. (At least none that I know of.)
I think that the PDDP KEYWORDS are really functionally like tags in the blog/etc. sense, like in this sense: http://en.wikipedia.org/wiki/Tag_(metadata) I can't think of a common usage for the term 'keyword' for describing this, though its a synonym. So I wanted try to use the most common language possible.
But yes, I agree, calling it "tags" one place and "keywords" another will cause confusion. The term "KEYWORDS" isn't wrong, just much less common. Maybe it could incorporate both terms:
"Search by Keyword Tag"
.hc