- simplify message format (get rid of </user>?)
gulp task?- custom message interpolator
- Group configuration
- Create custom Insertables / Checker (?)
- similar to https://github.com/wikimedia/translatewiki/blob/master/groups/OpenStreetMap/Insertables.php
- see https://www.mediawiki.org/wiki/Help:Extension:Translate/Insertables
- ({{[a-z_]*}}|<[a-z\=\{\}\s_\|]*>)
- translationProvider has to know which languages are available and their localized names
- gulp task
- support for rtl languages
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Improve translation setup, add qqq.json, rtl support | labs/tools/crosswatch | master | +220 -63 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Sitic | T101438 Integrate with translatewiki | |||
| Resolved | Sitic | T108247 Add crosswatch project to translatewiki |
Event Timeline
Comment Actions
@Nemo_bis it got delayed a bit, but I probably will make a patch for translatewiki next week
Comment Actions
@Nemo_bis it got delayed a bit, but I probably will make a patch for translatewiki next week
Are you going to use Intuition or not? Using Intuition is waaaaaaay faster than adding your own project.
Comment Actions
Intuition is not really an option for me. First I don't use PHP so the framework in it self is no use to me. But the main reason is that I have translation strings like
<user> renamed user <user name={{olduser}}> ({{edits}} edits) to <user name={{newuser}}>
So I have to create a special Insertables.php and Checker.php for translatewiki.
(Also as I currently add new translation strings quite frequently I would prefer to have translatewiki pull and push the changes to my repository directly).