Jump to content

Recommended Posts

Posted

For filipino, we prefer to use English. As we know that if we use Tagalog (Filipino Language). We find it so hard or so etc etc.. xD 

Posted

Goddameit: Added to the list, thank you!

Lilith: Okay, great!

I've removed Filipino from the list unless anyone objects, then.

Posted

 

No Filipino Translation? xD

lol

no need

just who want participate, just post here and Euphy will list it.  /no1

there are some words on english that can't be translated on tagalog

Posted (edited)

Well, I'm not updating the current SVN version I have for my own personal reasons, but I'm working on the additions separately to translate the new ones. However, the translation will have all lines in the same file. Working!

 

Edit: I've translated it but I'll wait for Tragedy for revising the new messages. Link to the folder: https://drive.google.com/folderview?id=0B2UkVqklEED8Tkh5RmVqejhKc3c&usp=sharing

 

Edit 2: Slightly revised by me, but it's preferable to be revised by another person for obvious reasons.

Edited by jaBote
  • Upvote 2
Posted

I wonder if I could also suggest making a new atcommand called @reloadmsgconf or so (in case you haven't thought on it yet), which would let specify an optional parameter and make the server read the msg_conf again but with a specific language. For example:

Usage: @reloadmsgconf <language code>
ex: Makes the server read and use English msg_conf files:
ex: @reloadmsgconf en 
ex: Makes the server read and use Spanish msg_conf files:
ex: @reloadmsgconf es

And so for Indonesian, Chinese, French and so.

 

Opinions on this?

  • Upvote 1
Posted

yes jAbote this could be done as well.

would be direct for map but probably require a packet for char and log to keep them independant.

kinda thinking about how to store msg efficiently atm.

  • Upvote 1
Posted

<p>i've work on it today with what Lilith have done I now need the missing translation for the langage.</p>

<p>here the current avancement :</p>

<p> </p>

<p>enable/disable langage => ok</p>

<p>map multi msg => ok</p>

<p>import "foo" => ok</p>

<p>fallback lang not enable => ok</p>

<p>fallback lang return ?? => ok</p>

<p> </p>

<p>@langtype => ok</p>

<p>check enable/disable => ok</p>

<p>account wide ? => ok</p>

<p>kept in deco/reco => ok</p>

<p>reset to default if langtype disable => ok</p>

<p>available in charserv => impl not tested</p>

<p>available in logserv => impl not tested</p>

<p> </p>

<p>@reloadmsgconf => ok</p>

<p>rerad import as well ? => ok</p>

<p>reload charmsg => not impl yet</p>

<p>reload loginmsg => not impl (needed ?)<br />

<br />

Just need some optimisation and eventually some cleaning but it's probably ready for a beta release. Waiting Lilith opinion.</p>

  • Upvote 1
Posted

oh non pas des accents ! lol

Je n'aime pas trop :

1119 Vous êtes monté sur votre Dragon. =>  "Vous montez désormais votre Dragon" fin les "Vous êtes monté" c'est trop lourd je trouve.

1139 Vous n'êtes pas emprisonné => meme chose bref le passé composé c'est moche

1306: Retourné à l'état normal. => Retour à l'état normal

La plupart sont des messages d'état, de feedback pour dire que tel actions est effectué donc pas vraiment besoin de la mettre dans le passé qui fait juste alourdir.

 

======

Just a few notes on the translation saying some sentence even if ok and correctly translated was too bold.

nb : import: conf/import/msg_conf.txt should point to conf/import/msg_frn_conf.txt cause right now all translation point to the same import file wich gonna be a big mess.

  • Upvote 2
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...