Today I completed the translations of the manual. Jeff's going to put it up online by the end of the day today. We need to have some people to look over the translations and verify that they are correct. My friend, Sudha, who's going to be volunteering could take the first look at it. After that we could get some experts from OLE Nepal to take a look at it too.
Now, I'm waiting to hear from Abhishek about what to do next.
Thursday, June 16, 2011
Wednesday, June 15, 2011
Errors
Most of the errors/warnings I have been getting till now are to do with underlining and the toctree, which were fixed quite easily. However, today I got this weird warning
" WARNING: duplicate label search, other instance in /home/asharma/st-book-nep/source/search.rst "
This shows an error in the "search.rst" file which does not exist anywhere.
" WARNING: duplicate label search, other instance in /home/asharma/st-book-nep/source/search.rst "
This shows an error in the "search.rst" file which does not exist anywhere.
Monday, June 13, 2011
Bits and pieces
It's been a while since I blogged about what I'm doing. Mainly it's translating the manual. I have the translated version so it's not that hard but it takes some time to crop the pictures and make sure they fit in the page without looking too odd.
The other thing I have to do is to 'push' my translations into bzr. It's not that hard, but it took me some time to remember the commands.
to get to the school tool directory.
cd st-book-nep/
then make clean // cleans the build directory
and make html // generates html
there were some problems with the font and underlining. The font somehow got jumbled and did not show clearly in the terminal. And even though the underline looked fine in gedit, I kept getting errors that said the underline was too short.
So, we just made the underline much longer and that seemed to work.
Another error I got was in the toctree. I have to make sure that I add/remove the contents of the toctree as I build.
The other thing I have to do is to 'push' my translations into bzr. It's not that hard, but it took me some time to remember the commands.
to get to the school tool directory.
cd st-book-nep/
then make clean // cleans the build directory
and make html // generates html
there were some problems with the font and underlining. The font somehow got jumbled and did not show clearly in the terminal. And even though the underline looked fine in gedit, I kept getting errors that said the underline was too short.
So, we just made the underline much longer and that seemed to work.
Another error I got was in the toctree. I have to make sure that I add/remove the contents of the toctree as I build.
Friday, June 3, 2011
Getting the .po file to sphinx
We have the .po file ready. I sent it to Abhishek and he returned it after getting the experts at OLE Nepal to verify and complete the translations.
Now..getting it to sphinx
Matt started a discussion at sphinx-dev about our process of creating a Nepali translation of SchoolTool. I commented on it and added a link to the .po file that was saved in the public folder of my dropbox.
With that done, I'm now back to translating the SchoolTool Book. It's easier now since I am able to copy and paste from the manual. However, I have to be careful with keeping the format correct with Restructured text.
Also, there are some irregularities with the actual SchoolTool and the manual. They are not too many of them. Just a couple, and I'm debating whether to go along with the manual or to translate them. I have asked Abhishek what he wants..let's see.
Now..getting it to sphinx
Matt started a discussion at sphinx-dev about our process of creating a Nepali translation of SchoolTool. I commented on it and added a link to the .po file that was saved in the public folder of my dropbox.
With that done, I'm now back to translating the SchoolTool Book. It's easier now since I am able to copy and paste from the manual. However, I have to be careful with keeping the format correct with Restructured text.
Also, there are some irregularities with the actual SchoolTool and the manual. They are not too many of them. Just a couple, and I'm debating whether to go along with the manual or to translate them. I have asked Abhishek what he wants..let's see.
Wednesday, June 1, 2011
Wednesday June 1 - 11:30 am
We downloaded Madan font, but that still doesn't allow me to copy the text. So, I'm asking Abhiskek to send me the document in a different format that will allow me to copy and paste.
Wednesday, June 1
So, till now we have the .PO file mostly completed. I got some more translations done yesterday with the help of my dad. I'm still waiting to hear from Abhishek Singh from OLE Nepal. There are some words, which are too technical to be translated, like parameters. We might either have to transliterate them, or leave them in English. Whatever Abhishek says.
Continuing with the translations of the other documents, I'm going to start with the teacher manual, with that done, more people will be able to use it. The other documents like the release notes are not essential at the moment. OLE Nepal has done most of the translations already, but they are not done in Sphinx. We have them in form of google docs. I have the translated documents and as soon as we are able to download the true font that the document is written in, I should be able to copy and paste the translations. This will save me a lot of time.
So next, download Madan font
Continuing with the translations of the other documents, I'm going to start with the teacher manual, with that done, more people will be able to use it. The other documents like the release notes are not essential at the moment. OLE Nepal has done most of the translations already, but they are not done in Sphinx. We have them in form of google docs. I have the translated documents and as soon as we are able to download the true font that the document is written in, I should be able to copy and paste the translations. This will save me a lot of time.
So next, download Madan font
Monday, May 30, 2011
Friday, May 27
I started on my translations yesterday. With a lot of help from Matt and Jeff, I got this done.
I didn't really get to translating the sidebars, that seemed like it would take a lot of time, and I continued translating the other parts while Matt worked on figuring that out.
Later we saw that translating the whole document would take a lot of time, and I wouldn't be able to complete it during my Senior Experience. So, we decided to get the .PO file translated and send it to Sphinx.
Matt got that ready today, and I translated most of it today. There were a lot of technical words that when translated into Nepali would be more confusing for the users to understand. Abhishek Singh, our point of contact in OLE Nepal, said it would be no point in us translating if people found it more difficult to understand what was being said. So, I translated the ones that I thought were common words that Nepali people would be able to understand and other technical words, like JavaScript, I either transliterated them or left them in English.
I emailed the .PO file and the list of transliterated words to Abhishek, Jeff and Matt. We'll send the file to Sphinx as soon as we make the necessary changes after weget feedback from OLE Nepal.
I didn't really get to translating the sidebars, that seemed like it would take a lot of time, and I continued translating the other parts while Matt worked on figuring that out.
Later we saw that translating the whole document would take a lot of time, and I wouldn't be able to complete it during my Senior Experience. So, we decided to get the .PO file translated and send it to Sphinx.
Matt got that ready today, and I translated most of it today. There were a lot of technical words that when translated into Nepali would be more confusing for the users to understand. Abhishek Singh, our point of contact in OLE Nepal, said it would be no point in us translating if people found it more difficult to understand what was being said. So, I translated the ones that I thought were common words that Nepali people would be able to understand and other technical words, like JavaScript, I either transliterated them or left them in English.
I emailed the .PO file and the list of transliterated words to Abhishek, Jeff and Matt. We'll send the file to Sphinx as soon as we make the necessary changes after weget feedback from OLE Nepal.
Wednesday, May 25, 2011
Some technical stuff
Bazaar - is a revision control system that allows you to make revisions and lets you keep track of the changes you make to a project. So, if you decide that the revisions you made today weren't good and you want to revert to the one you had yesterday, bzr lets you do that.
Also, if there are multiple people working on the same project, each person can create their own branch to make changes, and later all the different revisions can be merged.
This is really useful for projects whose contents keep changing and projects that have a lot of people working on them. Changes can continually be made, and if they don't turn out as expected, there is already a back up of all the other revisions that were made earlier.
Launchpad - is a web application that allows users to develop and maintain software. It also allows for translations in various languages. The source code hosting for launchpad is done using the Bazaar version control system.
Sphinx - is a tool that allows for easy documentation. Most python projects use Sphinx for their documentation as it has great output formats, hierarchical structure, code handling, extensions and automatic indices that make documentation easy.
Hi! I started my Senior Experience yesterday. For the next 3-4 weeks I will be collaborating with School Tool and OLE Nepal. I will be working in the Arlington Career Center under the supervision of Mr. Jeff Elkner.
School Tool is a student information system which is used all over the world. It allows you to enter various information about the student like demographics, attendance and grades. It is now becoming widely used, and is translated/ being translated into several languages.
One of those being- Nepali. School Tool has not yet been fully translated into Nepali.
OLPC (One Laptop Per Child) is a global project that aims to provide every child a low-cost and a low-power laptop, which they will use for educational purposes.
Ole Nepal, (Open Learning Exchange Nepal) is a non-profit organisation that has been working on improving the standards of learning in all Nepali public schools. They are trying to integrate technology into Nepali education.
How do they tie in?
Ole Nepal has been trying to use School Tool as their student information system at their deployment sites in Nepal. The major task now is to make sure the information is easily understood by the Nepali community- most of whom are non- English speakers.
That's the big picture- improving the quality of education and increasing the access to educational resources by using technology- the laptops
Challenge- making sure that everybody, most of whom who have had no experience with technology and do not speak English, can make use of these technologies.
Introduction
School Tool is a student information system which is used all over the world. It allows you to enter various information about the student like demographics, attendance and grades. It is now becoming widely used, and is translated/ being translated into several languages.
One of those being- Nepali. School Tool has not yet been fully translated into Nepali.
OLPC (One Laptop Per Child) is a global project that aims to provide every child a low-cost and a low-power laptop, which they will use for educational purposes.
Ole Nepal, (Open Learning Exchange Nepal) is a non-profit organisation that has been working on improving the standards of learning in all Nepali public schools. They are trying to integrate technology into Nepali education.
How do they tie in?
Ole Nepal has been trying to use School Tool as their student information system at their deployment sites in Nepal. The major task now is to make sure the information is easily understood by the Nepali community- most of whom are non- English speakers.
That's the big picture- improving the quality of education and increasing the access to educational resources by using technology- the laptops
Challenge- making sure that everybody, most of whom who have had no experience with technology and do not speak English, can make use of these technologies.
Subscribe to:
Posts (Atom)