Just a little note, on my really busy days, as i recall, there were two options:
1. es as source lang, then translate en, then translate to a third lang (hard to keep up for fedora products)
2. es as source lang, then direct translation to a third lang (brazilliang lang was planned but no results so far)
I dunno about transifex limitations but i hope there will be no limitations on translators requirements. I do believe spanish <--> portuguese/brazillian is likely to happen translator case without English being the middle man (this translator might not handle english at all).
1. es as source lang, then translate en, then translate to a third lang (hard to keep up for fedora products)
2. es as source lang, then direct translation to a third lang (brazilliang lang was planned but no results so far)
I dunno about transifex limitations but i hope there will be no limitations on translators requirements. I do believe spanish <--> portuguese/brazillian is likely to happen translator case without English being the middle man (this translator might not handle english at all).
On Mon, Aug 12, 2013 at 9:38 AM, <bugzilla@xxxxxxxxxx> wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=768731
--- Comment #17 from Eric Christensen <sparks@xxxxxxxxxx> ---
I only know of one other project that had its base (source) language that
wasn't EN. The "problem" was solved by translating it to English and then to
other languages.
Unfortunately that is how our model is setup. Our expectation is that the
translators will translate text from English to another language. This should
limit someone's ability to write in their native language, though. There's
just another hop involved.
--
You are receiving this mail because:
You are the assignee for the bug.
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
--
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
