I like <a href="http://translia.com">translia.com</a> better. All the translation process is online. And I can get the translation result as soon as possible.<br><br><br><div class="gmail_quote">On Fri, Jul 23, 2010 at 5:47 AM, Yuval Hager <span dir="ltr"><<a href="mailto:yhager@yhager.com">yhager@yhager.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Wednesday 21 July 2010 17:51:56 Kevin Davison wrote:<br>
><br>
> The plan is to translate nodes on a staging/qa server, and then<br>
> deploy/migrate these translations to the production server. But what's<br>
> best? Who has done this already, and learned from a few mistakes I<br>
could<br>
> learn from?<br>
><br>
<br>
</div>Translation nodes are just new nodes, so you need just to transfer those<br>
new nodes (and make sure the relationship between the source and<br>
translated nodes is kept - I am not sure how the deploy module works in<br>
that sense).<br>
<br>
If you are outsourcing your translation, you might consider using a<br>
service like <a href="http://icanlocalize.com" target="_blank">icanlocalize.com</a> - in addition to providing the translation, they<br>
will push it into your site automatically. I assume they might have some<br>
method to push into QA servers first - but for more info you will have to<br>
contact them directly.<br>
<font color="#888888"><br>
--y<br>
</font><div><div></div><div class="h5"><br>
> Thank you,<br>
><br>
> Kevin<br>
><br>
> On Jul 21, 2010, at 14:15 PM, Sarah Poger Gladstone wrote:<br>
> > Kevin -<br>
> ><br>
> > You may be interested in the tool described at:<br>
> > <a href="http://www.transifex.net/help/faq/" target="_blank">http://www.transifex.net/help/faq/</a><br>
> ><br>
> > -Sarah<br>
> ><br>
> > On Wed, Jul 21, 2010 at 3:01 PM, Kevin Davison<br>
<<a href="mailto:kevin@quevin.com">kevin@quevin.com</a>> wrote:<br>
> >> How would you suggest a good process to test translations on in a<br>
QA<br>
> >> environment, and then deploy them to a production environment<br>
after<br>
> >> testing?<br>
> >><br>
> >> * Best practices?<br>
> >> * Deploy/Services modules?<br>
> >> * Node export/import?<br>
> >> * Translate interface export/import?<br>
> >> * Freeze production, work in QA, then move the DB over to<br>
production?<br>
> >> * Other?<br>
> >><br>
> >> Thank you,<br>
> >><br>
> >> Kevin<br>
> >><br>
> >> PS May be looking for paid consultation on this matter...<br>
> >> _______________________________________________<br>
> >> consulting mailing list<br>
> >> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
> >> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
><br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> consulting mailing list<br>
> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>A decathlon Drupal developer & programmer<br><a href="http://blog.eood.cn/">http://blog.eood.cn/</a><br>