Support Forums
ATutor Feature Requests
Changes to translation engine
You must be signed-in to post.
| Author | Subject | |
|---|---|---|
| Page: 1 | ||
IndieRect | Subject: Changes to translation engine |  |
| Another approach for determining on which pages language vars are used is required. Many, really MANY variables remain in Unused list even when the system has been being used for a long time. We've been testing/using ATutor for approx half a year and have 358 such ones. Some of them, if not most, are obviously not used any more (some even bear a text they've been removed in v1.1, like req_message* family). I suggest implementing this in an other way. The pages using each variable could be statically written to the DB in a distributed package. This would be even more useful if extrapolated to _msgs vars. Mostly they are self descriptive enough, but in a number of cases I don't get the context, especially if %s are present in those vars (in my language usage of appropriate endings is required for each word to make them what is called a sentence). The current approach is absolutely N/A to them, for obvious reasons. I'm sure you're aware of this problem since in newly introduced vars (e.g. $AT_ERROR_NO_LOGS_SELECTED) a workaround is present. Still, I believe that there should be some more generalized way. Besides making the translation easier that would also help spotting and removing vars that are really not used. Best wishes, Serhiy Kostyshyn aka IndieRect Posted: 2005-04-19 10:55:52 | ||
 | ||
| Page: 1 | ||
You must be signed-in to post.