From 9521f609d89c0e93213ff799e069b6082a9f6e8a Mon Sep 17 00:00:00 2001 From: wisp3rwind Date: Fri, 18 Dec 2020 16:28:35 +0100 Subject: [PATCH] docs: backtick fixes - in the gettext() examples, at least the _() triggers italics - add missing closing backtick --- docs/reference/gtk/question_index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/gtk/question_index.md b/docs/reference/gtk/question_index.md index c080b5d35e..98e69881e6 100644 --- a/docs/reference/gtk/question_index.md +++ b/docs/reference/gtk/question_index.md @@ -97,11 +97,11 @@ the question you have, this list is a good place to start. #define N_(x) x #define C_(ctx,x) pgettext (ctx, x) - You use N_() (N stands for no-op) to mark a string for translation in + You use `N_()` (N stands for no-op) to mark a string for translation in a location where a function call to gettext() is not allowed, such as in an array initializer. You eventually have to call gettext() on the - string to actually fetch the translation. _() both marks the string for - translation and actually translates it. The C_() macro (C stands for + string to actually fetch the translation. `_()` both marks the string for + translation and actually translates it. The `C_()` macro (C stands for context) adds an additional context to the string that is marked for translation, which can help to disambiguate short strings that might need different translations in different parts of your program. @@ -190,7 +190,7 @@ the question you have, this list is a good place to start. encode string literals in UTF-8 by using octal or hexadecimal escapes like `\212` or `\xa8` to encode each byte. This is portable, but modifying the escaped strings is not very convenient. Be careful when - mixing hexadecimal escapes with ordinary text; `"\xa8abcd" is a string + mixing hexadecimal escapes with ordinary text; `"\xa8abcd"` is a string of length 1 ! - Runtime conversion