[Koha-translate] Some best practice questions for an upcoming translation to Swedish

[Viktor.Sarge at regionhalland.se]

Thanks for the help!

It seems to me that we will have to accept that a first time translation might be too much work to handle between string freeze and the release. So having Koha ship with a full translation included might have to wait until 3.12 even if we translate 3.10.

Nice to see a Finnish colleague! You have some really sweet libraries over there :)

Kind regards!
/Viktor Sarge

________________________________
[Beskrivning: Region Halland]
Viktor Sarge
Utvecklingsledare
Kulturavdelningen
Regionkontoret
TFN: 035-17 98 73
E-POST: Viktor.Sarge at regionhalland.se
BESÖKSADRESS: Södra vägen 9, 30238 Halmstad
www.regionhalland.se<http://www.regionhalland.se>

Från: Hailuodon Kunnankirjasto [mailto:m.kirjasto.hailuoto at gmail.com]
Skickat: den 20 augusti 2012 10:41
Till: Sarge Viktor RK
Kopia: Koha-translate at lists.koha-community.org
Ämne: Re: [Koha-translate] Some best practice questions for an upcoming translation to Swedish

Hi! My twocents here, i hope it helps,

·         Is offline translation more effective?
- depends on your habits and whole work flow idea. I, working alone on en->fi here, have found both quite similar in my eyes.

·         When should we translate to keep out of trouble with string freeze etc of new versions?
I understand that Koha 3.10 should arrive 22 november. Would that give us six months of peace to translate the intranet?
- That might be a good idea. Anyway the new translation project inherits something like 80% from the old version. And preferences can also be translated while waiting. And then when you get the terminology sorted in intranet, translating OPAC for patron's eyes is already right on tested, solid ground.

·         How much translation work does a new .X version usually introduce? Is translating 3.10 the best idea when go-live is something like spring 2013 or should we translate 3.12 instead?
In my shallow experience, something like 20%  The main problem in translation schedule is of course that you dont get the new files to translate until the new version is ready!! :)  Basically translate always the newest avilable, because the new templates for future versions are drawn from those. That way the work done won't get lost. UNLESS of course you for some reason have decided to hold onto a certain version number.

Kind regards

Thanks, likewise! I am glad to find you here. Keep up the good worrk!

--
kirjastonhoitaja-kulttuurisihteeri mr. Kari Blomster

Hailuodon kunnankirjasto / Luovontie 61 / 90480 HAILUOTO / kirjasto at hailuoto.fi<mailto:kirjasto at hailuoto.fi> / puh. +358444973565 / avoinna ti 10-16, ke 14-20, pe 14-20.

* Kotisivut: http://www.hailuoto.fi/sivu/fi/kuntapalvelut/perus/Sivistyspalvelut/kirjasto/
* Kuvablogi: http://www.flickr.com/photos/luovonkirjastonhoitaja/
* @Facebook: http://www.facebook.com/#!/pages/Hailuodon-kirjasto-Hailuoto-Public-Library/352032659853

/Viktor Sarge
________________________________
[Beskrivning: Region Halland]
Viktor Sarge
Utvecklingsledare
Kulturavdelningen
Regionkontoret
TFN: 035-17 98 73
E-POST: Viktor.Sarge at regionhalland.se<http://d.se>
BESÖKSADRESS: Södra vägen 9, 30238 Halmstad
www.regionhalland.se<http://www.regionhalland.se>


_______________________________________________
Koha-translate mailing list
Koha-translate at lists.koha-community.org<mailto:Koha-translate at lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate
website: www.koha-community.org<http://www.koha-community.org>
git: git.koha-community.org<http://git.koha-community.org>
bugs: bugs.koha-community.org<http://bugs.koha-community.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-translate/attachments/20120829/a596aa7d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6205 bytes
Desc: image001.png
URL: </pipermail/koha-translate/attachments/20120829/a596aa7d/attachment.png>