1) Add new files to po/POTFILES.in

2) Fix some unmatched quotes (in some cases, they were spelling errors)


git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@18016 57a11ea4-9604-0410-9ed3-97b8803252fd

lib/libqof/backend/file/qsf-xml.h

@@ -127,7 +127,7 @@ available within the available QSF objects.
 
 Some defaults will relate to how to format descriptive dates, whether discount
 should be considered, which account to use for certain QSF data from applications
-that don't use accounts.
+that do not use accounts.
 
 Some defaults are pre-defined and cannot be over-written:
 - qsf_time_now
@@ -159,7 +159,7 @@ QSF deals with partial QofBooks - each object is fully described but the
 book does not have to contain any specific object types or have any
 particular structure. To merge partial books into usual QofBook data
 sources, the map must deal with entities that need to be referenced in
-the target QofBook but which simply don't exist in the QofBook used to generate
+the target QofBook but which simply do not exist in the QofBook used to generate
 the QSF. e.g. pilot-link knows nothing of Accounts yet when QSF creates
 a gncInvoice from qof-datebook, gncInvoice needs to know the GUID of 
 certain accounts in the target QofBook. This is handled in the map 
@@ -262,7 +262,7 @@ a more readable set function.
 #define QSF_CONDITIONAL_ELSE "else" /**< Alternative
 
 if(){} else{} is also supported. Nesting of conditionals causes problems for
-validating the final map against any sensible XML Schema and a map that doesn't 
+validating the final map against any sensible XML Schema and a map that does not 
 validate will be rejected. When editing conditionals in a QSF map, ALWAYS 
 validate the map using xmllint. If necessary, define a variable at the foot of 
 the definitions block, using a similar syntax to a default, then use that 

lib/libqof/qof/qofclass.h

@@ -101,8 +101,8 @@ These are \b NOT the same as the main collections in the QofBook.
 -# Each ::QofCollection contains one or many entities - *all* of a single type.
 -# The entity type within the collection can be determined at run time.
 -# Easy conversions to GList or whatever in the param_setfcn handler.
--# Each parameter can have it's own collection.
--# Each entity can have a different *type* of collection to it's siblings, 
+-# Each parameter can have its own collection.
+-# Each entity can have a different *type* of collection to its siblings, 
 provided that it is acceptable to the set function.
 -# Each object decides which types are acceptable for which parameter in the 
 set functions. This is then part of the API for that object.