Hi, sorry for not beeing clear in what I meant - Marco's patch matches 100% what I want to do. I agree with Marco that it is not possible to change a constant defined value - otherwise you have to change the int/de.php (for example). All I want to do is add new constants for a theme template and translate them. Big thanx for beeing such quick in applying that change ^^ Greets, Marcus. Marcus Kimpenhaus Polsumer Str. 56 45896 Gelsenkirchen +49 (209) 9256075 marcus at kimpenhaus.de Sameer D'Costa schrieb: > Maybe I misunderstood Marcus' original point. I thought he wanted his > theme to change the constants defined in intl/de.php and add new ones. > Maybe he only wanted to add new constants. Sorry. > > Sameer > > > On Tue, Sep 20, 2005 at 06:22:32PM +0200, Marco Bonetti wrote: > > >>Date: Tue, 20 Sep 2005 18:22:32 +0200 >>From: Marco Bonetti <mbonetti at gmail.com> >>To: gregarius-dev at sinless.org >>Subject: Re: [greg-dev] i18n and templating >>Reply-To: mbonetti at gmail.com, gregarius-dev at sinless.org >> >>Sameer, >> >>as far as I know there is no way to override a constant defined with >>"define()". The idea behind theme-specific l10n is that theme authors >>can localize theme-specific labels (e.g. labels required by their >>theme and used in their theme alone) >> >>Or maybe I was missing Marcus' original point? >> >> -m >> >>On 9/20/05, Sameer DCosta <sameerslists at gmail.com> wrote: >> >>>Marco, >>> >>>I have a small question. Reading the code, it seems that if your lang >>>is de then the theme cannot override any of the constants in de.php. >>>Is this correct? I am sorry for bothering you if I am missing >>>something. >>> >>>Sameer >>> >>>On 9/20/05, Marco Bonetti <mbonetti at gmail.com> wrote: >>> >>>>Marcus, >>>> >>>>I've added theme-specific l10n handling as of changeset [888]. >>>>http://svn.gregarius.net/trac/changeset/888 >>>> >>>>I hope this suits your needs. >>>> >>>> -m >>>> >>>> >>>>On 9/19/05, Marco Bonetti <mbonetti at gmail.com> wrote: >>>> >>>>>Marcus, >>>>> >>>>>Good point. We already have template-specific plugin handling. I'll >>>>>try and add something similar for translation files. >>>>> >>>>>That being said should be pretty safe if you chose to update your svn >>>>>copy as Subversion handles modified files and is pretty at good >>>>>merging them. >>>>> >>>>>(And should a merging problem arise subversion will save your copy as >>>>>de.php.mine and won't "overwrite" your copy) >>>>> >>>>> >>>>>On 9/19/05, Marcus Kimpenhaus <marcus at kimpenhaus.de> wrote: >>>>> >>>>>>it's me again, >>>>>> >>>>>>I was trying to update to a new version (the svn-trunk) - and I >>>>>>recoginzed that my template is using some special translations, which I >>>>>>put into the language file (de.php). >>>>>> >>>>>>If I am going to update the sources I am afraid to overwrite my >>>>>>translations or have to merge the new ones from release 0.5.1 with them. >>>>>> >>>>>>It would be very nice to have template-specific and application-specific >>>>>>translation? >>>>>> >>>>>>What do you think? >>>>>> >>>>>>greets, >>>>>>Marcus. >>>>>> >>>>>>-- >>>>>>Marcus Kimpenhaus >>>>>> >>>>>>Polsumer Str. 56 >>>>>>45896 Gelsenkirchen >>>>>> >>>>>>+49 (209) 9256075 >>>>>>marcus at kimpenhaus.de >>>>>>_______________________________________________ >>>>>>gregarius-dev mailing list >>>>>>gregarius-dev at sinless.org >>>>>>http://sinless.org/mailman/listinfo/gregarius-dev >>>>>> >>>>> >>>>_______________________________________________ >>>>gregarius-dev mailing list >>>>gregarius-dev at sinless.org >>>>http://sinless.org/mailman/listinfo/gregarius-dev >>>> >>> >>_______________________________________________ >>gregarius-dev mailing list >>gregarius-dev at sinless.org >>http://sinless.org/mailman/listinfo/gregarius-dev > > _______________________________________________ > gregarius-dev mailing list > gregarius-dev at sinless.org > http://sinless.org/mailman/listinfo/gregarius-dev