Insufficient Boxes For My Address In "Identity" [Questions on localization]

HowardGS

I have an address that has a street name, a complex name, a block number, floor number and door number. Then there is the Town, Principality and Postcode.
To enter all of these long names it means that the first five items are in one box, extend out of view and when entered into an on line page will no doubt be wrongly placed or not fit. When editing they overlap and are unreadable.
I would prefer to have " line 1, line 2, line 3" which makes more sense than if I am working or not.
Also I have a UK IPhone sim, a Spanish IPhone Sim, and an IPad Sim and I would like to label them, not as default, work, or home.
Is there a better way to suit people who don't live on America, as we don't even have zip codes etc.
I note that when editing the Address, it comes out as address when the others are preset with a capital letter. Lots of issues in one simple setup? Or is it me?

Ben

Hi @HowardGS,

Can't say I've ever seen an address quite that complex before. :) Must make manually addressing envelopes a pain.
Additionally most web forms I've seen for ordering only offer at most two address fields in addition to city, state, and zip (or town, principality, and postcode, as appropriate). Is it common for you to see order forms etc that offer three address lines in addition?

Also I have a UK IPhone sim, a Spanish IPhone Sim, and an IPad Sim and I would like to label them, not as default, work, or home.

I'm not sure I follow. Could you please elaborate?

I note that when editing the Address, it comes out as address when the others are preset with a capital letter.

Again, I'm not entirely sure I follow. Where are you seeing this, and what effect does it have?

Please let me know.

Ben

HowardGS

Hello Ben, you have probably guessed I am new to the forum and the software, and whilst I have been a happy Roboform user on a PC for years and now on my IPad and IPhones (2) plus I have a MacBook on order, I was interested in the "cloud" use for synchronisation which is certainly simpler.
Starting with the user info, firstly I don't work as I don't need to so the OCCUPATION, COMPANY, DEPARTMENT, AND JOB TITLE, (I have never seen boxes requiring those before) are overkill, but I have on numerous occasions seen auto fill for three line addresses, plus town, county, and postcode. I live in the UK and Spain, and have three addresss at present. When in Spain I want to auto fill a Spanish address for instance for deliveries, and when in the UK a choice of two addresses for similar reasons depending where I am.
The Spanish address is the problem one as it has line one (a road and street number) line 2 (the private estate name) line 3 (the block on the estate, floor level, and door number), line 4 (the town) line 5, (the principality) line 6 (the postcode). I have in the past minimised these and had items never arrive. It seems the postal system and couriers are somewhat pedantic. Also I am not sure why you list a zip code before the town and principality. It seems like you are deciding how the rest of the world display an address using a U.S. standard. How about recognising one size does not fit all situations and allow user labelling? Also once a long address is entered you can't see it all and if you do an add address it ends up over another entry as over typing.
The phones, I have an IPhone with my SPANISH sim, an IPhone with my UK, sim, and an IPad with its own dedicated sim as in Spain they give you a free second sim and you can split your usage as you please on the same account. The labelling of DEFAULT, HOME, CELL, BUSINESS, are all incorrect as they are all cell phones, nothing to do with business, are all defaults in their own right and all related to my home in some way. Again generic labelling doesn't work and editable is the way to go. When adding a new field I could edit using a capital letter, but I could not delete the preset boxes. I would love to do this as I have created my own entries including phones so the generic ones just double up.

I hope that's clearer as I was hoping to move to 1Password totally and drop Roboform but for every improvement there is at least one detrimental situation that Roboform does better. And it's CHEAPER.

H.

ag_kevin

Hi @HowardGS ,

Thank you for the detailed feedback. The identity item type was designed based on the common fields that are seen on web page forms requiring addresses and phone information. With that in mind, that may explain why some things in the form are designed the way they are.

1. Occupation, Department, and Job title are not required. You can leave them blank and they won't show up when viewing the identity.
2. You are correct in that in many places addresses require more lines to display information. I can make a request to the development team on your behalf to consider this.
3. I don't follow you on the zip code issue. The zip code is listed right before the country field, which is last. This is fairly typical for most countries. Unless you have entered town and principality information in the country field, tt shouldn't be listing the zip code before that. If you can, please post a screenshot (with fake data, of course) showing this issue.
4. The phone number labels are the typical phone number labels that you see on web page forms for the purposes of autofilling. Web page forms asking for different mobile numbers is fairy rare. However, if you have purchased the Pro features, you can add as many custom fields as you like and name the field labels to whatever you like. It currently doesn't have specific phone number fields but you can store phone numbers in a text field though.

I hope this has addressed your concerns. Please feel free to reply if you have further questions or concerns.

ref: OPI-2628

HowardGS

Hi, Thanks for the response.
If the boxes are tagged for certain form filling then whatever I wish to name them shouldn't matter and for a more rounded product suited to more countries perhaps some sort of drop down option would be better? My default is whatever country I happen to be in and I also travel a lot socially. In Romania for example I buy a local sim, therefore in Romania for a month I might like to chose that sim. People are more mobile now and I hope you might consider that fact please.



