X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/7bcee7b394f4e64700ed499f6c65e02fcc053e6e..3960a1f7c057b9521d181ed19ff80b4446b78347:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index 7741e00372..a4b0c0356f 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,89 @@ http://people.skolelinux.org/pere/blog/ + + Språkkoder for POSIX locale i Norge + http://people.skolelinux.org/pere/blog/Spr_kkoder_for_POSIX_locale_i_Norge.html + http://people.skolelinux.org/pere/blog/Spr_kkoder_for_POSIX_locale_i_Norge.html + Fri, 11 Apr 2014 21:30:00 +0200 + <p>For 12 år siden, skrev jeg et lite notat om +<a href="http://i18n.skolelinux.no/localekoder.txt">bruk av språkkoder +i Norge</a>. Jeg ble nettopp minnet på dette da jeg fikk spørsmål om +notatet fortsatt var aktuelt, og tenkte det var greit å repetere hva +som fortsatt gjelder. Det jeg skrev da er fortsatt like aktuelt.</p> + +<p>Når en velger språk i programmer på unix, så velger en blant mange +språkkode. For språk i Norge anbefales følgende språkkoder (anbefalt +locale i parantes):</p> + +<p><dl> +<dt>nb (nb_NO)</dt><dd>Bokmål i Norge</dd> +<dt>nn (nn_NO)</dt><dd>Nynorsk i Norge</dd> +<dt>se (se_NO)</dt><dd>Nordsamisk i Norge</dd> +</dl></p> + +<p>Alle programmer som bruker andre koder bør endres.</p> + +<p>Språkkoden bør brukes når .po-filer navngis og installeres. Dette +er ikke det samme som locale-koden. For Norsk Bokmål, så bør filene +være navngitt nb.po, mens locale (LANG) bør være nb_NO.</p> + +<p>Hvis vi ikke får standardisert de kodene i alle programmene med +norske oversettelser, så er det umulig å gi LANG-variablen ett innhold +som fungerer for alle programmer.</p> + +<p>Språkkodene er de offisielle kodene fra ISO 639, og bruken av dem i +forbindelse med POSIX localer er standardisert i RFC 3066 og ISO +15897. Denne anbefalingen er i tråd med de angitte standardene.</p> + +<p>Følgende koder er eller har vært i bruk som locale-verdier for +"norske" språk. Disse bør unngås, og erstattes når de oppdages:</p> + +<p><table> +<tr><td>norwegian</td><td>-> nb_NO</td></tr> +<tr><td>bokmål </td><td>-> nb_NO</td></tr> +<tr><td>bokmal </td><td>-> nb_NO</td></tr> +<tr><td>nynorsk </td><td>-> nn_NO</td></tr> +<tr><td>no </td><td>-> nb_NO</td></tr> +<tr><td>no_NO </td><td>-> nb_NO</td></tr> +<tr><td>no_NY </td><td>-> nn_NO</td></tr> +<tr><td>sme_NO </td><td>-> se_NO</td></tr> +</table></p> + +<p>Merk at når det gjelder de samiske språkene, at se_NO i praksis +henviser til nordsamisk i Norge, mens f.eks. smj_NO henviser til +lulesamisk. Dette notatet er dog ikke ment å gi råd rundt samiske +språkkoder, der gjør +<a href="http://www.divvun.no/">Divvun-prosjektet</a> en bedre +jobb.</p> + +<p><strong>Referanser:</strong></p> + +<ul> + + <li><a href="http://www.rfc-base.org/rfc-3066.html">RFC 3066 - Tags + for the Identification of Languages</a> (Erstatter RFC 1766)</li> + + <li><a href="http://www.loc.gov/standards/iso639-2/langcodes.html">ISO + 639</a> - Codes for the Representation of Names of Languages</li> + + <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n897-14652w25.pdf">ISO + DTR 14652</a> - locale-standard Specification method for cultural + conventions</li> + + <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n610.pdf">ISO + 15897: Registration procedures for cultural elements (cultural + registry)</a>, + <a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n849-15897wd6.pdf">(nytt + draft)</a></li> + + <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/">ISO/IEC + JTC1/SC22/WG20</a> - Gruppen for i18n-standardisering i ISO</li> + +<ul> + + + S3QL, a locally mounted cloud file system - nice free software http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html @@ -809,94 +892,5 @@ mailing list</a> if you want to help make this vision come true.</p> - - How to add extra storage servers in Debian Edu / Skolelinux - http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html - http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html - Wed, 12 Mar 2014 12:50:00 +0100 - <p>On larger sites, it is useful to use a dedicated storage server for -storing user home directories and data. The design for handling this -in <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>, is -to update the automount rules in LDAP and let the automount daemon on -the clients take care of the rest. I was reminded about the need to -document this better when one of the customers of -<a href="http://www.slxdrift.no/">Skolelinux Drift AS</a>, where I am -on the board of directors, asked about how to do this. The steps to -get this working are the following:</p> - -<p><ol> - -<li>Add new storage server in DNS. I use nas-server.intern as the -example host here.</li> - -<li>Add automoun LDAP information about this server in LDAP, to allow -all clients to automatically mount it on reqeust.</li> - -<li>Add the relevant entries in tjener.intern:/etc/fstab, because -tjener.intern do not use automount to avoid mounting loops.</li> - -</ol></p> - -<p>DNS entries are added in GOsa², and not described here. Follow the -<a href="https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions -in the manual</a> (Machine Management with GOsa² in section Getting -started).</p> - -<p>Ensure that the NFS export points on the server are exported to the -relevant subnets or machines:</p> - -<p><blockquote><pre> -root@tjener:~# showmount -e nas-server -Export list for nas-server: -/storage 10.0.0.0/8 -root@tjener:~# -</pre></blockquote></p> - -<p>Here everything on the backbone network is granted access to the -/storage export. With NFSv3 it is slightly better to limit it to -netgroup membership or single IP addresses to have some limits on the -NFS access.</p> - -<p>The next step is to update LDAP. This can not be done using GOsa², -because it lack a module for automount. Instead, use ldapvi and add -the required LDAP objects using an editor.</p> - -<p><blockquote><pre> -ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no -</pre></blockquote></p> - -<p>When the editor show up, add the following LDAP objects at the -bottom of the document. The "/&" part in the last LDAP object is a -wild card matching everything the nas-server exports, removing the -need to list individual mount points in LDAP.</p> - -<p><blockquote><pre> -add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no -objectClass: automount -cn: nas-server -automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no - -add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no -objectClass: top -objectClass: automountMap -ou: auto.nas-server - -add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no -objectClass: automount -cn: / -automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/& -</pre></blockquote></p> - -<p>The last step to remember is to mount the relevant mount points in -tjener.intern by adding them to /etc/fstab, creating the mount -directories using mkdir and running "mount -a" to mount them.</p> - -<p>When this is done, your users should be able to access the files on -the storage server directly by just visiting the -/tjener/nas-server/storage/ directory using any application on any -workstation, LTSP client or LTSP server.</p> - - -