Closed
Bug 711119
Opened 14 years ago
Closed 13 years ago
[lij] Enable Ligurian localization on SUMO
Categories
(support.mozilla.org :: Localization, task, P1)
support.mozilla.org
Localization
Tracking
(Not tracked)
VERIFIED
FIXED
2012-03-06
People
(Reporter: Pike, Assigned: rrosario)
References
Details
(Whiteboard: u=user c=general s=2012.5 p=1)
We need to enable the localization of SUMO in Ligurian [lij].
Alessio, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that. Italian would be the obvious choice, I guess, and they also have a pretty active community on SUMO.
And, Alessio, we'd need "Ligurian" in Ligurian again to set this up, please add that here, utf-8 encoded. Thanks.
Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.
-Yes can you redirect in Italian, is one of my native language... thanks
-The "Ligurian" language is "Lìgure" in ligurian, that is more correct but in Italy(and Liguria) is more popolar the name "Zenéize"...
So can you call it something like: "Lìgure(zenéize)" ?
(In fact we translate in the most used variant of Ligurian that is spoken in Genoa(Zêna in ligurian) area)
Maybe is better only "Lìgure"..
I've decided call ligurian in ligurian "Lìgure"
Sorry :)
Comment 3•14 years ago
|
||
Can we please redirect lij to it and close this one?
Thanks.
Comment 4•13 years ago
|
||
Ping?
Assignee | ||
Comment 5•13 years ago
|
||
(In reply to Milos Dinic [:Milos] from comment #3)
> Can we please redirect lij to it and close this one?
I am not sure what you mean? Do we just want to add this locale to SUMO?
Whiteboard: u=user c=general s=2012.5 p=1
Comment 6•13 years ago
|
||
Nope, we want to redirect all users from /lij/ to /it/.
Comment 7•13 years ago
|
||
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #5)
> (In reply to Milos Dinic [:Milos] from comment #3)
> > Can we please redirect lij to it and close this one?
>
> I am not sure what you mean? Do we just want to add this locale to SUMO?
Just add 'lij': 'it' to the NON_SUPPORTED_LOCALES dict[1].
[1] https://github.com/mozilla/kitsune/blob/master/settings.py#L88
Assignee | ||
Comment 8•13 years ago
|
||
Sorry I didnt read "it" as Italian but as .. well ... it. :-)
Comment 9•13 years ago
|
||
Ricky,
Any ETA on when can this be done?
Assignee | ||
Comment 10•13 years ago
|
||
(In reply to Milos Dinic [:Milos] from comment #9)
> Ricky,
>
> Any ETA on when can this be done?
It is targeted for our next sprint, which means it will land in 2-3 weeks.
Reporter | ||
Comment 11•13 years ago
|
||
4-5 weeks for a redirect? Really?
Assignee | ||
Comment 12•13 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #11)
> 4-5 weeks for a redirect? Really?
Sorry, we have 2 week sprints and this got targeted for the next one. We could swap this bug for another one (that is up to :Topal). Or if somebody sends a pull request I will be more than happy to r? and merge :-). It still would be 2 weeks unless it gets in before a branch shortly for next week.
Comment 13•13 years ago
|
||
Axel, I'll swap it, if you think it's important, but it seems like it would affect a small number of people, and the other items on our list affect a really large amount of people.
Updated•13 years ago
|
Priority: -- → P2
Comment 14•13 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #11)
> 4-5 weeks for a redirect? Really?
All that needs to happen is in comment 7, if you want to submit a patch or pull request. It's not a question of difficulty it's a question of best using the time of the few developers we have right now.
Assignee | ||
Updated•13 years ago
|
Priority: P2 → P1
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Comment 15•13 years ago
|
||
https://github.com/mozilla/kitsune/commit/34afd8122b30b57755766bf46d118128a31cff5b
QA: Any /lij/* URL should redirect to /it/*.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2012-03-06
You need to log in
before you can comment on or make changes to this bug.
Description
•