From geeklog-translations-admin at lists.geeklog.net  Thu Feb  5 14:51:56 2004
From: geeklog-translations-admin at lists.geeklog.net (geeklog-translations-admin at lists.geeklog.net)
Date: Thu, 5 Feb 2004 20:51:56 +0100
Subject: [geeklog-translations] Script to merge language files with english.php
Message-ID: <20040205195156.8336@smtp.haun-online.de>

Hi,

I wrote a tiny little script that can merge a (foreign) language file
with english.php, thus (hopefully) helping in updating the language files
when a new version of Geeklog comes out.

I plan to run all of the existing language files through this script
prior to the release of the first release candidate for the next version
of Geeklog (which is still a few weeks away). I have done some tests, but
would like to hear some feedback, whether you consider it useful.

The script was written for Geeklog 1.3.9, but should work just fine with
older versions. So you can run it on the language files you already have
(it also does some source code beautifying as a side effect).

The script can be downloaded from geeklog.net:

    http://www.geeklog.net/filemgmt/singlefile.php?lid=290

I'm including the README below.

bye, Dirk

--- snip ---
lm.php v0.1

This little script merges a Geeklog (foreign) language file with the
english.php language file, so that new strings added to english.php are
automatically added to the other language file as well.

Usage:

    lm.php langfile.php > new-langfile.php

This script, while written in PHP, is supposed to be run from the command
line and thus requires the CLI version of PHP to be installed on your
computer. It also displays the merged language file on the screen, so you
should redirect the output to a new file. It also expects to find the
english.php language file in the current directory.

What it can do:

- add new individual strings and string arrays to the language file
- does some pretty printing

What it can not do:

- remove obsoleted strings
- detect changed strings

Since we don't usually remove obsoleted strings from Geeklog (in the hope
that they can be reused at a later date), the first issue shouldn't be a
problem.

For changes in existing strings, it is recommended that you subscribe to
the geeklog-translations mailing list, where such information will be posted
when a new version of Geeklog is about to be released.

You can subscribe to the Geeklog mailing lists at

    http://lists.geeklog.net/listinfo

This script was written for Geeklog 1.3.9, which has not been released at
the time of this writing. It should work just fine with language files
from older versions, though.

This script was written 2004 by Dirk Haun, <dirk at haun-online.de>,
and is released under the GNU General Public License v2.
--- snip ---


-- 
http://www.haun-online.de/
http://www.tinyweb.de/



From dirk at haun-online.de  Mon Feb 16 17:11:25 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 16 Feb 2004 23:11:25 +0100
Subject: [geeklog-translations] Language files in Geeklog 1.3.9rc1
Message-ID: <20040216221126.16820@smtp.haun-online.de>

In case you haven't seen it: The first Release Candidate for Geeklog
1.3.9 is available:

    http://www.geeklog.net/article.php?story=20040216152145594

As announced, I have now run all of the existing language files through
the "merge" script (see my earlier post).

This means that all the included language files can be used right away -
only the new strings will be in English. I will compile a (probably
short) list of the text strings that have changed since 1.3.8, as my
script did not catch those, and post it here later this week.

As usual, please send any updated language files to my email address (as
a .zip or .gz file, please!) and I will make sure that they will be
included in the next release.

bye, Dirk


-- 
http://www.geeklog.net/
http://geeklog.info/



From ihra at dlc.fi  Tue Feb 17 07:12:28 2004
From: ihra at dlc.fi (Jussi Josefsson)
Date: Tue, 17 Feb 2004 14:12:28 +0200
Subject: [geeklog-translations] Finnish translation for 1.3.9rc1
Message-ID: <4032214C.20621.2034C6F6@localhost>

Hello,

I updated the finnish.php to get along the 1.3.9rc1. I followed the 
instructions and left the obsolete admin/word.php strings intact.

I uploaded zipped language file to geeklog.net, hopefully it would be 
available soon.

Shortly in finnish (for search engines):

Geeklog 1.3.9rc1 suomenkielinen kieli-tiedosto. K??nnettyn? 
uusimmasta kielitiedostosta suomenkielelle.

Yours,

Jussi "ihra" Josefsson

--
Ihra * Ugi * Mieli-Kieli-Keho * ihra at dlc.fi
http://www.nominaali.net
Rokki-Ukki




From geeklog-translations at 1212.co.il  Thu Feb 19 12:46:21 2004
From: geeklog-translations at 1212.co.il (Tal Vizel)
Date: Thu, 19 Feb 2004 19:46:21 +0200
Subject: [geeklog-translations] Language files in Geeklog 1.3.9rc1
References: <20040216221126.16820@smtp.haun-online.de>
Message-ID: <00df01c3f710$4a7d2a00$7e4416ac@PENTUME>

I have Hebrew translation. It's not finished completely, but most important
things are
translated.
I use utf-8 encoding.

----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-translations at lists.geeklog.net>
Sent: Tuesday, February 17, 2004 12:11 AM
Subject: [geeklog-translations] Language files in Geeklog 1.3.9rc1


> In case you haven't seen it: The first Release Candidate for Geeklog
> 1.3.9 is available:
> 
>     http://www.geeklog.net/article.php?story=20040216152145594
> 
> As announced, I have now run all of the existing language files through
> the "merge" script (see my earlier post).
> 
> This means that all the included language files can be used right away -
> only the new strings will be in English. I will compile a (probably
> short) list of the text strings that have changed since 1.3.8, as my
> script did not catch those, and post it here later this week.
> 
> As usual, please send any updated language files to my email address (as
> a .zip or .gz file, please!) and I will make sure that they will be
> included in the next release.
> 
> bye, Dirk
> 
> 
> -- 
> http://www.geeklog.net/
> http://geeklog.info/
> 
> _______________________________________________
> geeklog-translations mailing list
> geeklog-translations at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-translations
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hebrew.php
Type: application/octet-stream
Size: 71340 bytes
Desc: not available
URL: <https://pairlist8.pair.net/pipermail/geeklog-translations/attachments/20040219/4c35b204/attachment.obj>

