Translate ScummVM in other languages

General chat related to ScummVM, adventure gaming, and so on.

Moderator: ScummVM Team

Post Reply
User avatar
criezy
ScummVM Developer
Posts: 608
Joined: Sat Sep 23, 2006 10:41 am
Location: West Sussex, UK

Post by criezy » Wed Nov 24, 2010 11:46 am

saulob wrote:Well, I need some help. The 'original' PO was updated with more text right? How can I add the 'new' text on the already translated PO that I have?

Or I should start again? I don't want to miss the 370 strings I already translated ;)
Get the pt_BR.po file I committed to our repository (e.g. from http://scummvm.svn.sourceforge.net/view ... /trunk/po/). It contains all the strings you have already translated and the new untranslated ones.[/url]

shurlogg
Posts: 18
Joined: Sat Jun 09, 2007 2:03 pm

Post by shurlogg » Wed Nov 24, 2010 1:10 pm

BeleG wrote:Sierra games came dithered, so dithering is not the real ScummVM feature, there's nothing to "disable". I believe it would be more correct to express it like "Enable EGA undithering", as undithering is the authentic ScummVM feature, which you can enable or leave disabled (if it's going to be disabled by default).
From the UI design point of view, there is another reason why no setting should be called "Disable ..." - the setting is represented by a checkbox, which can either be checked (enabled) or unchecked (disabled) - the enabled state of the checkbox representing the disabled state of some functionality would simply be confusing and bad UI design.

I would suggest to simply call the setting "Undithering". I'd leave the word "EGA" out too because that is too focused on DOS games - who knows if there is going to be undithering for games from other systems (or even undithering for VGA games) in the future as well, and if there is, there should probably not be a second, independent setting for it.

User avatar
bobdevis
Posts: 563
Joined: Fri Jan 16, 2009 10:52 am

Post by bobdevis » Wed Nov 24, 2010 5:42 pm

shurlogg wrote: From the UI design point of view, there is another reason why no setting should be called "Disable ..." - the setting is represented by a checkbox, which can either be checked (enabled) or unchecked (disabled) - the enabled state of the checkbox representing the disabled state of some functionality would simply be confusing and bad UI design.
There are more ways you can go with this.

You could claim that the default state should always be the disabled/unchecked one so that the user knows that everything that is enabled is done so by himself. If feature x is enabled by default then the option should be checked to disable it.

You could claim that options should be formulated such that the wording is the shortest and/or best comprehensible. Let's say you have a game where you can toggle sound from different sources on and off (music, effects, speech, etc..). A global sound toggle option should be called "Disable All Sound" or "Mute All" and not "Allow Sound".

Flo
Posts: 58
Joined: Tue Aug 05, 2008 1:50 pm

Post by Flo » Wed Nov 24, 2010 6:00 pm

It's a matter of consistency. If you have a list of features that you can enable and disable with a checkbox, you shouldn't reverse the meaning of a "checked" box halfway through.

User avatar
saulob
Posts: 89
Joined: Fri Dec 01, 2006 4:06 am
Location: Brazil

Post by saulob » Wed Nov 24, 2010 8:50 pm

criezy thanks. Got the PO file, I'm working on it right now.

I have one small question, it's about the Poedit colors, sorry but I was unable to find anything on the oficial page or google.

Well, check the image:

Image

The colors, blue it's for untranslated strings, black for already translated, but what about this brown/yellow one?

It's the 'fuzzy' strings right? Should I edit it again? I'm seeing that some strings changed. Should I updated it?

Thanks. It's getting perfect :)

User avatar
criezy
ScummVM Developer
Posts: 608
Joined: Sat Sep 23, 2006 10:41 am
Location: West Sussex, UK

Post by criezy » Wed Nov 24, 2010 9:59 pm

saulob wrote:what about this brown/yellow one?

It's the 'fuzzy' strings right? Should I edit it again? I'm seeing that some strings changed. Should I updated it?
Yes it's the fuzzy strings. Usually they are new strings for which there was already a similar string in the po file from which it borrowed the translation. You will want to check all of these (most of the time I found the proposed translation is wrong) and either fix the translation or remove the fuzzy flag.

