Non-US use cases

Use cases that should work:

1. The standard feature of ImportQIF is to add the account name  and type to a QIF file so that Quicken will allow it to be imported into Quicken.  Since ImportQIF doesn't change any of the existing QIF data if the QIF file is compatible with the version of Quicken that it is being imported into, then this functionality will work for basically any known QIF file.
2. ImportQIF will now convert most non US date formats to the US format during a QIF to QIF conversion if the Non US Date option is used, but note that means that the converted QIF can only be imported into a US version of Quicken.
3. If your data is using this format for currency 1.000.000,00 (instead of 1,000,000.00) be sure to select the Comma Decimal Mark option.
4. If you are using a version of Quicken other than the US or Canadian version and it takes a QIF file date format other than MM/DD/YYYY, you can now select a date format for the output QIF (Converted.QIF) in the Non Standard Options section on the Options tab.  The Australian version of Quicken from Reckon needs the DMY format selected.

Things that might cause problems:

1. Non English characters.  Actually ImportQIF should just pass the characters through to Quicken and it will be up to Quicken to do the right or wrong thing (most likely wrong thing). It has been confirmed that at least with the US version of Quicken (and mostly likely all versions of Quicken), Quicken does not support Unicode characters.  That means that Quicken will not support any character set that needs two bytes per character and most likely not display any non English characters correctly.
2. The feature to automatically import the QIF into Quicken is dependent on finding Quicken's main window and selecting certain menus/buttons so it is language dependent.  So, this feature presently will only work if Quicken is in English.

Based on feedback:
Whether I will work on any other these problems depends on the feedback I get on the need for them.