aboutsummaryrefslogtreecommitdiff
path: root/doc/translation_strings_policy.md
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2015-10-22 18:09:19 +0200
committerMarcoFalke <falke.marco@gmail.com>2015-10-28 22:11:43 +0100
commit040c0ea0935ffa0a23972250c23cd0d7b6b1b702 (patch)
tree909f7fcc87ae78c17de9c4f36ebca500619a8c6f /doc/translation_strings_policy.md
parent6782f58368af09a3507004edc761fb233a95bfae (diff)
downloadbitcoin-040c0ea0935ffa0a23972250c23cd0d7b6b1b702.tar.xz
Init: Cleanup error and warning strings
Also update doc/translation_strings_policy.md
Diffstat (limited to 'doc/translation_strings_policy.md')
-rw-r--r--doc/translation_strings_policy.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/translation_strings_policy.md b/doc/translation_strings_policy.md
index 936a6112c6..b95259cdc9 100644
--- a/doc/translation_strings_policy.md
+++ b/doc/translation_strings_policy.md
@@ -52,7 +52,7 @@ Try to write translation strings in an understandable way, for both the user and
### Do not translate internal errors
Do not translate internal errors, or log messages, or messages that appear on the RPC interface. If an error is to be shown to the user,
-use a generic message, then log the detailed message to the log. E.g. "Error: A fatal internal error occurred, see debug.log for details".
+use a translatable generic message, then log the detailed message to the log. E.g. "A fatal internal error occurred, see debug.log for details".
This helps troubleshooting; if the error is the same for everyone, the likelihood is increased that it can be found using a search engine.
### Avoid fragments