From dirk at haun-online.de  Sat Feb 21 11:40:34 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 21 Feb 2004 17:40:34 +0100
Subject: [geeklog-translations] Language files in Geeklog 1.3.9rc1
In-Reply-To: <20040216221126.16820@smtp.haun-online.de>
References: <20040216221126.16820@smtp.haun-online.de>
Message-ID: <20040221164034.15813@smtp.haun-online.de>

I wrote:

>I will compile a (probably
>short) list of the text strings that have changed since 1.3.8, as my
>script did not catch those, and post it here later this week.

Sorry, took me a bit longer than expected. Here it is now:

in $LANG21

old: 18 => "Please fill in the Block Title, Security Level and Content
fields",
new: 18 => 'Please fill in the Block Title and Content fields',

There's no way you can not fill in the security settings for a block ...


also in $LANG21

old: 31 => 'Error in PHP Block.  Function, $function, does not exist.',
new: 31 => 'Error in PHP Block.  Function, %s, does not exist.',

With $function, it can't display the actual function name here.


and again in $LANG21

old: 42 => "You must enter the blockorder and security level for Geeklog
default blocks",
new: 42 => 'You must enter the block title and block order for Geeklog
default blocks.',

That message was simply wrong in telling the user which entries had to be
filled in.


in $MESSAGE

old: 6 => "Your display preferences have been successfully saved.",
new: 6 => 'Your preferences have been successfully saved.',

The "Display Preferences" menu entry (in the User Functions block) was
renamed to "Preferences" in 1.3.8.


also in $MESSAGE

old: 21 => "The new user has been successfully saved.",
new: 21 => 'The user has been successfully saved.',

That message was confusing, as it always said a _new_ user was saved,
even if you only edited an existing user's information.


That's all (5 changes). All the other new text strings have already been
merged into the language files. You only need to translate them. Please
note that a few previously empty strings are now being used, so not all
new strings are at the end of the arrays.

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



From gape at gape.org  Mon Feb 23 15:13:25 2004
From: gape at gape.org (gape)
Date: Mon, 23 Feb 2004 21:13:25 +0100
Subject: [geeklog-translations] Language files in Geeklog 1.3.9rc1
References: <20040216221126.16820@smtp.haun-online.de> <20040221164034.15813@smtp.haun-online.de>
Message-ID: <0ae601c3fa49$7e95f7e0$1700a8c0@gapelt>

it looks to me that i don't understand this diff thing
http://cvs.geeklog.net/chora/diff.php/geeklog-1.3/language/slovenian.php?r1=1.4&r2=1.5&ty=u&Horde=06fffa610336476d09b0afcab765a7e2

dirk you mentioned 5 diffs

next one is
in LANG21 
57 =>

diff is not working for me, it states all lines to be different

is there a list of lines that were changed since the last version, i.e. 1.3.8. ?
i understand there are more ... 
*
| That's all (5 changes). All the other new text strings have already been
| merged into the language files. You only need to translate them. Please
| note that a few previously empty strings are now being used, so not all
| new strings are at the end of the arrays.
*


or should i check it line by line?

With Love & Light
gape
www.gape.org


----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-translations at lists.geeklog.net>
Sent: Saturday, February 21, 2004 5:40 PM
Subject: Re: [geeklog-translations] Language files in Geeklog 1.3.9rc1


| I wrote:
| 
| >I will compile a (probably
| >short) list of the text strings that have changed since 1.3.8, as my
| >script did not catch those, and post it here later this week.
| 
| Sorry, took me a bit longer than expected. Here it is now:
| 
| in $LANG21
| 
| old: 18 => "Please fill in the Block Title, Security Level and Content
| fields",
| new: 18 => 'Please fill in the Block Title and Content fields',
| 
| There's no way you can not fill in the security settings for a block ...
| 
| 
| also in $LANG21
| 
| old: 31 => 'Error in PHP Block.  Function, $function, does not exist.',
| new: 31 => 'Error in PHP Block.  Function, %s, does not exist.',
| 
| With $function, it can't display the actual function name here.
| 
| 
| and again in $LANG21
| 
| old: 42 => "You must enter the blockorder and security level for Geeklog
| default blocks",
| new: 42 => 'You must enter the block title and block order for Geeklog
| default blocks.',
| 
| That message was simply wrong in telling the user which entries had to be
| filled in.
| 
| 
| in $MESSAGE
| 
| old: 6 => "Your display preferences have been successfully saved.",
| new: 6 => 'Your preferences have been successfully saved.',
| 
| The "Display Preferences" menu entry (in the User Functions block) was
| renamed to "Preferences" in 1.3.8.
| 
| 
| also in $MESSAGE
| 
| old: 21 => "The new user has been successfully saved.",
| new: 21 => 'The user has been successfully saved.',
| 
| That message was confusing, as it always said a _new_ user was saved,
| even if you only edited an existing user's information.
| 
| 
| That's all (5 changes). All the other new text strings have already been
| merged into the language files. You only need to translate them. Please
| note that a few previously empty strings are now being used, so not all
| new strings are at the end of the arrays.
| 
| bye, Dirk
| 
| 
| -- 
| http://www.haun-online.de/
| http://www.macosx-faq.de/
| 
| _______________________________________________
| geeklog-translations mailing list
| geeklog-translations at lists.geeklog.net
| http://lists.geeklog.net/listinfo/geeklog-translations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-translations/attachments/20040223/80957b50/attachment.html>

