Author Topic: TEMPLATE: 9-verb MI-style 1.3 UPDATE (15th Feb 2011) (Read 17571 times) Tweet Share

Unai · « **Reply #100 on:** 20 Jan 2011, 16:35 »

Quote from: Unai on 18 Jan 2011, 22:34

Just in case "Restable" is a typo :p

Sorry!

About Unhadled... I'd translate them... would be a bit weird to have just some lines in english, would probably confuse people that don't speak english at all (the ones that will probably seek a translation)

abstauber · « **Reply #101 on:** 20 Jan 2011, 19:30 »

Quote

would be a bit weird to have just some lines in english, would probably confuse people that don't speak english at all

Hehe, since there's no localized version of the AGS editor yet, I suppose that doesn't count

How about "P.defecto" then?

Unai · « **Reply #102 on:** 20 Jan 2011, 19:40 »

Monsieur OUXX · « **Reply #103 on:** 25 Jan 2011, 12:21 »

I've translated only the lines that will be visible to the player, not the lines that will be used by the developer (because I guess they're used by the code and it would break the module)

abstauber · « **Reply #104 on:** 26 Jan 2011, 10:44 »

Thanks a lot for the input, everyone. Here's the new beta:

http://shatten.sonores.de/wp-content/uploads/2011/01/9verbs_13_beta.zip

1.3 added GUI translations for Spanish, French and German
slightly expanded buttons in options GUI
added old school inv handling

@Unai and Monsieur OUXX

Could you please check if I've included your translations correctly?
In guiscript.asc, just change line 6 to
int lang = eLangES;
or
int lang = eLangFR;

poplamanopla · « **Reply #105 on:** 27 Jan 2011, 12:19 »

Hi, I'm not Unai but I can also help to you ...

At first glance, all seems be OK (spanish translation).

If you allow me a suggestion you can add more comment more before line 6:

// Setup the default Language (only affects the provided GUIs)
//
// eLangDE (German)
// eLangEN (English)
// eLangES (Spanish)
// eLangFR (French)
//

It would be good a translation into Italian

A little mistake (if can be called mistake ...)

In line 569 comment is // Spanish (again) but should be // French.

By other way.

I see that text in options aren't centered (in previous version too) if can't resolved easily, you could always use sprites like in the verbs.

That's not very important but would be more nice.

abstauber · « **Reply #106 on:** 27 Jan 2011, 13:12 »

Alright, fixed my copy paste comments

As far as the option buttons are concerned, I'd rather not switch over to sprites: text is so much more convenient.
The only reason why the verbs are implemented as sprites is that you can't have highlighting on text buttons.

Oh and yes, more translations are very welcome!

Giowe · « **Reply #107 on:** 27 Jan 2011, 14:19 »

tnx for the help. now i have an other problem:
when i have more then 5 or 6 dialog opions they will disappear, how can i implement the famous 2 monkey island style arrows to scroll the dialog options up and down?

abstauber · « **Reply #108 on:** 27 Jan 2011, 14:30 »

Scrolling dialogs, eh?

Well, I'm afraid you've to master another module

http://www.bigbluecup.com/yabb/index.php?topic=36313.0

Monsieur OUXX · « **Reply #109 on:** 27 Jan 2011, 16:45 »

I understand that it is your design choice that the GUI language supercedes the game's language. Is it a wise choice?

Also, how does the "lang = eLangFR" relate to "if (tr_lang =="fr")"? The first one is for the game GUI, and the other one for the game's translations?

Giowe · « **Reply #110 on:** 27 Jan 2011, 18:22 »

perfectly done! u are the best

abstauber · « **Reply #111 on:** 27 Jan 2011, 20:06 »

@Giowe:
Great. Good to hear that's not too hard to master the CDG module

@Monsieur OUXX:
Of course it is

Hehe, from a more serious point of view, I think it is very convenient and also attracts more beginners to start a 9verb game in their language.

