Trouble with Identity filling

Erich Zgraggen

I use 1password since ever and I'm very happy with the application. It works wonderful and is very useful.

The only thing I really miss is the implementation of other languages than english.



You would have much, much more users if there would be the possibility using other languages.



For example, using the different profiles saved in 1password is not very helpful on german sites, because it does not recognize the words "Strasse" for street, "Ort" for town .....



Ok, thousands of users and future users would be very appreciate this nice feature.



Hopefully,

Erich

DBrown

Welcome to the forum, Erich, and thanks for letting us know what you'd find useful!

khad

Erich, I split your post from the other thread about 1Password for Windows UI localization since I think you bring up a separate issue: international [i]form filling[/i].



1Password's [i]form filling[/i] [b]already[/b] contains support for international websites. This is not the same as having the UI localized.



1Password fills information based on the underlying field names in the code on each website. For example, if there is a form field that has the word "Straße" next to it, the actual name of the input field to which that text refers may be called "street," "strasse," or "geschmacksache." Each website has complete control over what they name their fields. 1Password is smart enough to deal with multi-lingual variations of common field names for addresses, phone numbers, and the other information used in Identity filling, but it is not comprehensive.



We certainly have our work cut out for us if we try to guess what the trillions of websites on the Internet are going to be naming their fields (in the thousands of languages spoken all over the world). Thankfully, there is a standard!



Now, the tricky thing about HTML, CSS, and other web standards is that they are not mandatory. People just agree, "This is a good way to do this, and if we all do it this way everything will work together better." The [url="http://tools.ietf.org/html/rfc4112"]Electronic Commerce Modeling Language (ECML), Version 2 Specification[/url] is such a standard. When websites follow this international standard when creating forms, 1Password fills in the forms quite well because 1Password also follows the ECML standard for filling forms. Beautiful harmony. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />



Unfortunately, not all websites follow this standard, and we end up back where we started: a seemingly impossible task of keeping track of the form fields used on all the websites in all the languages in the world.



I certainly can't guarantee that it will make a difference, but you might try contacting the owners of the websites where you are having these problems and point them to the ECML specification. Many web developers are not aware of the specification and are happy to make the simple changes to the code of their forms. As a bonus, this can also provide better interoperability for disabled users who rely on assistive technology. Everybody wins!



We have had some very conscientious web developers ask us how to make their websites compatible with 1Password. I am always pleased when I can point them to an international standard which benefits everyone rather than something we just made up that only benefits 1Password users.



With that said, we're excited to tackle this very difficult problem, and form filling is something that we are constantly working to improve (even if some web developers are not so conscientious). Future updates of 1Password will increase the accuracy of the form filler for both credit cards and identities.



Could you provide us with the URL where you are having trouble?



Mit freundlichen Grüßen,