When downloading the Sketch Resource on https://ant.design/docs/resources > RENEW Sketch Symbols, everything inside the document is Japanese (?) instead of English. Where can I find the english resource? (And yes I am browsing the site in english). When downloading the XD version it is English. My company however does everything in Sketch wand would prefer that format!
Thanks for the help!
Found out that Sketch files are just Chinese open source and not translated. Paid versions are. Just putting it out there.
Related
When we create a group or folder in Xcode, must we name the group or folder in English?
I heard about all the people saying yes, but my master told me that we can use Chinese (another language) name groups or folder, too. So now I am a little confused about this. Is there any hidden danger when we use Chinese? Could anyone tell me the truth and the reason?
No, in past I've builded a project entirely in italian without any problem, and I'm speaking about Xcode 5.
However you can find official documents here
And you can find also the support to Right-to-Left and Left-to-Right language here.
P.S. If you want to change entirely language to add some charset, look the Apple official instruction to do it here
My app only supports english. I am using base internationalization (English- Development Language)
Steps I followed:
1. Separate out user-facing text using NSLocalizedString();
2. Using Genstrings command i have added Localizable.strings in base.lproj.
3. In Editor >> Export for Localization
4. Save en.xliff and provide to translator team for updating English content
5. While importing updated en.xliff file, i got below error.
Might be i doing in wrong way to export/import for English. Please suggest me the best approach for handling English content. (development language).
It is not obvious to me what you want to achieve: do you want to have your strings translated into some language other than English, or do you want to run your strings through an English linguistic review? For the first case the error message is pretty clear: check if the file element in your translated XLIFF file has a target-language attribute and add it if not. Details about this attribute can be found in the XLIFF spec here.
If adding this attribute is not enough you may also want to look at the answer to this previously asked question.
For the second case XLIFF is not really a good format.
I have been using Google's Translation web site to translate my localizable.strings file to multiple languages, but it is very tedious.
Does anyone know if there is a better way to do this?
Don't do that! Most people will prefer a non-localized English version to a poorly translated one.
Either contact a localization service (they will translate the .strings files directly) or don't localize your app.
Attempts
I tried:
Virtaal
PoEdit (not xliff but convertible)
Open Language Tools TransEditor
LocFactory Editor
And I think I'm getting nuts.
Virtaal
With Virtaal it seems I can't create files (or am I to stupid ?). Also when I open the tutorial .po and try to save that, Virtaal crashes.
PoEdit
With PoEdit I can create a new project but on finishing he throws me an error:
Poedit did not find any files in scanned directories.
Entries in the catalog are probably incorrect.
Updating the catalog failed. Click on 'More>>' for details.
Open Language Tools TransEditor
And in Open Language Tools TransEditor I created a new project but I can't create any new lines/translations.
LocFactory Editor
I also tried LocFactory Editor. When I launch it I get
No document could be created
And in the menus I also can't find anything like New File or so.
Question
So what is that ? Am I to dumb to create xliff files using an xliff editor ? should I google for xliff creator or what ?
Requirements
I want to have xliff files for a FLOW3 project.
I'd like to use an editor that supports plural forms.
Support for Mac OS X
Hi you can try this one
XLIFFTool
You may want to try OmegaT.
It's not just for XLIFF, but it should work reasonably well with XLIFF documents.
Make sure the elements have a copy of the text to translate before opening the file in OmegaT. You can also use Rainbow to create an OmegaT project with XLIFF files: it will add the copy of the source text for you.
Hope this helps,
-ys
There is free XLIFF online editor at Brightec. Not sure about plural forms support.
you can use poedit tool for that.
Is there any other way to localize iPhone apps beside the use of Localizable.strings? Can I use Google Translate or something like that?
I have my application written in English, and I have created Localizable.strings files for about twenty languages. I have the English Localizable.strings working perfectly, and I have tried Italian as well. Is there any way to translate these Localizable.strings to the rest of the languages automatically?
I mean is there any program or something to do the job for me?
In short: No, there is no program for that. It's the same problem as translating any text: You need to understand the meaning to give useful translations.
As a quick fix, you can of course simply take the strings in your Localizable.strings file and copy them into a Spreadsheet, then run one column through Google Translate and copy the result back. Then reverse the procedure and you have a translated Localizable.strings. A regex for doing this would be:
^"(.*)"\s*=\s*"(.*)";$
that works fine in eg. TextWranger with grep mode on, then you can replace the text with
\1\t\2
to create a the tab-delimited file from a strings file.
I still suggest you invest in a native speaker of each language to double-check the translations, or your app will become a laughing stock. Google Translate just can't replace a real human yet...
To localize your app you can use Localizable.strings or use localized XIB.
I don't use the second approach because it is more cumbersome to manage.
With Localizable.strings you have to code a little bit more but I prefere it.
To translate I think you can use google translate (I do that) and build the file for each language.
If you want to use an online translator, remember that it can be not always available and your user must be connected all the time.
So my advice is to build all the language files since they are managed by the OS and you will have a more reliable solution.
You should create Localizable.strings for each language and translate them with any translation tool