User:Xavi/Test

June 2005

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 @ irc.freenode.net) was to switch to <div id="anchor"></div> — which I'm testing.

New laptop.org POT files

The results were positive and the PO-laptop.org-en-US has been split (thus also the PO-laptop.org-es 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''...