Closed Bug 668771 (fx-l10n-csb) Opened 8 years ago Closed 8 years ago

[csb] Firefox release tracker Kashubian

Categories

(Mozilla Localizations :: csb / Kashubian, defect)

defect
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Pike, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 3 obsolete files)

This is a tracker bug for releasing Firefox csb.

This bug is not that detailed, but as we get particular work items, they should
block this bug for tracking and discoverability.

The "bugs" here are tracking indiviual items of work. Some of those will depend on the localization team to be driven to completion, others are for infrastructure that will be handled by staff. I'll indicate which in the individual bugs.
Depends on: 627680
We'll want a team page on wikimo, too. Not creating a tracker for that, and Milos is gonna whack the way we do that hopefully soon, so noting that as a TODO: https://wiki.mozilla.org/L10n:Teams:csb
Depends on: 668772
Depends on: 668773
Depends on: 668775
Depends on: 668776
Depends on: 668777
Depends on: 668778
Depends on: 668779
Depends on: 668780
Depends on: 668781
Depends on: 668782
Depends on: 668783
Axel, Milos,

Let me know what I need to do next. I have contacted my team members for suggestions on bugs 668775 and 68778 so these should be resolved soon. Since most users reside in Poland, defaulting to Polish preferences makes sense (in most cases). 

I also looked at bugs: 668773, 668776, 668777, 668779, 668780, 668781, 668782, 668783 and tried to address them (as appropriate).

Thank you for your support!

Jurk
Hey Jurk, we're still waiting for some bugs to be fixed. Once that's done, we'll make notes in the bugs and let you know. Thanks for the effort!
Sorry for the lag, I've now landed csb in mercurial, will get builds next.

I did a few changes:

- converted line endings to unix. please make sure to keep them as such?
- removed some obsolete files

A few things I found during review:

- the plural form may want to be https://developer.mozilla.org/en/Localization_and_Plurals#Plural_rule_.239_%283_forms%29 ?
- do you want to add "pl" as language to accept-lang?
(both in toolkit/chrome/global/intl.properties)
- check the lengths in security/manager/chrome/pipnss/pipnss.properties, those constraints are brutal. If you can't localize in that length, use abbreviations, or transcribe into latin to get around the bytes in utf-8 or what not.
Attached file pipnss.properties (obsolete) —
Axel,

Issue 1: - the plural form may want to be https://developer.mozilla.org/en/Localization_and_Plurals#Plural_rule_.239_%283_forms%29 ?


ANS: Please, use the polish forms (PL)

Issue 2: - do you want to add "pl" as language to accept-lang?
(both in toolkit/chrome/global/intl.properties)

ANS: Assuming we’re talking about defaulting to Polish if Kashubian is unavailable, YES, please use “pl”

Issue 3: - check the lengths in security/manager/chrome/pipnss/pipnss.properties, those constraints are brutal. If you can't localize in that length, use abbreviations, or transcribe into latin to get around the bytes in utf-8 or what not.

ANS: attached is the pipnss.properties file checked for size problems. 

(Thanks to Michal Ostrowski)

PS Bug 668772 was resolved but I still cannot commit the translations (user name: choszcz)
We'll need you to do the actual work here, a Firefox localization is not about "mozilla does what you ask us for". So, to get stuff landed on hg.mozilla.org, you an attach patches to bugs and ask for someone to step in, but you should probably file an account request, following the description and the links in https://wiki.mozilla.org/L10n:Becoming_an_Official_Localization#hg_write_access. The username for hg will be tied to an email address, btw, so likely jurk@linuxcsb.org.
Axel,

This goes without saying: once we get access to the mercurial, we'll get on it :) So far, we only had access to Narro.

Jurk
Milos,

Thank you for the explanation. We were able to clone the repository. Currently working bugs:

668773
668775
668776
668777
668778
668779
674192
Attached file Comment4_Patches (obsolete) —
Axel,

I'm attaching 2 patched (zipped) to address the issues identified in Comment 4 of this bug. Please, review.
Attachment #549118 - Attachment is obsolete: true
Component: Other → csb / Kashubian
QA Contact: csb
Comment on attachment 553535 [details]
Comment4_Patches

Hi Jurk, I'm happy to review the changes, but please attach a single patch for the files instead of a zip. Then I can just do this in the web interface.
Attachment #553535 - Attachment is patch: false
Attachment #553535 - Attachment mime type: text/plain → application/zip
Attachment #553535 - Flags: review-
Axel,

I will resubmit after the .orig is removed from them. 

Thx
Attached patch Comment 4 Patches (obsolete) — Splinter Review
Milos,

Attached is a patch that addresses Axel's Comment 4 of this bug. Please, review.
Attachment #553535 - Attachment is obsolete: true
Attachment #555092 - Flags: review?(milos)
Jurk,

I'm not gonna give you r- on this yet, before I check you only want `pl` value in accept-lang header. What Axel meant by adding `pl`, is probably:

intl.accept_languages=csb, csb-PL, pl, en-US, en

Other than that, patch looks fine. Would you please create a new patch and flag me for a review.

Thanks!
Status: NEW → ASSIGNED
Milos,

Here is a correct version of the patch.
Attachment #555092 - Attachment is obsolete: true
Attachment #555465 - Flags: review?(milos)
Attachment #555092 - Flags: review?(milos)
Comment on attachment 555465 [details] [diff] [review]
Comment 4 Patches

