I am in the process of proposing an ongoing automated edit of phone numbers in Brazil. However first the formatting of the numbers needs to be discussed.
In most of the rest of the world, only spaces are used to separate parts of a number (country code, area code, subscriber number). I can see that a lot of numbers in Brazil have variously used hyphens.
My question is in two parts, first what formats should be considered as valid and allowed? (In most other countries where the bot is running this is spaces anywhere in the number, the exact placement of those spaces not being enforced. In the USA it is any combination of spaces and hyphens). I recently changed the website, following the example of Argentina, to allow a hyphen before the final 4 digits, this has dramatically reduced the number of detected ‘issues’.
Please select all formats that should be considered valid and not be affected by an automated edit.
Which of these should be considered allowed formats (other than differences in spaces)
I didn’t want to also add options like +55 AA XXXXXXXX, +55 AAXXXXXXXX which would be allowed if +55 AA XXXX XXXX is allowed.
+55 AA XXXX XXXX
+55 AA XXXX-XXXX
+55 AA-XXXX-XXXX
+55-AA-XXXX-XXXX
+55 AA-XXXXXXXX
+55-AA-XXXXXXXX
0voters
How should number be formatted in suggestions on the website and by the bot edit?
This is for numbers entered in national format or with other characters such as brackets, which would be removed.
+55AAXXXXXXXX
+55 AAXXXXXXXX
+55 AA XXXX XXXX
+55 AA XXXX-XXXX
+55 AA-XXXX-XXXX
+55-AA-XXXX-XXXX
+55 AA-XXXXXXXX
+55-AA-XXXXXXXX
0voters
I am aware of mobile numbers having a 9 after the area code, but did not want to make the polls any more complicated.
Also, the Senate communication manual (usually used in lots of places), says that, in writing, the format should be:
(XX) 1234-5678 (hyphen compulsory) and 0800 123456 (toll-free numbers). It’s not there, but I suppose for mobiles the extra 9 comes bundled with the 1234, no space.
This is what is usually used everywhere, so I expect (and from my experience it’s true) that there will be LOTS of phones formatted like that, basically because people don’t know that standard and this is what’s used in real life.
EDIT: by the way, EveryDoor adds the hyphen automatically when one is adding a new phone in a POI there! For example, if I add +551234567890, it becomes +55 12 3456-7890!
Maybe that explains all of the values without a plus that I have seen then.
That is the format that libphonenumber (the standard for validating and formatting numbers) uses when asked for national format, and there also appear to be quite a few cases like this in OSM data.
I have said it elsewhere, but will repeat now, that clearly there should be a distinction between how phone numbers are formatted in the database and how they are displayed to users. However, I do not know of any apps that actually reformat numbers for users (e.g. displaying them in national format without the country code when you are in that country).
I agree with you. If I had time I could probably take a go in CoMaps, but it’s not on my priorities. But indeed it would be great! (also, please check my edited message above about EveryDoor, it can be a point of conflict)
O fato da discussão estar se dando em idioma que não o português, infelizmente já afasta boa parte do pessoal de participar, apesar de ter a funcionalidade para traduzir, acaba sendo uma dificuldade a mais para ficar por dentro do assunto. Creio que muitos a desconhecem.
Dica para quem ainda não conhece a funcionalidade (destacada em vermelho na imagem), ela fica logo abaixo das mensagens.
Indeed, sorry for that. I was not sure if it was better to machine translate first or just let people do it on the site. I guess I read the forum enough that I am familiar and comfortable with using the translate button.
Edit: would you prefer that this be reposted in Portuguese, by either me or someone else?
Sugiro deixar como está mesmo. Também não sei se o pessoal tem opinião formada sobre o assunto, mas creio que a maioria não, assim como eu também não tenho. Compartilhei no grupo Telegram da Comunidade para ver se mais gente participa.
Olhando as fachadas de lojas notei também que não há consenso das pessoas quanto ao assunto.
Algumas obervações:
Apenas números (sem espaços, traços, pontos, etc): Faz caber mais números no valor (caso um local tenha vários números telefônicos). Porém dificulta a leitura e conferência do valor por parte de quem está cadastrando, ou conferindo o cadastro, no OSM.
O traço “-”, por não costumar estar no layout principal do teclado em dispositivos móveis, acaba gerando ao usuário ter que teclar em mais teclas para formatar certinho conforme esse padrão. O que para mim, parece uma desvantagem neste caso.
Para o software que vai consumir este dado, não vejo dificuldade alguma em reformatar o número da maneira que preferir para mostrar ao seu usuário, desde que todos os digitos estejam lá.
