You cannot post messages because only members can post, and you are not currently a member.
Description:
Discuss iLocalize: comments, feedbacks, tips, bug reports and more.
|
|
|
Feature Request: %d / %@ / etc validation
|
| |
Hi!
It would be really cool if in the "Clean" tool, there was an option to
check for missing variables and highlight them where necessary.
For example, translators sometimes mess them up and I have to manually
search through documents to ensure they are there.
So IF source text contains one of these variables AND translated text... more »
|
|
|
Fuzzy stats in ilocalize
|
| |
Hello
I'm new to ilocalize and I am wondering how i can get fuzzy matches
stats.
Client has send me something like this:
Item Unit ES IT
Translation and Review
Repetitions word 232 225
100% matched (need review) word 402 415
100% matched (no review) word 48,461 48,458... more »
|
|
|
iLocalize freeze just after upgrade from 3.x to 4.1
|
| |
Hi, Jean,
I've just upgrade my MacBook pro to Lion 10.7.3, then I upgrade my
xCode to 4.3.1 and then I upgrade iLocalize from 3.8.3 to 4.1. At
first launch, iLocalize ask me that it is necessary to update my
project. I clic on the button to accept this and then the spining
beach ball appears and iLocalize freeze. I was obliged to go to my... more »
|
|
|
NIB re-layouting doesn't remove outdated NIB components
|
| |
Jean, I wonder if this behavior is intended or a mistake: I have a project where the English base NIB file now only contains the two components - designable.nib - keyedobjects.nib while many localized languages still carry along these components from older NIB versions, too: - classes.nib - data.depencency... more »
|
|
|
Source strings containing double spaces can't be reimported through XLIFF
|
| |
Hi Jean,
I often find that some of the strings I try to re-import from a XLIFF
file just won't be read by iLocalize. Today I ran a few tests and
found that such strings always contain a double space in the source
string.
"Export strings" works just perfect, but "Update strings" misses all
of them, having to enter them manually, which can be totally... more »
|
|
|
Problems with translations after a colon ":" (Ilocalize v 4.1 (593))
|
| |
If I translate a phrase who contain a colon like Street: Enter here your ... - Strae: Geben Sie hier ... and I hit after the translation the enter key, then the phrase get changed into Strae: Enter here your .... Used Ilocalize version: 4.1 (593) Pls. Can you give me a workaround? Regards Daniel
|
|
|
Repetitions won't import back into iLocalize
|
| |
Hi all,
I have been holding yet another doubt regarding how iLocalize works.
Whenever I export strings for translation into a XLIFF file, any
repeated source text goes in the file normally. However, at the time
of reimporting those strings, only the first instance of each source
string would be reimported, leaving me with the task to populate them... more »
|
|
|
ZH_CN language setting not available?
|
| |
Hi all,
I'm working very actively with iLocalize and so questions keep rising
up.
This time, I'm wondering if there is any way to force iLocalize to
name a language as "ZH_CN", as that specific language code is not
included among the list of available languages to add, but it's one of
my regulars.... more »
|
|
|
Can't leverage nor export Localizable.strings file
|
| |
Hi all,
I hope someone may be able to throw some light into this issue I have.
I got a new bundle for an ongoing project and after updating from it,
I found my previous localizable.strings file was not leveraged at all,
having now a 100% of the strings to be translated again. No way (we
are talking about over 1300 strings in that file only).... more »
|
|
|
