1Password 8: Import or open .PIF file

Hi @Chr1sS

Thank you for your most kind words; they are much appreciated.

The good news is that you were able to achieve your goal. The bad news is that I failed to make it clear(er) that I'm not a 1Password employee, as I don't want anyone to be mislead. I'm keenly aware that there is a significant amount of trust (or code review) required by users to use a tool such as the converter suite given the highly sensitive nature of data such as their passwords and personal life information.

Regarding storing code on GitHub, this has come up a few times. I've considered it, and periodically revisit my thinking and reasoning on this. Thus far, I've avoided it for a several reasons:

1. it adds to my workload and provides me personally with very little benefit
2. it creates yet another branch of communication and tracking (I'm not a fan of multiple mechanisms for bug reporting, issue tracking, feedback). I'm fairly certain, based on feedback, that the vast majority of converter suite users have come in through this forum, and it has seemed best to use their help request thread as the point of communication.
3. my self-imposed requirement is to ensure that (almost all) communication regarding the suite is available in one area, for openness, transparency, any oversight, and long-term trust building / maintenance. It also makes search, and thread referencing much easier. When I have offline conversations, I summarize here.
4. GitHub is not a site / service geared towards non-technical users. A landing page of a listing of code files is just plain wrong for the suite's primary audience.
5. My build workflow for the documentation won't generally work for others, as it requires some local tools and configuration.

That said, I'm still receptive to the idea. I just need a sufficiently large enough overall value-add or benefit to nudge me in that direction.

Related to the sepchar issue, I just now received an email from the developer:

Thanks, fixed, committed and pushed.

MrC