Re: Localization, Internationalization, Multilanguatisation
alex black <[email protected]>
| Newsgroups | gmane.comp.lib.binarycloud.devel |
|---|---|
| Message-ID | <[email protected]> |
>> Ok. We would obviously need heavy caching of processed files. >> If we do preprocess php with a special include - we must ensure that >> the _original_ source php is valid. I want to ensure that the string >> replacement, if skipped, would just result in string replacements >> breaking. Nothing else. > > > Okay, if this is your requirement: I think we can do this pretty > easily. There is a parse_php() function - isn't it? I don't think we need a parse_php function - I think all strings to be processed just need to be in quotes: "##somestring.id##" etc so we don't have invalid php floating around in svn. _a