Gathering Strings for Localization

[Edi]

Hello,

I'm looking for a way to gather all strings for localization. (using /resources-hidden/_resource_xx.html files)

My idea was I'd hook into the LiftRules.localizationLookupFailureNotice and write the strings to a file. 

Then I'd browse each page on the website to collect the strings.

Almost works :) 

Works for components where I call S.?()

Doesn't seem to work for <lift:loc> tags (does not seem to fire LiftRules.localizationLookupFailureNotice - though looking at the source code it should)

Anybody found a simpler way to do this? 

Thank you.

[Antonio Salazar Cardozo]

Is it possible lift:loc is hitting LiftRules.localizeStringToXml instead?

No simpler way to do it comes to mind off the top of my head, though perhaps

you could implement a resource bundle subclass that you then set as the parent

of the application's bundles. I believe missed lookups in the child resource bundles

then delegate to the parent, who could look out for them. This would be more

generic than hooking into Lift functionality to do it. Depends on whether you consider

that a positive or negative, though, and I've never done it before so there could be

caveats I'm not aware of ;) 

Thanks,

Antonio

[j...@joescii.com]

I've done extensive work for a client to localize a Lift app. We never even attempted to find a way to do what you are asking. This is due to the project size and that strings can originate in Scala code or Javascript code anyway.

The biggest reason I would discourage solving this problem by code scanning is rather pragmatic and business-oriented. We took the approach of localizing features / pages. Then you have something you can test and release incrementally. This might not be valuable in your case of course. 

Joe