Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
In the world of internationalization, CLDR (Common Locale Data Repository) seems to be the ultimate database and as I learned, many systems derive their locale data from that.
However, I compared CLDR data and the locales in Windows 7 and currency formatting is different in many cases.
For example, Canadian dollar in locale "English (Canada)" is formatted as follows:
Windows: $1,235.00, -$1,235.00
CLDR...: $1,235.00, ($1,235.00)
Or let's take Spanish (Colombia) and Colombian peso:
Windows: $ 1.235,00, ($ 1.235,00)
CLDR...: $1.235,00, -$1.235,00
Note variations in negative numbers and spacing. What should I think of this? Most likely there are more such differences. Are both formatting rules OK, or could it happen that one is perceived by local users as wrong?
Although it is not programming related, I will try to answer your question.
I once asked on CLDR's internal mailing list about (incorrect) Polish date formats and suggested changes to it providing legal (Polish Standard) reference. The answer was that CLDR tries to follow national standards, but sometimes it might be a good idea to use commonly used format instead.
There are two answers to your question:
either the format defined is more commonly used than the one specified by the national standard
or simply there is an error in the definition - browse CLDR's bug tracking system, maybe there is (or was) something about it
As for Microsoft, I believe they are trying to follow national regulations and standards.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
has anyone had any experience with ISOBUS Iso-XML (ISO 11783-10)?
I would like to convert some geojson and/or shapefiles (.shp) to this format but am having trouble finding any information.
The specification of ISO 11783-10 is not free. You can buy the specification (google for "ISO 11783-10"), the documentation is high quality and affordable (I'm not affiliated in any way). The bought documents are distributed with some "license" and will be marked with your name, so buyers will be reluctant to share them. There are many concepts involved and details are cryptic, therefore you really need the specification to work with this format.
If you write source code encoding/decoding this format, it will depend on the specification. Distributing your source code + documentation might or might not infringe on the IP/license (I'm not a lawyer). Publishing detailed responses on this subject in open fora on the internet might or might not infringe.
There are quite some developers writing code which deals with ISO 11783-10, but I think the scarcity of freely available source code (e.g. on github) and open discussions on internet is a direct effect of the specification publication policy. It's sad because this domain is complex, has high impact, has many details which are very instance-specific (e.g. for a specific vehicle-manufacturer, accidental complexity), so open discussions and source code could improve productivity for many.
Agleader software SMS Basic has the option to export shapefiles to ISOBUS format.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have a weird requirement where all my data to be displayed in the app is coming from a remote server. The data consists of simple text, numbers, dates and prices. Now, had all this data been static, the task was simple but here the problem is that the data is dynamic (coming from the server) and also the app has to be localised in at least 20 languages. The biggest challenge is to convert the price values into user selected currencies on his device settings on the run.
For currency conversion, you can use the Yahoo API. Examples can be seen in this StackOverflow question.
http://finance.yahoo.com/currency-converter/#from=USD;to=EUR;amt=1
This url format could be used to fetch conversion rates in different formats.
http://download.finance.yahoo.com/d/quotes.csv?s=AUDUSD=X&f=nl1d1t1
Substitute quotes.csv with appropriate format and parameters with the required codes
As far as localization of your text coming from the server, that's a much more difficult problem. I think it would be very difficult to translate this "on the fly". The correct solution is to include the language in the request and have the server return any text in the requested language.
I guess another approach you could take (which may not be feasible depending on how many different strings you are dealing with) is enumerate all the possible strings returned from the server. Then take the more traditional approach of having these strings translated and included in your app.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have been trying to create a game using OpenEars. I am using dynamic language model method. But the performance is not up to the mark. Recognition is very low. Is there any advantage in using static language model ?? Any other method to improve speech recognition ???
OpenEars developer here. There are a few things that can result in sub-par recognition. Here are the really big ones:
Testing recognition using the Simulator rather than a real device
Having misspelled words in your language model (this is a big one
that accounts for a very large number of reported issues – if the
word is misspelled, how will its correct pronunciation be found or
derived and entered in the phonetic dictionary? It can't be, and then
correct pronunciations get false negatives)
Having extraneous punctuation in your language model. Check this out by taking a look at the .arpa file contents and the .dic file contents and seeing if the entries in each seem to match each other or not.
Having a native-speaker accent which is very different from the US accents the acoustic model is trained with, or having a non-native-speaker accent (this isn't fair, but it's reality)
Having the language model largely consist of non-English words such as non-English last names, non-English street names, or intentionally-misspelled band/startup names, since all pronunciation ends up being estimated.
But static language models versus dynamic language models have never been a big consideration for accuracy levels. If you'd like to troubleshoot this with me further I'd recommend that you visit the OpenEars support forums where I'd be happy to help with that, since Stack Overflow is not intended for ongoing back-and-forth troubleshooting processes and this is probably one of those.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I currently use the Google Translate API (v2) to translate content from US English into various other languages that we support in our software. We then have a process whereby users can submit translation corrections so that we end-up with fairly well-done translations.
We would like to now add support for UK English so that our English-speaking software users in the UK may have a better user experience.
Is there any way to automate the conversion between US English and UK English, or do we just have to manually fix everything?
Don't know of anything automatic. But you could try to identify the most common differences and then search for them.
There is a list here:
http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences
This would at least help with the manual effort.
Here are two tools I have found to do this:
http://www.us2uk.eu/ (dead website)
http://www.infoenglish.net/american-to-british-english/
I haven't tried these on large text blocks, however.
There's another tool which is available:
https://codewordsolver.com/american-british-english-translator (online)
https://github.com/hyperreality/American-British-English-Translator (source code)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Unfortunately, I can't use rtf2latex2e because it says that DropUNIX "no longer supports the classic environment". I barely know what I'm doing otherwise, besides dropping my .rtf file onto the DropUNIX program.
What else can I use? I don't mind which type of file it is I'm converting to LaTeX (.doc would also be OK, as long as it keeps my formatting).
I am using Mac OS 10.5.8.
Open Office can. Download it.
See the fmtconv question on the UK TeX FAQ, or, more specifically, the page on Converters from PC Textprocessors to LaTeX - Overview, which is specifically about this question and has many many examples. This general list of word-processor filters may help too.
UnRTF claims to be able to convert RTF to LaTeX as well as other formats (e.g. HTML). It claims to support HTML best, so perhaps RTF->HTML->LaTeX (e.g. with html2latex) might work better. I haven't actually tried any of this though.
Make your rtf/doc document into docx, and convert it using docx2tex.
You need the System.IO.Packaging .NET class to get this to work, which is no problem if you are using Windows, and is in principle supported by Mono if you are not. If anyone has success doing this with Mono, I'd like to hear of your experiences: this didn't work a year or so ago, but their implementation of that class has improved since then.
I say more about the utility in an answer at tex.stackexchange. Suffice it to say that I consider this by far the cleanest, most Latex-friendly option out there.