Oh yeah, they already have the documentation with the screen shots in
english...
Well I have worked with companies in the past who "supposedly" knew
how to work with nibs, and the screwed them all up for us. I really
don't want any body near the nibs, but me :) Just want to save myself
a lot of work.
On Feb 2, 2009, at 2:44 PM, Ricky Sharp wrote:
On Feb 2, 2009, at 12:35 PM, development2 wrote:
Yes I understand that. I will have to modify/resize the UI once I
have the strings in there. But the people who we are sending the
strings out to be localized do not know anything about IB, so I
don't want to confuse them or have them screw anything up. Once the
strings have been localized we will go back and look a the UI and
modify the sizes, alignment, etc. of the UI elements. I just
thought there was an easy way to get the text out and put it back
in the UI elements. I guess I will change the code to read all the
strings from the .strings file, and we can send that out, and not
have to worry about that part.
But at a minimum, the localizers will also need screenshots. If you
simply extract text out of the nibs, they'll be no contextual clues
to aid in translation.
That's why it's always preferable to work with a company that knows
how to work with nibs.
___________________________________________________________
Ricky A. Sharp mailto:rsh...@instantinteractive.com
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
