Drupal Norge

We suggest you read the details and tips here, but if you'd like to go ahead and try this out now, just go to http://localize.staging.drupal.org, enter drupal/drupal for the HTTP authentication prompt when requested, then log in with your drupal.org username and password and play around. Have fun and provide us feedback! Thanks for your help.

The main translation user interface of localize.drupal.org as we know it today is a result of collaboration between myself and the amazing Young Hahn of Development Seed. His work with the user interface covered making a previously unsexy interface more appealing and useful. However, given how early that was done, we did not know the actual user scenarios of language teams having contributors of all levels.

Looking at the issue queues, the most pressing problem on localize.drupal.org is the "uncontrollable" flow of suggestions. Of course you can call this the success of our web based translation interface. There is a huge number of suggestions coming in. If you look at the numbers, we have over 300.000 translations recorded and over 100.000 suggestions as well in the system. So 25% of the active text in our database is not yet approved or declined.

I've got various requests of both translators and moderators to the effect that the translation user interface is inadequate to handle the suggestions. The UI is very inviting to submit new suggestions, but the existing ones are hidden behind a little hardly visible star:

Additionally, if you click on the suggestion star, the original translation is hidden, so you cannot tell the difference between the two or more pieces of text. Clearly, both to handle existing suggestions and submit new ones, seeing the current translation with all the suggestions listed makes processing the community submissions much easier.

read more

Tenkte vi kunne bruke denne siden til å skrive opp relevante ting for folk som liker å oversette vha po-filer. Mange som har oversatt en del foretrekker å bruke po-redigeringsprogram som poEdit, Virtaal eller Lokalize (Linux/KDE) fordi det er mer effektivt. (Dette kan man lese mer om andre steder.) Min [hansfn] konklusjon så langt er at redigering vha po-filer ikke er veldig godt støttet.

For å kunne laste ned nyeste versjoner av oversettelser til bokmål og nynorsk (både til kjernen og tilleggsmoduler) må du:

1. Logge inn her med drupal.org-brukernavnet ditt
2. Melde deg inn i gruppa for det språket du vil ha oversettelser til
3. Gå til http://localize.drupal.org/translate/languages/nb/export (for bokmål) eller http://localize.drupal.org/translate/languages/nn/export for nynorsk og hente ut de oversettelsene du er interessert i

For å kunne laste ned nyeste versjoner av oversettelser til bokmål og nynorsk (både til kjernen og tilleggsmoduler) må du:

1. Logge inn her med drupal.org-brukernavnet ditt
2. Melde deg inn i gruppa for det språket du vil ha oversettelser til
3. Gå til http://localize.drupal.org/translate/languages/nb/export (for bokmål) eller http://localize.drupal.org/translate/languages/nn/export for nynorsk og hente ut de oversettelsene du er interessert i

