📅 Original date posted:2012-08-12
📝 Original message:On 11.08.2012 20:56, Wladimir wrote:
> Duplicate strings are not a problem. Some strings are used multiple
> times in the program, and thus appear multiple times in the translation.
> This is because there are cases in which a string that is the same in
> English is translated differently in another language based on the context.
That makes sense. But it's hard to translate when you just see the same
string twice and don't know the context where it will be used.
> At least Qt translator fills duplicates in automatically, with the
> option to change them if desired. I'm not sure about Transifex but I've
> heard it's the same there.
No, I just use copy and paste.
> Use UPnP to map the listening port (default: 0)
> Use UPnP to map the listening port (default: 1 when listening)
>
> The default depends on compiler flags, hence the two messages. I suppose
> the message could be split up, so that "Use UPnP to map the listening
> port" is factored out.
Sorry, forgot there was a compiler flag for this. No need to split this
up. As long as there is no explanation or description for each string I
think it's easier to translate whole sentences.
On 11.08.2012 20:32, Wladimir wrote:
> By the way, by far the most common support request I have at my pool is
>
> users withdrawing coins and not seeing it in their wallet because it's
> not up-to-date with the block chain. Might be worth adding
something in
> the bitcoin-qt GUI to make it more obvious that users can't see new
> transactions and why.
>
> For 0.7 we've added a red "(out of sync)" warning to the balances when
> the block chain is out of date.
Perfect. This will prevent a lot of confusion. Thanks!
Regards,
Geir H. Hansen, bitminter.com
Geir Harald Hansen [ARCHIVE] /
npub1kp…7e3fd
2023-06-07 10:27:57
in reply to nevent1q…jz0t
Author Public Key
npub1kpxa282a99fc93xx30ru3sfmqnyqk3r8aurz3znzxyslhd7felfsg7e3fdPublished at
2023-06-07 10:27:57Event JSON
{
"id": "71e4f8558176edbdfdcf2d6b2062e5ee6c80bd191edc7dd5eceb4573de1f2e08",
"pubkey": "b04dd51d5d295382c4c68bc7c8c13b04c80b4467ef06288a623121fbb7c9cfd3",
"created_at": 1686133677,
"kind": 1,
"tags": [
[
"e",
"1e24f91d557d5b3b5790c0913e37914cf91f091a9accdcc4f0b92b8098b7dfdc",
"",
"root"
],
[
"e",
"4d81c62729e50c9939ff3efd0f2dcdcca39a8d0e6a224e282b07209c7a939ab6",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "📅 Original date posted:2012-08-12\n📝 Original message:On 11.08.2012 20:56, Wladimir wrote:\n\u003e Duplicate strings are not a problem. Some strings are used multiple\n\u003e times in the program, and thus appear multiple times in the translation.\n\u003e This is because there are cases in which a string that is the same in\n\u003e English is translated differently in another language based on the context.\n\nThat makes sense. But it's hard to translate when you just see the same\nstring twice and don't know the context where it will be used.\n\n\u003e At least Qt translator fills duplicates in automatically, with the\n\u003e option to change them if desired. I'm not sure about Transifex but I've\n\u003e heard it's the same there.\n\nNo, I just use copy and paste.\n\n\u003e Use UPnP to map the listening port (default: 0)\n\u003e Use UPnP to map the listening port (default: 1 when listening)\n\u003e \n\u003e The default depends on compiler flags, hence the two messages. I suppose\n\u003e the message could be split up, so that \"Use UPnP to map the listening\n\u003e port\" is factored out.\n\nSorry, forgot there was a compiler flag for this. No need to split this\nup. As long as there is no explanation or description for each string I\nthink it's easier to translate whole sentences.\n\nOn 11.08.2012 20:32, Wladimir wrote:\n\u003e By the way, by far the most common support request I have at my pool is\n\u003e\n\u003e users withdrawing coins and not seeing it in their wallet because it's\n\u003e not up-to-date with the block chain. Might be worth adding\nsomething in\n\u003e the bitcoin-qt GUI to make it more obvious that users can't see new\n\u003e transactions and why.\n\u003e\n\u003e For 0.7 we've added a red \"(out of sync)\" warning to the balances when\n\u003e the block chain is out of date.\n\nPerfect. This will prevent a lot of confusion. Thanks!\n\nRegards,\nGeir H. Hansen, bitminter.com",
"sig": "58ed12891aa296688a56221faefd8ee9a5dded43ef4c8b2d5aba8e67372c8d55f7e627602f4eed1803d51a84987877feb0d2a32e97dffbd89006dd3d26fcdd30"
}