diff options
| author | Behdad Esfahbod <behdad@src.gnome.org> | 2008-12-15 20:30:18 +0000 |
|---|---|---|
| committer | Behdad Esfahbod <behdad@src.gnome.org> | 2008-12-15 20:30:18 +0000 |
| commit | 6afcfe2bce6eeb82ab08efe99003ecc3cd2c1200 (patch) | |
| tree | 1ed24f4229a3576bdf62ea610b9bff67f9d3e9c9 | |
| parent | ca92a5e890704d87d6f5d5b9753c57994dc8dfa6 (diff) | |
| download | vte-6afcfe2bce6eeb82ab08efe99003ecc3cd2c1200.tar.gz | |
Fix doc syntax
svn path=/trunk/; revision=2347
| -rw-r--r-- | src/vteunistr.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/vteunistr.c b/src/vteunistr.c index 75054f4f..f324497c 100644 --- a/src/vteunistr.c +++ b/src/vteunistr.c @@ -49,9 +49,9 @@ * form it. That's what VteUnistrDecomp is. That is the decomposition. * * We start giving new vteunistr's unique numbers starting at - * VTE_UNISTR_START+1 and going up. We keep the decompositions in a GArray, + * %VTE_UNISTR_START+1 and going up. We keep the decompositions in a GArray, * called unistr_decomp. The first entry of the array is unused (that's why - * we start from VTE_UNISTR_START *plus one*). The decomposition table provides + * we start from %VTE_UNISTR_START plus one). The decomposition table provides * enough information to efficiently answer questions like "what's the first * gunichar in this vteunistr?", "what's the sequence of gunichar's in this * vteunistr?", and "how many gunichar's are there in this vteunistr?". |