From dirk at haun-online.de  Mon Feb 23 15:33:48 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 23 Feb 2004 21:33:48 +0100
Subject: [geeklog-translations] Language files in Geeklog 1.3.9rc1
In-Reply-To: <0ae601c3fa49$7e95f7e0$1700a8c0@gapelt>
References: <0ae601c3fa49$7e95f7e0$1700a8c0@gapelt>
Message-ID: <20040223203348.15533@smtp.haun-online.de>

Gape,

>diff is not working for me, it states all lines to be different

That's because I ran all the language files through my "merge" script. It
automatically added all the _new_ strings, but also does some pretty-
printing (e.g. preferrably enclosing the strings in single quotes instead
of double quotes).

The 5 changes I posted wdere those that the script could not find, since
the texts were not new.


>or should i check it line by line?

I would have hoped that the English strings are easy to spot. Apologies
if that's not the case.

I was actually hoping that it would be easier this way, as you wouldn't
have to mess with diff and possibly overlooking texts ...

bye, Dirk


-- 
http://www.haun-online.de/
http://www.haun.info/



From sam at stonemicro.com  Tue Feb 24 02:40:34 2004
From: sam at stonemicro.com (Samuel Stone)
Date: Tue, 24 Feb 2004 02:40:34 -0500
Subject: [geeklog-translations] Comment on Chinese Translations
In-Reply-To: <20040221180011.15148.94311.Mailman@internal.iowaoutdoors.org>
Message-ID: <008301c3faa9$7ff02f10$9ef4fea9@Vaio>

Hi Dirk,

Thanks for packaging the two Chinese translations in GB and Big5 codes.
>From my experience, these codes have much limitations when used with
Geeklog.  I had to convert them to Unicode(UTF-8) on my sites.  Unicode is
replacing these codes and much flexible in usage.  I suggest that we package
the unicode version for Chinese translations in the future because it works
better with GL.

Sam



-----Original Message-----
From: geeklog-translations-request at lists.geeklog.net
[mailto:geeklog-translations-request at lists.geeklog.net] 
Sent: Saturday, February 21, 2004 1:00 PM
To: geeklog-translations at lists.geeklog.net
Subject: geeklog-translations digest, Vol 1 #30 - 1 msg


Send geeklog-translations mailing list submissions to
	geeklog-translations at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-translations
or, via email, send a message with subject or body 'help' to
	geeklog-translations-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-translations-admin at lists.geeklog.net

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


Today's Topics:

   1. Re: Language files in Geeklog 1.3.9rc1 (Dirk Haun)

--__--__--

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-translations at lists.geeklog.net>
Subject: Re: [geeklog-translations] Language files in Geeklog 1.3.9rc1
Date: Sat, 21 Feb 2004 17:40:34 +0100
Organization: Terra Software Systems
Reply-To: geeklog-translations at lists.geeklog.net

I wrote:

>I will compile a (probably
>short) list of the text strings that have changed since 1.3.8, as my 
>script did not catch those, and post it here later this week.

Sorry, took me a bit longer than expected. Here it is now:

in $LANG21

old: 18 => "Please fill in the Block Title, Security Level and Content
fields",
new: 18 => 'Please fill in the Block Title and Content fields',

There's no way you can not fill in the security settings for a block ...


also in $LANG21

old: 31 => 'Error in PHP Block.  Function, $function, does not exist.',
new: 31 => 'Error in PHP Block.  Function, %s, does not exist.',

With $function, it can't display the actual function name here.


and again in $LANG21

old: 42 => "You must enter the blockorder and security level for Geeklog
default blocks",
new: 42 => 'You must enter the block title and block order for Geeklog
default blocks.',

That message was simply wrong in telling the user which entries had to be
filled in.


in $MESSAGE

old: 6 => "Your display preferences have been successfully saved.",
new: 6 => 'Your preferences have been successfully saved.',

The "Display Preferences" menu entry (in the User Functions block) was
renamed to "Preferences" in 1.3.8.


also in $MESSAGE

old: 21 => "The new user has been successfully saved.",
new: 21 => 'The user has been successfully saved.',

That message was confusing, as it always said a _new_ user was saved, even
if you only edited an existing user's information.


That's all (5 changes). All the other new text strings have already been
merged into the language files. You only need to translate them. Please note
that a few previously empty strings are now being used, so not all new
strings are at the end of the arrays.

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



--__--__--

_______________________________________________
geeklog-translations mailing list geeklog-translations at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-translations


End of geeklog-translations Digest






From dirk at haun-online.de  Tue Feb 24 15:56:30 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Tue, 24 Feb 2004 21:56:30 +0100
Subject: [geeklog-translations] Comment on Chinese Translations
In-Reply-To: <008301c3faa9$7ff02f10$9ef4fea9@Vaio>
References: <008301c3faa9$7ff02f10$9ef4fea9@Vaio>
Message-ID: <20040224205630.8461@smtp.haun-online.de>

Sam,

>Thanks for packaging the two Chinese translations in GB and Big5 codes.
>From my experience, these codes have much limitations when used with
>Geeklog.  I had to convert them to Unicode(UTF-8) on my sites.  Unicode is
>replacing these codes and much flexible in usage.  I suggest that we package
>the unicode version for Chinese translations in the future because it works
>better with GL.

