I don't think it's necessary to run it on headers. I think the only
possible use could be to catch macros including NSLocalizedString,
but I don't think they occur in any header. As for vendorsrc, all
localized strings for the Omni frameworks should be in the special
tables. Other 3rd party sources could contain NSLocalizedString, but
a quick Find does not show any. Subprojects can also contain
NSLocalizedString, in fact BTParse does. So I think that one at least
needs to be parsed (or can it be contained in its own Resources? I
don't know precisely where localized strings in frameworks look). So
I think we can safely leave out most of vendorsrc. Would it be
possible to move BDSKErrorObject.* to ./BTParse/ and just include ./*.
{m,h} ./BTParse.{m,h} and ./inputmanager/*.{m,h}, I think that covers
all occurences of NSLocalizedString.
Christiaan
On 3 Nov 2007, at 8:37 PM, Adam R. Maxwell wrote:
> Do we need to run genstrings on header files and vendorsrc? Running
> on vendorsrc is a side effect of now having it live inside the main
> source folder, but genstrings is incredibly slow here.
>
> adam
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bibdesk-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
