(1)
Your rating: Now say why...
- Download Now
2.5 MB -
Visit Developer's Site
Nobuatsu Sekine
iLingual helps you localize other applications. There are other localizing tools like AppleGlot but, for many, they are too complicated and too difficult to use. I wanted an easier, more "Mac"-feeling tool, so I created iLingual.
There are no complicated settings; just drag and drop files, and you are ready. It has a dictionary, of course, and so you don't need to repeat work you have already done. You can just focus on a small number of keywords.
If you want to use iLingual for commercial use (to localize shareware, package-ware or to localize for payment) then
There are no complicated settings; just drag and drop files, and you are ready. It has a dictionary, of course, and so you don't need to repeat work you have already done. You can just focus on a small number of keywords.
If you want to use iLingual for commercial use (to localize shareware, package-ware or to localize for payment) then
What's New
Version 1.2.3:
- Fixed bug that iLingual doesn't read previous translation result if key of .strings contains backslash character.
- Fixed Added Greek Resources. (Thanks to George)
Requirements
PPC / Intel, Mac OS X 10.4.11 or later, and DeveloperTools.
PPC / Intel, Mac OS X 10.4.11 or later, and DeveloperTools.
iLingual User Discussion (Write a Review)
Overall:
(1)
(1)
| Downloads:6,785 |
| Version Downloads:2,171 |
| Type:Development : Reference |
| License:Free |
| Date:18 Sep 2009 |
| Platform:PPC / Intel |
| Price:Free |
Overall (Version 1.x): |
| Features: |
| Ease of Use: |
| Value: |
| Stability: |
-
-
-
iLingual helps you localize other applications. There are other localizing tools like AppleGlot but, for many, they are too complicated and too difficult to use. I wanted an easier, more "Mac"-feeling tool, so I created iLingual.
There are no complicated settings; just drag and drop files, and you are ready. It has a dictionary, of course, and so you don't need to repeat work you have already done. You can just focus on a small number of keywords.
If you want to use iLingual for commercial use (to localize shareware, package-ware or to localize for payment) then iLingual is shareware and costs $30. Please check the documentation about licensing.
However, if you want to use iLingual for non-commercial use (to localize freeware or to localize as volunteer) then it is freeware. Feel free to use it.
There are no complicated settings; just drag and drop files, and you are ready. It has a dictionary, of course, and so you don't need to repeat work you have already done. You can just focus on a small number of keywords.
If you want to use iLingual for commercial use (to localize shareware, package-ware or to localize for payment) then iLingual is shareware and costs $30. Please check the documentation about licensing.
However, if you want to use iLingual for non-commercial use (to localize freeware or to localize as volunteer) then it is freeware. Feel free to use it.
Copyright © 2012 MacUpdate LLC
- -
+24
I hope for you that iLingual works after you installed the Developer Tools.
You are not ... it's a mistake everyone can make.
To be honest, as a betatester I have the Developer Tools always installed on my Mac.
I had just read a few houres ago, in the requirements from iLingual, that you need Xcode.
I'm using iLingual for a long time now and I honestly did not knew that you needed the Developer Tools for this program.
It's because I always have those tools installed on my Mac that I've not made the same mistake ;-).
Please let us know if this solved your problem?
Thanks & good luck.
Leppe
+14
This time I try with Raw Photo Processor.
Either I try with the freeware or its resources package, it doesn't work. Nothing appears in the window.
+24
I just tried a local translation from Raw Photo Processor in to my native language and it worked fine.
When I start a translation the first thing I do is (besides launching iLingual) is to make sure that the files sidebar is open. You can open this sidebar by clicking on the Files button.
Then I drag & drop the program that I want to translate in this sidebar. (It's safe to work with a copy from the program).
Raw Photo Processor is a large translation, so it takes a few seconds to load the file.
Then I simply start to translate. After each word I translate I click on "Checked". Then the program goes to the next word.
When I'm done I simply click the Export button and I select the program (or the copy I'm working on). The translation folder (.lproj) saves directly in to the recourses folder from the program.
I start the program and everything is translated. So no problems here...
Like always this program performs very well. Even with a large translation like Raw Photo Processor.
I hope my comment helps you a bit.
With kind regards.
+14
In that case, the file to translate is MainMenu.nib, ok.
If I do as you say, nothing appears, I've been waiting for minutes.
In other way, if I click on the Add File button, same result.
+24
it's indeed the file MainMenu.nib that you need to translate.
I've tried to translate Raw Photo Processor again (for the second time with a clean copy) and I have encountered (more or less) the same problem.
I think that's a bug? But I'm not sure... We should check this with the developer. It's the first time I've noticed this issue because I never had to translate the same program twice.
It seems that when I try to translate Raw Photo Processor (a clean original copy) again (for the second time) I can't see anything to translate. Just like you (I think). The MainMenu nib file appeared in the sidebar (in red) but there was nothing to translate. That's because I translated the program before and all the words where already in the dictonary.
So I decided to empty my dictionary!
-So try empty the dictionary browser (MenuBar, Dictionary, Show Browser) when iLingual is launched. (Load no file yet)
-When your dictionary browser is empty, quit iLingual.
-Then restart iLingual again and check if your dictionary browser is empty.
-If so, then try to open a copy (for instance from your Desktop) from Raw Photo Processor.
-If a window opens with the question to select a previous localized file, click Cancel.
-A few seconds later the MainMenu nib file should be open.
This worked for me.
BTW: My hardware is PowerMac G5, 2x2.7Ghz, 8Gb Ram, ATI X800XT, 256Mb VRAM, 10.5.6 & the latest developer tools from Apple.
Regards,
Leppe
+14
I don't know why, but nothing appear in the window.
My dictionary is empty.
My Mac is a G5 PPC, 10.5.6.
+24
Maybe a stupid question from me, but have you installed Apple Developer Tools (Xcode 3.2.1)?
http://www.macupdate.com/info.php/id/13621/apple-xcode
PS: Sometimes I try to manual translate a nib file with Interface Builder. That's a program which is part of the Developer Tools from Apple.
But with Interface Builder you need to open the package contents from a program and you have to search for every nib file...
Regards,
Leppe
+14
Perhaps the developper could help me with my problem.
Thanks a lot for your kindness.
+14
+24
Leppe reviewed on 07 Mar 2009
I'm using iLingual for my personal translations/localizations and it works great!
I just translated the new Safari4 beta for personal use and everything went very well.
This is a very Mac friendly program and easy to learn.
It's also great that the program has a browser where you can store new words for future translations/localizations. That's a very good feature!
I'm using this program for a long time now.
-It's very easy to learn.
-The price is right (free for personal use).
-It never crashed on my hardware!
-It's very Mac friendly.
-It always did the job for me!
So in short, iLingual is for me the best program for my personal translations/localizations of all the programs which are not supported in my native language.
I highly recommend this program.
@the developer(s) from the program. Thank you very much for this great program and the latest update 1.2.1 which supports .xib files! You did a great job!
With kind regards,
Leppe
+42
http://www.loc.gov/standards/iso639-2/php/code_list.php
+4
+1
I tried those 2 apps and yes I can't localize Opera.
Because it has unexpected resource names like "en.lproj".
(It should be "English.lproj".)
I don't know whether it's a legal name or not but at least it isn't a common names.
So if you need to localize Opera, please take out those resources from inside of the package, and add these .nib files and .strings files to iLingual.
And Skype, it seems OK.
It takes a little bit long time but it can import appropriate files.
Please try again and if you still can't,
please tell me your environment.
(Version of Skype, languages you select...)
+4
but skype - still doesn't work. i pick "skype.app" from applications and try to add it. as i understand, the file list must appear in the main window, but it doesnt. i wait for a while.
i use english-to-russian direction. skype 2.6.0.137. intel 10.4.9
+1
>i use english-to-russian direction. skype 2.6.0.137. intel 10.4.9 (5/23/2007, Version: 1.0.4)
I tried to set up english-to-russian localizing and it seems fine.
Please try to localize as same way as Opera.
In that process, I think you may encounter some problems, in that case, please let me know.
Oh, I forget one thing.
Please remove "English-Russian.strings" file.
It is in "Library/Application Support/iLingual/" folder of your home directory.
It is dictionary file and if it has any problem,
iLingual may cause some problems.
Or just change its name.
Thanks.
+42
"I don't know whether it's a legal name or not but at least it isn't a common names."
These are actually in the i18n Proposed List of 2nd level Language Identifiers in RFC 3066 and also an ISO Standard.
http://www.ietf.org/rfc/rfc3066.txt
Country identification, such as en-US are described in ISO 639.
Parent:
en
Children:
en-AU
en_US
en_GB
Quite a few applications use this style for localization so it's certainly worth adding direct support for in iLingual.