Some questions about translations

[Ben Hearsum]

Hi all,

While working on translations on Narro I often have trouble translating
technical (and sometimes other) words. As well, there are some classes of
strings that I'm not sure should be translated at all or not. If someone
could tell me if there's a definitive answer for any of these questions I'd
really appreciate it!
- Is there a list of words that should never be translated? (For example,
I've noticed that "Profile" has no translation so far, even in approved
strings.)
- Should non-translated words be Filipino-ized? (Eg, should "release notes"
be "release notes", "mga note ng release", "notes ng release", ???)
- Should CSS and Javascript errors be translated at all? Similarly, should
error messages such as problems with certificates or the "suspect attack
site" page be translated?

Salamat!
- Ben

[Robert DC. Reyes]

Hi Ben! Thanks for the inputs! Basically, for me, my rule of thumb is that
if a term (sentence, or phrase) sounds too technical, I leave it as it is.
You are correct, there is not direct translation of "Profile" to Tagalog. I
do not think that CSS/JavaScript errors should be translated at all :) they
may sound "corny", or worst, misleading.


brgds,
Bob

> _______________________________________________
> community-philippines mailing list
> community-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/community-philippines
>

[Regnard Raquedan]

Hi guys,

I agree with Bob-- there are technical terms that don't have a direct
translation in Tagalog. And if they do, it's very likely that it's not
popular.

That said, my philosophy in localizing has been to make it it
conversational and think how the local channels would translate it.

--
*Regnard Raquedan, MBA, MSc.*
reg...@raquedan.com
(+1) 416 841 0552
http://www.raquedan.com

[Allan Caeg]

>
> - Is there a list of words that should never be translated? (For example,
> I've noticed that "Profile" has no translation so far, even in approved
> strings.)

Afaik, #fistbump might create some sort of brand family tree. That way, it
will be clear if something is a brand or not. Brands, like "Firefox",
shouldn't (I hope so) be translated. Same goes for products inside Firefox
like "Sync"

- Should non-translated words be Filipino-ized? (Eg, should "release notes"
> be "release notes", "mga note ng release", "notes ng release", ???)

I agree with Robert and Regnard's stand on this

> - Should CSS and Javascript errors be translated at all? Similarly, should
> error messages such as problems with certificates or the "suspect attack
> site" page be translated?
>

I suggest not translating these as the audience will be very comfortable
with the dev language and error messages should be SEOd so people
everywhere can identify the same issues and solve problems together

Your thoughts, Arky? Are there international guidelines that we can follow?

Regards,*
*
*Allan Caeg*
User Experience Designer and Senior Product Manager
http://allancaeg.com
+63 918 948 2520

[Gen Kanai]

On 2/20/12 3:51 PM, Allan Caeg wrote:
> Your thoughts, Arky? Are there international guidelines that we can follow?

I won't answer for Arky but I do know that there are no hard/fast
international guidelines.

In some countries there are new terms created by government agencies
(French is a good example) so that there will be "French" ways of saying
computer (or whatever the technical term is.)

In other countries there are guidelines put out by leading universities.

So I don't think there is any set way to do this.

As many of you may remember, Google's localization of the Philippines
home page caused a lot of confusion due to the terms that they chose, so
I think we want to be cognizant of that and not make the same mistakes.

Gen

--
Gen Kanai

[Ben Hearsum]

Thanks Regnard and Bob! I've got a couple of other questions, if you don't
mind:
- Is there a preferred possessive form? (aking mga tab vs. mga tab ko)
- Is there a preferred way to pluralize English terms (mga Bookmark vs.
Bookmarks)

Noong Pebrero 19, 2012 23:47, Regnard Raquedan si <reg...@raquedan.com> ay
sumulat:

[Regnard Raquedan]

"Mga tab ko" is more conversational, while "aking mga tab" looks like
something in a poem. :P

I think "mga bookmark" is more acceptable and structurally more accurate.

[Robert DC. Reyes]

I agree with Regnard, the "mga" already means something/someone in plural
form. Thus, "Mga Bookmarks" sounds redundant :D "Mga Bookmark" is more
proper.


--

Robert "Bob" Reyes
Mozilla Representative (PHL)
http://www.bobreyes.com

[Allan Caeg]

Yep, it should be either "Mga Bookmark" or a simple untranslated
"Bookmarks". If we're not going to translate "Bookmark" anyway, I'd prefer
the latter. There's little value to adding a localized plural treatment if
the term stays english anyway, particularly because "mga" prefixes (and
makes harder to read) the important word (i.e. Bookmark)

[arky]

On 02/20/2012 01:51 PM, Allan Caeg wrote:
>
>
> Your thoughts, Arky? Are there international guidelines that we can
> follow?
>

Perhaps we can put together some ideas into a Tagalog style guide.

You can also track the development of generic Mozilla L10N style guide
here: https://bugzilla.mozilla.org/show_bug.cgi?id=840448

Cheers

--arky