I have no experience or knowledge with asian languages, so I wouldn't
know. The two original files were sent in by native speakers. They seemed
to work, so I included them. I guess it wouldn't hurt to include all 4
variants, at least for a while?

I noticed that Geeklog's beautifying attempts (in the preferences) failed
with your UTF-8 files: "Chinese (Fan_utf-8)" and "Chinese (Jan_utf-8)"
don't look to good (and onyl differ in one character). I could attempt to
get rid of the underscore and use an uppercase 'U': "Chinese (Fan Utf-8)"
... Not much better. Any ideas?

Also, I seem to remember that you uploaded some other UTF-8 language
files on geeklog.net but I never approved them since you uploaded them as
.php files, which are a bit of a pain to handle with the File Management
plugin (you have to approve and immediately withdraw them, then pack them
manually and update the information manually, too). Are you planning to
update those for 1.3.9, too?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



From sam at stonemicro.com  Wed Feb 25 18:39:31 2004
From: sam at stonemicro.com (Samuel Stone)
Date: Wed, 25 Feb 2004 18:39:31 -0500
Subject: [geeklog-translations] UTF-8 Code files
In-Reply-To: <20040225180011.23950.38181.Mailman@internal.iowaoutdoors.org>
Message-ID: <001e01c3fbf8$9f8bb420$1202a8c0@samstone>

Hi Dirk,

Including all 4 would be a better idea.  Unicode is now preferred
because of multi-lingual exchangeability with Western languages and now
almost all new Chinese software that came out in 2003 use Unicode.
Having all 4 would at least provide backward compatibility.

By beautifying, do you mean the look of name itself?  I wondered about
that too.  Average users will not know what UTF-8 is.  How about just
name it straight forwardly as "Jan" and "Fan" or "Simplified" and
"Traditional", or even "Sim" and "Trad"?  As long as the installer
himself know that's Unicode, that's enough.

Regarding other languages in utf-8 that I submitted before.  I do have
English version for my sites because they need to mix English with
Chinese.  I am glad that you remember I submitted once before.  Since I
wasn't informed why it wasn't approved, I thought I must have stepped on
someone's toe in messing up with their translations.  Later I realized
that it must be because I didn't archive them.

I can definitely help in converting files of other languages to UTF-8 to
make Geeklog switchable between Asian and European languages. I love GL
and would be very happy if I can be useful.

If you agree, I will start submitting UTF-8 files for other languages
that I am able to convert successfully.

Sam



-----Original Message-----
From: geeklog-translations-request at lists.geeklog.net
[mailto:geeklog-translations-request at lists.geeklog.net] 
Sent: Wednesday, February 25, 2004 1:00 PM
To: geeklog-translations at lists.geeklog.net
Subject: geeklog-translations digest, Vol 1 #32 - 1 msg


Send geeklog-translations mailing list submissions to
	geeklog-translations at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-translations
or, via email, send a message with subject or body 'help' to
	geeklog-translations-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-translations-admin at lists.geeklog.net

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


Today's Topics:

   1. Re: Comment on Chinese Translations (Dirk Haun)

--__--__--

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-translations at lists.geeklog.net>
Subject: Re: [geeklog-translations] Comment on Chinese Translations
Date: Tue, 24 Feb 2004 21:56:30 +0100
Organization: Terra Software Systems
Reply-To: geeklog-translations at lists.geeklog.net

Sam,

>Thanks for packaging the two Chinese translations in GB and Big5 codes.

>From my experience, these codes have much limitations when used with 
>Geeklog.  I had to convert them to Unicode(UTF-8) on my sites.  Unicode

>is replacing these codes and much flexible in usage.  I suggest that we

>package the unicode version for Chinese translations in the future 
>because it works better with GL.

I have no experience or knowledge with asian languages, so I wouldn't
know. The two original files were sent in by native speakers. They
seemed to work, so I included them. I guess it wouldn't hurt to include
all 4 variants, at least for a while?

I noticed that Geeklog's beautifying attempts (in the preferences)
failed with your UTF-8 files: "Chinese (Fan_utf-8)" and "Chinese
(Jan_utf-8)" don't look to good (and onyl differ in one character). I
could attempt to get rid of the underscore and use an uppercase 'U':
"Chinese (Fan Utf-8)" ... Not much better. Any ideas?

Also, I seem to remember that you uploaded some other UTF-8 language
files on geeklog.net but I never approved them since you uploaded them
as .php files, which are a bit of a pain to handle with the File
Management plugin (you have to approve and immediately withdraw them,
then pack them manually and update the information manually, too). Are
you planning to update those for 1.3.9, too?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



--__--__--

_______________________________________________
geeklog-translations mailing list geeklog-translations at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-translations


End of geeklog-translations Digest





From euan at euans.net  Wed Feb 25 19:02:49 2004
From: euan at euans.net (Euan McKay)
Date: Thu, 26 Feb 2004 09:02:49 +0900 (JST)
Subject: [geeklog-translations] UTF-8 Code files
In-Reply-To: <001e01c3fbf8$9f8bb420$1202a8c0@samstone>
References: <20040225180011.23950.38181.Mailman@internal.iowaoutdoors.org>
    <001e01c3fbf8$9f8bb420$1202a8c0@samstone>
Message-ID: <33258.219.103.225.109.1077753769.squirrel@www.euans.net>

My 2 bits:

Keep the UTF-8 in the title. In the some cases, there are similar
encodings for different languages: eg EUC-JP and EUC-KR (Japanese and
Korean). Having the encoding is useful to some users - some users are
fairly computer literate, and it shouldn't be a problem in the case of
Chinese to have a UTF-8 in the title if it starts with "Traditional" or
"Simplified" etc. Also, in the case of Japanese there is no fundamental
difference between different language encodings as there is in Traditional
and Simplified Chinese, so you need Japanese-UTF-8, Japanese-EUC,
Japanese-SJIS, etc.

