Import from Wallet 4X [Converter Available]
Comments
-
This means that it is possible?
0 -
Ok. Thanks.
0 -
Is German the only language for Wallet 4X?
The converters I create generally target English as the primary language, but some support localized languages. The lookup-tables I use internally are all in English, and I generally want to keep things that way. So if this is a German-only password management program, it will be a little unique. A converter will work fine, but since German is not a language I speak, I'll struggle a bit to understand all the terms used for the categories, fields, export directions, etc.
Also, are you able to export only a subset of records? For example, if I have you create some sample data for me, can you do that, only exporting the samples (and not your private data)? I won't want you to edit the data with an editor, since that may alter the internal format.
0 -
-
Wallet 4i (iOS version of Wallet 4X) supports English.
0 -
Create a couple of records of different types / categories such as the 1Password equivalents of Logins, Secure Notes, and perhaps Credit Cards. Use dummy data. Be sure to use double quotes in some field, such as a password, as well as a comma. Also, in the notes or memo section of an entry, add a multiple line note, and include various Unicode characters such as è, ü, Ę, and æ. Export these records as CSV and send them to me at mike at cappella dot us. You might also send an html export as well.
0 -
Thanks.
Double quotes: Create entries in the various fields that have both commas (,) and double quotes ("), such as:
Password: super"secret,sauce username: joe,the,plumber Field 1: an "entry" with quotes Notes: My multiline notes field that contains Unicode chars: è, ü, Ę, and æ.
These are the characters that need to be properly escaped in CSV exports, and many password managers fail to do so properly.
0 -
I have received your files - thanks.
The CSV data is lossy - it does not preserve Unicode characters, turning abcdè!üĘæ into abcd?!???. So the CSV is not a viable option.
The HTML appears to be sufficient.
To be sure, I'll purchase the app and create the test data I need to verify its convertibility.
0 -
It appears that Subsembly provides a Wallet 4W download for a free 30 day trial, so I am using that to generate test data.
Edit: there is no need to send me additional CSVs. I'm going to parse the HTML, since exporting CSV is too cumbersome; you have to export every folder and subfolder.
But if you can, please tell me the templates you have in use. There are about 20 or so in the program, and I'll implement the ones you use first so that I can get your data converted as quickly as possible.
In it, I discover that you can both set the delimiter (which defaults to semicolon), and the encoding (which on Windows defaults to Windows-1252). Can you re-export and email to me the test CSV files you generated for me, with the delimiter set to comma, and the encoding set to UTF-8? See screenshot.
I believe this should make the CSV lossless and I can use that to verify my test data is similar to your version from the App Store.
0 -
That's perfect. I'll have a converter done tonight California time
0 -
I have the converter working with a few limitations:
- I do not yet have all the categories completed. I have: address, bankacct, creditcard, email, login, software, and notes.
- I have only partially localized the converter. I will need your help in localizing the remaining strings. Until the strings are localized, some entries will be mis-categorized as Secure Notes. There is a languages file that you will update with the English to German string names.
- I have not yet updated the README file for this converter, specifically the export instructions. You'll want to export your data to HTML, and convert that file.
- I have not tested it against the App Store version of Wallet 4X, but rather Wallet 4W (the Windows counterpart). The data should be the same or very close.
- Sub-folders are not being captured. Only the top-level folder is captured. There is some ambiguity in the HTML, and I'm not certain I can capture deeper folder levels (the entries are captured, just not the sub-folder hierarchy. Folder names get stored in Tags).
Here's how to start testing the converter.
- Download the 1.09 version from Testing Bits, as per the directions in the first post of the converter suite thread.
- Export your Wallet 4X data as HTML, and follow the instructions in the README.pdf. The converters name is wallet4.
- Add the --lang option to the command line, to tell the converter to use German (I believe that's your language). The option you will add will be
--lang de.
Your command will look basically like this:
perl convert_to_1p4.pl wallet4 ~/Desktop/wallet4x_export.html -v --lang de
Once you've imported the data, examine the records. You'll see some did not make it into the correct category, and you'll find certain fields are in the entry's Notes section. This will most likely be because there are missing translation strings in the file Languages/wallet4.de.txt. Edit that file with a text editor and add the strings, following the format in the file. You need to match the English names found at the top of the file Converters/Wallet4.pm. In the screenshot below, you the English name Password is added to the Languages/wallet4.de.txt as the entry:
"Password" = "Kennwort"
You only need to add entries if an entry is being incorrectly categorized, or if a field that should be placed into a stock 1Password field is going into Notes. The supported stock 1Password fields that are also used by Wallet 4 are shown in the %card_field_specs table.
Here's how my sample data HTML in English looks against your sample HTML export data - you can see the string mappings:
After you add more localization entries, you can re-run the converter. You may want to delete your entries in 1Password, or leave them and compare your before and after.
Once you have a working Languages/wallet4.de.txt file, I'd like to get your updates to add to the converter suite.
Let's take the remainder of this offline - send me an email as we work through the details, since it is easier to work in email than the forums here.
0 -
I've done more work on the converter to handle all of the stock folder/categories - please wait until I update the 1.09 version in Testing Bits. A Favorites entry or TAN lists will break parsing, and my update will resolve this.
I'll post here when it is ready.
0 -
Hi @masc,
The 1.09 version in Testing Bits has been updated and is ready for you to test. It now supports the folder hierarchy (as tags, and also as folders with the --folder option enabled). The README.pdf has been updated.
Sorry about the delay in this. To support folders properly, I had to rewrite how I was processing the HTML structured data. I'm much happier with it now. :-)
0
