Re: [Radiant] translation of the admin interface
Hi Andre, I wouldn't use the Jargon branch, it is very old and missing a lot of the ffunctionality of the current branch. Plus the current version has had ALL the views rewritten. I have been wanting to start work on it again, but simply don't have time at the moment. The original translation only took a day or two, but it was intense work. If you are interested in helping update the Jargon branch and change the views to Haml, I would love some help. I can get a github branch started and rescue what I can from the old jargon branch. Let me know. Keith On Sep 8, 2008, at 9:09 PM, Andre Garzia wrote: Hello Folks, I need to have a Portuguese translation of the admin interface and I've wondered what is the most sensible option, if it is hard coding the translation of the current version or work with the Jargon branch. That branch appears to be based on some old Radiant version and the translation functionality is not all there (we get some mixed english/whatever strings). As I need a portuguese admin interface and I also need to build some custom extensions for this project, I don't know what version to use. Should I go and try to fix the jargon branch or should I begin from scratch? I don't need user selectable language, it should only be portuguese and thats all. Thanks in advance for any advise andre -- http://www.andregarzia.com All We Do Is Code. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] translation of the admin interface
I would love to help with translating the views. I'm just not experienced enough yet to mess with the core. So if most of functionality is working I can help converting the views. On Tue, Sep 9, 2008 at 9:12 AM, Keith Bingman [EMAIL PROTECTED] wrote: Hi Andre, I wouldn't use the Jargon branch, it is very old and missing a lot of the ffunctionality of the current branch. Plus the current version has had ALL the views rewritten. I have been wanting to start work on it again, but simply don't have time at the moment. The original translation only took a day or two, but it was intense work. If you are interested in helping update the Jargon branch and change the views to Haml, I would love some help. I can get a github branch started and rescue what I can from the old jargon branch. Let me know. Keith On Sep 8, 2008, at 9:09 PM, Andre Garzia wrote: Hello Folks, I need to have a Portuguese translation of the admin interface and I've wondered what is the most sensible option, if it is hard coding the translation of the current version or work with the Jargon branch. That branch appears to be based on some old Radiant version and the translation functionality is not all there (we get some mixed english/whatever strings). As I need a portuguese admin interface and I also need to build some custom extensions for this project, I don't know what version to use. Should I go and try to fix the jargon branch or should I begin from scratch? I don't need user selectable language, it should only be portuguese and thats all. Thanks in advance for any advise andre -- http://www.andregarzia.com All We Do Is Code. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Fix for DoS vulnerability in REXML?
I note there is now a fix for the Rails security issue that was announced earlier this year. http://www.ruby-lang.org/en/news/2008/08/23/dos-vulnerability-in-rexml/ I know the early patches broke radiant so I wanted to check if anyone found any problem with this fix in relation to radiant or has this been incorporated into one of the new releases? Many thanks Sharon This e-mail has been scanned for all viruses by MessageLabs. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Template contest! was: Radiant for a Static Site/ No Templates, etc.
I will be defining more details today. Have patience, my children! ;) Sean Mohit Sindhwani wrote: Christopher Dwan wrote: Before this gets under way, would it make sense for someone to define some standards/ conventions for building the templates? It would be great if the templates that come out of this are somewhat interchangeable, or tending in that direction. I absolutely agree with you! We need to define 2 things: 1. Templates: Are they 'style templates' that apply to a standard site type, e.g. to a blog, a company site, etc. - or are templates 'site templates' - including standard pages, etc. (e.g. Styled Blog and Simple Blog in the current Radiant). We should define this so that it's a little clearer what people will design. I think 'site templates' are a bit of a pre-requisite for 'style templates'. 2. Standard sections: We should minimize duplication. Therefore, we should try to reuse standard names as far as possible, exactly as what you have suggested. Technically, for each site template, there would be a set of standard snippets, parts, etc. These would include site_menu, nav_bar, tags_area (for blog), tag_cloud (too specific?), headings, header, footer, etc. This is what a style sheet would aim to supply. e.g: Assuming primary navigation will typically / always live in a snippet. Can we agree to generally always call it by a certain name, e.g. 'nav' or 'navigation' or 'nav_bar' ? I hope John Sean can guide a bit in this area? Radiant is beautiful in the way it allows so much freedom in the layout and design of a site. On the other hand, if a series of templates was created, it would be nice if they aren't all approached in radically different ways... A little bit of convention could go a long ways toward building momentum. Convention over configuration of course :) **Proposed action point:** Would it make sense for someone to create a sqlite database or packaged Radiant instance as a basis for all submitted templates? I'm not very good at themes, but again, like Summer Reboot, I'm willing to coordinate this! Cheers, Mohit. 9/9/2008 | 1:49 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Fix for DoS vulnerability in REXML?
That's already been added to edge, and will be included in the next release. Actually we may upgrade to Rails 2.1.1, which has the fix included. Sean Sharon Clift wrote: I note there is now a fix for the Rails security issue that was announced earlier this year. http://www.ruby-lang.org/en/news/2008/08/23/dos-vulnerability-in-rexml/ I know the early patches broke radiant so I wanted to check if anyone found any problem with this fix in relation to radiant or has this been incorporated into one of the new releases? Many thanks Sharon This e-mail has been scanned for all viruses by MessageLabs. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Template contest! was: Radiant for a Static Site/ No Templates, etc.
In which case, I must stress right now that if its templates of the second definition (site templates), then we really really need a volunteer to document how to add a site template to a Radiant install. Perhaps, we just need to extract carefully from the rake db:bootstrap but we'll need to do it. From now, I'm patient! Cheers, Mohit. 9/9/2008 | 11:09 PM. Sean Cribbs wrote: I will be defining more details today. Have patience, my children! ;) Sean Mohit Sindhwani wrote: Christopher Dwan wrote: Before this gets under way, would it make sense for someone to define some standards/ conventions for building the templates? It would be great if the templates that come out of this are somewhat interchangeable, or tending in that direction. I absolutely agree with you! We need to define 2 things: 1. Templates: Are they 'style templates' that apply to a standard site type, e.g. to a blog, a company site, etc. - or are templates 'site templates' - including standard pages, etc. (e.g. Styled Blog and Simple Blog in the current Radiant). We should define this so that it's a little clearer what people will design. I think 'site templates' are a bit of a pre-requisite for 'style templates'. 2. Standard sections: We should minimize duplication. Therefore, we should try to reuse standard names as far as possible, exactly as what you have suggested. Technically, for each site template, there would be a set of standard snippets, parts, etc. These would include site_menu, nav_bar, tags_area (for blog), tag_cloud (too specific?), headings, header, footer, etc. This is what a style sheet would aim to supply. e.g: Assuming primary navigation will typically / always live in a snippet. Can we agree to generally always call it by a certain name, e.g. 'nav' or 'navigation' or 'nav_bar' ? I hope John Sean can guide a bit in this area? Radiant is beautiful in the way it allows so much freedom in the layout and design of a site. On the other hand, if a series of templates was created, it would be nice if they aren't all approached in radically different ways... A little bit of convention could go a long ways toward building momentum. Convention over configuration of course :) **Proposed action point:** Would it make sense for someone to create a sqlite database or packaged Radiant instance as a basis for all submitted templates? I'm not very good at themes, but again, like Summer Reboot, I'm willing to coordinate this! Cheers, Mohit. 9/9/2008 | 1:49 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
