From 4e76651dbaf6a0159f2117482d778ff69127fdea Mon Sep 17 00:00:00 2001 From: Lasse Collin Date: Tue, 24 Feb 2026 18:34:19 +0200 Subject: [PATCH] Fix typos and grammar in comments and docs Fixes: https://github.com/dotnet/runtime/pull/124003#discussion_r2789354505 Fixes: https://github.com/dotnet/runtime/pull/124003#discussion_r2789354515 Fixes: https://github.com/dotnet/runtime/pull/124003#discussion_r2820960196 --- po/Makevars | 2 +- src/common/tuklib_gettext.h | 4 ++-- src/common/tuklib_mbstr_wrap.h | 4 ++-- src/common/w32_application.manifest.comments.txt | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/po/Makevars b/po/Makevars index 0d9182e4..b2d8a7cf 100644 --- a/po/Makevars +++ b/po/Makevars @@ -14,7 +14,7 @@ subdir = po top_builddir = .. # These options get passed to xgettext. -XGETTEXT_OPTIONS = --add-location=file --no-wrap --keyword=_ --keyword=N_ '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpret as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."' +XGETTEXT_OPTIONS = --add-location=file --no-wrap --keyword=_ --keyword=N_ '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpreted as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."' # This is the copyright holder that gets inserted into the header of the # $(DOMAIN).pot file. Set this to the copyright holder of the surrounding diff --git a/src/common/tuklib_gettext.h b/src/common/tuklib_gettext.h index e5ad5e6f..258156f2 100644 --- a/src/common/tuklib_gettext.h +++ b/src/common/tuklib_gettext.h @@ -41,11 +41,11 @@ #define N_(msgid) msgid // Optional: Strings that are word wrapped using tuklib_mbstr_wrap may be -// marked with W_("foo) in the source code. xgettext can then add a comment +// marked with W_("foo") in the source code. xgettext can then add a comment // to all such strings to inform translators. The following option needs to // be added to XGETTEXT_OPTIONS in po/Makevars or in an equivalent place: // -// '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpret as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."' +// '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpreted as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."' // // NOTE: The double-quotes in the --keyword argument above must be passed to // xgettext as is, thus one needs the single-quotes in Makevars. diff --git a/src/common/tuklib_mbstr_wrap.h b/src/common/tuklib_mbstr_wrap.h index 4e2f297d..a13be3a9 100644 --- a/src/common/tuklib_mbstr_wrap.h +++ b/src/common/tuklib_mbstr_wrap.h @@ -28,10 +28,10 @@ TUKLIB_DECLS_BEGIN /// One or more output lines exceeded right_margin. -/// This only a warning; everything was still printed successfully. +/// This is only a warning; everything was still printed successfully. #define TUKLIB_WRAP_WARN_OVERLONG 0x01 -/// Error writing to to the output FILE. The error flag in the FILE +/// Error writing to the output FILE. The error flag in the FILE /// should have been set as well. #define TUKLIB_WRAP_ERR_IO 0x02 diff --git a/src/common/w32_application.manifest.comments.txt b/src/common/w32_application.manifest.comments.txt index de5c2105..16f79ff0 100644 --- a/src/common/w32_application.manifest.comments.txt +++ b/src/common/w32_application.manifest.comments.txt @@ -37,7 +37,7 @@ This is useful for programs that use main(): * UTF-8 allows such programs to access files whose names contain characters that don't exist in the current legacy code page. However, filenames on Windows may contain unpaired surrogates - (invalid UTF-16). Such files cannot be accesses even with the + (invalid UTF-16). Such files cannot be accessed even with the UTF-8 code page. * UTF-8 avoids a security issue in command line argument handling: