applied typos and spelling error fixes patch from Olly Betts
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15779 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -149,7 +149,7 @@ the full control she needs.
|
||||
The comment lines beginning with <KBD>#,</KBD> are special because they are
|
||||
not completely ignored by the programs as comments generally are. The
|
||||
comma separated list of <VAR>flag</VAR>s is used by the <CODE>msgfmt</CODE>
|
||||
program to give the user some better disgnostic messages. Currently
|
||||
program to give the user some better diagnostic messages. Currently
|
||||
there are two forms of flags defined:
|
||||
|
||||
</P>
|
||||
@@ -171,7 +171,7 @@ search only. See section <A HREF="gettext_5.html#SEC26">Fuzzy Entries</A>.
|
||||
<DT><KBD>no-c-format</KBD>
|
||||
<DD>
|
||||
These flags should not be added by a human. Instead only the
|
||||
<CODE>xgettext</CODE> program adds them. In an automatized PO file processing
|
||||
<CODE>xgettext</CODE> program adds them. In an automated PO file processing
|
||||
system as proposed here the user changes would be thrown away again as
|
||||
soon as the <CODE>xgettext</CODE> program generates a new template file.
|
||||
|
||||
@@ -199,7 +199,7 @@ not having GNU Emacs handy should carefully continue reading on.
|
||||
<P>
|
||||
Each of <VAR>untranslated-string</VAR> and <VAR>translated-string</VAR> respects
|
||||
the C syntax for a character string, including the surrounding quotes
|
||||
and imbedded backslashed escape sequences. When the time comes
|
||||
and embedded backslashed escape sequences. When the time comes
|
||||
to write multi-line strings, one should not use escaped newlines.
|
||||
Instead, a closing quote should follow the last character on the
|
||||
line to be continued, and an opening quote should resume the string
|
||||
@@ -540,7 +540,7 @@ merely use <KBD>x</KBD> for making the switch.
|
||||
There are many different ways for encoding a particular string into a
|
||||
PO file entry, because there are so many different ways to split and
|
||||
quote multi-line strings, and even, to represent special characters
|
||||
by backslahsed escaped sequences. Some features of PO mode rely on
|
||||
by backslashed escaped sequences. Some features of PO mode rely on
|
||||
the ability for PO mode to scan an already existing PO file for a
|
||||
particular string encoded into the <CODE>msgid</CODE> field of some entry.
|
||||
Even if PO mode has internally all the built-in machinery for
|
||||
|
Reference in New Issue
Block a user