Sam, if you do the Japanese file into UTF-8 as well that would be a great
help.

Cheers,

Euan.

Samuel Stone said:
> Hi Dirk,
>
> Including all 4 would be a better idea.  Unicode is now preferred
> because of multi-lingual exchangeability with Western languages and now
> almost all new Chinese software that came out in 2003 use Unicode.
> Having all 4 would at least provide backward compatibility.
>
> By beautifying, do you mean the look of name itself?  I wondered about
> that too.  Average users will not know what UTF-8 is.  How about just
> name it straight forwardly as "Jan" and "Fan" or "Simplified" and
> "Traditional", or even "Sim" and "Trad"?  As long as the installer
> himself know that's Unicode, that's enough.
>
> Regarding other languages in utf-8 that I submitted before.  I do have
> English version for my sites because they need to mix English with
> Chinese.  I am glad that you remember I submitted once before.  Since I
> wasn't informed why it wasn't approved, I thought I must have stepped on
> someone's toe in messing up with their translations.  Later I realized
> that it must be because I didn't archive them.
>
> I can definitely help in converting files of other languages to UTF-8 to
> make Geeklog switchable between Asian and European languages. I love GL
> and would be very happy if I can be useful.
>
> If you agree, I will start submitting UTF-8 files for other languages
> that I am able to convert successfully.
>
> Sam
>


From sam at stonemicro.com  Thu Feb 26 01:26:03 2004
From: sam at stonemicro.com (Samuel Stone)
Date: Thu, 26 Feb 2004 01:26:03 -0500
Subject: [geeklog-translations] Uploade UTF-8 files
In-Reply-To: <20040225180011.23950.38181.Mailman@internal.iowaoutdoors.org>
Message-ID: <003101c3fc31$6b863360$9ef4fea9@Vaio>

Hi Dirk,

I uploaded 3 UTF-8 files while I was half asleep (English, German, and
Finnish).  So I don't know whether I submitted them archived or not, except
the last one. Please tell me so I can correct them.

Well, to make thing easier, since I will be busy with other things after
tonight, I will just reload the first two files archived.  Please delete the
.php files or the two repeated files.

I am a little sleepy, so please forgive me.

Sam




From sam at stonemicro.com  Thu Feb 26 14:09:14 2004
From: sam at stonemicro.com (Samuel Stone)
Date: Thu, 26 Feb 2004 14:09:14 -0500
Subject: [geeklog-translations] Japanese UTF-8
In-Reply-To: <20040226180010.32712.92631.Mailman@internal.iowaoutdoors.org>
Message-ID: <000001c3fc9c$07c2a3c0$1202a8c0@samstone>

Hi Euan,

Thanks for the comment.  I will try to convert the Japanese file.  Is it
updated for 1.3.9rc1 yet?  Should I just convert the one Dirk packaged
in the rc1?

Sam





-----Original Message-----
From: geeklog-translations-request at lists.geeklog.net
[mailto:geeklog-translations-request at lists.geeklog.net] 
Sent: Thursday, February 26, 2004 1:00 PM
To: geeklog-translations at lists.geeklog.net
Subject: geeklog-translations digest, Vol 1 #33 - 3 msgs


Send geeklog-translations mailing list submissions to
	geeklog-translations at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-translations
or, via email, send a message with subject or body 'help' to
	geeklog-translations-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-translations-admin at lists.geeklog.net

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


Today's Topics:

   1. UTF-8 Code files (Samuel Stone)
   2. Re: UTF-8 Code files (Euan McKay)
   3. Uploade UTF-8 files (Samuel Stone)

--__--__--

Message: 1
From: "Samuel Stone" <sam at stonemicro.com>
To: <geeklog-translations at lists.geeklog.net>
Date: Wed, 25 Feb 2004 18:39:31 -0500
Subject: [geeklog-translations] UTF-8 Code files
Reply-To: geeklog-translations at lists.geeklog.net

Hi Dirk,

Including all 4 would be a better idea.  Unicode is now preferred
because of multi-lingual exchangeability with Western languages and now
almost all new Chinese software that came out in 2003 use Unicode.
Having all 4 would at least provide backward compatibility.

By beautifying, do you mean the look of name itself?  I wondered about
that too.  Average users will not know what UTF-8 is.  How about just
name it straight forwardly as "Jan" and "Fan" or "Simplified" and
"Traditional", or even "Sim" and "Trad"?  As long as the installer
himself know that's Unicode, that's enough.

Regarding other languages in utf-8 that I submitted before.  I do have
English version for my sites because they need to mix English with
Chinese.  I am glad that you remember I submitted once before.  Since I
wasn't informed why it wasn't approved, I thought I must have stepped on
someone's toe in messing up with their translations.  Later I realized
that it must be because I didn't archive them.

I can definitely help in converting files of other languages to UTF-8 to
make Geeklog switchable between Asian and European languages. I love GL
and would be very happy if I can be useful.

If you agree, I will start submitting UTF-8 files for other languages
that I am able to convert successfully.

Sam



-----Original Message-----
From: geeklog-translations-request at lists.geeklog.net
[mailto:geeklog-translations-request at lists.geeklog.net] 
Sent: Wednesday, February 25, 2004 1:00 PM
To: geeklog-translations at lists.geeklog.net
Subject: geeklog-translations digest, Vol 1 #32 - 1 msg


