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

List:       kde-i18n-doc
Subject:    Re: kde-i18n-doc Digest, Vol 17, Issue 41
From:       yeshi wangchuk <yeshichuk () yahoo ! com>
Date:       2004-08-27 9:30:14
Message-ID: 20040827093014.40801.qmail () web50009 ! mail ! yahoo ! com
[Download RAW message or body]

dear sir, 
  stop giving me a mail.... i cannot read it for i am busy with my study these \
days... am student here in india.. thanks
yeshi.

kde-i18n-doc-request@kde.org wrote:
Send kde-i18n-doc mailing list submissions to
kde-i18n-doc@kde.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/kde-i18n-doc
or, via email, send a message with subject or body 'help' to
kde-i18n-doc-request@kde.org

You can reach the person managing the list at
kde-i18n-doc-owner@kde.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kde-i18n-doc digest..."


Today's Topics:

1. Re: flags and countries (Marko Rosic)
2. Re: problems with kbabel (Rinse de Vries)
3. Re: KDE Doc: We Need Writing Style Guide (Philip Rodrigues)
4. Re: flags and countries (Per Lindstr?m)
5. Re: KDE Doc: We Need Writing Style Guide (Kevin Donnelly)
6. Re: Improving KDE with translators (Vedran Ljubovi?)
7. Re: Improving KDE with translators (Erik Kj?r Pedersen)
8. Re: flags and countries (Nicolas Goutte)
9. Re: problems with kbabel (Malcolm Hunter)
10. Re: Old soc statistics for KDE_3_2_BRANCH (Claudiu Costin)


----------------------------------------------------------------------

Message: 1
Date: Thu, 26 Aug 2004 12:16:39 +0200
From: Marko Rosic 
Subject: Re: flags and countries
To: KDE i18n-doc 
Message-ID: <200408261216.39982.roske@kde.org.yu>
Content-Type: text/plain; charset="utf-8"

On среда 25 август 2004 21:36, Nicolas Goutte wrote:

> > Why?... I think kdebase/l10n/sr belongs to Suriname not to Serbia.
> 
> Why? I do not know. We were talking about a Serbian flag and one came
> up. (I did not realised that it was committed in the wrong directory.)

Corrected, sorry for the inconvinience :D

Though, Suriname was a flag for Serbian keyboard for a long time?!

-- 
Срдачан поздрав,
Марко  осић - Marko Rosić
Kоординатор пројекта KDE на српском - KDE in Serbian \
project coordinator


------------------------------

Message: 2
Date: Thu, 26 Aug 2004 13:13:56 +0200
From: Rinse de Vries 
Subject: Re: problems with kbabel
To: averneka@moj.net, KDE i18n-doc 
Message-ID: <200408261313.57046.rinsedevries@kde.nl>
Content-Type: text/plain; charset="us-ascii"

Op maandag 23 augustus 2004 16:52, schreef averneka@moj.net:
> I can report similar problems. KBabel crashes if I open a .po file from the
> Catalog Manager. The problem is probably not connected to the kde-redhat
> rpms as I compiled KDE from source on Fedora core

On my system a corrupted translation database is often the cause of a unstable 
kbabel.
Try removing it and see if it helps.
If the database gets corrupted very often you can try to make it readonly. 
Some teammembers reported that problems with the translation database don't 
happen when its readonly :o)

Rinse


------------------------------

Message: 3
Date: Thu, 26 Aug 2004 11:03:50 +0100
From: Philip Rodrigues 

Subject: Re: KDE Doc: We Need Writing Style Guide
To: kde-i18n-doc@kde.org
Message-ID: <200408261103.56610.philip.rodrigues@chch.ox.ac.uk>
Content-Type: text/plain; charset="us-ascii"

[I'm not subscribed to some of the other lists this message went to, and can't 
immediately see how to use gmane, so if this message is relevant to them, 
please forward, thanks]

Frans Englich wrote:

> We will apparently write tons of docs. In my work, I've discovered a lack
> of standardization in how texts should be designed, and I think that needs
> some clarification.
> 
> I see three text areas which needs standardization:
> 
> 1. Texts in interfaces; labels, buttons etc.
> 2. Application/KDE documentation
> 3. In-house documents
> 
> I think 2) and 3) can be treated as same, and is covered by:
> http://i18n.kde.org/doc/doc-primer

Agreed. Use of DocBook for 3 helps standardization too.

> These are issues I've found a lack of coordination(regardles of area):
> 
> A. Details on how to write texts for 2) and 3) above. For example, should
> we use endashes or emdashes? Should bullet lists end with a period? (etc.
> etc.) I guess this should go in:
> http://i18n.kde.org/doc/doc-primer

If we come up with guidelines on these issues, then the doc primer would be
a good place to put them. If you wish to discuss them further, you could
try contacting the proofreaders on kde-doc-english, as they have some
guidelines already, and can tell you more about the issues arising from
using proofreading guidelines.

On the other hand, I have to agree with David Johnson that we have a lot of
trouble recruiting and keeping documentation writers without adding a
greater burden of very specific house style.

