ufs at ufsoft
Nov 13, 2007, 12:41 PM
Post #1 of 1
(82 views)
Permalink
|
|
I18N Database Layout Brain Storm
|
|
Hello ppl!
I'm trying to create a trac plugin to help on the env's hosted projects I18N management.
I have a lot of ideas for it, yet, I'm stuck with the base of it, the database layout.
As a general idea, think of it as the rosetta for trac plugin of even the pootle for trac plugin.
I send attached the current database layout, which was initially meant to work with foreign keys,
yet sqlite does not support that, duh! Either way I thought I should stick with that design for
when trac moves to SQLAlchemy ;) which would make my life alot easier :)
Anyway, onto the subject which brought myself to you, the database layout.
The general idea is to import the catalog templates which are on the source control system,
this is using babel(of course), populate the database with the catalog template, then allow the
users coming to our trac env to create new translations and populate them.
These would of course need to be managed by an admin.
So, we need to store each version of the translation the users provide(per msgid), and the admin
then decides which is the best suited. Of course, projects need to get a manager for each of the
languages being translated as only one with full knowledge of the language will know what is the
best and most suitable translation. But this is yet another step.
As I said, I have the current database layout attached and also the model being used. Please, this
is really, really RAW code(and not all of it) since it's the first plug I'm coding which relies
on the database.
The idea I have now is:
* A repo path to a catalog template has a catalog associated to it, which itself has the several msgid's.
* Each msgid has user comments, auto comments, locations, flags, translations, etc
I need to handle plurals so, msgid and msgid_plural and then the necessary plural translations based on
the language some of them have more than 4 plural forms, way more.
I'd appreciate any comments, improvements or even ppl willing to help on coding it, but specially,
if this is/should be the db layout to use.
Best Regards,
--
Pedro Algarvio
__ ___ ___ _______ ___ __
| Y .' _| _ .-----.' _| |_ .-----.----.-----.
|. | | _| 1___| _ | _| _|__| _ | _| _ |
|. | |__| |____ |_____|__| |____|__|_____|__| |___ |
|: 1 | |: 1 | |_____|
|::.. . | |::.. . | ufs [AT] ufsoft [DOT] org
`-------' `-------' ufs [AT] sapo [DOT] pt
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users[at]googlegroups.com
To unsubscribe from this group, send email to trac-users-unsubscribe[at]googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|
db1.py
