summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorfrosch <frosch@openttd.org>2013-10-28 12:19:55 +0000
committerfrosch <frosch@openttd.org>2013-10-28 12:19:55 +0000
commitf0fbe7767da7b998d0dd13aa7c37117f333e8f43 (patch)
tree9049c01022c3191442da63141c9211983a803fdb /src
parent0bc436fec91d25058e534b74eb8f62a6278e5434 (diff)
downloadopenttd-f0fbe7767da7b998d0dd13aa7c37117f333e8f43.tar.xz
(svn r25926) -Change: capacious -> high-capacity.
Diffstat (limited to 'src')
-rw-r--r--src/lang/english.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lang/english.txt b/src/lang/english.txt
index 01ca3d9b9..adbb099fa 100644
--- a/src/lang/english.txt
+++ b/src/lang/english.txt
@@ -1587,7 +1587,7 @@ STR_CONFIG_SETTING_DEMAND_DISTANCE :Effect of dista
STR_CONFIG_SETTING_DEMAND_DISTANCE_HELPTEXT :If you set this to a value higher than 0, the distance between the origin station A of some cargo and a possible destination B will have an effect on the amount of cargo sent from A to B. The further away B is from A the less cargo will be sent. The higher you set it, the less cargo will be sent to far away stations and the more cargo will be sent to near stations.
STR_CONFIG_SETTING_DEMAND_SIZE :Amount of returning cargo for symmetric mode: {STRING2}
STR_CONFIG_SETTING_DEMAND_SIZE_HELPTEXT :Setting this to less than 100% makes the symmetric distribution behave more like the asymmetric one. Less cargo will be forcibly sent back if a certain amount is sent to a station. If you set it to 0% the symmetric distribution behaves just like the asymmetric one.
-STR_CONFIG_SETTING_SHORT_PATH_SATURATION :Saturation of short paths before using capacious paths: {STRING2}
+STR_CONFIG_SETTING_SHORT_PATH_SATURATION :Saturation of short paths before using high-capacity paths: {STRING2}
STR_CONFIG_SETTING_SHORT_PATH_SATURATION_HELPTEXT :Frequently there are multiple paths between two given stations. Cargodist will saturate the shortest path first, then use the second shortest path until that is saturated and so on. Saturation is determined by an estimation of capacity and planned usage. Once it has saturated all paths, if there is still demand left, it will overload all paths, prefering the ones with high capacity. Most of the time the algorithm will not estimate the capacity accurately, though. This setting allows you to specify up to which percentage a shorter path must be saturated in the first pass before choosing the next longer one. Set it to less than 100% to avoid overcrowded stations in case of overestimated capacity.
STR_CONFIG_SETTING_LOCALISATION_UNITS_VELOCITY :Speed units: {STRING2}