| Age | Commit message (Collapse) | Author |
|
Kohana makes this type of transition fairly straightforward in that
all controllers/helpers/etc are still located in the cascading
filesystem without any extra effort, except that I've temporarily
added a hack to force modules/gallery into the module path.
Rename what's left of "core" to be "application" so that it conforms
more closely to the Kohana standard (basically, just
application/config/config.php which is the minimal thing that you need
in the application directory)
There's still considerable work left to be done here.
|
|
|
|
|
|
client translation input field
|
|
- Get / verify API Key from l10n server
- Submit translations
- Fetch translations / updates
Reference: Tasks: 75, 76, 55
TODO: Move out of core (and a series of other tasks).
|
|
Only available to admins at this point.
|
|
|
|
|
|
translations to a translation server yet.
- Added an outgoing_translations table to store translations from the local translation UI.
- I18n class is checking incoming_ and outgoing_translations for translations, giving the latter priority.
- Not handling plural strings in the translations UI yet.
|
|
The code is based on the l10n_client module from Drupal 6, by Gabor Hojtsy (http://drupal.org/user/4166).
|