Why till today on glotpress there is no 3.4 branch and 3.5 but we are still at 3.3.x and 3.4 with this last one that is a 3.5alpha? Is going to be realsed 3.4.1 and we have to struggle with version to generate packages with right tag. Since last week when i asked about it noone answered… why? Pls we need an answer
Updates from SteveAgl Toggle Comment Threads | Keyboard Shortcuts
-
SteveAgl
-
SteveAgl
I have all translation uptodate, but on glotpress i still see 3.3.X and Development… if i try to generate a distro or i refer to 3.3.x or if i ggo trunk the laber is 3.5alpha. I have some erroneous string counts too in manin panels, but all file are fully translated.. i nedd someone fix it before relising the italian version THANK!
-
SteveAgl
I’m translating last strings for 3.4 in →Projects→WordPress→Development (future 3.4)→Italian i have no more string to translate but in the main list show up there is 6 strings untraslated… i checked there is no waiting translation nor fuzzy… someone can take care to solve count problem? Thams 🙂
-
SteveAgl
I’m getting ready to launch 3.3 italian version.. i went to check if there is last few strings etc and under 3.3. branch i get, not only for italian but for all languages that there is no translated strings… so italian version will be built using developer o it’s just a mistake? and when the translated strings will be available in 3.3 branch?
-
Zé
-
SteveAgl
Solved populating using 3.4… i read the answer to other post from Zé
-
Zé
Please see https://wppolyglots.wordpress.com/2011/12/13/trying-to-build-wordpress-arabic-but-cant-find/#comment-6300 sorry about the hassle
-
SteveAgl
I did all ok except that main translation file now give me -6 untraslated strings… but all is translated
-
-
-
-
SteveAgl
Hi! I’m the main administrator for all the italian project except buddypress. I’m here to ask to add a new validator to the team, the user name is flodit. Let me know when he’s been allowed to approve translation on all italian project. Thanks
-
Zé
You can simply add users with the ‘validator’ role on the dashboard of it.wordpress.org. Let me know if that works, as it has misbehaved before.
-
-
SteveAgl
As official translator for italian wordpress i wish to be added to manage revision and pproval for bbpress project on translate.wordpress.org thanks
-
Zé
I need your .org username…
-
SteveAgl
This one obviusly 🙂 SteveAgl
-
Zé
Done
-
-
-
-
SteveAgl
There is a plan otr maybe there is a method to get the nick/url/etc of alla the conrtibutors to glotpress translation so i can give credits when a new release happens to alla people that helped, suggested better translation etc to italian versione?.
-
Zé
Good point. Maybe create a ticket in the GlotPress Trac for this? (see: http://codex.wordpress.org/Reporting_Bugs for more info)
-
-
SteveAgl
How happens that at http://translate.wordpress.org/projects/wp/3.1.x/ italian translation shows -3 untralsated strings? Something wrong in string counts?
-
SteveAgl
Will jetpacjk be added to WP project? If yes when and il will be addedd to all offcial translator team?
-
Angelo Verona
Here is link GlotPress for Jatpack: http://translate.wordpress.com/projects/jetpack
-
SteveAgl
ah ok.. it’s mantained as a project from the wp.com tramslators team that not related with wordpress.org teams…
thanks for the answer
-
Zé
A little clarification: Jetpack is technically a .org plugin (although a few strings live in .com, try filtering by “jetpack” in the GlotPress WordPress.com project). The only reason it is not yet on GlotPress for .org is because we are going to be redefining language support for all plugins and it didn’t seem fair to include Jetpack just because it’s Automattic’s. We don’t want to have any “special priority” in relationship to other plugin authors.
This means that, for now, to validate Jetpack strings, you will need a WordPress.com username.
-
-
-
Wacław J., 
Angelo Verona are discussing. 
WP Polyglots 
Wacław J. 9:11 am on June 27th, 2012 Permalink |
https://wppolyglots.wordpress.com/2012/06/25/hi-when-will-be-a-3-4-sub-project/#comment-14165 🙂
SteveAgl 10:02 am on June 27th, 2012 Permalink |
I read it and i generated the italian 3.4 version… but i would like to get an official answer and the reasons why the glotpress is still unupdated… for year i generated the version using svn and all was under control, I was very happy for glotpress that made release easier than before.. but i would like to see more care for translation people that do a lot of work to spread the Word
Da^MsT 9:20 am on June 27th, 2012 Permalink |
Another reason that shows that we are definitely not ready for the full switch to GP…
Zé 9:52 am on June 27th, 2012 Permalink |
For all purposes we already did, I’m afraid.
Zé 9:51 am on June 27th, 2012 Permalink |
Because it takes time and we all have other lives that need tending to. Also, I wouldn’t describe finding the appropriate svn revision number as a “struggle”, it’s a simple process. Be it as it may, we’re working on it.
SteveAgl 10:05 am on June 27th, 2012 Permalink |
That take time i can agree… taht you have other lives… but it’s a non answer… all translation team try to give local version as fast as possible… we do on volunteer basis… if after the release someone wrote here explaining that glotpress will be updatedin weeks and why… noone would have said a word… i already asked about this problem and noone ansered but some other volunteer did… anyway thank for the answer
Wacław J. 10:06 am on June 27th, 2012 Permalink |
It would be nice if the GP branch (“project?”) was created ASAP though (but no pressure), so that strings that go missing during the development of 3.5 don’t get lost.
Andrew Nacin 2:56 pm on June 27th, 2012 Permalink |
There’s no 3.4.x project yet because I wanted to make sure we created the “branch” in a way that is smarter than what we’ve done in the past. Basically, I want to prevent you guys from re-importing everything into the branch, which is no fun, as well as maintaining history in a better fashion than the current pomo import.
No strings have been touched in 3.5 yet, and I actually paused the script to prevent trunk from overwriting things until we branch in GP. This should go ahead soon.