User avatar
md5
ScummVM Developer
Posts: 2260
Joined: Thu Nov 03, 2005 9:31 pm
Location: Athens, Greece

Post by md5 » Thu Nov 25, 2010 2:35 am

Yeah, enabling a "Disable" feature does sound odd. I've renamed the option to "Enable EGA undithering" (this only makes sense for EGA).

User avatar
saulob
Posts: 89
Joined: Fri Dec 01, 2006 4:06 am
Location: Brazil

Post by saulob » Thu Nov 25, 2010 1:53 pm

md5, nice update. thanks. but this will need another PO file? :)

I'm working on the late one from criezy. Is it already updated online so I can download the new one?

Thanks.

User avatar
md5
ScummVM Developer
Posts: 2260
Joined: Thu Nov 03, 2005 9:31 pm
Location: Athens, Greece

Post by md5 » Thu Nov 25, 2010 2:30 pm

Possibly, yeah, sorry :( Unless fuzzy matching handles this

I didn't update the checkbox name, so that the theme version remains the same, I'm unsure if I should update that as well

User avatar
saulob
Posts: 89
Joined: Fri Dec 01, 2006 4:06 am
Location: Brazil

Post by saulob » Sun Dec 05, 2010 4:30 pm

criezy, it's updated (2010-12-05). please check everything.

md5, no problem, hope that there's nothing missing.

Thank you guys

Btw, does the translations works on ports? Like the PSP port, DS port, iPhone Port.

Does the ScummvM ports have translations on it?

User avatar
LordHoto
ScummVM Developer
Posts: 1030
Joined: Sun Oct 30, 2005 3:58 pm
Location: Germany

Post by LordHoto » Sun Dec 05, 2010 5:38 pm

saulob wrote:Btw, does the translations works on ports? Like the PSP port, DS port, iPhone Port.

Does the ScummvM ports have translations on it?
That depends on whether the port enables the feature or not. I guess the DS port won't do it, since it's always struggeling with memory usage anyway. With the other ones there might be a better chance.

User avatar
saulob
Posts: 89
Joined: Fri Dec 01, 2006 4:06 am
Location: Brazil

Post by saulob » Sun Dec 05, 2010 10:55 pm

thanks for the info LordHoto.

Let's wait for the official release and see if the translations are applied.

criezy, saw your update at the tracker, something is wrong, I think you got the wrong file. Please check it out.

I update there too, dunno if you get info on that.

Thanks

User avatar
saulob
Posts: 89
Joined: Fri Dec 01, 2006 4:06 am
Location: Brazil

Post by saulob » Tue Dec 07, 2010 1:08 pm

criezy, just uploaded the v3, I created another one thread, named it v3, this one have all 511 strings. You can close the v2.

It's all ok, the only thing left it's to test on ScummVM itself, when the SVN is updated I will check it out and if anything goes wrong post a update on the v3.

Thanks :)

User avatar
saulob
Posts: 89
Joined: Fri Dec 01, 2006 4:06 am
Location: Brazil

Post by saulob » Mon Dec 20, 2010 12:03 pm

criezy, just saw the last update. Our translation (Brazilian) is in.

Thanks :)

But... there are some problems. Checking the final translation with the last svn version I downloaded (1.3.0svn54095 , Dec 14 2010 17:54:05), some texts are different...

I already identify a couple of them

Options menu.

- Audio tab
- Volume tab

I'm at work right now, but when I arrive at home I will take some prints and show to you. I will check everything, comparing the versions.

criezy, do you know why that happened?

Thanks.

User avatar
criezy
ScummVM Developer
Posts: 608
Joined: Sat Sep 23, 2006 10:41 am
Location: West Sussex, UK

Post by criezy » Mon Dec 20, 2010 1:02 pm

saulob wrote:criezy, just saw the last update. Our translation (Brazilian) is in.

Thanks :)

But... there are some problems. Checking the final translation with the last svn version I downloaded (1.3.0svn54095 , Dec 14 2010 17:54:05), some texts are different...
[...]
criezy, do you know why that happened?
I probably forgot to merge some of your updates into the translation that went into version 1.2.1. This version was built using a different branch of our code (and a different set of strings to translate). The translation used there is probably some of your earlier submission to which I forgot to apply the following updates you made. Sorry about that. :oops:

Post Reply