Prijava • Board Game Arena

Vse prijave

Prijave igre Unconditional Surrender! World War 2 in Europe

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

rejected: Razvijalci menijo, da to ni dobra ideja ali da je razmerje med stroški in koristmi preveliko

Na kaj se nanaša prijava?

Unconditional Surrender! World War 2 in Europe #124622537

Kaj se je zgodilo? Prosimo, izberi spodaj

Predlog: Menim, da bi igranje igre bistveno lahko izboljšali na naslednji način

Kaj se je zgodilo? Prosimo, izberi spodaj

Predlog: Menim, da bi igranje igre bistveno lahko izboljšali na naslednji način

Prosimo preverite ali že obstaja poročilo o isti zadevi

Če je tako, GLASUJTE za to poročilo. Poročila z največ glasovi se obravnavajo PREDNOSTNO!

#	Status	Votes	Game	Type	Title	Last update

Natančen opis

Zgodovina poročil

Nov 16 th 2020 23:08 • KongKing123 • Tega predloga še niso analizirali razvijalci:

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.
"

Nov 17 th 2020 07:36 • ufm • Tega predloga še niso analizirali razvijalci:

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.

Nov 28 th 2020 16:21 • Erwt • Tega predloga še niso analizirali razvijalci:

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 :(

Nov 28 th 2020 18:23 • Lunalol • Razvijalci menijo, da to ni dobra ideja ali da je razmerje med stroški in koristmi preveliko:

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...

Nov 28 th 2020 19:51 • KongKing123 • Razvijalci menijo, da to ni dobra ideja ali da je razmerje med stroški in koristmi preveliko:

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

Dodaj nekaj k temu poročilu

Dodajte vse, kar se zdi primerno, da bi lahko reproducirali ta napako ali razumeli vaš predlog:

Drug ID mize/ premikanje ID-ja
Ali je F5 rešil težavo?
Se je problem pojavil večkrat? Vsakič? Naključno?
Če imaš posnetek zaslona te napake (priporočljivo), ga lahko naložite na poljuben način (snipboard.io for example) in tukaj prilepite povezavo.

Prekliči Posodobi prijavo

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

Na kaj se nanaša prijava?

Kaj se je zgodilo? Prosimo, izberi spodaj

Kaj se je zgodilo? Prosimo, izberi spodaj

Prosimo preverite ali že obstaja poročilo o isti zadevi

Natančen opis

Zgodovina poročil

Dodaj nekaj k temu poročilu

Spremeni status prijave v:

Pomoč

Prispevaj

Navigacija

Spremljaj nas