Bug 1126 - 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.
Summary: Make a page similar to http://l10n.gnome.org/languages/sv/ for the Mageia SVN...
Status: RESOLVED INVALID
Alias: None
Product: Websites
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL: http://svnweb.mageia.org/soft/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-04 02:56 CEST by Kristoffer Grundström
Modified: 2011-05-04 14:08 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Kristoffer Grundström 2011-05-04 02:56:15 CEST
Description of problem: I wish that you guys make a page that works similar to http://l10n.gnome.org/languages/sv/ since that shows what PO's you should download to translate.
Kristoffer Grundström 2011-05-04 02:56:30 CEST

CC: (none) => kristoffer.grundstrom1983

Comment 1 Olav Dahlum 2011-05-04 04:47:40 CEST
Transifex does statistics, online translation and uploads/downloads of files: https://transifex.mageia.org/

CC: (none) => odahlum

Comment 2 Olav Dahlum 2011-05-04 04:50:30 CEST
There's no need for this as long as the translation platform handle it.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 3 Marek Laane 2011-05-04 04:51:35 CEST
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

Comment 4 Olav Dahlum 2011-05-04 05:00:29 CEST
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.
Comment 5 Oliver Burger 2011-05-04 08:31:27 CEST
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

Comment 6 Michael Scherer 2011-05-04 13:31:17 CEST
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

Comment 7 Olav Dahlum 2011-05-04 13:42:29 CEST
(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
Resolution: INVALID => (none)

Comment 8 Oliver Burger 2011-05-04 14:03:23 CEST
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
Resolution: (none) => INVALID

Comment 9 Olav Dahlum 2011-05-04 14:08:02 CEST
(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.

Note You need to log in before you can comment on or make changes to this bug.