In case you are also a non-English user, you may be interested in the following information:
This is a great bit of software, thanks: I’m using 1.3.3 Installer. The release notes to 1.3.0 suggest that some characters display strangely in Excel. I found this in spades when importing French and German text to Excel97 but with an up-to-date version of OpenOffice Calc everything was fine provided I changed the character set on Import to UTF-8.
This version fixes a major bug in v1.3.2:
- Evernote and XML Exports would produce files without data.
This version includes several core improvements to better support other operating systems (especially OSX) and several minor fixes to new features in 1.3.1:
- CSV Export uses the Date Interpreter setting to format output
- All of the default patterns have been reviewed and any issues were corrected. This should not affect working patterns.
- Settings dialog will default to the ‘Application’ page
- In Settings dialog, the default Import and Export Patterns will be automatically displayed
- The program will now place ‘settings.txt’ in a User’s Application Data folder for non-portable installations:
- If you’re migrating from a previous version, your current settings should be copied automatically.
- The precise location of this folder varies by OS.
- This will improve support for systems (like OSX) that do not allow an application to write to the folder that contains the program executable.
- On the back-end, PyQt4 has been replaced by PySide.
- PySide improves compatibility with virtualenv thanks to pip compatibility.
- As an added bonus, it provides a more flexible licensing arrangement.
- If you experience anything odd with the new UI, please report it! I don’t expect any major issues, but I have a brief window where I can reverse this change if it causes widespread problems.
- DaleyKlippings icon has been implemented in more places (installer, uninstaller, main window, taskbar, etc.)
This version includes several minor fixes to new features in 1.3.0:
- Dates will now display (not just edit) in the local format
- When the date language is changed, the editor (and corrected view) will now update
This version includes several significant improvements:
- Import Localization – this version significantly improves support for non-English versions of the Kindle.
- The date-interpreter is now able to accept localized dates (i.e. where months and days-of-week are in a local language). Under Settings, use the “Date Interpreter” dropdown to select the language you wish to use. NOTE: In some cases, date patterns need to be updated to ignore utility words like the Spanish ‘de’ that may be included in the date pattern.
- Some localized Kindles do not use the hyphen to indicate a page range. Instead, they use a word like “152 a 167”. The “Range Divider” option in the settings permits users to specify a custom connector for location and page ranges. NOTE: The default pattern for Page and Location only matches hyphens and numbers. Additional characters must be added to this pattern if you are using this feature.
- Sample patterns for Spanish and German are included. NOTE: These patters will only function correctly if all of the language settings are updated.
- The Date Language setting is also used to determine the way date and time are displayed in the main table.
- CSV Import/Export – This version offers CSV import and export using a fully featured CSV module instead of the Import/Export Pattern system.
- CSV Export was always possible, but this should improve the stability and reliability of the process.
- CSV Import was difficult or impossible using an Import Pattern. This new approach should address most of the potential issues.
- This system has been tested with Excel 2010 and is likely to work with Excel 2007 or newer. Some older versions of Excel do not correctly handle the file type used. Users report that the newest version of OpenOffice Calc does not exhibit these issues.
- Even in newer versions, some characters displayed strangely in Excel. In my testing, the characters were not corrupted and looked fine once the file was imported back into DaleyKlippings (even if other pats of the file were changed)
- While this feature should be a significant improvement on the existing system, it’s impossible to anticipate or test every circumstance. If you experience any issues with the system, please contact us.
- Upgrade Preserves Custom Settings – this version uses separate files for default and personalized settings. This allows you to install a new version of DaleyKlippings over an old version without losing your customizations. In previous versions, you had to manually backup and restore your settings file.
- A side-effect of this change is that Patterns are no longer permanently deleted. If you have not created a new patter with the same name, it can be recovered by manually modifying the “settings.txt” file.
- NOTE: If you create another pattern with the same name, the old pattern will get overwritten.
- Backup Settings – To minimize the odds of data loss, this version writes both a “settings.txt” and “settings.bak”. Even if one of the files gets corrupted during an abnormal exit, the other should not.
- New Version Numbering – From this point forward, DaleyKlippings will use three version numbers: <major>.<minor>.<release>.
- Major versions would involve significant (and usually not-backwards-compatible) changes to the architecture. This is unlikely to occur while this remains a side project of mine.
- Minor versions indicate additional features and are recommended. The mailing list will get notifications about these versions.
- Release versions are reserved primarily for bug fixes. If you aren’t experiencing any of the bugs included in the release, upgrading isn’t critical. The mailing list will only get a notification for these releases if the bug is impacting a wide number of users (whether or not the users realize).
- To ensure that all systems recognize this version as an upgrade, it uses the version number 1.3.0
- Bug Fixes – This version includes a few minor bug fixes
- The Author column should no longer use the Type dropdown
- The Type column should correctly use the Type dropdown
- Both the Location and Page fields should enforce the location patterns
- Fixed default Delimiter to use “==========” instead of “/r/n” to better reflect Kindle defaults.
- If you have localized the terms for “Highlight” and/or “Note”, matching between highlights and notes should be fully functional.