I tried this one already, it seemed to work only if the tookit dir is
under the pylons project tree like this:

myprojects/pylonsproject/
myprojects/pylonsproject/pylonsproject
myprojects/pylonsproject/toolkit

situation that I would like is:

myprojects/pylonsproject/
myprojects/pylonsproject/pylonsproject
myprojects/toolkit

I also tried to do symbolic link from myprojects/toolkit to
myprojects/pylonsproject/toolkit, but it did not work either...

- Mikael

On Jan 27, 2008 5:18 PM, Alberto Valverde <[EMAIL PROTECTED]> wrote:
>
>
> Mikael Lepist� wrote:
> > Hi,
> >
> > We have a toolkit library that we use in many pylons projects and it
> > is outside of normal pylons project tree. Now we have problem, that we
> > cannot get setup tools to extract messages outside of our pylons
> > source tree to get localization also for toolkit.
> >
> > our directory structure is basically like this:
> >
> > pylonsproject/
> > toolkit/
> >
> > I tried to make symbolic link to toolkit dir to
> > pylonsproject/pylonsproject/toolkit
> >
> > but it didn't work.
> >
> > Is it possible to read texts for pylons project from different
> > directory to the same catalog where is pylon project translations? Or
> > would it be possible to extract messages separately for toolkit and
> > set pylons to use them in addition to
> > pylonsproject/pylonsproject/i18n/pylonsproject.po stuff?
> >
> > We wold not like to do localizations same way that they are done with
> > validators, by passing strings for message-keys to the functions.
>
> This is how the relevant section of setup.py in a project of mine looks
> to extract messages using Babel from FormEncode:
>
>     message_extractors = {
>         'thirdparty/FormEncode/formencode': [
>             ('**.py', 'python', None),
>         ],
>         'myapp/templates' : ...,
>         etc...
>     }
>
> thirdparty/Formencode is a svn-external where I make a checkout of a FE tag.
>
> Although this solution works for me it is suboptimal IMO. Ideally there
> would be a way for catalogs from different eggs to be "merged" together
> somehow so that just installing an egg and probably listing it somewhere
> would do the job without needing a source checkout. Probably Babel's
> competence though.. Any ideas?
>
> Alberto
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to