Review of attachment 555465 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good to me. Axel. mind taking another look?
Attachment #555465 - Flags: review?(milos)
Attachment #555465 - Flags: review?(l10n)
Attachment #555465 - Flags: review+
Comment on attachment 555465 [details] [diff] [review]
Comment 4 Patches

Review of attachment 555465 [details] [diff] [review]:
-----------------------------------------------------------------

Yep, looks good to me, too.
Attachment #555465 - Flags: review?(l10n) → review+
Comment 4 patch was pushed to the repository
Axel,

This patch is identical to what you had already reviewed (comment 4). Narro had overwritten this patch. The other patches were left untouched. Please, reviewm
Attachment #558516 - Flags: review?(l10n)
Attachment #558516 - Flags: review?(l10n) → review+
Just a note:

Jurk finished all the webparts dependencies even before we filed them, so all the web pages that should be in webparts bug and therefore blocking this one are finished.

Awesome effort, Jurk.
Depends on: 691764
Milos,

Per Axel's Comment 1:

Someone has already localized L10n:Teams:csb in 2006. I'm able to login there with my LDAP account but cannot update the existing data (i.e. the spellings etc.) Can you please elevate my privileges for that site so I can do some house cleaning there?
Jurk,

You can't edit pages on wiki.mozilla.org? That's weird. Can you please give me your username so I can see what's actually happening?

Thanks!
Follow-up: I saw that you actually created this page, so you should be able to edit it, as well. Just open the page, and then click "Edit" link from top toolbar. That should give you an edit box where you can write more about your community.
Milos,

Yes, I'm able to add articles (I added something yesterday) but cannot edit menus, etc (I don't have admin rights). According to some of the postings, this site was created in 2006.
Are we talking about https://wiki.mozilla.org/L10n:Teams:csb or anything else? https://wiki.mozilla.org/index.php?title=L10n:Teams:csb&action=history shows only you as contributor.
That's correct. When I logged into https://wiki.mozilla.org/L10n:Teams:csb the menus were already translated into Kashubian - not sure who's done it. It'd be great to be able to update the menus with the contemporary spellings, but this isn't top priority though.
Oh, you're probably talking about the wiki itself. Those strings come from mediawiki upstream, and you're probably see those because you've set your language to csb on https://wiki.mozilla.org/index.php?title=Special:Preferences. That has nothing to do with the page content.
No longer depends on: 668778
FYI, csb should be part of the upcoming Beta release for Firefox 8.

It should not be part of the actual release, though, that will happen with the next cycle the earliest.
Hey Jurk,

I have filed a bug to add Kashubian beta builds to https://www.mozilla.org/en-US/firefox/all-beta.html and as soon as that's resolved, you should be able to see Kashubian localized builds on that page.

Now, Pascal pushed your webparts(www.mozilla.org pages) to production, so you should use those when promoting your new localized product - www.mozilla.org/csb.

Great to have Firefox in Kashubian!
Axel, 

Per Comment 27, will this release include support for Kashubian?
Firstly, congratulations team!

You have worked and managed to get all the dependencies for this bug fixed, which means that productization for Kashubian Firefox is all done. Please take a minute or two and read the next steps to follow.

== Aurora ==

Every 6 weeks, we will update aurora repositories with new strings that will require some additional time spent on it. As you probably already know, we advise all localizers to use Aurora channel for all translations, so that we can merge them with Beta channel when needed without any regressions. So, please use Aurora as your primary working repository, and in case you're landing a fix to Beta channel, please port it back to Aurora too. Once the Aurora builds are available, please use them as much as you can for the purpose of testing your own translations and making sure everything is as it should be.

== Bugs ==

Please check your dashboards every now and then to see if there are some bugs filed against Firefox in Kashubian. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n-stage-sj.mozilla.org/teams/bs . As the website evolves, you'll start using that as your primary source of info related to localization.

One other important thing to have in mind is webdashboard. We use webdashboard to show contributors bugs related to web localization for their locale. This is really important as we use our websites to promote localized Firefox builds.

== Staying connected ==

You should also follow the Mozilla l10n newsgroup, http://www.mozilla.org/community/forums/#dev-l10n, available as mailing list, newsgroup or Google group. The traffic isn't too high frequency. 

You'll find all announcements at http://www.mozilla.org/community/forums/#dev-l10n-announce . Those are vital to read, as they include things that the l10n-drivers want you to know and attend to. 

There's a third group, http://www.mozilla.org/community/forums/#dev-l10n-web, where we discuss web localization issues. That's a separate group as quite a few localization teams have dedicated volunteers for that.

Another important thing is staying in touch with community and make yourself available for anyone who wants to contribute. So, if possible, get in touch with community on community forums, get feedback and possibly more volunteers.

Enjoy and congratulations!
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
> You can check the status of your
> latest builds and some team info on l10n dashboard teams page at
> https://l10n-stage-sj.mozilla.org/teams/bs . 

That's for Bosnian (bs). For Kashubian it's actually https://l10n-stage-sj.mozilla.org/teams/csb 

Congrats from the Polish team. :)
Marek, thank you. Maybe we should mention it on the Polish site also? 

It's been quite a ride with ups and downs, but here it is! Thank you all for your great support and encouragement!

Jurk
Hubert, I think it would be nice to mention the Kashubian l10n on a more user-focused site like mozillapl.org...
(In reply to Marek Stępień [:marcoos] from comment #34)
> Hubert, I think it would be nice to mention the Kashubian l10n on a more
> user-focused site like mozillapl.org...

http://mozillapl.org/forum/viewtopic.php?f=15&t=43146
You need to log in before you can comment on or make changes to this bug.