> B. A much needed standardization of words and phrases. Badly needed.
> Should power management be referred to as ACPI, APM or Power Management?
> Display/Monitor? Etc. Etc.

If further discussion takes place on this issue, could you please cc
kde-doc-english, since this might tie in with our renovation of the
glossary, going on at the moment.

> C. Rules for writing texts for GUIs; Judging from reading kde-cvs we need
> guidelines that says "don't use smilies; don't use caps; don't pull jokes"
> -- basic stuff

This also applies for documentation, so I'll add it at
http://i18n.kde.org/doc/doc-primer/grammar.html
If anyone comes up with more ideas along these lines, please tell us at
kde-doc-english.

> Should we have "text guidelines" in the HIG, And in the KDE Documentation
> Guide(duplication perhaps)? Or have all text related(such as word
> reference) in the latter and reference that from the HIG and so forth?

I am quite happy to have the same content appear in the KDE Documentation
Guide and elsewhere - the more places the content appears, the more likely
that new contributors will find it. If this is done, we can discuss
technical ways to keep multiple guides in sync (entities, etc).

> I also think we should consider copy what the GNOME devs have done right
> off(HIG/Text Style Guide/whatever's suitable) and rewrite sections which
> are GNOME specific or exclude what we don't agree/understand(that's in my
> plans for some things). The GNOME folks do good stuff, and there's no
> reason to reinvent the wheel. We should also keep in mind that we will
> establish many new rules, and it wouldn't hurt if they happended to be
> identical to the GNOME HIG.

Lauri Watts has an early version of a joint KDE/GNOME style guide, which may
be of interest to you. I can't remember the link at the moment, but if
you're interested, I can find it, along with some more details.

Regards,
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20040826/837900f6/attachment-0001.pgp


------------------------------

Message: 4
Date: Thu, 26 Aug 2004 15:16:58 +0200
From: Per Lindstr?m 

Subject: Re: flags and countries
To: KDE i18n-doc 
Message-ID: <200408261516.59738.per.lindstrom@rixmail.se>
Content-Type: text/plain; charset="utf-8"

torsdagen den 26 augusti 2004 12.16 skrev Marko Rosic:
> On среда 25 август 2004 21:36, Nicolas Goutte wrote:
> > > Why?... I think kdebase/l10n/sr belongs to Suriname not to Serbia.
> > 
> > Why? I do not know. We were talking about a Serbian flag and one came
> > up. (I did not realised that it was committed in the wrong directory.)
> 
> Corrected, sorry for the inconvinience :D
> 
> Though, Suriname was a flag for Serbian keyboard for a long time?!

and "C" for Laotian, Polish (qwerty) & Frensh (alternate),
Algerian for Dzongka/Tibetan,
Bahamas for Bosnian,
Laotian for Georgian (latin) & Latin American,
Mali for Malayalam,
Russian for Georgian (russian) and
US for Croatian (amrican) & Maltese (american layout).

At least vor version 3.2.3

/Per Lindström


------------------------------

Message: 5
Date: Thu, 26 Aug 2004 14:42:32 +0100
From: Kevin Donnelly 
Subject: Re: KDE Doc: We Need Writing Style Guide
To: kde-i18n-doc@kde.org
Message-ID: <200408261442.32564.kevin@dotmon.com>
Content-Type: text/plain; charset="utf-8"

On Thursday 26 August 2004 5:05 am, Frans Englich wrote:
> We will apparently write tons of docs. In my work, I've discovered a lack
> of standardization in how texts should be designed, and I think that needs
> some clarification.

Well, call me a twit, but what's all this dirigisme that's coming over people? 
First Gerard, now you!