Jeg har forstått at det er gjort et bra stykke arbeid med å konvertere til a-endelser (se http://drupalnorge.no/innlegg/forum/innlegg-999). Arbeidet er ikke komplett i d6 kjernen, men det er likevel ganske bra gjennomført. Brannfakkel: Jeg synes ikke vi skal følge denne linjen videre. Den er anbefalt av velrennomerte skolelinux, men det finnes et par vektige grunner til å heller blande former eller benytte -en:

1. Profesjonelle oversettelsesbyråer følger ikke denne linjen, men bruker «lenken» fremfor «lenka», «godkjenningen» fremfor «godkjenninga», osv.

Hei!

Jeg skjønner at vi ikke alltid vil følge Språklege retningslinjer, men da foreslår jeg at vi faktisk dokumenterer/kommenterer dette i Drupal-ordlista. Hva synes dere?

I ordlista finner jeg:

Det er en del som skal oversettes. Alle her er flinke til å oversette. De som ser over og kontrollerer gjør også en god job. For å effektivisere oss enda mer vil jeg komme med et forslag om å oversette prioriterte emner først. Dette kan være Drupal hovedprosjektet. Deretter under prosjekter av Drupal. Vi burde også satse på store prosjekter og oversette dem før vi tar mindre prosjekter.

Noen innvendinger?

Språkrådet har gitt ut en artikkel om avløserord. Skal den Norske brukergruppen ta hensyn til å bruke noen av disse oversettelsene?

Selv synes jeg det høres ut som en god idee og bruke denne siden som en ressurs i vårt arbeid, samt at ordene kan gjenkjennes av Norske brukere.

http://www.sprakrad.no/Sprakhjelp/Raad/Norsk-for-engelsk/Avloeysarord/

For øvrig er også sprakrad.no en fin side for informasjon om Norsk og diverse.

(Nesten litt skummelt å skrive innlegg her. Redd for om norsken min ikke er god nok!)

Språkrådet har gitt ut en artikkel om avløserord. Skal den Norske brukergruppen ta hensyn til å bruke noen av disse oversettelsene?

Selv synes jeg det høres ut som en god idee og bruke denne siden som en ressurs i vårt arbeid, samt at ordene kan gjenkjennes av Norske brukere.

http://www.sprakrad.no/Sprakhjelp/Raad/Norsk-for-engelsk/Avloeysarord/

For øvrig er også sprakrad.no en fin side for informasjon om Norsk og diverse.

(Nesten litt skummelt å skrive innlegg her. Redd for om norsken min ikke er god nok!)

Jeg har gått i gang med å importere «fuzzy»-forslag basert på tidligere oversettelser (ref. http://drupal.org/node/680776). Har tatt:

- kjerne for bokmål

Gjenstår:

- alt for nynorsk
- ckk, filefield og imagefield for bokmål

Jeg har gått i gang med å importere «fuzzy»-forslag basert på tidligere oversettelser (ref. http://drupal.org/node/680776). Har tatt:

- kjerne for bokmål

Gjenstår:

- alt for nynorsk
- ckk, filefield og imagefield for bokmål

Drupal 7 Alpha 1 was just announced, while its tarball and release notes page was already available before. Because the package was up earlier today, localize.drupal.org's robot already went ahead and parsed the first Drupal 7 package source code. This means that now you are able to start work on the translation on the localize.drupal.org interface.

You can find out about the amount of new and changed strings (which are numerous) by going to your language team page (pick your language team and type Drupal on the front page of localize.drupal.org). Then on the translation page shown, pick the first 7.0 alpha from the release dropdown. With the landing of Drupal 7, you'll also notice the appearance of the context filter. Drupal 7 now supports contexts, so the translation of "May" can be different when in the "Long month name" context when it is translated without context (which assumed to be the short month name version). Watch for more use of contexts in the contributed module and theme space!

While Drupal 7's first alpha is intended to be generally stable in terms of UI text, translators are good in finding errors, omissions and outdated text. So do not consider this mass of text the absolute final version of Drupal 7's user interface.

If you went through previous major Drupal releases before, you might miss a crucial feature on localize.drupal.org, namely "fuzzy matching" of previous strings. When some text was only slightly changed, this fuzzy matching could offer the previous translation as a suggestion to help you start off with the translation. This is a great feature of several Gettext tools. Unfortunately we did not yet implement this due mostly to performance constraints. However, Hilde Austlid (aka zirvap) wrote up a nice summary for you on how you can do this with helper tools outside of localize.drupal.org to help you bootstrap your Drupal 7 translations. Merging in previous versions of the CCK, FileField, Imagefield, and other, now core-integrated modules is a genuinely useful tip. Many of the "new" strings in Drupal 7 are modifications or straight copies of text carried over from integrated contributed modules. While localize.drupal.org will pick up the straight copies, the slight modifications it will treat as completely different strings, so this msgmerge trick can be very useful.

Let us know if you find issues translating Drupal 7 (or any other problems on localize.drupal.org for that matter), our having issues page explains where to submit your problems or requests.

read more

In the past several days, I've been working on several bugfixes and performance improvements, preparing the site for the imminent landing of Drupal 7's first alpha release, which will also be the first tarball version of Drupal 7 and mark the string freeze stage of development on this latest Drupal version. What that means, is you might start flooding the site exporting and importing .po files as well as generally scramble to translate Drupal 7 and beat other language teams to it. You'll surely notice the start flag in a couple days to kick off the race.

Localize.drupal.org has support for Drupal 7's localization API for quite some time now, so that should not be an issue for us. However, there were some (admittedly fairly badly coded) SQL queries used when new release source codes were parsed and your .po files were imported, which were holding our servers down unnecessarily. Following a quick tip from Drupal.org user droplet, I've looked into implementing more elegant string matching solutions, which resulted in amazing performance increases when importing .po files and parsing source code for new releases. Updated code was deployed earlier this week. This should largely help with the potential flood of .po files coming in the following weeks.

While having translations on localize.drupal.org is fine, getting it to your Drupal sites is even more interesting. Therefore Jose Reyero picked up development of this functionality and is doing it in a new Localization update module. The reason it is not part of an existing module is that this will be required in any install profile which would need to be localized and bundling in a whole set of unrelated functionality (like the whole Localization client) might not be desired. There is also a Localized Drupal install profile which is forming to be a base install profile for a localized core-only distribution. We are preparing tools for install profile builders to include in their profiles to language-enable them as easily as possible.

Finally, unfortunately there is not that big of an activity around reworking the translation UI to a fancy new user interface that many people said they love. It would be great if more people could help out there refactoring this huge patch to smaller digestible chunks, so we can get the improvements in. Working with, reviewing and testing a 116K patch is no small feat. Thanks to anybody who is helping out.

read more

Vi har nå 261 forslag som venter på å bli godkjent/avvist/redigert. Hjelp til med å rydde opp! En del av dem har venta siden i høst!

På fredag kommer Drupal 7 (forhåpentligvis), det vil være flott om vi ikke har alt for mange gamle forslag liggende da.

Angie Byron, co-maintainer for Drupal 7 just published the target date for the first alpha release of Drupal 7. While the UI / string freeze for Drupal 7 was scheduled for 2008 November and then 2008 December previously, work is still ongoing to complete the overhaul of help text and menu items in some places. The new target date for text / UI changes is January 15, 2010. The first Drupal 7 alpha release is planned for that day, from when it should be available on localize.drupal.org for translation. Small text changes will still be allowed if related to critical bugfixes, but the plan as communicated by Angie is that otherwise we can consider the text in Drupal 7 frozen on that date.

[...] the plan is to treat Drupal 7 as a stable release from the first alpha, so that means no string fixes that don't fix bugs, same as Drupal 5 & 6.

Read more in her post titled Drupal 7.0 Alpha 1: Coming soon to a downloads page near you!

read more

Det har nå blitt mulig til å gi folk tillatelse til bare å godkjenne andres forslag, ikke sine egne. (Mer informasjon under «News».) Hvordan skal vi bruke dette for bokmål og nynorsk?

Det har nå blitt mulig til å gi folk tillatelse til bare å godkjenne andres forslag, ikke sine egne. (Mer informasjon under «News».) Hvordan skal vi bruke dette for bokmål og nynorsk?

Thanks to work done by Daniel Wehner, Konstantin Kaefer, Daniel F. Kudwien and myself, today I've deployed improvements to permission control in translation groups. Previously we had two levels of users: group administrators and group members. Group members could suggest, import and export and administrators could approve suggestions (and manage group members). To be able to approve suggestions, one needed to hand out group administration permissions to people (which allowed them greater control over the group, not just the approval process). It was also brought up several times, that allowing administrators to approve their own suggestions (or directly submit translations) might not be desired in some groups. We had a possibility to set groups to all open (where everybody is a moderator as well) or to use this controlled model.

Starting from today, we have more granular permissions available and they are handed out on the group level thanks to our new use of the 4.x branch of Organic Groups User Roles module. Permissions related to translations are not anymore related to group administration status; these are now two distinct concepts. The overly generic open and controlled group permission models which were previously available are now obsoleted by this more granular system. Let's see the changes detailed for different types of users.

read more

Noen ganger har du kanskje tid til å bidra, men ikke ork og overskudd til å tenke altfor dype tanker om gode formuleringer. Da kan det være greit å ha noen enkle rutineoppgaver å ty til. Her er noen tips. Dette er en wikiside, fyll gjerne ut med flere:

• «innstillinger» skrives med to n-er, men er ofte feilstava med bare en: http://localize.drupal.org/translate/languages/nb/edit?project=&status=2...

Velkommen til oversetting av Drupal til norsk nynorsk. Alle er velkomne til å bidra. Før du begynner å oversette må du lese:

• Retningslinjer for Drupal-oversetting
• Alle innlegg på hovedsida for nynorsk (her legger vi viktige kunngjøringer)

Det er en stor fordel om du også ser gjennom:

• Språklege retningslinjer for oversetting av fri programvare
• Drupal-ordlista