[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu-devel
Subject:    [kde-edu-devel] Re: klogoturtle.docbook from Holland
From:       "Mahfouf Anne-Marie" <annemahfouf () hotmail ! com>
Date:       2003-08-04 18:35:18
[Download RAW message or body]

Hi Cies,

Thank you for your work, I will merge your index.docbook with the existing 
one which is in cvs kdenonbeta/doc/klogoturtle/
and I'll add some information on the website as well, I'll do that this 
evening.

>Meanwhile still no running version of KLogo-Turtle. I need to run kde from 
>cvs
>+ qt-copy for this, right?
yes, you need at least qt-copy and kdelibs from CVS HEAD and the QTDIR and 
KDEDIR variables pointing to these install directories in order to compile 
KLogoTurtle.

>Oh, and -- i know i asked before -- but is it true that there are some
>portugese words used in the code? The one that came across was 'desenho', 
>now
>i see it again it could be some abbreviation.  [or should i ask this
>somewhere else; i.e. Euclides or the edu-list]
desenho is the name of a class in the code. Usually, using english class 
names and english variables names in the code is better as it's easier for 
anybody to understand the code. Maybe we'll change the portuguese code names 
later if Euclides agrees. Every string in the code must be in english in 
order to be translated later by all the KDE i18n teams (more than 50). A 
string is something that appears on a widget like "Messages:" or in the 
statusbar for example. I think that in KLogoTurtle, every string is in 
english.

However, there is something special in KLogoTurtle. The LOGO commands can be 
in Portuguese (instead of typing FORWARD 50 you type the Portuguese word for 
FORWARD). This will be available in other languages and you can translate 
all the commands in your language if you want. I think that we will make a 
script in order to allow to do that easily (for the developers: and to adapt 
the code as well: I think the commands for each language should be in 
separate files that would be read by the code, we'll have to think about the 
best way to do that) so maybe you can wait a bit more to do it.

Thank you so much for your contribution, this is great. I CC my answer and 
your mail to Euclides and to the KDE-Edu mailing list. Have a nice holiday,

Anne-Marie

>From: Cies Breijs <cies@showroommama.nl>
>To: "Mahfouf Anne-Marie" <annemahfouf@hotmail.com>
>Subject: klogoturtle.docbook from Holland
>Date: Mon, 4 Aug 2003 18:09:21 +0000
>
>Hi Anne-Marie,
>
>you asked me:
>
> > Maybe you also could translate the introduction to LOGO you have in 
>English
> > so we could add it on the webpage. Any material will be nice, just send 
>it
> > to me so I can include it.
>
>I made a small English introduction to KLogo-Turtle in the .docbook format
>(attached). Eventually I hope to finish it. I used the kicker's .docbook 
>file
>as a templated, cut out all I didn't need for example material (never did a
>.docbook before) and started to replace the texts. For now only the into is
>done the rest is kicker-text.
>
>Most of the info/fact for what i wrote here come from the everything2.com 
>node
>for Logo (http://www.everything2.com/index.pl?node=logo -- last post is
>best). Changed it a bit, hopefully no copyright problems ;-).
>
>Meanwhile still no running version of KLogo-Turtle. I need to run kde from 
>cvs
>+ qt-copy for this, right?
>
>Oh, and -- i know i asked before -- but is it true that there are some
>portugese words used in the code? The one that came across was 'desenho', 
>now
>i see it again it could be some abbreviation.  [or should i ask this
>somewhere else; i.e. Euclides or the edu-list]
>
>Anyway enough for now...
>
>Kind redards,
>Cies.

_________________________________________________________________
On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile

_______________________________________________
kde-edu-devel mailing list
kde-edu-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-edu-devel
[prev in list] [next in list] [prev in thread] [next in thread]