| Summary: | Make a page similar to http://l10n.gnome.org/languages/sv/ for the Mageia SVN to help users keep track of what's translated & how much it's translated. | ||
|---|---|---|---|
| Product: | Websites | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | Other | Assignee: | Atelier Team <atelier-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | lovaren, misc, odahlum, oliver.bgr, qiilaq69 |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://svnweb.mageia.org/soft/ | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Kristoffer Grundström
2011-05-04 02:56:15 CEST
Kristoffer Grundström
2011-05-04 02:56:30 CEST
CC:
(none) =>
kristoffer.grundstrom1983 Transifex does statistics, online translation and uploads/downloads of files: https://transifex.mageia.org/ CC:
(none) =>
odahlum There's no need for this as long as the translation platform handle it. Status:
NEW =>
RESOLVED There is now https://transifex.mageia.org/projects/p/mageia_i18n/r/mga1/ with similar information - alas, not Swedish yet, though it seems there is Swedish team http://mageia.org/wiki/doku.php?id=translators#swedish . But yes, essentially there might be also similar web page which would mirror directly SVN - something like Mandriva has at http://mdk.jack.kiev.ua/stats/gui/trunk/team/ CC:
(none) =>
bald Just a little follow up. If we're lucky, Transifex should be able to communicate with Subversion again. Last time I looked into this, it couldn't. It can't and I'm sure Mdv will run into a trap with the way, they are setting up the connection between Tx and svn. The problem is: we don't commit files from Tx into svn automatically because we don't want to have translations in svn, which were not approved of by the team coordinators and Tx has no "this translation is approved flag". When you now pull pot files automatically from svn to Tx, translations will get lost. This is why I always need some time to prevent this by merging the string changes into the po files from Tx. But the files in Tx are normally not far behind the state in svn (at the moment e.g. there shouldn't be any missing strings) So it is the easiest way for all of us to use what Tx gives us. Oliver CC:
(none) =>
oliver.bgr tx used to communicate with svn/etc before 1.0, but this was removed ( http://blog.transifex.net/2010/11/one-dot-zero/ ), and I think they do not plan to make this go back. CC:
(none) =>
misc (In reply to comment #6) > tx used to communicate with svn/etc before 1.0, but this was removed ( > http://blog.transifex.net/2010/11/one-dot-zero/ ), and I think they do not plan > to make this go back. Maybe we're better off with Pootle then. Remember our discussion about which solution I thought was better suited for entry level translators? Pootle should have no problems with communicating, but it's slow as hell. Status:
RESOLVED =>
REOPENED We now have a working solution, so I don't see the problems discussed here. We can rediscuss this after Mga1 release, but I think 6 days before freeze is just not the best idea. So it is invalid for now Status:
REOPENED =>
RESOLVED (In reply to comment #8) > We now have a working solution, so I don't see the problems discussed here. We > can rediscuss this after Mga1 release, but I think 6 days before freeze is just > not the best idea. > > So it is invalid for now I agree. |