luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-20 14:19:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

gstrfuncs: Use curly quotes in a documentation comment

Browse Source 
Nobody can argue with this: the documentation comment is about, and
contains, Unicode accents.

Signed-off-by: Philip Withnall <withnall@endlessm.com>
This commit is contained in:
Philip Withnall 2017-11-13 10:37:11 +00:00
parent e61c3c628d
commit 880f07f94c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
glib/gstrfuncs.c
View File

@ -3095,11 +3095,11 @@ g_str_tokenize_and_fold (const gchar *string,
* call g_str_tokenize_and_fold() on the search term and * call g_str_tokenize_and_fold() on the search term and
* perform lookups into that index. * perform lookups into that index.
* *
* As some examples, searching for "fred" would match the potential hit * As some examples, searching for ‘fred’ would match the potential hit
* "Smith, Fred" and also "Frédéric". Searching for "Fréd" would match * ‘Smith, Fred’ and also ‘Frédéric’. Searching for ‘Fréd’ would match
* "Frédéric" but not "Frederic" (due to the one-directional nature of * ‘Frédéric’ but not ‘Frederic’ (due to the one-directional nature of
* accent matching). Searching "fo" would match "Foo" and "Bar Foo * accent matching). Searching ‘fo’ would match ‘Foo’ and ‘Bar Foo
* Baz", but not "SFO" (because no word has "fo" as a prefix). * Baz’, but not ‘SFO’ (because no word has ‘fo’ as a prefix).
* *
* Returns: %TRUE if @potential_hit is a hit * Returns: %TRUE if @potential_hit is a hit
* *