Jump to: navigation, search

OLPC & User boxes

Nuvola apps edu miscellaneous.png This user is a teacher.

Template:XO source Template:XO source Template:XO source

es Castellano es la lengua materna de este usuario
en-4 This user speaks English at a near-native level.
fr-2 Cet utilisateur peut contribuer avec un niveau intermédiaire en français.
pt Este usuário é um falante nativo do português.
See also
Talk:Wiki Page Restructuring Common Room
Template talk:XO box

The following text generates the boxes on the right... yeah!

{{User teacher}}
{{XO source}}
{{XO source|1=[]}}
{{XO source|[]|RPM}}
{{olpcboxbreak|toptext=[[:Category:User languages|Languages]]}}
{{User es}}
{{User en-4}}
{{User fr-2}}
<div class="NavFrame" style="padding:0;border-style:none;">
<div class="NavFrame" style="border-style:none;padding:0;">
<div class="NavHead" style="background:#EDF1F1;text-align:left;text-style:normal">

Hide/Show doesn't work<div class="NavContent" style="display:none;">

{{User ru}}
{{User pt}}

The basic structure is:

...boxes...        # You may also add breaks using {{olpcboxbreak|toptext=Title}}

Geo Data

My intention was to have a page with some 'template like paramater data' (ie: User:Xavi/Test/GeoData) that could be fed (initially) as the parameters of a template (ie: User:Xavi/Templates/GeoXOGoogle). But even though the basic generation of the 'resulting template generation' (see #7 below) it doesn't actually get evaluated—#8 below is a manual copy-paste of the template-stitching.

Source Wiki Text Processed / Results
1 {{:User:Xavi/Test/GeoData}} User:Xavi/Test/GeoData
2 {{User:Xavi/Test/GeoData}} User:Xavi/Test/GeoData
3 {{:User:Xavi/Templates/GeoXOGoogle {{:User:Xavi/Test/GeoData}}}} {{:User:Xavi/Templates/GeoXOGoogle User:Xavi/Test/GeoData}}
4 {{User:Xavi/Templates/GeoXOGoogle {{:User:Xavi/Test/GeoData}}}} {{User:Xavi/Templates/GeoXOGoogle User:Xavi/Test/GeoData}}
5 {{User:Xavi/Templates/GeoXOGoogle {{User:Xavi/Test/GeoData}}}} {{User:Xavi/Templates/GeoXOGoogle User:Xavi/Test/GeoData}}
6 {{User:Xavi/Templates/GeoXOGoogle {{:User:Xavi/Test/GeoData}}}} {{User:Xavi/Templates/GeoXOGoogle User:Xavi/Test/GeoData}}
7 {{:User:Xavi/Templates/GeoXOGoogle{{:User:Xavi/Test/GeoData}}}} {{:User:Xavi/Templates/GeoXOGoogleUser:Xavi/Test/GeoData}}
8 {{:User:Xavi/Templates/GeoXOGoogle | lat = -34.291 | long = -56.389 | zoom = 10 | type = k | display = Cardal }} Cardal
Funny. Now that I remember, the Template:Babel-X (inspired in Wikipedia's and that didn't work until we enabled the ParserFunctions iirc) does something similar to this...

June 2007

After the update of the wiki a piece in the Translating puzzle has been broken: the use of <div id="anchor"/>. A possible solution (provided by Nikerabbit in #mediawiki @ was to switch to <div id="anchor"></div> — which I'm testing.

New POT files

The results were positive and the has been split (thus also the translation too). Hopefully it will help translators in their jobs... time will tell :) --Xavi 00:18, 2 April 2007 (EDT)

The actual (old) test

Testing an idea for the new round of Category:PO files... which happen to have grown quite a bit since the last time, making them not only a bigger effort but also a more complex one when trying to let several people tackle it at the same time due to possible conflicts.

 lines   size    POT file
   367  13.7 kb  POT
   320  15.5 kb  Es PO
  1144  50.0 kb  [[User:Felice/website_copy|New POT]]
  1162  56.2 kb  [[User:Felice/website copy/lang-es AR|New Es PO]]

So the idea that I'm playing with is to use subpages for each 'section' of the POT. This will obviously make it more complicated to set up a translation (there will be n new pages for each translation) but at the same time, translators can focus on separate sub-sections and have more manageable chunks to work on.

POT test results

Inclusion seems to work, but...

  • Included sub-pages have the <pre></pre> tags in them (mainly for aesthetics while editing that sub-page - haven't tried without them and see what they look like)
  • Comments (lines starting with # risk being converted into numbered-bullets by the wiki. This could be a major mangling risk.
    • The <pre></pre> are very delicate, a missing CR could create quite a bit of mess... so they should be in a line by themselves (is this obvious?)
    • If all sections are handled by sub-pages, most of the <pre></pre> are eliminated, leaving behind a compact set of template inclusions.

Possible extensions could be:

  • make a template that includes the original (english) sub-page by default, else the specified translation
    • this would allow to have the complete POT file for any language by just creating the central page that invokes the template with all the default (non-translated / original) sub-pages.
  • the template should leave behind a link to edit (or create) the sub-page holding the translated version...

POT proving grounds

But let's first the base idea to see if it works... then we'll see if it's applicable or useful...

... tests worked pretty good, no need to keep the ''sample text''...