> I started writing on two KDE Usability Articles but stopped since the above
> needed to be resolved first(and I doubt KUA is the right place). They're
> attached as example; they are buggy and incomplete and duplicate other
> docs(in case that shouldn't be clear..)

With the greatest respect, some of this makes no sense at all. KUA5 suggests 
using restart instead of reboot, which means we now have three words where 
formerly there was one (ie "restart your computer" instead of "reboot", 
because you have to specify what it is you're going to restart, so that the 
user doesn't think it's restarting a program, for instance). Is prolixity 
now a desirable element in doc-writing? Likewise for "default" and "restore 
initial settings".

Some points are non-points - "program's" is "of the program", "programs' " is 
"of the programs (plural)"; "lets" is an incorrect spelling of "let's" (="let 
us"), except where it's the 3rd pers sg of "let".

I don't want to whinge about KUA6 as well, although I could, but to take just 
one example:
"If a problem is solved by creating device nodes or changing permissions, do 
not ask the user to do that - he/she can't. Instead, show a link-label 
stating for example "Permissions for the device needs to be granted, you can 
do so by clicking here" and let the command be run through kdesu."
??? I'd rather know what I'm supposed to do instead of having it done for me 
and possibly messing up something else. And if you were previously assuming 
that the user can't change permissions by following a text message, you're 
now assuming that he has root access. In an office environment this may not 
be the case.

I think it's preferable to write some (any) documentation rather than worry 
excessively about whether a comma or bullet point is in the right place 
compared to where it was in some other documentation.

-- 

Pob hwyl (Best wishes)

Kevin Donnelly

www.kyfieithu.co.uk - Meddalwedd Rhydd yn Gymraeg
www.cymrux.org.uk - Linux Cymraeg ar un CD!


------------------------------

Message: 6
Date: Thu, 26 Aug 2004 15:57:36 +0200
From: Vedran Ljubovi? 
Subject: Re: Improving KDE with translators
To: KDE i18n-doc 
Message-ID: <200408261505.33010.vedran-liste@smartnet.ba>
Content-Type: text/plain; charset="iso-8859-1"

On Sunday 22 August 2004 09:04, Grard Delafond wrote:
(...)
> I suggest translations could be classified on a 5 stars scale
> -5 stars : perfect = 100% in GUIS, docs, screenshots, and no keyboard
> shortcuts clashes (as possible), more than 10 translators, more than 3
> years experience
> -4 stars : more than 90 % of the GUIs, 70% of the docs, screenshots of all
> translated apps
> -3 stars : more than 60 % of GUIs, 50 % of the docs, numerous screenshots
> -2 stars : 2 translators at least, more than 1 year, 20% of the GUIS, no
> docs -1 star : 1 translator, few GUIS, no doc, new team

So you would really like to make me feel bad about my (unpaid) work, because I 
can never dream to secure more then 2 stars by myself and I can't find anyone 
to help me?


------------------------------

Message: 7
Date: Thu, 26 Aug 2004 10:56:28 -0400
From: Erik Kj?r Pedersen 
Subject: Re: Improving KDE with translators
To: KDE i18n-doc 
Message-ID: <200408261056.28567.erik@binghamton.edu>
Content-Type: text/plain; charset="utf-8"

Torsdag 26 august 2004 09:57 skrev Vedran Ljubović:
> On Sunday 22 August 2004 09:04, Gérard Delafond wrote:
> (...)
> 
> > I suggest translations could be classified on a 5 stars scale
> > -5 stars : perfect = 100% in GUIS, docs, screenshots, and no keyboard
> > shortcuts clashes (as possible), more than 10 translators, more than 3
> > years experience
> > -4 stars : more than 90 % of the GUIs, 70% of the docs, screenshots of
> > all translated apps
> > -3 stars : more than 60 % of GUIs, 50 % of the docs, numerous screenshots
> > -2 stars : 2 translators at least, more than 1 year, 20% of the GUIS, no
> > docs -1 star : 1 translator, few GUIS, no doc, new team
> 
> So you would really like to make me feel bad about my (unpaid) work,
> because I can never dream to secure more then 2 stars by myself and I can't
> find anyone to help me?

Well if Gerard ever gets any of this crab through I am certainly quitting. I 
have rarely in my life heard nonsense like this.

Erik


------------------------------

Message: 8
Date: Thu, 26 Aug 2004 19:06:41 +0200
From: Nicolas Goutte 
Subject: Re: flags and countries
To: KDE i18n-doc 
Message-ID: <200408261906.41309.nicolasg@snafu.de>
Content-Type: text/plain; charset="utf-8"

On Thursday 26 August 2004 15:16, Per Lindström wrote:
> torsdagen den 26 augusti 2004 12.16 skrev Marko Rosic:
> > On среда 25 август 2004 21:36, Nicolas Goutte wrote:
> > > > Why?... I think kdebase/l10n/sr belongs to Suriname not to Serbia.
> > > 
> > > Why? I do not know. We were talking about a Serbian flag and one came
> > > up. (I did not realised that it was committed in the wrong directory.)
> > 
> > Corrected, sorry for the inconvinience :D
> > 
> > Though, Suriname was a flag for Serbian keyboard for a long time?!
> 
> and "C" for Laotian, Polish (qwerty) & Frensh (alternate),
> Algerian for Dzongka/Tibetan,
> Bahamas for Bosnian,
> Laotian for Georgian (latin) & Latin American,
> Mali for Malayalam,
> Russian for Georgian (russian) and
> US for Croatian (amrican) & Maltese (american layout).

Well, that are probably other problems (which of course would be nice to fix 
too.)

Have a nice day!

> 
> At least vor version 3.2.3
> 
> /Per Lindström



------------------------------

Message: 9
Date: Thu, 26 Aug 2004 19:32:22 +0100
From: Malcolm Hunter 
Subject: Re: problems with kbabel
To: KDE i18n-doc 
Message-ID: <200408261932.22480.malcolm.hunter@gmx.co.uk>
Content-Type: text/plain; charset="iso-8859-1"

On Thursday 26 Aug 2004 12:13, Rinse de Vries wrote:
> Op maandag 23 augustus 2004 16:52, schreef averneka@moj.net:
> > I can report similar problems. KBabel crashes if I open a .po file from
> > the Catalog Manager. The problem is probably not connected to the
> > kde-redhat rpms as I compiled KDE from source on Fedora core
> 
> On my system a corrupted translation database is often the cause of a
> unstable kbabel.
> Try removing it and see if it helps.
> If the database gets corrupted very often you can try to make it readonly.
> Some teammembers reported that problems with the translation database don't
> happen when its readonly :o)

The only annoying problem I get now is there is no text in the comment field 
whenever I open a file. Press PgDn, PgUp and it appears. Anyone else 
experience that?

Regards,
Malcolm
-- 
KDE Proof Reading Team
KDE British English Translation Team

http://i18n.kde.org/teams/info/en_GB


------------------------------

Message: 10
Date: Thu, 26 Aug 2004 22:07:48 +0300
From: Claudiu Costin 
Subject: Re: Old soc statistics for KDE_3_2_BRANCH
To: KDE i18n-doc 
Message-ID: <200408262207.52062@kde_is_very_cool>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

On Joi 26 August 2004 02:22, Erik Kjr Pedersen wrote:
> Onsdag 25 august 2004 18:53 skrev Pedro Morais:
> > Em Quarta, 25 de Agosto de 2004 22:48, Claudiu Costin escreveu:
> > > Dear friends,
> > > 
> > > Is there any team arround who improve translations
> > > for KDE_3_2_BRANCH and want to see associated DOC
> > > stats at http://i18n.kde.org/stats/doc/KDE_3_2_/BRANCH/ ?
> > > 
> > > If not, them I'll not update them anymore because
> > > take time and (maybe) serve nothing.
> > 
> > The pt_PT team has abandoned the 3_2_BRANCH with the release of 3.3.
> 
> I don't think it makes sense for anybody to work on KDE_3_2_BRANCH any more
> 
> Erik (Danish team)
> 
Ok, I'll disable them.

I observed that doc stats are bad. I think I screwed something
please give little time fix it (this weekend).

P.S. Sorry for spelling and URL mistakes. I was tired and in hurry.

-- 
kind regards,
Claudiu Costin, claudiuc@kde.org
Linux-KDE Romania http://www.ro.kde.org


------------------------------

_______________________________________________
kde-i18n-doc mailing list
kde-i18n-doc@kde.org
https://mail.kde.org/mailman/listinfo/kde-i18n-doc


End of kde-i18n-doc Digest, Vol 17, Issue 41
********************************************

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


[Attachment #3 (text/html)]

<DIV>dear sir, </DIV>
<DIV>&nbsp; stop giving me a mail.... i cannot read it for i am busy with my study \
these days... am student here in india..</DIV> <DIV>thanks</DIV>
<DIV>yeshi.<BR><BR><B><I>kde-i18n-doc-request@kde.org</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: \
#1010ff 2px solid">Send kde-i18n-doc mailing list submissions \
to<BR>kde-i18n-doc@kde.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, \
visit<BR>https://mail.kde.org/mailman/listinfo/kde-i18n-doc<BR>or, via email, send a \
message with subject or body 'help' to<BR>kde-i18n-doc-request@kde.org<BR><BR>You can \
reach the person managing the list at<BR>kde-i18n-doc-owner@kde.org<BR><BR>When \
replying, please edit your Subject line so it is more specific<BR>than "Re: Contents \
of kde-i18n-doc digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. Re: flags and \
countries (Marko Rosic)<BR>2. Re: problems with kbabel (Rinse de Vries)<BR>3. Re: KDE \
Doc: We Need Writing Style Guide (Philip Rodrigues)<BR>4. Re: flags and countries \
(Per Lindstr?m)<BR>5. Re: KDE Doc: We Need Writing Style Guide (Kevin Donnelly)<BR>6. \
Re: Improving KDE with translators (Vedran Ljubovi?)<BR>7. Re: Improving KDE with \
translators (Erik  Kj?r Pedersen)<BR>8. Re: flags and countries (Nicolas \
Goutte)<BR>9. Re: problems with kbabel (Malcolm Hunter)<BR>10. Re: Old soc statistics \
for KDE_3_2_BRANCH (Claudiu \
Costin)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: \
1<BR>Date: Thu, 26 Aug 2004 12:16:39 +0200<BR>From: Marko Rosic \
<ROSKE@KDE.ORG.YU><BR>Subject: Re: flags and countries<BR>To: KDE i18n-doc \
<KDE-I18N-DOC@KDE.ORG><BR>Message-ID: \
&lt;200408261216.39982.roske@kde.org.yu&gt;<BR>Content-Type: text/plain; \
charset="utf-8"<BR><BR>On среда 25 август 2004 21:36, Nicolas Goutte \
wrote:<BR><BR>&gt; &gt; Why?... I think kdebase/l10n/sr belongs to Suriname not to \
Serbia.<BR>&gt;<BR>&gt; Why? I do not know. We were talking about a Serbian flag and \
one came<BR>&gt; up. (I did not realised that it was committed in the wrong \
directory.)<BR><BR>Corrected, sorry for the inconvinience :D<BR><BR>Though, Suriname \
was a flag for Serbian keyboard for a long time?!<BR><BR>--  <BR>Срдачан \
поздрав,<BR>Марко &nbsp;осић - Marko Rosić<BR>Kоординатор \
пројекта KDE на српском - KDE in Serbian project \
coordinator<BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Thu, \
26 Aug 2004 13:13:56 +0200<BR>From: Rinse de Vries <RINSEDEVRIES@KDE.NL><BR>Subject: \
Re: problems with kbabel<BR>To: averneka@moj.net, KDE i18n-doc \
<KDE-I18N-DOC@KDE.ORG><BR>Message-ID: \
&lt;200408261313.57046.rinsedevries@kde.nl&gt;<BR>Content-Type: text/plain; \
charset="us-ascii"<BR><BR>Op maandag 23 augustus 2004 16:52, schreef \
averneka@moj.net:<BR>&gt; I can report similar problems. KBabel crashes if I open a \
.po file from the<BR>&gt; Catalog Manager. The problem is probably not connected to \
the kde-redhat<BR>&gt; rpms as I compiled KDE from source on Fedora core<BR><BR>On my \
system a corrupted translation database is often the cause of a unstable \
<BR>kbabel.<BR>Try removing it and see if it helps.<BR>If the database gets  \
corrupted very often you can try to make it readonly. <BR>Some teammembers reported \
that problems with the translation database don't <BR>happen when its readonly \
:o)<BR><BR>Rinse<BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: \
Thu, 26 Aug 2004 11:03:50 +0100<BR>From: Philip Rodrigues \
<PHILIP.RODRIGUES@CHCH.OX.AC.UK><BR>Subject: Re: KDE Doc: We Need Writing Style \
Guide<BR>To: kde-i18n-doc@kde.org<BR>Message-ID: \
&lt;200408261103.56610.philip.rodrigues@chch.ox.ac.uk&gt;<BR>Content-Type: \
text/plain; charset="us-ascii"<BR><BR>[I'm not subscribed to some of the other lists \
this message went to, and can't <BR>immediately see how to use gmane, so if this \
message is relevant to them, <BR>please forward, thanks]<BR><BR>Frans Englich \
wrote:<BR><BR>&gt; We will apparently write tons of docs. In my work, I've discovered \
a lack<BR>&gt; of standardization in how texts should be designed, and I think that \
needs<BR>&gt; some clarification.<BR>&gt; <BR>&gt; I see three text  areas which \
needs standardization:<BR>&gt; <BR>&gt; 1. Texts in interfaces; labels, buttons \
etc.<BR>&gt; 2. Application/KDE documentation<BR>&gt; 3. In-house documents<BR>&gt; \
<BR>&gt; I think 2) and 3) can be treated as same, and is covered by:<BR>&gt; \
http://i18n.kde.org/doc/doc-primer<BR><BR>Agreed. Use of DocBook for 3 helps \
standardization too.<BR><BR>&gt; These are issues I've found a lack of \
coordination(regardles of area):<BR>&gt; <BR>&gt; A. Details on how to write texts \
for 2) and 3) above. For example, should<BR>&gt; we use endashes or emdashes? Should \
bullet lists end with a period? (etc.<BR>&gt; etc.) I guess this should go \
in:<BR>&gt; http://i18n.kde.org/doc/doc-primer<BR><BR>If we come up with guidelines \
on these issues, then the doc primer would be<BR>a good place to put them. If you \
wish to discuss them further, you could<BR>try contacting the proofreaders on \
kde-doc-english, as they have some<BR>guidelines already, and can tell you more about \
the issues arising  from<BR>using proofreading guidelines.<BR><BR>On the other hand, \
I have to agree with David Johnson that we have a lot of<BR>trouble recruiting and \
keeping documentation writers without adding a<BR>greater burden of very specific \
house style.<BR><BR>&gt; B. A much needed standardization of words and phrases. Badly \
needed.<BR>&gt; Should power management be referred to as ACPI, APM or Power \
Management?<BR>&gt; Display/Monitor? Etc. Etc.<BR><BR>If further discussion takes \
place on this issue, could you please cc<BR>kde-doc-english, since this might tie in \
with our renovation of the<BR>glossary, going on at the moment.<BR><BR>&gt; C. Rules \
for writing texts for GUIs; Judging from reading kde-cvs we need<BR>&gt; guidelines \
that says "don't use smilies; don't use caps; don't pull jokes"<BR>&gt; -- basic \
stuff<BR><BR>This also applies for documentation, so I'll add it \
at<BR>http://i18n.kde.org/doc/doc-primer/grammar.html<BR>If anyone comes up with more \
ideas along these lines, please tell  us at<BR>kde-doc-english.<BR><BR>&gt; Should we \
have "text guidelines" in the HIG, And in the KDE Documentation<BR>&gt; \
Guide(duplication perhaps)? Or have all text related(such as word<BR>&gt; reference) \
in the latter and reference that from the HIG and so forth?<BR><BR>I am quite happy \
to have the same content appear in the KDE Documentation<BR>Guide and elsewhere - the \
more places the content appears, the more likely<BR>that new contributors will find \
it. If this is done, we can discuss<BR>technical ways to keep multiple guides in sync \
(entities, etc).<BR><BR>&gt; I also think we should consider copy what the GNOME devs \
have done right<BR>&gt; off(HIG/Text Style Guide/whatever's suitable) and rewrite \
sections which<BR>&gt; are GNOME specific or exclude what we don't \
agree/understand(that's in my<BR>&gt; plans for some things). The GNOME folks do good \
stuff, and there's no<BR>&gt; reason to reinvent the wheel. We should also keep in \
mind that we will<BR>&gt; establish many new  rules, and it wouldn't hurt if they \
happended to be<BR>&gt; identical to the GNOME HIG.<BR><BR>Lauri Watts has an early \
version of a joint KDE/GNOME style guide, which may<BR>be of interest to you. I can't \
remember the link at the moment, but if<BR>you're interested, I can find it, along \
with some more details.<BR><BR>Regards,<BR>Philip<BR>-------------- next part \
--------------<BR>A non-text attachment was scrubbed...<BR>Name: not \
available<BR>Type: application/pgp-signature<BR>Size: 187 bytes<BR>Desc: not \
available<BR>Url : http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20040826/837900f6/attachment-0001.pgp<BR><BR>------------------------------<BR><BR>Message: \
4<BR>Date: Thu, 26 Aug 2004 15:16:58 +0200<BR>From: Per Lindstr?m \
<PER.LINDSTROM@RIXMAIL.SE><BR>Subject: Re: flags and countries<BR>To: KDE i18n-doc \
<KDE-I18N-DOC@KDE.ORG><BR>Message-ID: \
&lt;200408261516.59738.per.lindstrom@rixmail.se&gt;<BR>Content-Type: text/plain; \
charset="utf-8"<BR><BR>torsdagen den 26 augusti  2004 12.16 skrev Marko \
Rosic:<BR>&gt; On среда 25 август 2004 21:36, Nicolas Goutte \
wrote:<BR>&gt; &gt; &gt; Why?... I think kdebase/l10n/sr belongs to Suriname not to \
Serbia.<BR>&gt; &gt;<BR>&gt; &gt; Why? I do not know. We were talking about a Serbian \
flag and one came<BR>&gt; &gt; up. (I did not realised that it was committed in the \
wrong directory.)<BR>&gt;<BR>&gt; Corrected, sorry for the inconvinience \
:D<BR>&gt;<BR>&gt; Though, Suriname was a flag for Serbian keyboard for a long \
time?!<BR><BR>and "C" for Laotian, Polish (qwerty) &amp; Frensh \
(alternate),<BR>Algerian for Dzongka/Tibetan,<BR>Bahamas for Bosnian,<BR>Laotian for \
Georgian (latin) &amp; Latin American,<BR>Mali for Malayalam,<BR>Russian for Georgian \
(russian) and<BR>US for Croatian (amrican) &amp; Maltese (american layout).<BR><BR>At \
least vor version 3.2.3<BR><BR>/Per \
Lindström<BR><BR><BR>------------------------------<BR><BR>Message: 5<BR>Date: Thu, \
26 Aug 2004 14:42:32 +0100<BR>From: Kevin Donnelly  <KEVIN@DOTMON.COM><BR>Subject: \
Re: KDE Doc: We Need Writing Style Guide<BR>To: kde-i18n-doc@kde.org<BR>Message-ID: \
&lt;200408261442.32564.kevin@dotmon.com&gt;<BR>Content-Type: text/plain; \
charset="utf-8"<BR><BR>On Thursday 26 August 2004 5:05 am, Frans Englich \
wrote:<BR>&gt; We will apparently write tons of docs. In my work, I've discovered a \
lack<BR>&gt; of standardization in how texts should be designed, and I think that \
needs<BR>&gt; some clarification.<BR><BR>Well, call me a twit, but what's all this \
dirigisme that's coming over people? <BR>First Gerard, now you!<BR><BR>&gt; I started \
writing on two KDE Usability Articles but stopped since the above<BR>&gt; needed to \
be resolved first(and I doubt KUA is the right place). They're<BR>&gt; attached as \
example; they are buggy and incomplete and duplicate other<BR>&gt; docs(in case that \
shouldn't be clear..)<BR><BR>With the greatest respect, some of this makes no sense \
at all. KUA5 suggests <BR>using restart instead of reboot, which  means we now have \
three words where <BR>formerly there was one (ie "restart your computer" instead of \
"reboot", <BR>because you have to specify what it is you're going to restart, so that \
the <BR>user doesn't think it's restarting a program, for instance). Is prolixity \
<BR>now a desirable element in doc-writing? Likewise for "default" and "restore \
<BR>initial settings".<BR><BR>Some points are non-points - "program's" is "of the \
program", "programs' " is <BR>"of the programs (plural)"; "lets" is an incorrect \
spelling of "let's" (="let <BR>us"), except where it's the 3rd pers sg of \
"let".<BR><BR>I don't want to whinge about KUA6 as well, although I could, but to \
take just <BR>one example:<BR>"If a problem is solved by creating device nodes or \
changing permissions, do <BR>not ask the user to do that - he/she can't. Instead, \
show a link-label <BR>stating for example "Permissions for the device needs to be \
granted, you can <BR>do so by clicking here" and let the command be run through  \
kdesu."<BR>??? I'd rather know what I'm supposed to do instead of having it done for \
me <BR>and possibly messing up something else. And if you were previously assuming \
<BR>that the user can't change permissions by following a text message, you're \
<BR>now assuming that he has root access. In an office environment this may not \
<BR>be the case.<BR><BR>I think it's preferable to write some (any) documentation \
rather than worry <BR>excessively about whether a comma or bullet point is in the \
right place <BR>compared to where it was in some other documentation.<BR><BR>-- \
<BR><BR>Pob hwyl (Best wishes)<BR><BR>Kevin Donnelly<BR><BR>www.kyfieithu.co.uk - \
Meddalwedd Rhydd yn Gymraeg<BR>www.cymrux.org.uk - Linux Cymraeg ar un \
CD!<BR><BR><BR>------------------------------<BR><BR>Message: 6<BR>Date: Thu, 26 Aug \
2004 15:57:36 +0200<BR>From: Vedran Ljubovi? <VEDRAN-LISTE@SMARTNET.BA><BR>Subject: \
Re: Improving KDE with translators<BR>To: KDE i18n-doc \
<KDE-I18N-DOC@KDE.ORG><BR>Message-ID:  \
&lt;200408261505.33010.vedran-liste@smartnet.ba&gt;<BR>Content-Type: text/plain; \
charset="iso-8859-1"<BR><BR>On Sunday 22 August 2004 09:04, Grard Delafond \
wrote:<BR>(...)<BR>&gt; I suggest translations could be classified on a 5 stars \
scale<BR>&gt; -5 stars : perfect = 100% in GUIS, docs, screenshots, and no \
keyboard<BR>&gt; shortcuts clashes (as possible), more than 10 translators, more than \
3<BR>&gt; years experience<BR>&gt; -4 stars : more than 90 % of the GUIs, 70% of the \
docs, screenshots of all<BR>&gt; translated apps<BR>&gt; -3 stars : more than 60 % of \
GUIs, 50 % of the docs, numerous screenshots<BR>&gt; -2 stars : 2 translators at \
least, more than 1 year, 20% of the GUIS, no<BR>&gt; docs -1 star : 1 translator, few \
GUIS, no doc, new team<BR><BR>So you would really like to make me feel bad about my \
(unpaid) work, because I <BR>can never dream to secure more then 2 stars by myself \
and I can't find anyone <BR>to help  \
me?<BR><BR><BR>------------------------------<BR><BR>Message: 7<BR>Date: Thu, 26 Aug \
2004 10:56:28 -0400<BR>From: Erik Kj?r Pedersen <ERIK@BINGHAMTON.EDU><BR>Subject: Re: \
Improving KDE with translators<BR>To: KDE i18n-doc \
<KDE-I18N-DOC@KDE.ORG><BR>Message-ID: \
&lt;200408261056.28567.erik@binghamton.edu&gt;<BR>Content-Type: text/plain; \
charset="utf-8"<BR><BR>Torsdag 26 august 2004 09:57 skrev Vedran Ljubović:<BR>&gt; \
On Sunday 22 August 2004 09:04, Gérard Delafond wrote:<BR>&gt; (...)<BR>&gt;<BR>&gt; \
&gt; I suggest translations could be classified on a 5 stars scale<BR>&gt; &gt; -5 \
stars : perfect = 100% in GUIS, docs, screenshots, and no keyboard<BR>&gt; &gt; \
shortcuts clashes (as possible), more than 10 translators, more than 3<BR>&gt; &gt; \
years experience<BR>&gt; &gt; -4 stars : more than 90 % of the GUIs, 70% of the docs, \
screenshots of<BR>&gt; &gt; all translated apps<BR>&gt; &gt; -3 stars : more than 60 \
% of GUIs, 50 % of the docs, numerous screenshots<BR>&gt; &gt; -2 stars :  2 \
translators at least, more than 1 year, 20% of the GUIS, no<BR>&gt; &gt; docs -1 star \
: 1 translator, few GUIS, no doc, new team<BR>&gt;<BR>&gt; So you would really like \
to make me feel bad about my (unpaid) work,<BR>&gt; because I can never dream to \
secure more then 2 stars by myself and I can't<BR>&gt; find anyone to help \
me?<BR><BR>Well if Gerard ever gets any of this crab through I am certainly quitting. \
I <BR>have rarely in my life heard nonsense like \
this.<BR><BR>Erik<BR><BR><BR>------------------------------<BR><BR>Message: \
8<BR>Date: Thu, 26 Aug 2004 19:06:41 +0200<BR>From: Nicolas Goutte \
<NICOLASG@SNAFU.DE><BR>Subject: Re: flags and countries<BR>To: KDE i18n-doc \
<KDE-I18N-DOC@KDE.ORG><BR>Message-ID: \
&lt;200408261906.41309.nicolasg@snafu.de&gt;<BR>Content-Type: text/plain; \
charset="utf-8"<BR><BR>On Thursday 26 August 2004 15:16, Per Lindström \
wrote:<BR>&gt; torsdagen den 26 augusti 2004 12.16 skrev Marko Rosic:<BR>&gt; &gt; On \
среда 25 август 2004 21:36,  Nicolas Goutte wrote:<BR>&gt; &gt; &gt; &gt; \
Why?... I think kdebase/l10n/sr belongs to Suriname not to Serbia.<BR>&gt; &gt; \
&gt;<BR>&gt; &gt; &gt; Why? I do not know. We were talking about a Serbian flag and \
one came<BR>&gt; &gt; &gt; up. (I did not realised that it was committed in the wrong \
directory.)<BR>&gt; &gt;<BR>&gt; &gt; Corrected, sorry for the inconvinience \
:D<BR>&gt; &gt;<BR>&gt; &gt; Though, Suriname was a flag for Serbian keyboard for a \
long time?!<BR>&gt;<BR>&gt; and "C" for Laotian, Polish (qwerty) &amp; Frensh \
(alternate),<BR>&gt; Algerian for Dzongka/Tibetan,<BR>&gt; Bahamas for \
Bosnian,<BR>&gt; Laotian for Georgian (latin) &amp; Latin American,<BR>&gt; Mali for \
Malayalam,<BR>&gt; Russian for Georgian (russian) and<BR>&gt; US for Croatian \
(amrican) &amp; Maltese (american layout).<BR><BR>Well, that are probably other \
problems (which of course would be nice to fix <BR>too.)<BR><BR>Have a nice \
day!<BR><BR>&gt;<BR>&gt; At least vor version 3.2.3<BR>&gt;<BR>&gt; /Per  \
 reported that problems with the translation database don't<BR>&gt; happen when its \
readonly :o)<BR><BR>The only annoying problem I get now is there is no text in the \
comment field <BR>whenever I open a file. Press PgDn, PgUp and it appears. Anyone \
else <BR>experience that?<BR><BR>Regards,<BR>Malcolm<BR>-- <BR>KDE Proof Reading \
Team<BR>KDE British English Translation \
Team<BR><BR>http://i18n.kde.org/teams/info/en_GB<BR><BR><BR>------------------------------<BR><BR>Message: \
10<BR>Date: Thu, 26 Aug 2004 22:07:48 +0300<BR>From: Claudiu Costin \
<CLAUDIUC@KDE.ORG><BR>Subject: Re: Old soc statistics for KDE_3_2_BRANCH<BR>To: KDE \
i18n-doc <KDE-I18N-DOC@KDE.ORG><BR>Message-ID: \
&lt;200408262207.52062@kde_is_very_cool&gt;<BR>Content-Type: text/plain; \
charset="iso-8859-1"<BR><BR>Hi,<BR><BR>On Joi 26 August 2004 02:22, Erik Kjr \
Pedersen wrote:<BR>&gt; Onsdag 25 august 2004 18:53 skrev Pedro Morais:<BR>&gt; &gt; \
Em Quarta, 25 de Agosto de 2004 22:48, Claudiu Costin escreveu:<BR>&gt; &gt; &gt; \
Dear  friends,<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Is there any team arround who \
improve translations<BR>&gt; &gt; &gt; for KDE_3_2_BRANCH and want to see associated \
DOC<BR>&gt; &gt; &gt; stats at http://i18n.kde.org/stats/doc/KDE_3_2_/BRANCH/ \
?<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; If not, them I'll not update them anymore \
because<BR>&gt; &gt; &gt; take time and (maybe) serve nothing.<BR>&gt; &gt;<BR>&gt; \
&gt; The pt_PT team has abandoned the 3_2_BRANCH with the release of 3.3.<BR>&gt; \
<BR>&gt; I don't think it makes sense for anybody to work on KDE_3_2_BRANCH any \
more<BR>&gt; <BR>&gt; Erik (Danish team)<BR>&gt; <BR>Ok, I'll disable them.<BR><BR>I \
observed that doc stats are bad. I think I screwed something<BR>please give little \
time fix it (this weekend).<BR><BR>P.S. Sorry for spelling and URL mistakes. I was \
tired and in hurry.<BR><BR>-- <BR>kind regards,<BR>Claudiu Costin, \
claudiuc@kde.org<BR>Linux-KDE Romania  \
http://www.ro.kde.org<BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>kde-i18n-doc \
mailing list<BR>kde-i18n-doc@kde.org<BR>https://mail.kde.org/mailman/listinfo/kde-i18n-doc<BR><BR><BR>End \
of kde-i18n-doc Digest, Vol 17, Issue \
41<BR>********************************************<BR></BLOCKQUOTE><p>__________________________________________________<br>Do \
You Yahoo!?<br>Tired of spam?  Yahoo! Mail has the best spam protection around \
<br>http://mail.yahoo.com 



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

Configure | About | News | Add a list | Sponsored by KoreLogic