¡° ¤Þz¡mmaddog(a)linuxhall.xn--orgn g-ygaczlu4vrwf1v
> Lio wrote (on) Today:
> > =A1=B0 =A4=DE=ADz=A1mmaddog(a)linuxhall.org (R.I.P. Deaddog)=A1n=A4=A7=BB=
> =CA=A8=A5=A1G
> > =B3=CC=AA=F1=B5=DB=A4=E2=C2=BD=C4=B6Gimp=AA=BAhelp=C0=C9=A1A=A7=C6=B1=
> =E6=B9L=B0}=A4l=B4N=AF=E0=A7=B9=A6=A8
> > =A9=A1=AE=C9=ADY=A6=B3=C2=D5=BB~=C1=D9=B1=E6=BD=D0=AB=FC=A5=BF :)
> > ps.=A5\=AF=E0=AA=BA=A6W=BA=D9=A1A=AD=EC=ABh=A4W=ACO=A4=A3=C2=BD
> You mean the help files from gimp!? Whoa, that means a great deal of work.
> Keep on your effort! :)
是的，就是Gimp1.2.2的求助檔
> For those functionality inside Gimp I was dealing with, I just try to
> translate those which have widely used translation, was used in other
> famous software (e.g. photoshop), or easy to understand ones. I dare not
> touch those entries having uncomprehensible meanings or having no good
> translation. But there are more than 4000 entries, so need somebody to
> review them too. Perhaps I can send them to you for reviewing once
> all/some po files are done?
我盡我的力量去翻譯，不過像是Filter的名稱不必要翻得，我就不會去做了
如果您願意寄給我的話，我也很樂意看po檔 :-)
--
[1;32m※ Origin: [33m碩誠資訊 [37m<bbs.cynix.com.tw> [m
[1;31m◆ From: [36m220196.d13-220.ncu.edu.tw[m
I am interested to know whether the following characters
which are part of ETen and the Microsoft Big5 implementation
are so commonplace nowadays in Traditional Chinese "Big5"
locales that they might be considered to be 'de-facto'
part of the common Big5 standards.
0xF9D6, 0xF9D7, 0xF9D8, 0xF9DA, 0xF9DB, 0xF9DC
The Big5 mapping on unicode.org site and the list of
source characters from the original (1984?) Big5
de-facto standard mapping table (in Unihan.txt for
Unicode 3.1) doesn't include these characters.
In reality are these characters now so widely implemented
in Tradional Chinese/Taiwanese Big5 locales on all
major information processing platforms (eg windows/unix/mainframe)
that it makes sense to fold them back into the common Big5
character set and to view them as de-facto rather than
characters which are particular to one or more of the Big5
extensions?
--Ian.
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Secure all your Web servers now: Get your FREE Guide and learn to: DEPLOY THE LATEST ENCRYPTION,
DELIVER TRANSPARENT PROTECTION, and More!
http://us.click.yahoo.com/VihfLB/nT7CAA/yigFAA/23wwlB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
i18n-chinese-unsubscribe(a)egroups.com
URL to this group:
http://www.egroups.com/group/i18n-chinese
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
On Wed, 22 Aug 2001, Thomas Diehl wrote:
> And what should the directory be named to (considering that we are
> about to switch to 3 letter codes anyway)? Anything else which will
> have to be adapted after the renaming?
If it's for the KDE 2.2.1 release, rename it to zh_TW.
Norwegian University of Science and Technology, Engineering Cybernetics
bieker(a)stud.ntnu.no / bieker(a)kde.org / +47 97651633
Dagaliveien 25 A | Elgesetergate 23 B
N-0776 Oslo | N-7030 Trondheim
Siste nytt fra industrien finner du på: WWW.Industri-Informasjon.NO
On Mon, 20 Aug 2001, Thomas Diehl wrote:
> I have to leave that to the people responsible for CVS and kcmlocale
> matters (ie to Coolo and to Hans Petter). Maybe they can comment on
> this.
We will do this after KDE 2.2.1. Even if you changed to UTF-8 in KDE
2.2.1, it will not be smart to rename the translation because it means
that the user would have to change the language in kcmlocale again.
And changing the .po file encoding isn't really smart unless it's a major
release. The reason is that some third part applications may be shipped
with the translations, and they should still work after you upgrade.
> Personally, I suspect that we won't probably do that for 2.2.1 since
> this should only be a bug fix release with minimal code changes. (I'm
> also no sure how this naming scheme would break the utf-8 conversion?)
It wouldn't break it. And the UTF-8 change is for HEAD only. It should
still be supported in KDE 2.2.x.
> After 2.2.1 we will probably have a lot of renaming since we are aiming
> at a conversion to 3-letter codes. This would be a better occasion to
> find a solution for the naming of traditonal Chinese as well.
Right.
Norwegian University of Science and Technology, Engineering Cybernetics
bieker(a)stud.ntnu.no / bieker(a)kde.org / +47 97651633
Dagaliveien 25 A | Elgesetergate 23 B
N-0776 Oslo | N-7030 Trondheim
Siste nytt fra industrien finner du på: WWW.Industri-Informasjon.NO
Hi,
I am translating kdemultimedia, any objection ?
Regards
Joe Man
_________________________________________________________
Do You Yahoo!?
建立個人網站 http://geocities.yahoo.com.hk
Build your own website at http://geocities.yahoo.com.hk
