About WebTranslateIt.com

WebTranslateIt.com is a web-based translation tool to translate documents and software.

Learn more at WebTranslateIt.com.

Subscribe to our newsletter

Get our monthly newsletter about WebTranslateIt’s latest features.

Recent posts

More API improvements

Posted by Edouard on January 9, 2010

I just updated the API with a few improvements and a new endpoint.

Improvements

The locale endpoint, which allows you to fetch a list of locales accepted by your project is now capable of returning xml, json or yaml by simply appending the format you want at the end of the URL.

For example, if you want your list of locales in YAML, you would call /api/projects/04b254da22a6eb301b103f848e469ad494eea47d/locales.yaml and it would return something like so:

--- 
locales: 
- name: French, France
  code: fr_FR

New Endpoint: Project information

This new endpoint can be very useful to develop an advanced integration between Web Translate It and your application.

It returns 5 things:

  • the project name,
  • a list of locales accepted by the project,
  • the project source locale,
  • the language file ids and names.

The data is available in xml, json or yaml.

An example of the data structure in YAML would be:

--- 
project: 
  name: Web Translate It
  source_locale: 
    name: English, United Kingdom
    code: en_GB
  target_locales: 
  - name: French, France
    code: fr_FR
    type: Locale
  project_files: 
  - name: fr.yml
    id: 1175
  - name: en.yml
    id: 1174

I hope these improvements will make easier for everyone to integrate Web Translate It with their application and develop awesome extensions.

For detailed API specifications, check API Information on Web Translate It.

New in Web Translate It: new API, updated plugin for Ruby on Rails

Posted by Edouard on January 4, 2010

The API and on the Web Translate It plugin for Ruby on Rails. All of what follows use Web Translate It’s API which is only available on paying accounts.

API upgrade

The new API use a different URL and allow users to fetch their strings file by file. This is especially important for projects with several files to fetch their strings via the API.

The older API is deprecated, but will keep functioning indefinitely, so there is absolutely no need to update anything on your side if the endpoint you currently use works well for your project.

The other new feature is the ability to update a language file through the API. This can be really useful if you want to automatise the workflow between your project and Web Translate It.

What you do of it is entirely up to you. It could be used by a nightly or weekly task to upload an updated version of your master language file. This way new strings would be automatically added on Web Translate It.

For more information, I invite you to refer to the new API documentation for developers on Web Translate It.

Rails plugin upgrade

The plugin for integrating Web Translate It with Ruby on Rails projects has had a nice update today and now use the new API.

Once installed and set up, it allows you —if you want to— to sync the translations between your app with Web Translate It for every page requested. This is great for translators to test their work on a staging website.

It also comes with 3 rake tasks to help you manage your translations:

  • rake trans:fetch:all to fetch all your translations in all languages,
  • rake trans:fetch[fr_FR] to only fetch the french translations,
  • rake trans:upload[en] to send a new version of your language file to Web Translate It.

Grab it on Github if you haven’t already!

Thanks for using Web Translate It!

New in Web Translate It: new stats, Markdown help

Posted by Edouard on January 2, 2010

Happy new year! Here are a bunch of improvements for 2010.

Statistics

This is not really a new feature, but rather a different way of calculating statistics. Instead of processing them on every page load and asking you to wait a few seconds until it loads, stats calculation is deferred and calculated in the background. This is the same system used for the language file importer/exporter and the search engine’s indexer.

Since you don’t have to wait for the stats calculations to finish, the pages load much faster. You will sometimes see a notice indicating the stats are not up to date.

Web Translate It will then bring the stats up to date and automatically display them when available. It usually takes less than two seconds.

The filters and the stats section on the top of the translation interface have been redesigned to be clearer and easier to use.

This improvement is the first part of an upcoming new feature: project reporting. With reporting, you will be able to get detailed stats about your project over time. This requires the ability to generate costly statistics without making the website slower.

On top of the statistics improvements, many other tweaks have been done to make the translation interface load faster.

Progress bars on language page

The language page now has a progress bar indicating the percentage of completed and translated strings for that project. Of course, it also use deferred calculations.

Better Markdown help

Comments on Web Translate It are formatted using Markdown, an easy to use markup language. The help section about Markdown was very poor. You now have a decent help page for helping you to write better comments.

I open-sourced it if you need this help page on your own project.

That’s it! I hope you will enjoy these improvements, thank you for using Web Translate It!

Coming up in 2010

Posted by Edouard on December 18, 2009

Web Translate It is now on feature freeze. What I am currently working on right now is too big to be finished before the Christmas break. So that’s it for 2009!

What’s coming up next?

In the near future (January 2010), I will focus on enhancing existing feature. The stats and the API will be updated.

Stats

The new stats will be able to count strings, words, and keep a daily history. You will also be able to generate nice graphs displaying the amount of strings and words per language over time.

To make this work smoothly, some work has to be done under the hood. Calculations have to be deferred instead of being made again and again for every page load. This will use once again the same technology than the file import/export workers that proved to work really well. About 30% of Web Translate It’s calculations currently take place in the background.

The advantage is that not only you will have more detailed stats, but the pages using stats will load faster.

New API

The current API works really well, but doesn’t allow you to fetch a specific language file. This is a problem if you have several language files in your project.

