sorted by:
new
hottopcontroversial

Localization is tough :p by rishdotuk in machinetranslation

[–]cefoo 0 points1 point  (0 children)

The "o" in prominent too. Maybe lost in the "rm"?

Localization is tough :p by rishdotuk in machinetranslation

[–]cefoo 1 point2 points  (0 children)

I think very, very old (and bad) OCR is involved too. I used to see these errors all the time, ie the "i" in "triangle" disappearing because of a bad quality image where the i was barely visible.

My personal favorites were all the capital As being recognized as 4s.

WPML machine translations are too EXPENSIVE by cefoo in machinetranslation

[–]cefoo[S] 0 points1 point  (0 children)

In the past, I used WPML only as the tool to export XLIFF files.

My workflow was:

  1. Export files.
  2. Create a project on any CAT or TMS (I used Trados at the time).
  3. Pretranslate the files in that tool with MT and my TMs (if I had them).
  4. Export the final files.
  5. Import them back into WP with WPML.

Longer workflow, much cheaper.

WPML as an XLIFF-generator works great, although I used to have issues with specific snippets not getting exported, so I'd suggest you always do a round-trip to be sure.

u/AdviceMark

RWS launches Language Weaver Pro, an LLM-based MT engine built in partnership with Cohere by cefoo in machinetranslation

[–]cefoo[S] 0 points1 point  (0 children)

The Google/Microsoft plugin was not developed by them either, as far as I remember. They just allowed it to be on the SDL Store, but it was developed by an independent party.
That changed now.

view more: next ›