summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2011-February/002922.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-February/002922.html')
-rw-r--r--zarb-ml/mageia-sysadm/2011-February/002922.html145
1 files changed, 145 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-February/002922.html b/zarb-ml/mageia-sysadm/2011-February/002922.html
new file mode 100644
index 000000000..f31f0de64
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2011-February/002922.html
@@ -0,0 +1,145 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] mediawiki
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20mediawiki&In-Reply-To=%3C201102251505.26840.bgmilne%40staff.telkomsa.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002776.html">
+ <LINK REL="Next" HREF="002923.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] mediawiki</H1>
+ <B>Buchan Milne</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20mediawiki&In-Reply-To=%3C201102251505.26840.bgmilne%40staff.telkomsa.net%3E"
+ TITLE="[Mageia-sysadm] mediawiki">bgmilne at staff.telkomsa.net
+ </A><BR>
+ <I>Fri Feb 25 14:05:25 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002776.html">[Mageia-sysadm] mediawiki
+</A></li>
+ <LI>Next message: <A HREF="002923.html">[Mageia-sysadm] mediawiki
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2922">[ date ]</a>
+ <a href="thread.html#2922">[ thread ]</a>
+ <a href="subject.html#2922">[ subject ]</a>
+ <a href="author.html#2922">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Thursday, 17 February 2011 21:22:39 Michael Scherer wrote:
+&gt;<i> Le jeudi 17 f&#233;vrier 2011 &#224; 20:42 +0200, Buchan Milne a &#233;crit :
+</I>&gt;<i> &gt; On Thursday, 17 February 2011 17:56:23 Michael Scherer wrote:
+</I>&gt;<i> &gt; &gt; Le jeudi 17 f&#233;vrier 2011 &#224; 17:32 +0200, Buchan Milne a &#233;crit :
+</I>&gt;<i> &gt; &gt; &gt; On Thursday, 17 February 2011 12:40:51 Buchan Milne wrote:
+</I>&gt;<i> &gt; &gt; &gt; 1 i-default
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I've added some debug logging (see patch below).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Firefox, to which I have added a number of languages, shows:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; [info] Languages: en-za,en-gb,en-us,en,af,nl,i-default, default: af,
+</I>&gt;<i> &gt; saving: en-za
+</I>
+I have added some rule-based changes to the language (e.g. fr-fr -&gt; fr), but
+allowing en-us,en-gb,pt-br,no-.*,xh-.*.
+
+The problem here is that, say we don't have or allow en-za, the user would
+want en-gb, but instead we currently heuristically give en.
+
+So, I think to solve this and prevent invalid values for preferredLanguage, it
+may be better to have language mapping entries in LDAP, e.g.:
+
+dn: supportedLanguage=en-gb,ou=Languages,cn=CatDap,ou=Settings,$suffix
+supportedLanguage: en-gb
+preferredLanguage: en-gb
+preferredLanguage: en-za
+preferredLanguage: en-ca
+
+or similar. Then, CatDap and slapo-constraint could use the same data.
+
+So, it may be time to start working on some LDAP schema ... so we will need to
+register an IANA Enterprise number at some stage.
+
+&gt;<i> &gt; (So, in this case, the interface is displayed in Afrikaans ... I guess I
+</I>&gt;<i> &gt; need to create at least 3 English translations - en, en_us, en_gb)
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Chromium with default language settings shows:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; [info] Languages: en-gb,en-us,en,i-default, default: en, saving: en-gb
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; So, I can imagine a case where it is the only language listed. In this
+</I>&gt;<i> &gt; case, I think we should either not set preferredLanguage, or set it to
+</I>&gt;<i> &gt; en.
+</I>&gt;<i>
+</I>&gt;<i> I would set it to en. Not setting a default one just push the decision
+</I>&gt;<i> of using default on every consumer of the information, and that doesn't
+</I>&gt;<i> sound good.
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; &gt; 1 es-pe
+</I>&gt;<i> &gt; &gt; &gt; 1 cs-cz
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Theses 3 one are likely wrong ( according to IANA registry )
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Do you have a URL handy?
+</I>&gt;<i>
+</I>&gt;<i> <A HREF="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</A>
+</I>&gt;<i>
+</I>&gt;<i> Fact is there is several registry of language ( like 6 iso standards +
+</I>&gt;<i> ietf one ), so people can easily have it wrong ( not to mention people
+</I>&gt;<i> who get it wrong with tld and country )
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; &gt; I guess I should filter these out, and replace with
+</I>&gt;<i> &gt; &gt; &gt; en,fr,es,ru,it,fi,et,es,tr ? I will fix the wrong ones in LDAP later.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; How can we enforce correct entry ? Should we maybe have a whitelist,
+</I>&gt;<i> &gt; &gt; and receive a monthly mail about wrong one ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; May be a good idea. Or, we could use slapo-constraint (with regex, or
+</I>&gt;<i> &gt; dynamic list in LDAP)
+</I>&gt;<i>
+</I>&gt;<i> We could feed the list from the one of tx
+</I>&gt;<i> ( <A HREF="http://www.transifex.net/languages/">http://www.transifex.net/languages/</A> but in a more exploitable, I
+</I>&gt;<i> assume this can be downloaded somewhere ).
+</I>&gt;<i>
+</I>&gt;<i> &gt; Maybe we should also compare to what localisation teams we have (or don't
+</I>&gt;<i> &gt; have), and indicate to users whose preferred languages isn't localised
+</I>&gt;<i> &gt; that they could contribute in that way.
+</I>
+Yes, maybe we can push the languages we have into LDAP, and for all languages
+not there, display a notice in CatDap that the interface is not in their
+language due to not having a localisation team?
+
+&gt;<i> Yup, nice idea. I was also about to think how we should manage i18n team
+</I>&gt;<i> in ldap, and if this is needed. This would requires to have the
+</I>&gt;<i> delegation feature working in catdap ( not sure of the status of this ).
+</I>
+Regards,
+Buchan
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002776.html">[Mageia-sysadm] mediawiki
+</A></li>
+ <LI>Next message: <A HREF="002923.html">[Mageia-sysadm] mediawiki
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2922">[ date ]</a>
+ <a href="thread.html#2922">[ thread ]</a>
+ <a href="subject.html#2922">[ subject ]</a>
+ <a href="author.html#2922">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
+mailing list</a><br>
+</body></html>