The new API will allow you do just that. Although not advertised anywhere, it is actually already in production and used by some customers.

The API will also allow you to upload an update for a translation file. You could for example set up a periodic task on your server to update your translation files on Web Translate It nightly.

The Web Translate It plugin for Ruby on Rails 2.3 will also be updated to integrate these changes.

Crowdsourced translations

By the end of January, I will tackle crowdsourced translations.

I will chunk this large feature into several, simple iterations. For the first iteration I will focus on working a very simple, yet fully functional crowdsourcing interface.

  • Your own user community will be able to request for a translator account. I will implement login by OpenID to make it easier for everyone to register.
  • You will be able to accept or refuse these requests.
  • Your community will be able to suggest new translations or vote for existing translations.
  • You will be able to make the interface visible publicly or not.
  • You will be able to choose among 3 different translation strategies for each language. For example:
    • Traditional: let professional translators translate that language.
    • Half Crowdsourcing: Let your users translate and suggest translations, and hire professional translators to proofread their translations. You save a fair share of the translation cost, while having high quality translations.
    • Full Crowdsourcing: Let your users translate and vote to decide which translations will go live. It can work very well if you have a huge user community for that language. It usually doesn’t work so well for smaller user communities.

That’s pretty much everything I have planned for now.

I wish you a pleasant holiday, see you in 2010!

Web Translate It survey result

Posted by Edouard on December 16, 2009

If you haven’t had a chance yet, please take the survey. It’s always good to get your voice heard, and I always consider all of your suggestions.

The results have been incredibly useful. Thank you everyone!

Appreciation Rating

Everyone who took the survey think Web Translate It’s service and support is good: 100% of you would recommend it. This is fantastic, I am glad you appreciate it, and thanks for all the kind words in the survey, I appreciate that :)

Pricing

When it comes to pricing, the answers depend on whether the interviewee is a developer or a translator.

Translation agencies, translators and large websites find the price well adjusted. Translation agencies use Web Translate It quite a lot, so the ratio time/monthly price is fair.

Development agencies and freelance developers think Web Translate It a bit pricey. I understand it just “doesn’t worth it”. The entry level is 39€/month, this is a big cost for a freelance developer or a small development agency for something you don’t need all the time.

I want to fix this. I will get back to this topic later in this post.

Features

This is not very surprising, the most wanted features also differ from the interviewee’s job. Everyone want features to make their work easier.

Developers want integration to a Version Control System, a better API (to upload files), the ability to attach files and images to comments and have a term base.

Translation agencies would rather have better translation tools: Search and replace comes first, the ability to branch translations and a have translation memory.

It helped me establishing my roadmap for the next few months. I will share it with you in another post this week.

Suggestions

Pricing

Someone suggested a pricing based per project. You would upload your strings, you would pay a certain sum, and then you’d get access to Web Translate It for as long as you want. If later you have more strings to translate, you upload them, pay for them and off you go.

It makes sense for developers who work on projects that have very little changes over time: once the project is translated and live, they don’t need Web Translate It much.

I completely understand that Web Translate It is overpriced for this kind of use. It’s a bit like taking a Hummer to go to the supermarket.

It was the business idea I had when I started working on Web Translate It. After more thought, I noticed this business model wouldn’t work well for me.

Web Translate It is a service, and I see two ways of selling a good and reliable service:

  • either by selling it monthly at a certain price. This price includes the time my customers don’t use it (week-end, holiday, when no work). This is what companies do with their employees.
  • or by selling it only when my customers need it. This extra flexibility comes at an extra price. This is what companies do when hiring consultants and freelancers: they are usually paid more than employees, but if used sparingly, they cost less to the company.

Consultants and freelancers’ businesses would not work if they were paid once and used indefinitely. There has to have a time limit.

What I am going to do

You will be able to top-up your Web Translate It account with some credit. This credit will stay on your account as long as you want and won’t lose value over time (unlike some dirty phone companies). With that credit you will be able to buy time on Web Translate It, depending on your needs of the moment.

To keep things simple, time will be divided by day —the day pass— or by month —the monthly pass.

It’s a pretty good deal: for example, if you translate a small project, you probably only need a few days. You can buy day passes, which give you access to Web Translate It for the time you need. After that, if you don’t need to translate anything for a while, it won’t cost you a thing.

When the time is up, your project will be automatically locked, so you won’t be able to access or edit it, unless you use another day pass or monthly pass.

The date is not defined yet. I believe it will be implemented sometime during the first semester of 2010.

Pricing is not defined either, but the idea is that if you have an occasional use of Web Translate It, this will be really cheaper than subscribing a monthly plan. Of course, if you use Web Translate It daily, monthly plans will be cheaper. I will announce more about it when I’ll have decided it.

Work offline

Someone suggested to have the ability to work offline, and I am really enthusiastic about this idea. I for one love to cut the wire sometimes.

I can’t promise a date for this, as I have a lot of pressing feature to implement, but I will definitely keep this suggestion in mind, thanks for sharing!

Do you have other suggestions?

If you have other suggestions or ideas to share, please let me know by e-mail or on the support forum.

Thank you for all the feedback, and thank you for using Web Translate It!