보고 • Board Game Arena

모든 보고

무조건 항복 보고

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

rejected: 개발자는 이 제안이 좋지 않거나 이점에 비해 너무 많은 노력이 들어간다고 생각합니다

무엇에 대한 보고입니까?

무조건 항복 #124622537

무슨 일이 발생했나요? 아래에서 선택하세요

제안: 이 기능을 사용하면 아마 게임 구축을 크게 향상시킬 수 있을 것입니다

무슨 일이 발생했나요? 아래에서 선택하세요

제안: 이 기능을 사용하면 아마 게임 구축을 크게 향상시킬 수 있을 것입니다

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

그렇다면, 이 보고를 추천해주세요. 추천을 가장 많이 받은 보고부터 우선적으로 처리됩니다!

#	Status	Votes	Game	Type	Title	Last update

상세한 설명

보고 이력

2020년 Nov 16일 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년 Nov 17일 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년 Nov 28일 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년 Nov 28일 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년 Nov 28일 19:51 • KongKing123 • 개발자는 이 제안이 좋지 않거나 이점에 비해 너무 많은 노력이 들어간다고 생각합니다:

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

리포트에 내용 추가하기

여기에 버그를 재현하거나 당신의 제안을 이해하는 데 관련 있는 내용을 아무것이나 남겨주십시오:

다른 테이블 번호 / 수 번호
새로고침을 해서 문제가 해결 되었습니까?
문제가 얼마나 자주 일어났습니까?
이 버그(좋은 예시)에 대한 스크린샷이 있으면, 호스팅 서비스의 그림을 업로드하고 링크를 복사/붙이기할 수 있습니다 (예를 들어 snipboard.io).

취소 업데이트 보고

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

무엇에 대한 보고입니까?

무슨 일이 발생했나요? 아래에서 선택하세요

무슨 일이 발생했나요? 아래에서 선택하세요

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

상세한 설명

보고 이력

리포트에 내용 추가하기

보고의 상태를 다음으로 변경:

도움말

기여하기

탐색하기

저희를 팔로우해주세요