Today I ran across a phone announcement in my RSS feed.
After a large paragraph of specifications come one of the smallest sentences possible in Japanese.
「Android は4.0。」, “Android is 4.0″.
Less than four years ago no android phones existed. Now any smartphone is an android unless specified otherwise. For every computer that has Ubuntu installed, 1.4 Android phones are sold every month.
I just picked up a Kobo Vox from Future Shop. The Vox is the first reasonably priced android tablet you can get in Canada. Americans have been able to get a Nook Colour for a while.
The build is solid and the matte padding on the back feels quite nice. The volume rocker is located lower than I expected it to be which is nice for holding the Vox horizontally as the rocker is away from your hand.
The backlight has some noticeable leakage on black screens.
The setup process rquires you to download a firmware update and create a kobo account.
In the marketing material I had read that Google’s android market would be available, this is not the case rather a getjar app is installed. Honestly I should have expected this since Google will not allow devices without GPS and other phone specific features to ship with the market.
Oddly enough there does not appear to be a way to associate the Vox with a Google account, something I have had to do even with cheap Chinese tablets. The Gmail app is really a link to the mobile version of gmail.
Update: I’ve played with the Vox for a few hours now. The lack of Google Market is very noticeable and annoying. I used this guide to install the Amazon Appstore which has more quality apps than the default getjar market. Open source apps are easier to get, often apks are available for download from the project’s website. By default the backlight is not set to auto, which it should be for the battery’s sake. I should mention again the build quality, the Vox is very nice to hold. The touch panel is very responsive.
Oh and angry birds works fine. Overall the Vox is a nice tablet.
Perhaps a bit verbose but the foomatic-db option’s human readable namespace refers to all the elements in our options that are meant for the end user. The foomatic-db data sets allow for multiple languages to be present in human readable elements. The issue is that only one xml in our repository uses this feature, the main proprietary Epson driver xml with its english and japanese comments.
Thus for all practical purposes foomatic-db is a mono lingual data set. This leaves downstream responsible for any translation.
Downstream may have an army of translators but they are going to have a hard time if the data set is inconsistent, ambiguous, and verbose. This is thus what I spent my remaining week of GSoC working on.
To do this I used Google Refine and a set of throw away scripts which created a csv with the xml filepath the human readable string.
With a global view of the namespace it became clear that it wasn’t as bad as I thought it would be. All Resolution options were consistently named, as were Page Size options, and others. Some things were simply misspelled or similar’arly spelled. Though in many cases I needed to do some digging to group things. In total I brought the total number of unique option choices from ~830 to ~740 with other uncounted improvements to readability. A brief and incomplete overview of the consolidation:
- Consolidated on Color spelling of Color
- Acronyms were expanded in some cases
- Standardized on ‘Economy Mode’
- Standardized on ‘Print Quality’
- Expanded ’600 DPI’ and like to ’600×600 DPI’
- Standardized on ‘Color Mode’
- If I noticed them I would remove redundant terms like ‘setting’*
It wasn’t a major overhaul but hopefully this will result in more complete and helpful translations for end users.
*The user is already being shown a setting dialog. Visually the presence of a toggle or checkbox communicates that something is a setting. Appending ‘setting’ to a setting is thus redundant.