[WG: I18N & L10N] [Building Sakai] Any German I18N/L10N work done?

Neal Caidin neal.caidin at apereo.org
Fri Sep 27 12:55:10 PDT 2013 

we lost the Internationalization group on this thread.  I want to copy them in case I've misstatted anything or we are going on the wrong path.

Cheers



Neal Caidin
Sakai CLE Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Sep 27, 2013, at 3:49 PM, "Gast, Cynthia (cmw6s)" <cmw6s at eservices.virginia.edu> wrote:

> Hi Neal:
> Thanks for your emails!  I apologize for confusing the terminology, and I agree with all you've said to untangle my wording :-)
> 
> Cindy
> 
> From: Neal Caidin [neal.caidin at apereo.org]
> Sent: Friday, September 27, 2013 3:37 PM
> To: Gast, Cynthia (cmw6s)
> Cc: sakai-dev at collab.sakaiproject.org; oit-atg at virginia.edu
> Subject: Re: [Building Sakai] Any German I18N/L10N work done?
> 
> After I almost completed responding to your email below, I think I see a terminology problem which may clear all this up.
> 
> Jira has a field called Component, which is strictly controlled. We will not be adding a "German" component or any other language. We will also not be adding "UVaTranslation" as a component. The component field has options like Translation, Config, etc, which you seem to be familiar with. 
> 
> Jira has another field called Labels, which is not controlled. You can type in any value in a Label that you want. It acts as a keyword. Just like the Component field, Labels can have many values, not just one. Unlike Components, these values can be anything (they seem to be case sensitive though, so be careful). They are essentially meaningless in our management of our Jira Workflow and are only there as a convenience. Some of us have found them very convenient indeed. I hope that makes my comments below more sensible.
> 
> Tag - there is no field in our Jira configuration called Tag. But Tag logically seems like the same thing as a Component or a Label. I think this is the source of confusion, using the word Tag and having multiple meanings for it. 
> 
> I hope this helps.
> 
> Thanks!
> Neal
> 
> 
> 
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Sep 27, 2013, at 2:20 PM, "Gast, Cynthia (cmw6s)" <cmw6s at eservices.virginia.edu> wrote:
> 
>> Hi Neal:
>> Thanks for your help with this.  Most of what you said does make sense to me.  I have a few thoughts on your proposal; see what you think.  Bottom line: I'm happy to proceed however you'd like, to best manage this effort.
>> 
>> I think the existing Sakai JIRAs are already tagged with "Translation", plus the component the issue represents. 
> Yes, they should have the Translation component. 
> 
>> It may then be possible to filter on this existing tag(s). 
> Yes, though the Translation component filter will pick up many other Jiras that may not be related to your issue. If you are okay with that, then going with this approach is nice and simple. 
> 
> 
>> So I would *not* be in favor of adding a "UVaTranslate" tag to these, because (if I'm understanding things correctly) Cris has already reported/created and contributed the tar files for each existing JIRA (and UVa has not yet been involved).
> The label (tag, but Jira calls it a label) is just this really nice convenience in Jira that we can use for whatever we want, to simplify things. It is easy to create labels and remove labels. And it is extremely easy to create a filter based on a label. If you don't want to do that, that's fine. If you want to do it but prefer a different label other than UVaTranslate , that's okay too. Putting a UVaTranslate label does not imply that UVa owns the tickets nor anything else. And a ticket can have more than one label, so it does not prevent other labels. I just happen to think labels are peachy, but that does not mean that we need to use them for this purpose.
> 
> 
>> 
>> I would be happy to create JIRAs, which will be sub-tickets to the existing Translation/Component issues, to address the German-only effort.  And if there is a tag to be added (i.e. 'German'?) to these, happy to add them, along with the existing component-name tag, and probably "Translation" (as in the parent).  
> That sounds good to me. You probably will put German in the title (Jira "summary" field) of the sub-ticket Jiras anyway, so a label is probably not needed. Component of Translation? Yes, please.
> 
> 
>> 
>> An example:  
>>     SAK-22971 Translations for config -- Tags:  Config, Translation   (existing JIRA created by Cris)
>>     
>>     -->   UVa creates a new JIRA, as a sub-task to SAK-22971, to handle only the German translations for 'config', with Tags: Config, Translation, German (if approved)
> See my comments at the top of the email. I don't think we want to add a German component. And I don't think we need a German label either. 
>> 
>> 
>> How does this sound to you?  
>> 
>> Thanks, 
>> Cindy @ UVa
>> 
>> 
>> From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Neal Caidin [neal.caidin at apereo.org]
>> Sent: Friday, September 27, 2013 1:53 PM
>> To: sakai-dev at collab.sakaiproject.org; oit-atg at virginia.edu
>> Subject: Re: [Building Sakai] Any German I18N/L10N work done?
>> 
>> So I learn that these tickets are not just German translations. That makes it a little less elegant. On a translation ticket which I handled, for merging into trunk, I've been breaking up the separate translations into separate tickets as sub-tasks.
>> 
>> How about we start by tagging these issues with something like UVaTranslate, just for the purpose of easily creating a filter for this set of issues. And perhaps as UVa goes through the issues, they can break out new Jira tickets for the German translations (which would need to be done anyway, correct?). Each of those new tickets will be a sub-ticket for the corresponding ticket that has multiple translations for that same functional area. 
>> 
>> Does that make sense?
>> 
>> Thanks,
>> Neal
>> 
>> 
>> 
>> Neal Caidin
>> Sakai CLE Community Coordinator
>> neal.caidin at apereo.org
>> Skype: nealkdin
>> Twitter: ncaidin
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Sep 27, 2013, at 1:02 PM, Neal Caidin <neal.caidin at apereo.org> wrote:
>> 
>>> 
>>> Sounds great! 
>>> 
>>> I'm looping in the Internationalization/Localization group to keep them in the loop.
>>> 
>>> There are several ways to link the tickets together. To me, the two easiest seem to be to create a parent ticket and add links to all these Jiras , or label them with something like "GermanTranslation" . I can create a filter and make it public. I think either way would be fine.
>>> 
>>> Cheers,
>>> Neal
>>> 
>>> 
>>> Neal Caidin
>>> Sakai CLE Community Coordinator
>>> neal.caidin at apereo.org
>>> Skype: nealkdin
>>> Twitter: ncaidin
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Sep 27, 2013, at 12:43 PM, Cris J Holdorph <holdorph at unicon.net> wrote:
>>> 
>>>> I also sent you the entire set of German files under a direct email. 
>>>> The compressed tar archive was 500k in case anyone else wants a copy. 
>>>> There is nothing different about this file from what's in the separate 
>>>> jira's, just a simpler way to get a hold of the entire German translation.
>>>> 
>>>> ---- Cris J H
>>>> 
>>>> On 09/27/2013 09:30 AM, Gast, Cynthia (cmw6s) wrote:
>>>>> Thanks for the list, Cris... I'll start looking thru these, and ask questions as needed :-)  Yes, I see what you mean, it sure would be nice if there was a parent JIRA and these were all either liked to it or sub-task children...  I see the tar files attached to each one, so assuming this contains German (and other) language files.
>>>>> 
>>>>> We will start here by applying any German files to our local test Sakai 2.9.1, and testing for our users.  I'll update the cited JIRAs as we make progress with the German effort.
>>>>> 
>>>>> Thanks,
>>>>> Cindy
>>>>> 
>>>>> ________________________________________
>>>>> From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Cris J Holdorph [holdorph at unicon.net]
>>>>> Sent: Friday, September 27, 2013 11:55 AM
>>>>> To: sakai-dev at collab.sakaiproject.org
>>>>> Cc: oit-atg at virginia.edu
>>>>> Subject: Re: [Building Sakai] Any German I18N/L10N work done?
>>>>> 
>>>>> There were several jiras, one for each module.
>>>>> 
>>>>> SAK-22971
>>>>> SAK-22970
>>>>> SAK-22969
>>>>> SAK-22968
>>>>> SAK-22967
>>>>> SAK-22966
>>>>> SAK-22965
>>>>> SAK-22964
>>>>> SAK-22963
>>>>> SAK-22962
>>>>> SAK-22961
>>>>> SAK-22960
>>>>> SAK-22959
>>>>> SAK-22958
>>>>> SAK-22957
>>>>> SAK-22954
>>>>> SAK-22953
>>>>> SAK-22952
>>>>> SAK-22951
>>>>> SAK-22950
>>>>> SAK-22949
>>>>> SAK-22948
>>>>> SAK-22947
>>>>> SAK-22946
>>>>> SAK-22945
>>>>> SAK-22944
>>>>> SAK-22943
>>>>> SAK-22942
>>>>> SAK-22941
>>>>> SAK-22940
>>>>> SAK-22939
>>>>> SAK-22938
>>>>> SAK-22937
>>>>> SAK-22936
>>>>> SAK-24399
>>>>> SAK-24246
>>>>> STAT-334
>>>>> SRCH-108
>>>>> SAM-2026
>>>>> PRFL-787
>>>>> POLL-185
>>>>> MSGCNTR-742
>>>>> LSNBLDR-157
>>>>> LSNBLDR-156
>>>>> 
>>>>> ---- Cris J H
>>>>> 
>>>>> On 09/27/2013 08:34 AM, Gast, Cynthia (cmw6s) wrote:
>>>>>> Hi Cris:
>>>>>> 
>>>>>> Thanks for your reply and this very encouraging information.
>>>>>> 
>>>>>> UVa would like to help get the German translations into Sakai, and we could start by adding them here, updating as needed (we are running 2.9.1) for the tools we use here.  Then, contributing them back to Sakai.
>>>>>> 
>>>>>> We'd like to take you up on your offer to send us the German translations you have.  Also, if there is any open Sakai JIRA that applies to this effort, please let me know and we will update it.
>>>>>> 
>>>>>> Thanks very much!
>>>>>> Cynthia Gast
>>>>>> UVa Sakai development team
>>>>>> cmw6s at virginia.edu
>>>>>> 
>>>>>> ________________________________________
>>>>>> From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Cris J Holdorph [holdorph at unicon.net]
>>>>>> Sent: Friday, September 27, 2013 11:20 AM
>>>>>> To: sakai-dev at collab.sakaiproject.org
>>>>>> Subject: Re: [Building Sakai] Any German I18N/L10N work done?
>>>>>> 
>>>>>> Pearson donated a lot of translations in various jira tickets a while
>>>>>> back.  Among the languages donated were German.  Unfortunately each
>>>>>> module had to be individually committed by the maintainer.  And because
>>>>>> Pearson was donating several translations at once, I uploaded them all
>>>>>> as one .tar bundle.  Unfortunately, some of the translations were not
>>>>>> accepted (e.g., French), which has caused the entire process to slow down.
>>>>>> 
>>>>>> I don't know how to get the German files committed to Sakai quicker, but
>>>>>> if someone is interested, they can email me and I'll try to provide the
>>>>>> files I have.
>>>>>> 
>>>>>> Our translations were based on 2.9.x, and there are a couple of tools
>>>>>> where we've made substantial modifications, so the translations might
>>>>>> not be a one-to-one match for those tools (mostly gradebook, but some
>>>>>> differences in samigo too).
>>>>>> 
>>>>>> ---- Cris J H
>>>>>> 
>>>>>> On 09/27/2013 07:40 AM, Gast, Cynthia (cmw6s) wrote:
>>>>>>> Hello:
>>>>>>> We've had a group express interest in German language support for
>>>>>>> Sakai.  Is there any work going on in this area?  If not, what guidance
>>>>>>> is available for adding such support?
>>>>>>> 
>>>>>>> Thanks for any information.
>>>>>>> 
>>>>>>> Cynthia Gast, UVa Sakai development team
>>>>>> 
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>> 
>>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>>> 
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>> 
>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>> 
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>> 
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20130927/39617234/attachment-0001.html

More information about the i18n mailing list