It’s not too hard to roll your own, if you want something basic:
But generally, my attitude is that a translation interface is not the
focus
of our business, so we happily use a commercial offering instead of
putting
in the hours to do it ourselves.
But generally, my attitude is that a translation
interface is not the focus of our business, so we happily
use a commercial offering instead of putting in the hours to
do it ourselves.
- Martin
On Tue, Mar 27, 2012 at 12:03,
Andrés
gutiérrez <[email protected]>
wrote:
Hi, this isa
question thatarisesrecurrentlyme
How do you handletranslations
ofyourapplications?
They look good.But
I was wonderingif there issomething I can manage myself
without
relying onoutside
companies.
Before Iupgraded torails3.1 I usedTolkhttps://github.com/dhh/tolk
But isn't compatible with rails 3
The old dilemma third party service or doing your own thing. As devs we
tend to create our own solution, but I can tell you, focus on your core
business.
My guess is your core business has nothing to do translation,
localization,
… so I would recommend using a SAAS based solution.
Services bring you a lot of features and stability you otherwise have to
do
on your own: Syntax Checking, Keeping track of the translation texts
(status, review process, …), char count (for external translators),
context (WYSIWYT) and so on.
As the founder of lingohub.com I am clearly biased, but we ourselves use
many other services as well because making software translation as easy
as
possible is our core business. Not issue tracking (JIRA), repo hosting
(Github), Continues Integration (Codeship), …
And the good thing, there is no vendor lock-in, you always have your
resource file. If you are not happy with a service, you can leave at any
time.
If you have questions about lingohub, just contact helmut - at -
lingohub .
com