Also, we've now ensured that all this hard work gets into core more quickly,
by adding it to our build infrastructure on teamcity.silverstripe.org.
The following tasks now happen hourly, as opposed to once every couple of months:
- Generate new master language files (through i18nTextCollector)
- Uploading the master to getlocalization.com and committing it to git
- Downloading new translations from getlocalization.com and committing them to git
On Monday, June 25, 2012 2:29:37 PM UTC+2, Ingo Schommer wrote:
> The following tasks now happen hourly, as opposed to once every couple of > months: > - Generate new master language files (through i18nTextCollector) > - Uploading the master to getlocalization.com and committing it to git > - Downloading new translations from getlocalization.com and committing > them to git
> On Monday, June 25, 2012 2:29:37 PM UTC+2, Ingo Schommer wrote:
> The following tasks now happen hourly, as opposed to once every couple of months:
> - Generate new master language files (through i18nTextCollector)
> - Uploading the master to getlocalization.com and committing it to git
> - Downloading new translations from getlocalization.com and committing them to git
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/JrOEh0umd3EJ.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
Hello there, I've had a look in our build server,
there was a flag which stated "only trigger build with pending changes".
Since that's relating to git changes only, it was effectively ignoring
the hourly setup. I've changed that, and will keep an eye on it.
Agreed that its frustrating to have to wait for the translations
to become available - its a more complex process than I hoped
when first starting to use getlocalization.com,
particularly I've overlooked the fact that only admins
can download the YML files from the website (which sucks).
Ah well, we're getting there - thanks for your work!
> On Monday, June 25, 2012 2:29:37 PM UTC+2, Ingo Schommer wrote:
> The following tasks now happen hourly, as opposed to once every couple of months:
> - Generate new master language files (through i18nTextCollector)
> - Uploading the master to getlocalization.com and committing it to git
> - Downloading new translations from getlocalization.com and committing them to git
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/JrOEh0umd3EJ.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
I've done some Polish translations in framework, because that's where they are lacking the most. Haven't touched cms yet.
Downloading YML for nonadmins seems like a feature request for getlocalization.com that shouldn't be too hard for them to implement. Or do they have some rationale behind this limitation?
I've seen some mentions about onsite translation on the forums -- is there a howto about it? Would love to try it, especially because Polish grammar is much more complex than English one and it's way easier to translate in context.
W dniu wtorek, 3 lipca 2012 23:01:46 UTC+2 użytkownik Ingo Schommer napisał:
> Hello there, I've had a look in our build server,
> there was a flag which stated "only trigger build with pending changes".
> Since that's relating to git changes only, it was effectively ignoring
> the hourly setup. I've changed that, and will keep an eye on it.
> It looks like your changes came in 21h ago though:
> Agreed that its frustrating to have to wait for the translations
> to become available - its a more complex process than I hoped
> when first starting to use getlocalization.com,
> particularly I've overlooked the fact that only admins
> can download the YML files from the website (which sucks).
> Ah well, we're getting there - thanks for your work!
> On Monday, June 25, 2012 2:29:37 PM UTC+2, Ingo Schommer wrote:
>> The following tasks now happen hourly, as opposed to once every couple of >> months:
>> - Generate new master language files (through i18nTextCollector)
>> - Uploading the master to getlocalization.com and committing it to git
>> - Downloading new translations from getlocalization.com and committing >> them to git
> -- > You received this message because you are subscribed to the Google Groups > "SilverStripe Core Development" group.
> To view this discussion on the web visit > https://groups.google.com/d/msg/silverstripe-dev/-/JrOEh0umd3EJ.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to > silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at > http://groups.google.com/group/silverstripe-dev?hl=en.
I think their reluctance to provide YML download
is processing time rather than implementation complexity.
Generating the ZIP with all ~50 languages takes 2 minutes.
Given that its a free service, thats quite a bit of CPU for each language.
I agree that they should provide it, but can also understand their reasoning.
It looks like the onsite translation (JavaScript editor) is discontinued,
since the embed codes for it disappeared from my admin menu.
I've asked them about it two weeks ago, no reply yet :/
> I've done some Polish translations in framework, because that's where they are lacking the most. Haven't touched cms yet.
> Downloading YML for nonadmins seems like a feature request for getlocalization.com that shouldn't be too hard for them to implement. Or do they have some rationale behind this limitation?
> I've seen some mentions about onsite translation on the forums -- is there a howto about it? Would love to try it, especially because Polish grammar is much more complex than English one and it's way easier to translate in context.
> W dniu wtorek, 3 lipca 2012 23:01:46 UTC+2 użytkownik Ingo Schommer napisał:
> Hello there, I've had a look in our build server,
> there was a flag which stated "only trigger build with pending changes".
> Since that's relating to git changes only, it was effectively ignoring
> the hourly setup. I've changed that, and will keep an eye on it.
> Agreed that its frustrating to have to wait for the translations
> to become available - its a more complex process than I hoped
> when first starting to use getlocalization.com,
> particularly I've overlooked the fact that only admins
> can download the YML files from the website (which sucks).
> Ah well, we're getting there - thanks for your work!
>> On Monday, June 25, 2012 2:29:37 PM UTC+2, Ingo Schommer wrote:
>> The following tasks now happen hourly, as opposed to once every couple of months:
>> - Generate new master language files (through i18nTextCollector)
>> - Uploading the master to getlocalization.com and committing it to git
>> - Downloading new translations from getlocalization.com and committing them to git
>> -- >> You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
>> To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/JrOEh0umd3EJ.
>> To post to this group, send email to silverstripe-dev@googlegroups.com.
>> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/DQOtLWWQ0NkJ.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
2 minutes for such processing seems a bit too long, but fair enough - they won't allow it for free users. I wonder if it could be enabled if I paid for my user account (I don't want to have my projects there, but I use SilverStripe a lot and I want it to look as good as it can to my customers, so I have interest in translating it well). Anyway, not a question to this newsgroup :-)
It's a pity onsite translation is discontinued. No reply for two weeks doesn't sound too good, certainly doesn't make me want to use their services.
> Generating the ZIP with all ~50 languages takes 2 minutes.
> Given that its a free service, thats quite a bit of CPU for each language.
> I agree that they should provide it, but can also understand their > reasoning.
> It looks like the onsite translation (JavaScript editor) is discontinued,
> since the embed codes for it disappeared from my admin menu.
> I've asked them about it two weeks ago, no reply yet :/
No JS integration yet, waiting for somebody to pick up this ticket: http://open.silverstripe.org/ticket/7235 For now, please send us pull requests (just for JS files, not for PHP files). Thanks!
> 2 minutes for such processing seems a bit too long, but fair enough - they won't allow it for free users. I wonder if it could be enabled if I paid for my user account (I don't want to have my projects there, but I use SilverStripe a lot and I want it to look as good as it can to my customers, so I have interest in translating it well). Anyway, not a question to this newsgroup :-)
> It's a pity onsite translation is discontinued. No reply for two weeks doesn't sound too good, certainly doesn't make me want to use their services.
> W dniu środa, 4 lipca 2012 13:49:24 UTC+2 użytkownik Ingo Schommer napisał:
> Generating the ZIP with all ~50 languages takes 2 minutes.
> Given that its a free service, thats quite a bit of CPU for each language.
> I agree that they should provide it, but can also understand their reasoning.
> It looks like the onsite translation (JavaScript editor) is discontinued,
> since the embed codes for it disappeared from my admin menu.
> I've asked them about it two weeks ago, no reply yet :/
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/X479y2YMYmgJ.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
Bumping this topic: I just finished translating the remaining Framework strings into German but there is still a lot to do. My question, what would be the best way to define language guidelines that authors can follow. At the moment there are a lot of inconsistencies regarding wording (e.g. "Benutzer" or "Mitglied"), form (Klein- / Großschreibung sie / Sie), structure, etc.
It doesn't look like getlocalization allows for a structured approach like that. Are there any ideas how to best accomplish this? I could just sit down and spend a few hours writing something that I think is consistent, but that wouldn't be in the spirit, would it. :)
BTW: It seems that the auto commits are currently turned off? Would like to test my changes, but there is no simple way to create the YML file by myself.
Good suggestions. Ingo's back in a couple of days and might have some
thoughts about the consistency stuff. I guess some overall guidelines on a
wiki, and some language specific guidelines stemming off that, would be
useful.
There is an issue with the system auto committing currently. When
fixed we're also looking to stand up a website that lets you preview your
translations near realtime; will post here when done.
> Bumping this topic: I just finished translating the remaining Framework
> strings into German but there is still a lot to do. My question, what would
> be the best way to define language guidelines that authors can follow. At
> the moment there are a lot of inconsistencies regarding wording (e.g.
> "Benutzer" or "Mitglied"), form (Klein- / Großschreibung sie / Sie),
> structure, etc.
> It doesn't look like getlocalization allows for a structured approach like
> that. Are there any ideas how to best accomplish this? I could just sit
> down and spend a few hours writing something that I think is consistent,
> but that wouldn't be in the spirit, would it. :)
> BTW: It seems that the auto commits are currently turned off? Would like
> to test my changes, but there is no simple way to create the YML file by
> myself.
> On Friday, July 6, 2012 6:41:27 PM UTC+2, Ingo Schommer wrote:
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/silverstripe-dev?hl=en.
-- Sigurd Magnusson
Business Relationship Manager
SilverStripe
> Good suggestions. Ingo's back in a couple of days and might have some
> thoughts about the consistency stuff. I guess some overall guidelines on a
> wiki, and some language specific guidelines stemming off that, would be
> useful.
> There is an issue with the system auto committing currently. When
> fixed we're also looking to stand up a website that lets you preview your
> translations near realtime; will post here when done.
> Thanks for completing the German translation btw!
> Submit new file as a ticket as open.silverstripe.org ...
> Cheers!
> Sigurd.
> On 2 August 2012 03:18, Dominik <dominik.droesc...@gmail.com> wrote:
>> Bumping this topic: I just finished translating the remaining Framework
>> strings into German but there is still a lot to do. My question, what would
>> be the best way to define language guidelines that authors can follow. At
>> the moment there are a lot of inconsistencies regarding wording (e.g.
>> "Benutzer" or "Mitglied"), form (Klein- / Großschreibung sie / Sie),
>> structure, etc.
>> It doesn't look like getlocalization allows for a structured approach
>> like that. Are there any ideas how to best accomplish this? I could just
>> sit down and spend a few hours writing something that I think is
>> consistent, but that wouldn't be in the spirit, would it. :)
>> BTW: It seems that the auto commits are currently turned off? Would like
>> to test my changes, but there is no simple way to create the YML file by
>> myself.
>> On Friday, July 6, 2012 6:41:27 PM UTC+2, Ingo Schommer wrote:
>> To post to this group, send email to silverstripe-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> silverstripe-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/silverstripe-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "SilverStripe Core Development" group.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/silverstripe-dev?hl=en.
I've fixed the TeamCity builds … configuration error on my behalf.
Lots of moving parts, sorry that I've overlooked this.
Will keep an eye on the builds in the next days.
Defining language guidelines: Getlocalization has a "translation memory",
which looks like it might help. It fuzzy matches words and phrases,
looks for existing translations, and suggests them directly above the
translation edit box. Enabled by default, so I would hope translators use it already.
> Currently working myself into github, so I am not sure this is the correct approach. Will add the bug if you prefer that.
> On Wed, Aug 1, 2012 at 9:44 PM, Sigurd Magnusson <sig...@silverstripe.com> wrote:
> Good suggestions. Ingo's back in a couple of days and might have some thoughts about the consistency stuff. I guess some overall guidelines on a wiki, and some language specific guidelines stemming off that, would be useful.
> There is an issue with the system auto committing currently. When fixed we're also looking to stand up a website that lets you preview your translations near realtime; will post here when done.
> Thanks for completing the German translation btw!
> Submit new file as a ticket as open.silverstripe.org ...
> Cheers!
> Sigurd.
> On 2 August 2012 03:18, Dominik <dominik.droesc...@gmail.com> wrote:
> Bumping this topic: I just finished translating the remaining Framework strings into German but there is still a lot to do. My question, what would be the best way to define language guidelines that authors can follow. At the moment there are a lot of inconsistencies regarding wording (e.g. "Benutzer" or "Mitglied"), form (Klein- / Großschreibung sie / Sie), structure, etc.
> It doesn't look like getlocalization allows for a structured approach like that. Are there any ideas how to best accomplish this? I could just sit down and spend a few hours writing something that I think is consistent, but that wouldn't be in the spirit, would it. :)
> BTW: It seems that the auto commits are currently turned off? Would like to test my changes, but there is no simple way to create the YML file by myself.
> On Friday, July 6, 2012 6:41:27 PM UTC+2, Ingo Schommer wrote:
> They made the in-page editor a paid feature ...
> Guess that's what you have to put up with if using free services.
> https://twitter.com/getlocalization/status/220806794623188993
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