Send geeklog-translations mailing list submissions to
	geeklog-translations at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-translations
or, via email, send a message with subject or body 'help' to
	geeklog-translations-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-translations-admin at lists.geeklog.net

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


Today's Topics:

   1. Re: Comment on Chinese Translations (Dirk Haun)

-- __--__-- 

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-translations at lists.geeklog.net>
Subject: Re: [geeklog-translations] Comment on Chinese Translations
Date: Tue, 24 Feb 2004 21:56:30 +0100
Organization: Terra Software Systems
Reply-To: geeklog-translations at lists.geeklog.net

Sam,

>Thanks for packaging the two Chinese translations in GB and Big5 codes.

>From my experience, these codes have much limitations when used with
>Geeklog.  I had to convert them to Unicode(UTF-8) on my sites.  Unicode

>is replacing these codes and much flexible in usage.  I suggest that we

>package the unicode version for Chinese translations in the future
>because it works better with GL.

I have no experience or knowledge with asian languages, so I wouldn't
know. The two original files were sent in by native speakers. They
seemed to work, so I included them. I guess it wouldn't hurt to include
all 4 variants, at least for a while?

I noticed that Geeklog's beautifying attempts (in the preferences)
failed with your UTF-8 files: "Chinese (Fan_utf-8)" and "Chinese
(Jan_utf-8)" don't look to good (and onyl differ in one character). I
could attempt to get rid of the underscore and use an uppercase 'U':
"Chinese (Fan Utf-8)" ... Not much better. Any ideas?

Also, I seem to remember that you uploaded some other UTF-8 language
files on geeklog.net but I never approved them since you uploaded them
as .php files, which are a bit of a pain to handle with the File
Management plugin (you have to approve and immediately withdraw them,
then pack them manually and update the information manually, too). Are
you planning to update those for 1.3.9, too?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



-- __--__-- 

_______________________________________________
geeklog-translations mailing list geeklog-translations at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-translations


End of geeklog-translations Digest




--__--__--

Message: 2
Date: Thu, 26 Feb 2004 09:02:49 +0900 (JST)
Subject: Re: [geeklog-translations] UTF-8 Code files
From: "Euan McKay" <euan at euans.net>
To: geeklog-translations at lists.geeklog.net
Reply-To: geeklog-translations at lists.geeklog.net

My 2 bits:

Keep the UTF-8 in the title. In the some cases, there are similar
encodings for different languages: eg EUC-JP and EUC-KR (Japanese and
Korean). Having the encoding is useful to some users - some users are
fairly computer literate, and it shouldn't be a problem in the case of
Chinese to have a UTF-8 in the title if it starts with "Traditional" or
"Simplified" etc. Also, in the case of Japanese there is no fundamental
difference between different language encodings as there is in
Traditional and Simplified Chinese, so you need Japanese-UTF-8,
Japanese-EUC, Japanese-SJIS, etc.

Sam, if you do the Japanese file into UTF-8 as well that would be a
great help.

Cheers,

Euan.

Samuel Stone said:
> Hi Dirk,
>
> Including all 4 would be a better idea.  Unicode is now preferred 
> because of multi-lingual exchangeability with Western languages and 
> now almost all new Chinese software that came out in 2003 use Unicode.

> Having all 4 would at least provide backward compatibility.
>
> By beautifying, do you mean the look of name itself?  I wondered about

> that too.  Average users will not know what UTF-8 is.  How about just 
> name it straight forwardly as "Jan" and "Fan" or "Simplified" and 
> "Traditional", or even "Sim" and "Trad"?  As long as the installer 
> himself know that's Unicode, that's enough.
>
> Regarding other languages in utf-8 that I submitted before.  I do have

> English version for my sites because they need to mix English with 
> Chinese.  I am glad that you remember I submitted once before.  Since 
> I wasn't informed why it wasn't approved, I thought I must have 
> stepped on someone's toe in messing up with their translations.  Later

> I realized that it must be because I didn't archive them.
>
> I can definitely help in converting files of other languages to UTF-8 
> to make Geeklog switchable between Asian and European languages. I 
> love GL and would be very happy if I can be useful.
>
> If you agree, I will start submitting UTF-8 files for other languages 
> that I am able to convert successfully.
>
> Sam
>

--__--__--

Message: 3
Date: Thu, 26 Feb 2004 01:26:03 -0500
From: Samuel Stone <sam at stonemicro.com>
To: geeklog-translations at lists.geeklog.net
Subject: [geeklog-translations] Uploade UTF-8 files
Reply-To: geeklog-translations at lists.geeklog.net

Hi Dirk,

I uploaded 3 UTF-8 files while I was half asleep (English, German, and
Finnish).  So I don't know whether I submitted them archived or not,
except the last one. Please tell me so I can correct them.

Well, to make thing easier, since I will be busy with other things after
tonight, I will just reload the first two files archived.  Please delete
the .php files or the two repeated files.

I am a little sleepy, so please forgive me.

Sam




--__--__--

_______________________________________________
geeklog-translations mailing list geeklog-translations at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-translations


End of geeklog-translations Digest





From dirk at haun-online.de  Thu Feb 26 17:07:37 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Thu, 26 Feb 2004 23:07:37 +0100
Subject: [geeklog-translations] UTF-8 Code files
In-Reply-To: <001e01c3fbf8$9f8bb420$1202a8c0@samstone>
References: <001e01c3fbf8$9f8bb420$1202a8c0@samstone>
Message-ID: <20040226220737.22747@smtp.haun-online.de>

Sam,

>By beautifying, do you mean the look of name itself?

