[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: I18n in koffice scripts
From: Dag Andersen <danders () get2net ! dk>
Date: 2008-12-18 8:36:46
Message-ID: 200812180936.46573.danders () get2net ! dk
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Onsdag 17 december 2008 22:54:40 Sebastian Sauer wrote:
> On Wednesday 17 December 2008, Dag Andersen wrote:
> > On Mandag 15 december 2008 21:43:04 Albert Astals Cid wrote:
> > > A Dilluns 15 Desembre 2008, Dag Andersen va escriure:
> > > > Ok, I've been around the block a few times more, so I'll try to sum
> > > > up my findings.
> > > > First the premisses for this:
> > > > I want to have some scripts translated :)
> > > > These scripts are always run from within a koffice application (eg
> > > > kplato) and can be regarded as an extension/part of that applications
> > > > functionallity. This means that the user expects the language (and
> > > > locale in general) to be the same as the rest of the application.
> >
> > (snip)
> >
> > > IMHO it makes much more sense to it to be in kross and not in kokross,
> > > any other program using kross will have the same problem than KPlato is
> > > facing now. kross core already depends on a load of kdelibs libs using
> > > KIcon, KUrl, KMimeType, KStandardDirs, i18n, etc.
> >
> > Yes, ok, last attempt.
> > I have created a new module "kdetranslation" in kross/modules (not
> > committed) that encapsulates the i18n* methods. Use in python:
> > import Kross
> > t = Kross.module("kdetranslation")
> > print t.i18n("This string can be translated")
> >
> > This is implemented in kdelibs/kross/modules so it is availabale to all
> > kde scripts, and it doesn't depend on core being kde, so if core i's
> > moved later, no problem.
> > Why not just stuff it into the "forms" module? Well, I think this is
> > cleaner. Sebastian, is this ok with you?
>
> Absolute yes :)
Comitted, so now scripts can use the above mentioned method for i18n.
But, just remembered, koffice wants to stay compatibel with kdelibs 4.1.
How to achive that?
--
Mvh.
Dag Andersen
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; \
font-weight:400; font-style:normal;">On Onsdag 17 december 2008 22:54:40 Sebastian \
Sauer wrote:<br> > On Wednesday 17 December 2008, Dag Andersen wrote:<br>
> > On Mandag 15 december 2008 21:43:04 Albert Astals Cid wrote:<br>
> > > A Dilluns 15 Desembre 2008, Dag Andersen va escriure:<br>
> > > > Ok, I've been around the block a few times more, so I'll try to \
sum<br> > > > > up my findings.<br>
> > > > First the premisses for this:<br>
> > > > I want to have some scripts translated :)<br>
> > > > These scripts are always run from within a koffice application \
(eg<br> > > > > kplato) and can be regarded as an extension/part of that \
applications<br> > > > > functionallity. This means that the user expects \
the language (and<br> > > > > locale in general) to be the same as the \
rest of the application.<br> > ><br>
> > (snip)<br>
> ><br>
> > > IMHO it makes much more sense to it to be in kross and not in \
kokross,<br> > > > any other program using kross will have the same problem \
than KPlato is<br> > > > facing now. kross core already depends on a load of \
kdelibs libs using<br> > > > KIcon, KUrl, KMimeType, KStandardDirs, i18n, \
etc.<br> > ><br>
> > Yes, ok, last attempt.<br>
> > I have created a new module "kdetranslation" in kross/modules (not<br>
> > committed) that encapsulates the i18n* methods. Use in python:<br>
> > import Kross<br>
> > t = Kross.module("kdetranslation")<br>
> > print t.i18n("This string can be translated")<br>
> ><br>
> > This is implemented in kdelibs/kross/modules so it is availabale to all<br>
> > kde scripts, and it doesn't depend on core being kde, so if core i's<br>
> > moved later, no problem.<br>
> > Why not just stuff it into the "forms" module? Well, I think this is<br>
> > cleaner. Sebastian, is this ok with you?<br>
><br>
> Absolute yes :)<br>
Comitted, so now scripts can use the above mentioned method for i18n.<br>
But, just remembered, koffice wants to stay compatibel with kdelibs 4.1.<br>
How to achive that?<br>
-- <br>
Mvh.<br>
Dag Andersen</p></body></html>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic