Re: localization when part of the code is in different place than pylons project.
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 pylons-discuss@googlegroups.com
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
-~--~~~~--~~--~--~---
localization when part of the code is in different place than pylons project.
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. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Having some trouble getting started with Pylons
On Jan 26, 7:25 pm, Mike Orr [EMAIL PROTECTED] wrote: In production.ini (development.ini for now): host = 12 7.0.0.1 port = 8080 Here is what I have: /var/www/helloworld# ls *.ini development.ini test.ini /var/www/helloworld# wget http://127.0.0.1:8080 --09:54:01-- http://127.0.0.1:8080/ = `index.html.3' Connecting to 127.0.0.1:8080... failed: Connection refused. Is that okay? The only time you'd put 0.0.0.0 or your public IP in production.ini is if you're not running Apache/lighthttpd and you want the public to access the Paste HTTP server directly. In that case it must run on port 80 or users will have to put the :port_number in their URL. And the program would have to run as root to open port 80. That might work for me. I am just trying to install, and learn, some Pylons right now. I have root access. I will not need to have anything accessed by the public for a few weeks, at least. If it is any easier to get started, I am willing to sacrifice public access. At least for now. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Having some trouble getting started with Pylons
On Sun, 2008-01-27 at 09:04 -0800, walterbyrd wrote: Here is what I have: /var/www/helloworld# ls *.ini development.ini test.ini /var/www/helloworld# wget http://127.0.0.1:8080 --09:54:01-- http://127.0.0.1:8080/ = `index.html.3' Connecting to 127.0.0.1:8080... failed: Connection refused. Is that okay? I'm going to be frank: you aren't giving anywhere near enough information for anyone to help you. Did you actually start pylons with paster serve development.ini? Cliff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Having some trouble getting started with Pylons
On Jan 27, 2008 9:04 AM, walterbyrd [EMAIL PROTECTED] wrote: On Jan 26, 7:25 pm, Mike Orr [EMAIL PROTECTED] wrote: In production.ini (development.ini for now): host = 12 7.0.0.1 port = 8080 Here is what I have: /var/www/helloworld# ls *.ini development.ini test.ini /var/www/helloworld# wget http://127.0.0.1:8080 --09:54:01-- http://127.0.0.1:8080/ = `index.html.3' Connecting to 127.0.0.1:8080... failed: Connection refused. Is that okay? No, it means the Pylons app is not running. Or more precisely, that no service is running on port 8080. -- Mike Orr [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~--~~~~--~~--~--~---
Documentation for begginers
Hi everyone :) I've just started to have some fun with pylons and I've got a question - what's wrong with the documentation? I mean - it's cool because it's there but there's almost no tutorials and stuff... is someone working on it? Or maybe someone could give us (begginers) some links to them? :) Best wishes, Mike *mikeroz* Rozycki --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~--~~~~--~~--~--~---
