[kde-edu]: i18n issues with step

Wed Nov 26 11:52:14 CET 2008

Hello Albert,

Yes, now StepCore uses only tr. All tr calls are in kdeedu/step/stepcore, all 
i18n calls are in kdeedu/step/step and currently Messages.sh extracts both of 
them in one .pot file.

On Tuesday 25 November 2008 02:31:11 Albert Astals Cid wrote:
> Did you finally only use tr() in stepcore?
>
> If that's what you did, tell me which directories use tr() and which ones
> use i18n() because we should create two .po files. Otherwise the KDE
> translation system tries to do smart things on tr() and it will explode.
>
> Albert
>
> A Dijous 20 Novembre 2008, Vladimir Kuznetsov va escriure:
> > Hello,
> >
> > I agree with you about the problems with objinfo files. However simple
> > inlining them into .cc or .desktop files won't work since they are
> > supposed to be full HTML files in the future. For example they can
> > contain a table describing properties of the object, links to wikipedia,
> > etc. Wrapping them in XML could be possible, I'll think about it.
> >
> > On Tuesday 18 November 2008 16:45:08 Burkhard Lück wrote:
> > > Am Dienstag 18 November 2008 11:35:09 schrieb Vladimir Kuznetsov:
> > > > Objinfo files can be translated, but in different way. I've just
> > > > added example of translation to l10n-kde4/de/data/kdeedu/step.
> > >
> > > Noticed that already and checked it;-)
> > >
> > > It works, but how to keep the objinfo files in step and in all
> > > translations in sync?
> > >
> > > You generate the html for missing documentation on the fly from text
> > > with i18n calls.
> > >
> > > Maybe this is also possible for the objinfo files, which consist of a
> > > few lines of html stuff, a title string and a few lines of text inside
> > > <body></body>?
> > >
> > > You only need to generate the file content at runtime with two
> > > translatable strings, the text inside <title></title> and the text
> > > inside <body></body>.
> > >
> > > Then scripty can keep the strings in source and translations via
> > > step.po in sync, just change or add text with i18n calls and all
> > > changes are merged with the translations.
> > >
> > > Another possible solution is to use desktop files or xml files. You
> > > find more information about this issue on
> > > http://techbase.kde.org/Development/Tutorials/Localization/i18n_Challen
> > >ge s# Translating_Data
> > >
> > > This could also give some hints how to make the tutorials and examples
> > > translatable.
> > >
> > > > Tutorials are still non-translatable. For now I can implement the
> > > > similar translation method for them as used for objinfo files, but
> > > > this is not optimal because it will be hard to keep translations in
> > > > sync. Another solution is probably to modify .step file format to to
> > > > include translations directly into .step files, but then it won't be
> > > > possible to translate object names (like "particle1"). What do you
> > > > thing about it ?
>
> _______________________________________________
> kde-edu mailing list
> kde-edu at mail.kde.org
> https://mail.kde.org/mailman/listinfo/kde-edu

-- 
      Best Regards,
        Vladimir