报告 • Board Game Arena

所有案件

无条件投降！二战欧战风云的案件

#28306: "Split up long strings in the translation system"

rejected: 开发者认为这是个馊主意，或投资报酬率过低

这个案件是关于哪方面的？

无条件投降！二战欧战风云 #124622537

发生什么事? 请从下方选择

建议：依我来看，接下来的这些方法十分有助于改善游戏的实现

发生什么事? 请从下方选择

建议：依我来看，接下来的这些方法十分有助于改善游戏的实现

请检查是否已有同课题案件

若肯定，请「投票」给这桩案件。最高票的案件将「优先」处理！

#	Status	Votes	Game	Type	Title	Last update

细节描述

案件历史

2020年Nov16日 23:08 • KongKing123 • 此建议尚未被开发者分析过:

Example of a string that's way too long:

"
This represents superior planning, intelligence, materiel, etc. The phasing faction may put a Surprise Attack marker in a hex by performing a Special Marker Action (6.1). Reminder: This marker cannot be placed during a unit’s activation. More than one Surprise Attack may be placed in the same Sub-Phase, but no more than one in the same hex. Immediately after placing the marker, if the placement hex is part of a Sea Zone (1.3.6), the phasing faction declares whether the marker is considered in the hex or in the Sea Zone. It cannot be considered in both. Once declared, it is considered in that location for the remainder of the Actions Sub-Phase. • If it is in a hex, the phasing faction applies a +1 DRM to any combat against a unit defending in a hex within a 2-hex range of the marker. If both sides committed an air unit to a ground combat, this DRM is applied to the air combat if the defending ground unit is within range of the marker. There is no DRM for an air/naval combat occurring within a Sea Zone, even if the placement hex is part of that Sea Zone. Example: The Western faction puts a Surprise Attack marker in 2912 and declares it is being placed in the hex. Later, the Axis faction intercepts a Western convoy performing naval movement in Sea Zone 10. Even though hex 2912 is part of Sea Zone 10, the convoy does not receive the Surprise Attack marker’s DRM in the interception’s air/naval combat. • If it is in a Sea Zone, then within that Sea Zone (including all its coastal hexes and any port hex within it), the following applies. ♢ For any air/naval combat, the phasing faction applies a +1 DRM. There is no DRM for a ground combat. ♢ The phasing faction may perform a Carrier Strike (6.4.5). The carrier unit does not have to start in the Sea Zone with the Surprise Attack marker. ♢ The phasing faction may perform one Amphibious Invasion (6.3.2) per Surprise Attack marker. The phasing faction cannot declare the same invasion hex more than once per Actions Sub-Phase. Important: If more than one Surprise Attack marker is on the map, only one +1 DRM per combat is applied from these markers. A Surprise Attack marker has a country specification, but any friendly unit may receive the benefits listed above. The country specification denotes who buys the marker in the Mobilization Phase so that it may be used again later. When removed at the end of the phasing faction’s Actions Sub-Phase, put it in its Faction Card’s Surprise Attack Marker Holding Box. It may be bought back in a Mobilization Phase (8.3).
"

---

Example of a string that's long, but still workable:

"
Maybe doing nothing while Hitler conquers Europe is not a good idea. This marker is put on the Turn Track due to the East Invaded (13.3) or West Invaded (13.8) Conditional Event. If both the Appeasement and Nazi-Soviet Pact policies have already ended when this marker is removed from the Turn Track, no event occurs and remove this marker from the scenario. Otherwise, the Allied faction with the policy in effect rolls a die. If the result is 1-3, put the marker on the next turn on the Turn Track. If the result is 4-6; that policy ends.
"

2020年Nov17日 07:36 • ufm • 此建议尚未被开发者分析过:

I did all of them already. Surely felt they too long to be translated as a single string, but actually it was easier to translate because I didn't have to look through every text of the matching section in translation HQ to translate it.

2020年Nov28日 16:21 • Erwt • 此建议尚未被开发者分析过:

Most of the very long strings are texts that contain the following elements:

1) Introduction that describes what a specific special marker represents.
2) Explanation of how and when to use it.
3) Enumeration of exceptions and special cases.

Things would be more manageable to translate if these 3 parts would be split up.

Especially since the fields these strings are in have the same readability as reading an End User License Agreement :(

2020年Nov28日 18:23 • Lunalol • 开发者认为这是个馊主意，或投资报酬率过低:

Sorry, but it not a priority for me and I have no time for that.
These long texts are from rulebook or playbook.
It can be translated using cut and paste with a text editor.
Every wargame player must use English because most of game are not translated.
It was an option to put tool-tips or not.
Perhaps later...

2020年Nov28日 19:51 • KongKing123 • 开发者认为这是个馊主意，或投资报酬率过低:

Ok, too bad. But maybe something to keep in mind in the future (for new strings for this game or another).

增加一些新内容到这篇报告

任何可能重现这项漏洞或了解你的建议之相关资讯，都请在此填写:

其他的游戏桌 ID / 移动 ID
按 F5 是否解决了这个问题？
问题是否发生了好几次？还是每次都发生？还是时好时坏？
如果你已截取此Bug的屏幕截图（好习惯），可使用任意图片托管服务（例如snipboard.io）上传后，将链接复制粘贴至此处。

取消更新报告

#28306: "Split up long strings in the translation system"

这个案件是关于哪方面的？

发生什么事? 请从下方选择

发生什么事? 请从下方选择

请检查是否已有同课题案件

细节描述

案件历史

增加一些新内容到这篇报告

更改案件状态为：

帮助

贡献

导航

关注我们