Op 29 okt 2010, om 14:36 heeft Bryan Tong Minh het volgende geschreven:
On Fri, Oct 29, 2010 at 2:25 PM, Krinkle krinklemail@gmail.com wrote:
For one, tags would not be hierarchical and not stored under a name, rather a number (an id if you will).
I would store the tag-i18n definitions in a separate Tag: namespace. Then you don't need to create the history tracking etc. all by yourself. You will need a unique identifier though, but I don't see a problem making the unique identifier equal to the content language.
Bryan
Now that I re-read my mesage I see I didn't use the word Namespace litterly but that's what I meant, yes. A seperate Tag: namespace that contains 'pages' that are either titled by numbers or by a name in the main content language. (in contrary to the interwiki-transclusion thing the title of the Tag- pages are pretty much hidden from everybody)
I just read another discussion about seperating license/author information from page-text. This brought me on another idea.
If Tags are stored seperatedly, there's no need to have any 'wiki- text' at all. Atleast not visible to the end user.
A tag:-page could simply contain a form with the current translations (editable) and a [+]-button to add a translation. roughly shaped: Pagename: [[Tag:Flower]] <form> <table> <tr> <td>English</td> <td><input>flower</input></td> </tr> <tr> <td>Nederlands</td> <td><input>boem</input></td> </tr>> <tr> <td>Deutsch</td> <td><input>Blume</input></td> </tr> </table> <select> ...languages not translated yet ...</select> <input type=submit value='Add translation for this language' /> <input type="submit" value="Save" /> </form>
Saving would extract the info and store it in the tag_i18n table (or page_props if that's more appropiate - anyway)
Since we like keeping history of everything it may be wise to also store this as wikitext for the Tag:Flower page as something like: {{en:flower}} {{nl:bloem}} {{de:Blume}} but that would only be visible in diff-views and history.
-- Krinkle