Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - GunChleoc

Pages: 1 [2]
26
I think the question in the Game menu breaks the pattern and thus disrupts usability, as well as creating localization issues. Could we please split the string into two separate strings? The English version would benefit as well, because then you cold have a full question in the following dialog instead of just "Exit game?"


27
I have just finished translating into Scots Gaelic and for some of the explanations in the Very Basic Tutorial, I need 3 more lines to make it fit above the button. Can we add more lines, or have a scroll bar?

Screenshots:





Tested on:

CPU: Intel Core2 Duo E7400
OS: Windows XP SP3
RAM: 2 GB
Graphics: MSI NX8400GS (NVidia GeForce 8400 GS)

Game version: MegaGlest 3.6.0.3

Resolution: 1024x768-32

28
MegaGlest / Scots Gaelic translation MegaGlest 3.6.0.3
« on: 13 May 2012, 12:06:40 »
I have made a translation of MegaGlest version 3.6.0.3 into Scots Gaelic. Here it is: http://www.foramnagaidhlig.net/temp/MegaGlest_gd_3.6.0.3.zip

29
In the upgrade screens, affected units are listed and commas + ampersand added automatically by the script:



I am working on a translation for Scottish Gaelic, which uses 7 instead of &. I imagind if we get people translation into languages that don't use Latin script, like Arabic or Chinese, they will have issues with this as well, and with the commas.

Maybe do away with the ampersand and have a comma instead, and then make the comma translatable?

30
%s needs to be replaced with translation of the resource name, if a translation is available. Strings affected in main language file: BuildingNoRes1, BuildingNoRes2, MorphNoRes1, MorphNoRes2, UnitNoRes1, UnitNoRes2, UpgradeNoRes1, UpgradeNoRes2



Attack type names and Armour type names aren't translated for all units:



ETA: I overlooked the first problem has already been reported: https://forum.megaglest.org/index.php?topic=7051.0

31
Bug reports / [Fixed] 0.3.93 Menus - untranslated strings
« on: 12 May 2012, 10:23:10 »
The following strings are not translated:

Join Game Menu, after an aborted network search: Not Connected. Last search cancelled.



New Game Menu: Player, No Player



Victory screen: Player, CPU Player, Victory, Defeat



I managed to work around the string length issue, so ignore the third red box in the screen shot.

32
Shields level 1 and 2 both have upgrade_shield as their language name, but the variables in the language file and the prerequisites in the XML are called shield_level_1 and shield_level_2.

english.lng has blade_weapons and piercing_weapons as variables, but the XML has upgrade_blade_weapons and upgrade_piercing_weapons.

33
General discussion / Translation Scottish Gaelic done.
« on: 7 May 2012, 18:52:09 »
I have finished translating Glestae 0.3.93. There are a few strings that are still too long in the top right widget, but that can't be helped.

Which encoding do you need for the files in order to package them? They are currently ANSI but I can encode to UFT8 or whatever you need. Will upload once I know which encoding to use.

ETA: Done and uploaded http://www.foramnagaidhlig.net/temp/glestae_gd_0.3.93.zip

34
In Glestae 0.3.93, the Battle Machine properties don't display attack_skill, attack_arrow_skill properly when you hover over Patrol, Guard, Hold Position



ETA: Same with Ornithopter, molotov_skill and arrow_skill

35
MegaGlest / Localisation: CURL version [%s] [%s]
« on: 7 April 2012, 13:54:07 »
For my translation I have a question regarding the following string:
Code: [Select]
ModDownloadTilesetFail=FAILED to download the tileset: [%s] using CURL version [%s] [%s]
What is behind the [%s] [%s] at the end? Are they both to mark the version, or is there an extra message in the last [%s]?

Thanks!

36
When I play the basic or the advanced tutorials, the objectives are missing. They were still visible in version 0.3.2 on top of the screen.

37
Opaque String is missing from English language file

Textures3D does not get used, the program wants 3D Textures instead. (Options -> Video -> Water Shader)

Game version: glestae-0.3.93-win32.exe

38
Hi All,

thanks for making translation for the tech tree possible, you rock!

I have made a full translation into Scottish Gaelic including magitech and tutorials. Shibboleth is still missing.

I have also posted some issues that affect both branches in General Discussion

[big]Strings I have trouble translating[/big]

With the main language file, I lack context for the following strings to properly translate, but I can't find them in the code or in gameplay, are they obsolete?
Code: [Select]
Effects
Kills
MaxRange
Range
Fields

[big]Gameplay[/big]

I have some issues in gameplay. I don't know if they need to go on the bug list and how to separate them.

Weird spacing with some of the tooltips.

Swordman:



Technodrome:



ETA: Comments updated to latest Beta. I still need to translate some stings and then will upload new version.

39
General discussion / Translation issues
« on: 3 April 2012, 10:56:16 »
I have just started on a translation for Scots Gaelic, and I decided to start with Glest_3.2.2 before I do the branches. Some of these issues will affect both branches, so I'm posting it here.

  • *resolved*
  • Assembled strings - can word order be made flexible, using %s, %d etc? For example, Initiate reqs
  • UpgradeSpeed, ProductionSpeed, OrdersOnQueue etc - Can you switch off auto caps? They look really weird in Gaelic
  • Gaelic repeats the verb in order to say yes/no. I have a conflict I can't resolve (ETA: see also my post below with the screen caps):

    Options -> Textures3D:
    Yes/no, should be on/off = Air/Dheth

    ExitGame?=Am bu toil leat an geama fhàgail?
    Yes/no =  Bu toil/Cha bu toil

    *resolved in GAE and MegaGlest* - strings removed
  • Also, can a line break be added before ExitGame?
    My string is too long and I can't make it shorter. A new line would give me more space.

    *partially resolved in GAE* - automatic line break, but window title still a bit too long

Pages: 1 [2]