The template only provides translations for the GUI elements, so you can directly jump in and start making the game without the need to worry how .trs files work or how to set up those wicked text strings for the verb buttons.

Just think how it would be in 1.2.1:
- First you have to create new verb sprites and announce them deep inside the script, using a cryptic space separated string.
- Then you hopefully create a game and think about translations. You have to add more verb sprites and create the .trs files.
- Then you need to adjust the text strings inside the .trs and finally send it to your translators.
Not to mention that you also need to understand how the sprite verb systems works.

In 1.3 it is:
- Set lang to your preferred language, like "eLangFR"
- Make your game
- Create e.g. "spanish.trs", translate "GAME_LANGUAGE" to "es" and send it away (or do it afterwards)
Done

From a designers point of view, it's the template's task to provide the GUI and the users task to make that game. Therefore it's not the users top priority to worry about how one can setup GUI buttons with nine text strings

Monsieur OUXX · « **Reply #112 on:** 28 Jan 2011, 10:15 »

Quote from: abstauber on 27 Jan 2011, 20:06

@Monsieur OUXX:
From a designers point of view, it's the template's task to provide the GUI and the users task to make that game. Therefore it's not the users top priority to worry about how one can setup GUI buttons with nine text strings

You do make sense -- I was just wondering why the template doesn't simply get its default language value from the game's selected runtime language.
Something like: lang = tr_lang (it wouldn't work like that but you know what I mean).

It's just a suggestion. Otherwise if the game creator distributes his game with an "English" GUI, then no matter what language the player selects, he'll be stuck with an English GUI, even though the rest of the game will be in German/Spanish/French..

abstauber · « **Reply #113 on:** 28 Jan 2011, 11:37 »

Doesn't this piece of code take care of it?

[code]
function game_start() {

String tr_lang;
// --- translate GUI action buttons ---
tr_lang = GetTranslation("GUI_LANGUAGE");
tr_lang = tr_lang.LowerCase();

if (tr_lang == "de") {
lang = eLangDE;
}
else if (tr_lang =="es") {
lang = eLangES;
}
else if (tr_lang =="fr") {
lang = eLangFR;
}
else if (tr_lang =="en") {
lang = eLangEN;
}
.....
[/code]

GUI_LANGUAGE appears in the .trs file and needs to be set to the according language

Monsieur OUXX · « **Reply #114 on:** 28 Jan 2011, 11:55 »

Quote from: abstauber on 28 Jan 2011, 11:37

Doesn't this piece of code take care of it?

OK I guess that's what confusing me : when I tested beta 1.3, the GUI was in French because of that line :
int lang = eLangFR;

Is it something you added just for test's sake?

abstauber · « **Reply #115 on:** 28 Jan 2011, 12:10 »

Yep

edit--

or wait:

"int lang = eLangFR" is for the initial language setup. GUI_LANGUAGE from the .trs overrides this once you have translation files.

But initially it should be eLangEN, which I forgot to set back.

Monsieur OUXX · « **Reply #116 on:** 28 Jan 2011, 13:07 »

Quote from: abstauber on 28 Jan 2011, 12:10

or wait:

HA! YOU SUCK!

Hehe, ok, that makes more sense. Bottom line is : Great module!!!

Giowe · « **Reply #117 on:** 30 Jan 2011, 13:33 »

i found a bug:
if you click rapidly many times the left button of the mouse to say to your character to go in a place, every time you click he stop his movement, and, after a series of clicks he stops definitively and you cant move at all...

abstauber · « **Reply #118 on:** 31 Jan 2011, 10:53 »

Hmmm... I can't replicate this (AGS 3.2) and I clicked like 2 minutes on the same spot.
Roger never totally stopped walking or animating. Anyone else having this problem?

Giowe · « **Reply #119 on:** 31 Jan 2011, 13:03 »

i use ags 3.1. i'l try with 3.2... the error was my fault but if u click many times in different spots he will stop :\
anyway you see that if u click many times the character nearly stop?