I am building a website with laravel 9 that will store integer numbers/data in English format. But I want to show the numbers/data in another language on my website.
How can I do that?
Related
How do we handle multi language requirements in our customisation? We can use suitescript API nlapiGetContext().getPreference('language') to retrieve the user preference.
My question is - what is the best practice to store the localized strings?
Should these be stored in multiple files in the file cabinet? Or should these be in a library module?
Is there a tighter support within NetSuite to handle this scenario?
In Netsuite you can use (For the backend) Custom Records (Customization > List, Records & Fields > Record Types > New) for storing the localized string which you can fetch in your suitelet or client script.
As long as it is a small string (or even for large) you can use custom records or there is another way you can use Email Template(Documents > Templates > Email Templates > New) for the same but here you need to create multiple files per language per string (I recommend this only for the long strings.)
Based upon the language you can compare and load the appropriate string.
You can fetch Email template using: nlapiLoadRecord('emailtemplate', 'template-id')
and Custom Records using: nlapiLoadRecord("record-id","row-id")
I the same problem, not being able to easily localise the language of NetSuite SuiteScript 2 scripts so I built my own language module that I just include in my scripts.
It allows you to separate all the text strings out of the actual coding so they can be easily updated / translated into any language.
Take a look at the project on my GitHub here:
https://github.com/mdbkaustralia/netsuite_language_controller_module
There is a short help doc in the readme, plus there is a working example you can upload to your NetSuite to try it out!
I'm working on a "cook book" app that has multiple (language) versions.
Apple says I can't upload multiple apps that are almost the same, so how can I achieve what is mentioned below in single app release ?
multiple languages (possible)
multiple logos (possible)
different "config" file for each language - e.g. file with API URLs
Each language version "separately" on App store so a user can download both english and spanish versions
My biggest problem is #4, it has to be possible that one can decide which language version he downloads.
You're most likely still looking at one app with multiple languages included in it, which are picked based on user local. If you want the user to decide which language they'd like after install, give them an option. Many apps do this already.
I think you can follow these steps to create the app you'd like to make.
Localize your application. (This tutorial might be useful.)
Add a language parameter to your API calls and return the data based on the language parameter. Thus you won't be displaying a content which is not available in that language.
For your 4th requirement if you'd like to use versioning on each language (I do not know why but if you must) then you can use the language paramter you'll add on API calls. Just create a releation between the languages and the versions you are using then display the views and contents based on the relation.
I'm trying to enable translating some text in my app. I want user to be able to launch whichever translation tool they use on their device (Google Translate or iTranslate) and see the translation without having to type it. For this, I'm using the url schemes:
googletranslate://
itranslate://
Now, I need to pass the query to those apps. I know how to do this for iTranslate:
itranslate://translate?from=auto&to=en&text=<encoded_string>
This is cool, now I would like to know how to do the same for Google Translate. It needs to automatically detect the language and translate it to english.
It is not currently possible to prefill UI elements in the Google Translate iOS application when opening it from googletranslate:// URLs. The contents of the URL after googletranslate:// appear to be completely ignored. So the most you can get from using these links at the moment is opening the iOS application.
If this does get implemented at some point in the future, one can test by opening a link like googletranslate://example%20text/?param=value&from=zh_TW. I would strongly recommend that you let your voice be heard on the Google Translate product forum by requesting this feature.
In the meantime, you may want to consider using Translation API to provide translations within your application. This can be achieved using the REST API.
If is there anyone still looking for the answer, you can use it like this.
googletranslate://?sl=en&tl=tr&text=hello%20world
You can change the parameters
sl = source language
tl = translation language
text = the thing you want to translate
I'm working with BlackBerry API 7.1 on Eclipse and I want to know if it's possible to add localization for variations of the same language.
I'm working on an app that needs to be localized for 10 countries that speak Spanish, but every country uses different manners of speech.
The problem I'm seeing is that BlackBerry API 7.x's Locale class only has constants for Spain Spanish and Mexican Spanish. Does that mean localization for Spanish speaking countries such as Panama, Argentina, Colombia, etc. get a default localization as if it were Spain Spanish?
Also for this case where multiple variations of the same languages must be dealt with, how should I name the files? I tried adding locale_es-AR.rrc but the - is not admissible on Resource files names, but I don't know if locale_es_AR.rrc is the correct format.
I want to know before adding ten Resource files for these countries that may or may not be usable.
Is it possible what I'm looking for?
What you are trying is correct. Have a look at Localizing Your Files
This file must have the same name as the resource header file,
followed by an underscore (_) and the language code, and then,
optionally, by a single underscore (_) and a country code (for
example, AppName_en_GB.rrc).
I'm trying to build an iOS application that has to store lots of text (immutable) data (about 500 pages of a book) and should have the following functionalities:
Organize text into chapters and display
Search for words and autocomplete. Search results should be based on most number of occurrences of a word. The search functionality is key for the application.
Based on this i wanted to know a couple of things
Whats the best way to store and retrieve this data and to perform a search (everything is local , no data on a server)?
Are there any third party frameworks that help you to do this in a faster way?
I've looked at this already
How to store immutable text in iOS app (to be available at first and every launch)?
And this post suggests the use of CoreData and MagicRecord. Is this enough for me to integrate the search functionality as well?
More information on the same and other resources/tools/third party frameworks would be helpful!