Showing posts with label Documentation. Show all posts
Showing posts with label Documentation. Show all posts

Sunday, April 03, 2011

#StatusNet has all its core messages documented

#Translatewiki.net offers localisers an environment where the technical vagaries of updating the code is not their worry. This is a major attraction. Another important tool for localisers is documentation for messages.

When messages are to be translated, it is often not immediately clear what a message is to achieve. The order of variables in a messages may have to change depending on the language. This is where documentation makes a big difference.

For some applications like Status.net developers document the messages and this seriously affects not only the flow of localisations but also their quality. It is an investment well worth it because great localisations make for a great experience.
Thanks,
     GerardM

Sunday, June 28, 2009

More thoughts on book sprints

This is my second day that I have been working on a "book sprint". The one thing that I have learned about the process is, that the success is defined by the quality of the people involved. When you combine people like Adam Hyde and Allen Gunn in the mix, there will be something usable at the end.

Having worked for two days with the software used by FLOSS manuals, I am sure that a book sprint can also be done using MediaWiki. The key thing to consider is not so much can you do this, but what is the added value. Writing FLOSS manuals is what FLOSS manuals does and a community has formed around it. Replicating this effort only makes sense when it grows the creation beyond the autonomous growth of FLOSS manuals.

However, when an application is found for writing outside this domain, there might be a point to experiment with MediaWiki.
Thanks,
      GerardM

Saturday, June 27, 2009

OTT09 book sprint

When you assemble people for a conference, you bring together all the people clued in on a subject. The Open Translation Tool '09 conference brought together many of the people who are involved in translation, localisation, content and technology.

Floss manuals has this brilliant notion of a "book sprint". In a book sprint a group of people write a book in a short period of time like up to a week. At the end of the week the resulting document is published and available either as a PDF or in a printed form.
Thanks,
      GerardM