Forum Discussion
Language can be understood perfectly without diacritical. Short message are widely spread and don�t use them.
Some banks (Ex a Caixa) do not accept diacritical�s in the transaction!!!!
Most important setbacks:
a. - Not being able to filter words with diacritical�s.
What I do in some cases I have to Data fields. One with diacritical�s to view en another one without just to filter.
Would be nice to have a javascript code to substitute before importing and transforming csv.
I use some regex such as
var valorFormat = row["valorUnitario"].replace("R$", "\ ");
var valorFormat2 = valorFormat.replace(/\s+/g, '');
csv_line.push(valorFormat2);
But have not managed to be consistent in the transformation.
Would be nice to be able to substitute while writing, in SOME ESPECIAL DATA FIELDS THAT YOU PREVIUSLY KNOW YOU ARE GOING TO FILTER
b. - After importing something from excel etc. Database gets corrupted with strange signs.
Most of this things can be solved by Orienting customers how to set browsers and excel, but there is no a One Place to look at, so we learn by experimentation.
ONE IMPORTANT THING: CSV formatting here in brazil is a little bit crazy and does not seem to follow a strict standard. Sometimes comma sometimes semi coma.
When exporting form excel you must now what CSV format to use (WINDOWS CSV).
Find difficulties in Using quick base native synchronise CSV for that reason. I don�t use it a lot because i usually transform before importing
c. - Most users get paralyzed when they see a pop up in �ENGLISH�.
There are few pops up so when they learn what it is it is ok. Even though for a deployment I think that service worker translation can be a solution.
There isa standard Brazilian keyboard used and if so are there special keys or key combinations used to enter diacritical characters?
YES
Brazilian formatting conventions are used for (a) date and time and (b) currency values (where are comma's and periods used)?
Date ddmmYYY
Number xxx.xxx.xxx,xx
4.- In some cases you have to create an extra Formula Field to get things done in table to table import etc but is quite simple.
- _anomDiebolt_7 years agoQrew EliteI read your fully reply - I think we can address all of these issues satisfactorily.
The only think I can't address is the encoding of QuickBase's pages which is Windows-1252 not the more common UTF-8. There is some voodoo going on which I don't completely understand as this is a bit of an esoteric topic.
When I did the English to French conversion it overlapped in time with QuickBase's move to new servers and at various times people were reporting the dreaded REPLACEMENT CHARACTER showing up randomly and QuickBase pages were at different times reporting a charset of Windows-1252 and UTF-8. That problem has been fixed in terms of the user interface but there are some things I don't completely understand about Windows-1252 and why QuickBase is even using it.
Hey I got an idea - let's conjure my favorite community manager and product manager by name and see what they have to say:
�������������������������������������Hey Evan Marrtinez and Sam Jones why is QuickBase using Windows-1252 encoding and what are the plans for using UTF-8?
U+FFFD � REPLACEMENT CHARACTER used to replace an unknown, unrecognized or unrepresentable character
https://en.wikipedia.org/wiki/Specials_(Unicode_block)