Some fixes and improvements suggested by leper

This was SVN commit r18336.
This commit is contained in:
Itms 2016-06-05 20:48:22 +00:00
parent ee8061d867
commit 260f925ad9
3 changed files with 8 additions and 4 deletions

View file

@ -4,8 +4,12 @@
; * DO NOT EDIT THIS FILE if you want personal customisations: *
; * create a text file called "local.cfg" instead, and copy *
; * the lines from this file that you want to change. *
; * You also need to copy the section tags ([hotkey], [gui], *
; * etc.) for the things you change. *
; * *
; * If a setting is part of a section (for instance [hotkey]) *
; * you need to append the section name at the beginning of *
; * your custom line (for instance you need to write *
; * "hotkey.pause = Space" if you want to change the pausing *
; * hotkey to the spacebar). *
; * *
; * On Linux, create: *
; * $XDG_CONFIG_HOME/0ad/config/local.cfg *

View file

@ -457,7 +457,7 @@ function getHealerTooltip(template)
sprintf(translatePlural("%(label)s %(val)s %(unit)s", "%(label)s %(val)s %(unit)s", template.healer.HP), {
"label": g_TooltipTextFormats.header[0] + translate("Heal:") + g_TooltipTextFormats.header[1],
"val": template.healer.HP,
// Translation: Short for hitpoints (that are healed in one healing action)
// Translation: Short for hit points (or health points) that are healed in one healing action
"unit": g_TooltipTextFormats.unit[0] + translatePlural("HP", "HP", template.healer.HP) + g_TooltipTextFormats.unit[1]
}),
sprintf(translatePlural("%(label)s %(val)s %(unit)s", "%(label)s %(val)s %(unit)s", template.healer.Range), {

View file

@ -2,7 +2,7 @@ As a free, open source game, we don't have the resources to test on a wide range
The following data will be sent to our server:
• A random user ID (stored in %APPDATA%\0ad\config\user.cfg on Windows, $HOME/.config/0ad/config/user.cfg on Unix), to let us detect repeated reports from the same user.
• A random user ID (stored in %APPDATA%\0ad\config\user.cfg on Windows, ~/.config/0ad/config/user.cfg on Unix), to let us detect repeated reports from the same user.
• Game version number and basic build settings (optimisation mode, CPU architecture, timestamp, compiler version).
• Hardware details: OS version, graphics driver version, OpenGL capabilities, screen size, CPU details, RAM size.
• Performance details: a snapshot of timing data a few seconds after you start a match or change graphics settings.