🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: pl.comp.lang.java
Article #153120

Re: kodowania znaków

#153120
From: Jacek Czerwinski
Date: Sat, 12 Nov 2011 12:58
5 lines
1343 bytes
W dniu 2011-11-12 09:30, Hollow Quincy pisze:

> Jakiego kodowania powinienem użyć UTF-8, UTF-16, Unicode,
UTF-8 i UTF-16 to JEST Unicode.
Ewentualnie ja cię nie rozumiem.
Technical Details
Message-ID: <j9lqh7$vjh$1@news.onet.pl>
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!news.onet.pl!.POSTED!not-for-mail
References: <76fe3b04-a851-44de-9908-1745ab57fdc4@r9g2000vbw.googlegroups.com> <j9eavk$8qq$1@news.onet.pl> <j9ebcd$ad7$1@news.onet.pl> <j9ebh8$agn$1@news.onet.pl> <j9ebl8$b6b$1@news.onet.pl> <bf023f23-90da-41f7-95a6-e7b2c6965f61@s5g2000vbe.googlegroups.com> <j9fp4q$a7f$1@news.onet.pl> <d1397dfb-f5be-4258-a9a3-c4159e04fff3@s7g2000yqa.googlegroups.com>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!news.onet.pl!.POSTED!not-for-mail
From: Jacek Czerwinski <x@y.z.pl>
Newsgroups: pl.comp.lang.java
Subject: Re: kodowania znaków
Date: Sat, 12 Nov 2011 13:58:14 +0100
Organization: http://onet.pl
Lines: 5
Message-ID: <j9lqh7$vjh$1@news.onet.pl>
References: <76fe3b04-a851-44de-9908-1745ab57fdc4@r9g2000vbw.googlegroups.com> <j9eavk$8qq$1@news.onet.pl> <j9ebcd$ad7$1@news.onet.pl> <j9ebh8$agn$1@news.onet.pl> <j9ebl8$b6b$1@news.onet.pl> <bf023f23-90da-41f7-95a6-e7b2c6965f61@s5g2000vbe.googlegroups.com> <j9fp4q$a7f$1@news.onet.pl> <d1397dfb-f5be-4258-a9a3-c4159e04fff3@s7g2000yqa.googlegroups.com>
NNTP-Posting-Host: 77-254-215-234.adsl.inetia.pl
Mime-Version: 1.0
X-Trace: news.onet.pl 1321102695 32369 77.254.215.234 (12 Nov 2011 12:58:15 GMT)
X-Complaints-To: niusy@onet.pl
NNTP-Posting-Date: Sat, 12 Nov 2011 12:58:15 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
In-Reply-To: <d1397dfb-f5be-4258-a9a3-c4159e04fff3@s7g2000yqa.googlegroups.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit