所有案件
Pax Renaissance 的案件
#118311: "Major ambiguity with ${tkn_playerName} leading to many grammatical problems "
#118311: "Major ambiguity with ${tkn_playerName} leading to many grammatical problems "
這是關於哪方面的案件?
發生什麼事? 請從下方選擇
遺漏翻譯:部分字句顯示為英文而非我的語言
發生什麼事? 請從下方選擇
遺漏翻譯:部分字句顯示為英文而非我的語言
請檢查是否已有同課題案件
若肯定,請「投票」給這樁案件。最高票的案件將「優先」處理!
# | Status | Votes | Game | Type | Title | Last update |
---|
細節描述
• 如果可以的話,請轉貼螢幕顯示的錯誤訊息。
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 請說明你當時想做什麼,你做了什麼,然後發生了什麼事
see above• 你的瀏覽器是什麼?
Google Chrome v121
• 請轉貼未翻譯的英文字句。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 這些文字存在於 翻譯系統 中嗎?若為真,其是否已被翻譯超過 24 小時?
see above• 你的瀏覽器是什麼?
Google Chrome v121
• 請簡明精確地解釋你的建議,以便讓人一目了然。
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 你的瀏覽器是什麼?
Google Chrome v121
• 當你不能動作時,螢幕上顯示什麼?(螢幕全黑?部份遊戲介面?錯誤訊息?)
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 你的瀏覽器是什麼?
Google Chrome v121
• 遊戲規則的哪部分在 BGA 版本有所錯漏?
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 這項違反規則之處可否在遊戲重播中看到?若可以是在哪步?(重播時左上角資訊)
see above• 你的瀏覽器是什麼?
Google Chrome v121
• 你當時想採取哪個遊戲行動?
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 你想觸發這個遊戲行動時做了什麼?
see above• 當你試著這麼做時發生了什麼(錯誤訊息、遊戲狀態條訊息...)?
• 你的瀏覽器是什麼?
Google Chrome v121
• 問題發生在遊戲的哪一步?(當前遊戲指示是什麼)
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 當你試著進行遊戲動作時發生了什麼(錯誤訊息、遊戲狀態條訊息...)?
see above• 你的瀏覽器是什麼?
Google Chrome v121
• 請描述顯示問題。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 你的瀏覽器是什麼?
Google Chrome v121
• 請轉貼未翻譯的英文字句。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 這些文字存在於 翻譯系統 中嗎?若為真,其是否已被翻譯超過 24 小時?
see above• 你的瀏覽器是什麼?
Google Chrome v121
• 請簡明精確地解釋你的建議,以便讓人一目了然。
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• 你的瀏覽器是什麼?
Google Chrome v121
案件沿革
2024年 3月22日 13:30 • Phoxtrot • 開發者尚未重現這項錯誤:
Some related generic consideration:
For the "context" in the traduction center, what would help us for French (but I'm sure other languages too) is something along the line:
- is it a command from the player to the game ( in French we will use the infinitive for that "kill" -> "tuer" )
- or is it instead a command form the game to the player (in French we will use the imperative for that "kill" -> "tuez" )
- or is it a description (this will usually translate into an indicative in French "you kill" -> "vous tuez" but an infinitive can also work)
It is usually best to split sentences than can be used in such different contexts into multiple entries in the traduction center..
------------------------------------------------
Hanging texts like for instance " ( 2 remaining)" can be very delicate and should usually be avoided because:
- the literal translation is "restant" but that is most often not the best translation. If it is instead integrated in each of the sentences that uses it, it's easier to choose the best word for the context.
- "restant" is the masc form. If we don't know the related gender, we should probably write "restant(e)" or "restant·e"
- there might be languages where putting that hanging text at the end will not be normal. And care should obviously be taken so that it still work for right to left languages
Now I understand that this has downsides to: I you have many sentences that can sometimes have that hanging part and sometimes not or sometimes a different hanging part, that can be annoying...
And this can also recoup the recommendation since the hanging part is often present or not depending on whether it is used as a command from the player to the game or as a description.
------------------------------
For the "context" in the traduction center, what would help us for French (but I'm sure other languages too) is something along the line:
- is it a command from the player to the game ( in French we will use the infinitive for that "kill" -> "tuer" )
- or is it instead a command form the game to the player (in French we will use the imperative for that "kill" -> "tuez" )
- or is it a description (this will usually translate into an indicative in French "you kill" -> "vous tuez" but an infinitive can also work)
It is usually best to split sentences than can be used in such different contexts into multiple entries in the traduction center..
------------------------------------------------
Hanging texts like for instance " ( 2 remaining)" can be very delicate and should usually be avoided because:
- the literal translation is "restant" but that is most often not the best translation. If it is instead integrated in each of the sentences that uses it, it's easier to choose the best word for the context.
- "restant" is the masc form. If we don't know the related gender, we should probably write "restant(e)" or "restant·e"
- there might be languages where putting that hanging text at the end will not be normal. And care should obviously be taken so that it still work for right to left languages
Now I understand that this has downsides to: I you have many sentences that can sometimes have that hanging part and sometimes not or sometimes a different hanging part, that can be annoying...
And this can also recoup the recommendation since the hanging part is often present or not depending on whether it is used as a command from the player to the game or as a description.
------------------------------
2024年 3月22日 14:01 • Thalack • 開發者已確認這項錯誤:
Thanks for bringing this to my attention!
I think it should be fine to switch sentences to use ${you}. I set it up this way initially because some of the player names (and 'you' when in the title bar) need to have a text-shadow, but I have found another way to solve that. Alternatively if that doesn't work I can change it to ${tkn_you} as a backup solution. But it will cause some retranslation / extra translations.
I cannot do anything about the context in the translation center. It's just the file name of the file where it's defined.
With the (x remaining) I see your point, but BGA actually recommends to use nested logs to limit the number of translations (though I guess with the amount of text in a game like Pax Ren I am not sure how much that matters). But I will take a look at it as this probably concerns sentences suffering from the ${you} issue as well so I might just be able to change them as a retranslation is needed anyway.
I think it should be fine to switch sentences to use ${you}. I set it up this way initially because some of the player names (and 'you' when in the title bar) need to have a text-shadow, but I have found another way to solve that. Alternatively if that doesn't work I can change it to ${tkn_you} as a backup solution. But it will cause some retranslation / extra translations.
I cannot do anything about the context in the translation center. It's just the file name of the file where it's defined.
With the (x remaining) I see your point, but BGA actually recommends to use nested logs to limit the number of translations (though I guess with the amount of text in a game like Pax Ren I am not sure how much that matters). But I will take a look at it as this probably concerns sentences suffering from the ${you} issue as well so I might just be able to change them as a retranslation is needed anyway.
2024年 3月22日 14:25 • Phoxtrot • 開發者已確認這項錯誤:
Thanks.
Note that some entries will have to be split like the one below as they are used both for 'you' and for third person. I don't think there are that many of them but there are some and it's a bit difficult to detect all the instances from within the game.
${tkn_playerName} must select a Concession to Tax
Note that some entries will have to be split like the one below as they are used both for 'you' and for third person. I don't think there are that many of them but there are some and it's a bit difficult to detect all the instances from within the game.
${tkn_playerName} must select a Concession to Tax
2024年 3月22日 15:08 • Thalack • 開發者已確認這項錯誤:
I just deployed a release to fix this. Please let me know if this is ok now.
The entries that were used for both instances should be split automatically. I basically need to mark a string for translation and BGAs system detects if there are duplicates and only add them once. In the code this is already split so two strings '${tkn_playerName} must select a Concession to Tax' were marked for translation, while now it will be two different ones.
The (x remaining) should also be better translatable now.
The entries that were used for both instances should be split automatically. I basically need to mark a string for translation and BGAs system detects if there are duplicates and only add them once. In the code this is already split so two strings '${tkn_playerName} must select a Concession to Tax' were marked for translation, while now it will be two different ones.
The (x remaining) should also be better translatable now.
為本案件添加內容
任何可能重現這項錯誤或了解你的建議之相關資訊,都請在此填寫:
- 其他同樣狀況的桌號/步數
- 按 F5 是否解決了這個問題?
- 問題是否發生了好幾次?每次都發生?時好時壞?
- 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
更改案件狀態為:
bug?id=118311