[WG: I18N & L10N] [Building Sakai] Any German I18N/L10N work done?
Gast, Cynthia (cmw6s)
cmw6s at eservices.virginia.edu
Thu Oct 17 10:05:12 PDT 2013
Hello Jean-Francois:
Thank you for your reply.
>About 3), I would prefer a new ticket. I will link to the tool-specific
>ones that include different languages when I commit.
OK. I can create a single JIRA for the German language support, and you can handle it how you describe.
>About 4), because we don't have a lot of old German files, a diff will
>be as big as providing the files and this will mean more work on my
>side. An archive with all the German files will be fine.
Makes sense. I will attach the archive provided to me by Cris Holdorph of Unicon; Pearson contributed the German translations along with others (my understanding), and Cris pulled out the German ones for me when I inquired if any German support existed.
Cindy / UVa
________________________________________
From: Jean-Francois Leveque [jean-francois.leveque at upmc.fr]
Sent: Thursday, October 17, 2013 4:18 AM
To: Gast, Cynthia (cmw6s)
Cc: Cris J Holdorph; sakai-dev at collab.sakaiproject.org; i18n
Subject: Re: [Building Sakai] Any German I18N/L10N work done?
Hello Cindy,
About 3), I would prefer a new ticket. I will link to the tool-specific
ones that include different languages when I commit.
About 4), because we don't have a lot of old German files, a diff will
be as big as providing the files and this will mean more work on my
side. An archive with all the German files will be fine.
Thanks,
J-F
On 16/10/2013 20:09, Gast, Cynthia (cmw6s) wrote:
> Hello Jean-François,
>
> Thank you for your email, glad you are feeling better. Yes, Neal assisted and I'm now added to the i18n email list.
>
> In the past few weeks,
> 1) Cris Holdorph sent me an archive of the German-only files (happy to share this),
> 2) I recently added them here to our Sakai 2.9.1 and they are now in production here (I don't read German, but sites are changed successfully to display the german; we have a group who offered to look at the German from a language perspective),
> 3) Neal suggested I create sub-jira for each existing I18N project jira, and submit the german-only files,
> 4) I'm about ready to start doing that, planning to submit svn-diff patch files for each, based on what has been committed to our SVN 2.9.1 repository.
>
> Let me know if you'd like a different approach? I'm happy to continue, or happy to turn it over to you.
>
> Thanks,
> Cindy / UVa
>
>
> ________________________________________
> From: Jean-Francois Leveque [jean-francois.leveque at upmc.fr]
> Sent: Wednesday, October 16, 2013 10:54 AM
> To: Gast, Cynthia (cmw6s)
> Cc: Cris J Holdorph; sakai-dev at collab.sakaiproject.org; i18n
> Subject: Re: [Building Sakai] Any German I18N/L10N work done?
>
> Hi,
>
> I'm afraid I've been very busy, then ill, then very busy again in the
> past weeks. I'm back and hope to be able to contribute my volunteer time
> to the i18n/L10n community more regularly. I will be away from work on
> Halloween's week, BTW.
>
> Cynthia, why don't you join i18n at collab.sakaiproject.org?
>
> If someone could create an archive with only the German files that I
> could unarchive into a checkout of sakai-trunk, it would greatly
> accelerate my merge of it into trunk. Feel free to create a JIRA for this.
>
> When this is done, we could update Crowdin's content with those files.
>
> Did I miss something else?
>
> Cheers,
>
> Jean-François
>
> On 14/10/2013 21:35, Gast, Cynthia (cmw6s) wrote:
>> Hi Mark,
>> (note: someone may need to forward this to the I18N group; I'm not able to post to it...)
>>
>> I have German files for 44 Sakai projects. Here is a list of the projects:
>>
>> access
>> alias
>> announcement
>> archive
>> assignment
>> authz
>> basiclti
>> calendar
>> chat
>> citations
>> config
>> content
>> dav
>> emailtemplateservice
>> help
>> jobscheduler
>> jsf
>> lessonbuilder
>> login
>> message
>> memory
>> metaobj
>> msgcntr
>> podcasts
>> polls
>> portal
>> postem
>> presence
>> profile2
>> reset-pass
>> roster
>> rwiki
>> sam
>> search
>> site
>> site-manage
>> sitestats
>> taggable
>> tool
>> user
>> usermembership
>> velocity
>> web
>> webservices
>>
>> 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, October 11, 2013 11:05 AM
>> To: sakai-dev at collab.sakaiproject.org
>> Subject: Re: [Building Sakai] Any German I18N/L10N work done?
>>
>> You're missing several of the German property files that were uploaded
>> to the various jira tickets. Where did you get the German files you
>> imported?
>>
>> ---- Cris J H
>>
>>
>> On 10/11/2013 12:03 AM, Mark Breuker wrote:
>>> Hi Cyntia,
>>>
>>> I recently imported the German translations from Sakai trunk into
>>> Crowdin (an online translation tool). It appears that the German
>>> translation is about 15% complete.
>>>
>>> http://crowdin.net/project/sakai-cle/de
>>>
>>> Kind regards,
>>>
>>> Mark
>>> ------------------------------------------------------------------------
>>> *Van:* sakai-dev-bounces at collab.sakaiproject.org
>>> [sakai-dev-bounces at collab.sakaiproject.org] namens Gast, Cynthia (cmw6s)
>>> [cmw6s at eservices.virginia.edu]
>>> *Verzonden:* donderdag 10 oktober 2013 21:45
>>> *Aan:* Neal Caidin
>>> *CC:* oit-atg at virginia.edu (oit-atg at Virginia.EDU);
>>> i18n at collab.sakaiproject.org i18n; sakai-dev at collab.sakaiproject.org
>>> Sakai-Dev
>>> *Onderwerp:* Re: [Building Sakai] Any German I18N/L10N work done?
>>>
>>> Hi Neal,
>>> I see I received an error on my post ("You do not have permission to
>>> post to this list."), so perhaps the I18N group did not see my posting?
>>>
>>> Cindy
>>>
>>> ------------------------------------------------------------------------
>>> *From:* Neal Caidin [nealcaidin at sakaifoundation.org] on behalf of Neal
>>> Caidin [neal.caidin at apereo.org]
>>> *Sent:* Thursday, October 10, 2013 12:34 PM
>>> *To:* Gast, Cynthia (cmw6s)
>>> *Cc:* holdorph at unicon.net; sakai-dev at collab.sakaiproject.org Sakai-Dev;
>>> oit-atg at virginia.edu (oit-atg at Virginia.EDU);
>>> i18n at collab.sakaiproject.org i18n
>>> *Subject:* Re: [Building Sakai] Any German I18N/L10N work done?
>>>
>>> Hi Cindy,
>>>
>>> I don't know that it is up to me per se' (i.e. I don't think my approval
>>> is needed) , but it sounds like a good plan to me. If you open the
>>> tickets, that will give visibility and anyone can comment on them.
>>>
>>> I'm glad you copied the Internationalization group on this ticket.
>>> Perhaps Jean-Fraçois would like to comment or somebody else from i18n?
>>> Any concerns?
>>>
>>> Thanks,
>>> Neal
>>>
>>>
>>>
>>> Neal Caidin
>>> Sakai CLE Community Coordinator
>>> neal.caidin at apereo.org<mailto:neal.caidin at apereo.org>
>>> Skype: nealkdin
>>> Twitter: ncaidin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Mark Breuker
>>> Product Owner
>>> Tel.: +31 71 5451 203
>>>
>>> Leidse Onderwijsinstellingen bv
>>> Leidsedreef 2
>>> 2352 BA Leiderdorp
>>> www.loi.nl
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> Nederland wordt steeds slimmer. Leidse Onderwijsinstellingen
>>>
>>> De informatie verzonden met dit e-mailbericht (en bijlagen) is
>>> uitsluitend bestemd voor de geadresseerde(n) en zij die van de
>>> geadresseerde(n) toestemming hebben dit bericht te lezen. Gebruik door
>>> anderen dan geadresseerde(n) is verboden. De informatie in dit
>>> e-mailbericht (en de bijlagen) kan vertrouwelijk van aard zijn en kan
>>> binnen het bereik vallen van een wettelijke geheimhoudingsplicht. Indien
>>> u deze e-mail ten onrechte ontvangen hebt, wordt u verzocht ons daarvan
>>> zo spoedig mogelijk per e-mail of telefonisch op de hoogte te stellen,
>>> en het ontvangen bericht (en de bijlagen) te wissen zonder deze te
>>> lezen, te kopiëren of aan derden bekend te stellen.
>>>
>>> P Denk aan het milieu voordat u dit bericht print
>>>
>>>
>>> On Oct 10, 2013, at 11:24 AM, "Gast, Cynthia (cmw6s)"
>>> <cmw6s at eservices.virginia.edu<mailto:cmw6s at eservices.virginia.edu>> wrote:
>>>
>>>> Hi Neal and Cris:
>>>>
>>>> Update: UVa has applied, built and unit tested the German files to
>>>> our Sakai 2.9.1 dev and test instances, along with updating
>>>> sakai.properties to include the German locale. We are planning to
>>>> roll this out to production this weekend. Unit testing consisted of
>>>> making sure we see German for various tools that are supported. We
>>>> have a group here interested in this support, and we expect them to
>>>> review more specifically once this is in production.
>>>>
>>>> It seems reasonable for me to start the process we discussed, Neal, to
>>>> create sub-tast JIRAs for the current Sakai JIRAs (for each affected
>>>> project) and attach the German-only files that have been provided to
>>>> Sakai and us by Unicon (courtesy of Pearson). Let me know if this
>>>> meets with your approval or if you have additional guidance about this.
>>>>
>>>> Thanks,
>>>> Cindy Gast, UVa
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>> *From:*Neal Caidin [neal.caidin at apereo.org
>>>> <mailto:neal.caidin at apereo.org>]
>>>> *Sent:*Friday, September 27, 2013 3:55 PM
>>>> *To:*Gast, Cynthia (cmw6s)
>>>> *Cc:*sakai-dev at collab.sakaiproject.org
>>>> <mailto:sakai-dev at collab.sakaiproject.org> Sakai-Dev;
>>>> oit-atg at virginia.edu<mailto:oit-atg at virginia.edu>
>>>> (oit-atg at Virginia.EDU<mailto:oit-atg at Virginia.EDU>);
>>>> i18n at collab.sakaiproject.org<mailto:i18n at collab.sakaiproject.org> i18n
>>>> *Subject:*Re: [Building Sakai] Any German I18N/L10N work done?
>>>>
>>>> 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<mailto: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<mailto: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
>>>>> <mailto:neal.caidin at apereo.org>]
>>>>> *Sent:*Friday, September 27, 2013 3:37 PM
>>>>> *To:*Gast, Cynthia (cmw6s)
>>>>> *Cc:*sakai-dev at collab.sakaiproject.org
>>>>> <mailto:sakai-dev at collab.sakaiproject.org>;oit-atg at virginia.edu
>>>>> <mailto: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<mailto: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<mailto: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
>>>>>> <mailto:sakai-dev-bounces at collab.sakaiproject.org>[sakai-dev-bounces at collab.sakaiproject.org
>>>>>> <mailto:sakai-dev-bounces at collab.sakaiproject.org>] on behalf of
>>>>>> Neal Caidin [neal.caidin at apereo.org<mailto:neal.caidin at apereo.org>]
>>>>>> *Sent:*Friday, September 27, 2013 1:53 PM
>>>>>> *To:*sakai-dev at collab.sakaiproject.org
>>>>>> <mailto:sakai-dev at collab.sakaiproject.org>;oit-atg at virginia.edu
>>>>>> <mailto: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<mailto:neal.caidin at apereo.org>
>>>>>> Skype: nealkdin
>>>>>> Twitter: ncaidin
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sep 27, 2013, at 1:02 PM, Neal Caidin<neal.caidin at apereo.org
>>>>>> <mailto: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<mailto:neal.caidin at apereo.org>
>>>>>>> Skype: nealkdin
>>>>>>> Twitter: ncaidin
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sep 27, 2013, at 12:43 PM, Cris J Holdorph<holdorph at unicon.net
>>>>>>> <mailto: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
>>>>>>>>> <mailto:sakai-dev-bounces at collab.sakaiproject.org>[sakai-dev-bounces at collab.sakaiproject.org
>>>>>>>>> <mailto:sakai-dev-bounces at collab.sakaiproject.org>] on behalf of
>>>>>>>>> Cris J Holdorph [holdorph at unicon.net<mailto:holdorph at unicon.net>]
>>>>>>>>> Sent: Friday, September 27, 2013 11:55 AM
>>>>>>>>> To:sakai-dev at collab.sakaiproject.org
>>>>>>>>> <mailto:sakai-dev at collab.sakaiproject.org>
>>>>>>>>> Cc:oit-atg at virginia.edu<mailto: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<mailto:cmw6s at virginia.edu>
>>>>>>>>>>
>>>>>>>>>> ________________________________________
>>>>>>>>>> From:sakai-dev-bounces at collab.sakaiproject.org
>>>>>>>>>> <mailto:sakai-dev-bounces at collab.sakaiproject.org>[sakai-dev-bounces at collab.sakaiproject.org
>>>>>>>>>> <mailto:sakai-dev-bounces at collab.sakaiproject.org>] on behalf of
>>>>>>>>>> Cris J Holdorph [holdorph at unicon.net<mailto:holdorph at unicon.net>]
>>>>>>>>>> Sent: Friday, September 27, 2013 11:20 AM
>>>>>>>>>> To:sakai-dev at collab.sakaiproject.org
>>>>>>>>>> <mailto: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
More information about the i18n
mailing list