Yes. Geeklog only has the file names to work with. So it takes
french_canada.php and presents it as French (Canada) to the user. Pretty
simple transformation.

If we could agree that, say, a second underscore would be translated into
a comma and a space, we could transform chinese_traditional_utf-8.php
into Chinese (Traditional, Utf-8). How's that?


>How about just
>name it straight forwardly as "Jan" and "Fan" or "Simplified" and
>"Traditional", or even "Sim" and "Trad"?  As long as the installer
>himself know that's Unicode, that's enough.

Well, I wouldn't know what "Jan" or "Fan" is supposed to mean, but then
again I wouldn't be able to read any of them ;-) I wouldn't worry about
lang file names, if that's what's keeping you from using "traditional" in
a name.

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



From euan at euans.net  Thu Feb 26 21:55:30 2004
From: euan at euans.net (Euan McKay)
Date: Fri, 27 Feb 2004 11:55:30 +0900 (JST)
Subject: [geeklog-translations] UTF-8 Code files
In-Reply-To: <20040226220737.22747@smtp.haun-online.de>
References: <001e01c3fbf8$9f8bb420$1202a8c0@samstone>
    <20040226220737.22747@smtp.haun-online.de>
Message-ID: <32819.219.103.224.166.1077850530.squirrel@www.euans.net>

> If we could agree that, say, a second underscore would be translated into
> a comma and a space, we could transform chinese_traditional_utf-8.php
> into Chinese (Traditional, Utf-8). How's that?

I'd second that. Makes sense to me.

japanese_utf-8.php
japanese_euc-jp.php

What does Sakata-san think?

Cheers,

Euan.


From sam at stonemicro.com  Fri Feb 27 22:54:30 2004
From: sam at stonemicro.com (Samuel Stone)
Date: Fri, 27 Feb 2004 22:54:30 -0500
Subject: [geeklog-translations] RE: geeklog-translations digest, Vol 1 #34 - 3 msgs
In-Reply-To: <20040227180014.9206.48249.Mailman@internal.iowaoutdoors.org>
Message-ID: <001e01c3fdae$91f78340$9ef4fea9@Vaio>

> If we could agree that, say, a second underscore
> would be translated into a comma and a space, we 
> could transform chinese_traditional_utf-8.php 
> into Chinese (Traditional, Utf-8). How's that?

I agree.  Let's also forget about Jan and Fan; we'll use English meaning
Simplified and Traditional.  For better beautifying effect, I would suggest
using UTF-8 rather than Utf-8.  I think it looks smother in the eyes.  So
the names for the Chinese packs will be:

chinese_traditional_UTF-8.php
chinese_simplified_UTF-8.php
chinese_BIG5.php
chinese_GB.php

All right?

