One for all
A few posts back, we have seen a method to merge TM files using a project. But what if you want to look through your memories in a view while you still keep them in separate files, being organized as you always do?
Sharing corpus is not only for others on network. As a matter of fact, you can open a proxy corpus for your open corpora as well. Let's see how it works:
Of course, you get the most out of this feature when you do some collaboration work with your colleagues.
In the next post, we will see a new filter plugin for nib files. Stay tuned.
Sharing corpus is not only for others on network. As a matter of fact, you can open a proxy corpus for your open corpora as well. Let's see how it works:
Of course, you get the most out of this feature when you do some collaboration work with your colleagues.
In the next post, we will see a new filter plugin for nib files. Stay tuned.
posted by hiruneko at 12:11 AM
2 Comments:
This is a great blog. Looking forward to see the entry about the nib plug-in.
Just curious, since you seem to be an Apple internal localizer: How do you find out which dialogs need resizing after translation? Is there a secret unpublished tool that tells you this or do you also open each nib file in IB and do a visual check? Can't believe there's not an easier way... I guess I'm spoiled by Windows loc tools.
-Tom
Hi. I'm afraid but I'm not a pro in that field. So here's my best answer. As you might have found it already, there's a validation tool built in Interface Builder (Layout > Validate Layout), that pretty much does what you need I believe. You may end up to know that you have to retranslate strings rather than resizing them. To my knowledge, there's no good tool that lets you totally free from visual checking...
Post a Comment
<< Home