I have attached 3 spoof entries. They show the edit with half hidden, the entry showing I am filling the correct boxes, and the final entry with the Postcode before the Town, Principality, and Country. The format in the UK and Spain (as provided to me by a Spaniard) is Town, Principality, Postcode, Country. Something is not right here. Also I noticed that for the UK, whilst filling in the box after Town, which we call County, the data did not save and I just did it again at the same time as my spoof entry. On the point of capitals I was able to edit sex to Sex but others I could not. I know correct English is no longer that important to some but I do like to hold on to Name, Address, Date of Birth, Sex, Occupation etc as was intended in our English language. Pedantic I know but also correct as a sentence of one word always starts with a capital letter and the ability to edit for correct English before Mine is degraded even further would be appreciated.

HowardGS

Today I came to the conclusion that whilst 1password will be a useful backup to my Roboform it just isn't good enough to replace it for the following reasons:
It is designed totally for the American market and makes no attempt to respect the other countries address conventions, documents or languages.

Take a simple example other than those in posts above; when creating an address in Spain I chose Spain and it says Spain. Spain is not called Spain when in Spain or linked with a Spanish address. Sure chose Spain but respect the country enough to convert that to Espana. Also don't limit the keyboard to English and Emoji, let those of us who have tried to learn some Spanish or are Spanish, use installed keyboards with the correct Spelling e.g. Málaga.

I like the sync after creation across my IPhone's and IPad, and I like the fingerprint recognition but I don't only want to use Safari, and I don't want to delete boxes just to create more appropriate ones that probably will not auto fill.

I paid for the App upgrade only to find all documentation required me to create pretty much every field myself just to simulate UK documents as opposed to US ones. I am guessing trying to create Spanish forms will be a joke. How you can think I would pay more money for a Mac or PC version is just wishful thinking. The App fee for what I gained was about 700% too high.

I read reviews probably from US users and took the plunge and it reminds me of when I bought software like Windows 95, and Millenium and when software didn't work it was always someone else causing the problem. I am sorry to say that in this case 1Password is the problem unless you stop selling Internationally on the premise that it's universal. In that respect it is a huge fail.

"Back to the drawing board"

littlebobbytables

Hi HowardGS,

In 1Password for Mac and iOS we've attempted to follow Apple's lead when it comes to address formatting and localisation. The idea was to create a more consistent feel between the 1Password and the operating system. Now I'm not going to say we've got it perfect, in creating some screenshots to highlight this I can see certain localisation issues but we're constantly working to improve this.

To put this into context my Mac and iOS devices are set up with the preferred language being English (U.K.) and the region set to United Kingdom.

I don't know if you use Apple's Contacts application or not but if you do you're probably aware that you can change the address formatting to a specific country.

Here are two addresses in a Contact item in Contacts (OS X)

Here are two addresses in an Identity item in 1Password for Mac

and here are two addresses in an Identity item in 1Password for iOS

There are a few items to address when viewing these three images.

1. The localisation between iOS and Mac in 1Password is a work in progress. This is why Mac says post code where iOS says zip. So there is a lack of consistency here.
2. On the Mac I suspect the word state is an error in the UK translation rather than a localisation issue. Region may be a more appropriate word.
3. We use a single set of words to describe the four parts of an address in contrast to Apple who are a little more dynamic e.g. postcode for the UK, ZIP for the US. The set of words we use are dependent on the preferred language set in the OS, at least with the Mac anyway (see 1.).
4. The structure of the address though is consistent over iOS and Mac and consistent with Apple. I know the structure for Germany and Poland are correct from my European friends but I can't comment on Spain.
5. We seem to follow Apple's style for using non-capitalised field titles.

One area where Apple's Contacts application could be seen as more powerful is the ability to add custom field titles. For a telephone number the defaults are limited to mobile or iPhone for non-landline types. You can can add a custom title and my preference has been to set it to "mobile (XX)" where XX is the two letter ISO country code. In 1Password though you would use a custom field set to the telephone type to create the same effect.

Regarding keyboards, I'm not sure I understand the point you've raised. I can easily swap between multiple Apple keyboards, moving freely from English (UK) to Español from within 1Password. Now if your alternative keyboard is a 3rd party offering then we do disable access by default as a security precaution. The reason is many keyboards require full access which does include internet access. It was deemed prudent to disable by default given the sensitivity of the information held in a vault. However custom keyboards can be enabled from within 1Password for iOS' settings in the Advanced screen if the user wishes. Would that explain the absence of a specific keyboard for you?

Going forward.

1. We know we need to improve on multi-line addresses, a shortcoming possibly picked up by following Apple's lead. ref: OPM-1053 & OPI-2628
2. Consistency between the platforms as we improve on the current localisation.
3. When picking a address format, I like the idea of a list of countries localised for the user's specified language but then translated to the specific country for the purposes of displaying e.g. It would list Spain for selection purposes but display España. You may be the first person to request this as I can't find an open ticket on this subject.

Now it may be 1Password isn't for you. We all have to find something that fits in with us. For me it was the fact that I am in control of my vault and it isn't sitting in a server somewhere, possibly in a country that doesn't respect my privacy. In fact that one is something I hear from a number of our users. Still, it's all about finding what works for you.

HowardGS

Thanks for your comprehensive and very professional response. I will review changes and perhaps one day the software may have the International appeal which is lacking from my perspective.
I appreciate your diligence.

Ben

Thank you for your feedback, HowardGS! :)