(BTW, don't go watch The Passion of The Christ unless you are perfectly
healthy.  I came out with an headache, my mother came out nausea.  I still
have the headache after 24 hours.  Yes, it's powerful and life changing, but
it's a painful two hours.)

Sam







From euan at euans.net  Fri Feb 27 23:11:10 2004
From: euan at euans.net (Euan McKay)
Date: Sat, 28 Feb 2004 13:11:10 +0900 (JST)
Subject: [geeklog-translations] RE: geeklog-translations digest,
      Vol 1 #34 - 3 msgs
In-Reply-To: <001e01c3fdae$91f78340$9ef4fea9@Vaio>
References: <20040227180014.9206.48249.Mailman@internal.iowaoutdoors.org>
    <001e01c3fdae$91f78340$9ef4fea9@Vaio>
Message-ID: <33632.218.225.143.4.1077941470.squirrel@www.euans.net>

Would there be any point in adding an entry to the files with a
description of the contents? The charset is already in there, what about
adding strings for geeklog to use when displaying the options in the
language list?

$_LANG['en_GB'] = "English (British)";
$_LANG['ja_JP_UTF-8'] = "Japanese (Japan, UTF-8 encoding)";
$_LANG['ja_JP_EUC-JP'] = "Japanese (Japan, EUC-JP encoding)";
$_LANG['zh_CN_BIG5'] = "Chinese (China, BIG5 encoding)";
$_LANG['zh_CN_GB'] = "Chinese (China, GB encoding)";
$_LANG['zh_CN_jan_UTF-8'] = "Chinese (China, Simplified, UTF-8 encoding)";
$_LANG['zh_CN_fan_UTF-8'] = "Chinese (China, Traditional, UTF-8 encoding)";

etc.

This would give you a language-specific select box on the preferences
page, but would alos mean checking that each language file existed before
building the select box HTML and having these titles in every language
file. On the other hand:

* you wouldn't need to parse the filenames to get titles.
* you could create an admin panel to enable/disable languages if wanted
(although this could be done anyway).

Just an idea.

Euan.

Samuel Stone said:
>
>> If we could agree that, say, a second underscore
>> would be translated into a comma and a space, we
>> could transform chinese_traditional_utf-8.php
>> into Chinese (Traditional, Utf-8). How's that?
>
> I agree.  Let's also forget about Jan and Fan; we'll use English meaning
> Simplified and Traditional.  For better beautifying effect, I would
> suggest
> using UTF-8 rather than Utf-8.  I think it looks smother in the eyes.  So
> the names for the Chinese packs will be:
>
> chinese_traditional_UTF-8.php
> chinese_simplified_UTF-8.php
> chinese_BIG5.php
> chinese_GB.php
>
> All right?
>
> (BTW, don't go watch The Passion of The Christ unless you are perfectly
> healthy.  I came out with an headache, my mother came out nausea.  I still
> have the headache after 24 hours.  Yes, it's powerful and life changing,
> but
> it's a painful two hours.)
>
> Sam
>


From dirk at haun-online.de  Sat Feb 28 03:53:06 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 28 Feb 2004 09:53:06 +0100
Subject: [geeklog-translations] RE: geeklog-translations digest, Vol 1
 #34 - 3 msgs
In-Reply-To: <33632.218.225.143.4.1077941470.squirrel@www.euans.net>
References: <33632.218.225.143.4.1077941470.squirrel@www.euans.net>
Message-ID: <20040228085306.27768@smtp.haun-online.de>

Euan,

>Would there be any point in adding an entry to the files with a
>description of the contents?

Won't work, I'm afraid. Geeklog would have to load all the language files
first then, which would create conflicts with the current language file.

bye, Dirk


-- 
http://www.haun-online.de/
http://www.tinyweb.de/



From dirk at haun-online.de  Sat Feb 28 04:43:15 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 28 Feb 2004 10:43:15 +0100
Subject: [geeklog-translations] RE: geeklog-translations digest, Vol 1
 #34 - 3 msgs
In-Reply-To: <001e01c3fdae$91f78340$9ef4fea9@Vaio>
References: <001e01c3fdae$91f78340$9ef4fea9@Vaio>
Message-ID: <20040228094315.25814@smtp.haun-online.de>

Sam,

>I agree.  Let's also forget about Jan and Fan; we'll use English meaning
>Simplified and Traditional.  For better beautifying effect, I would suggest
>using UTF-8 rather than Utf-8.  I think it looks smother in the eyes.

I added some more guesswork to the beautifying code: If a word contains a
digit, it is displayed in all uppercase. Check it out in your preferences
on geeklog.net.

The file names are:

chinese_big5.php
chinese_gb2312.php
chinese_simplified_utf-8.php
chinese_traditional_utf-8.php

(I renamed the "Jan" file to "traditional" and "Fan" to "simplified" - I
hope that's correct)

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



From sam at stonemicro.com  Sat Feb 28 21:48:24 2004
From: sam at stonemicro.com (Samuel Stone)
Date: Sat, 28 Feb 2004 21:48:24 -0500
Subject: [geeklog-translations] Wrong guess
In-Reply-To: <20040228180011.17618.63329.Mailman@internal.iowaoutdoors.org>
Message-ID: <000601c3fe6e$81f858a0$1202a8c0@samstone>

> (I renamed the "Jan" file to "traditional" 
> and "Fan" to "simplified" - I hope that's correct)
>
> bye, Dirk

Oops!  It's just the opposite.  "Jan" means "Simplified" and "Fan" means
"Traditional."

Thanks for your automating the upper and lower cases.

Sam






From dirk at haun-online.de  Sun Feb 29 05:08:24 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 29 Feb 2004 11:08:24 +0100
Subject: [geeklog-translations] Wrong guess
In-Reply-To: <000601c3fe6e$81f858a0$1202a8c0@samstone>
References: <000601c3fe6e$81f858a0$1202a8c0@samstone>
Message-ID: <20040229100824.23080@smtp.haun-online.de>

Sam,

>Oops!  It's just the opposite.  "Jan" means "Simplified" and "Fan" means
>"Traditional."

Well, I did have a 50:50 chance ;-)

I've added your UTF-8 files to CVS now with the following names:

-rw-r--r--  1 dirk  dirk  47890 24 Feb 11:34 chinese_simplified_utf-8.php
-rw-r--r--  1 dirk  dirk  47912 24 Feb 11:33 chinese_traditional_utf-8.php
-rw-r--r--  1 dirk  dirk  55200 26 Feb 00:37 english_utf-8.php
-rw-r--r--  1 dirk  dirk  55271 26 Feb 01:06 finnish_utf-8.php
-rw-r--r--  1 dirk  dirk  58783 26 Feb 00:39 german_utf-8.php

They are also installed on geeklog.net.

It looks like we're going to release 1.3.9rc2 later today, and those will
already be included.

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/



From dirk at haun-online.de  Sun Feb 29 15:37:51 2004
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 29 Feb 2004 21:37:51 +0100
Subject: [geeklog-translations] Geeklog 1.3.9rc2 out - any more translations?
Message-ID: <20040229203751.32638@smtp.haun-online.de>

For those who haven't seen it: The second Release Candidate for Geeklog
1.3.9rc2 it now out:

    http://www.geeklog.net/article.php/2004022914355494

It includes new Croation, Finnish, Hebrew, and an updated Dutch
translation as well as UTF-8 versions of the Chinese, English, Finnish,
and German translations.

Barring any problems / surprises, the final 1.3.9 release could be out in
a week or two, so now would be a good time to send in any new or updated
translations that you want to see included in the final version ...

bye, Dirk


-- 
http://www.haun-online.de/
http://geeklog.info/



From geeklog-translations at 1212.co.il  Sun Feb 29 18:49:50 2004
From: geeklog-translations at 1212.co.il (Tal Vizel)
Date: Mon, 1 Mar 2004 01:49:50 +0200
Subject: [geeklog-translations] Fw: hebrew lang for GL
Message-ID: <003401c3ff1e$b97d3c40$7e4416ac@PENTUME>

This is the latest Hebrew translation for GL.

Is this a way that I will be able to update my translating by my self?



Also, is it possible to move "Event Type" in the "Submit a Event section in
the calendar, from config.php to the language file?



Tal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hebrew.php
Type: application/octet-stream
Size: 73303 bytes
Desc: not available
URL: <https://pairlist8.pair.net/pipermail/geeklog-translations/attachments/20040301/f497506a/attachment.obj>