What’s the current rosetta deployment policy? I translated the file last night, but do I need SVN access to upload it?
I see from other messages that we’re meant to request deployment through the locale site’s Tools > Deploy Request menu, but I’m unsure how I should be transferring the file to you for deployment.
The translated file can be found here.
Zé 2:00 pm on November 2, 2010 Permalink |
No need to send the file, we commit and deploy from your current SVN translation (by the way, cy.wordpress.org needs a screenshot
)
gruffprys 5:35 pm on November 2, 2010 Permalink |
Thanks for the reply Zé. I’m probably being a bit thick, but I can’t find the current Welsh SVN translation for the rosetta theme at http://svn.automattic.com/wordpress-i18n/cy/ . I don’t believe I have SVN commit rights either – can that be arranged?
Please point me in the right direction if I’m looking in the wrong place! (I’d also appreciate knowing where to put the screenshot…)
Zé 10:09 am on November 3, 2010 Permalink |
The screenshot goes here: http://svn.automattic.com/wordpress-i18n/cy/rosetta/shot-cy.png. Lemme check those SVN perms.
Zé 10:17 am on November 3, 2010 Permalink |
We have “sleblog” committing to trunk, is that you? (sorry, can’t remember)
gruffprys 1:27 pm on November 3, 2010 Permalink
Nope. Slebog was responsible for the 1.52 translation back in the day. I think he’s currently travelling the world. Hell of a username, though!
I’m a bit confused by the relationship between SVN and GlotPress. The Export interface on cy.wordpress.org’s Dashboard gives the option of creating a WordPress package from either SVN or GlotPress. Does this mean that there are two independent version of the translation, or does GlotPress feed directly into SVN?
Are there any plans to include the rosetta theme and screenshots etc within GlotPress?
(Sorry for the deluge of questions!)
Zé 3:05 pm on November 3, 2010 Permalink
Ok,
SVN (as in the-po-and-mo-in-svn) has no relationship to GlotPress. The purpose of there being two separate instances of the translations is to offer an alternative for downloading *just the language files* directly from SVN.
Think of it like this: GlotPress is used to build your release, (say, 3.0.1, for instance), and SVN would be used for direct download of language files (without all the php core code) for those who already have WordPress installed or for when you want to make minor corrections to the translation without releasing a whole new 3.0.1 package on your language’s site.
My flow is to have everything ok in GP, export that to a .po, generate the .mo and upload both to SVN.
Makes sense?
Rosetta in GlotPress? (screenshot is kind of hard, heh?) Why not? Wnat to open a new issue for discussing this?
gruffprys 5:32 pm on November 3, 2010 Permalink
Yes, that makes sense. Thanks for taking the time to explain
My flow is to have everything ok in GP, export that to a .po, generate the .mo and upload both to SVN.
How about the following as a suggestion for a rainy day?
Sync and automate these procedures by splitting rosetta’s current Export function in two:
‘Export Localized Test Package’ – exactly the same as the current export function
‘Create Localized Release Package’ – this would generate a complete WordPress package, update the .mo and .po files in SVN, and add a download widget to the local homepage with a big link to the complete package and little links below it to the .mo and .po files individually
(just a suggestion)
As to rosetta, it would certainly be more convenient if it was in GlotPress. I see your point about the screenshot. Ideally, you’d be able to upload a screenshot from the locale Dashboard in rosetta.
However, I’m sure I can manage with SVN for the time being!
Zé 4:03 pm on November 3, 2010 Permalink |
Also you now have commit perms on http://svn.automattic.com/wordpress-i18n/cy/
gruffprys 5:33 pm on November 3, 2010 Permalink |
Thanks Zé!