Return-Path: Delivered-To: apmail-tapestry-users-archive@www.apache.org Received: (qmail 62892 invoked from network); 4 Dec 2008 09:19:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2008 09:19:19 -0000 Received: (qmail 5553 invoked by uid 500); 4 Dec 2008 09:19:27 -0000 Delivered-To: apmail-tapestry-users-archive@tapestry.apache.org Received: (qmail 5539 invoked by uid 500); 4 Dec 2008 09:19:27 -0000 Mailing-List: contact users-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tapestry users" Delivered-To: mailing list users@tapestry.apache.org Received: (qmail 5528 invoked by uid 99); 4 Dec 2008 09:19:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2008 01:19:27 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jwlasko@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2008 09:17:56 +0000 Received: by ug-out-1314.google.com with SMTP id j30so4392550ugc.13 for ; Thu, 04 Dec 2008 01:18:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=/6IXaR++8cYyGS9sxlJ3LBNLr9eHCjbH+ANnG9e4UHQ=; b=AbJOGucdu4qW/EyYAlSb0aKjQeMs1ULebS4ZsZdn8DM1W0BZk8Vc1WVdk2knPICoEQ zdiDq2VODrqvtzxmy2OPcrIH5QfgySe0+PMF/xLcQAqah/sMS7dZ/5T+peoXAVNMwF9L TP1DGho8qWBfE2vE11Uzm9hGhgM1gzHuQCLug= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=sUja2Lxpk43bE50jBkDpGM6QNuzCXuPKn3WUePwpiajqUGwmjmj/P1rPLKZmGDjG43 CYDzpc6Tu7VRHSvjCTNIp7pxe6SqP2wbPu3u2ioiqWihxt3YSVlPBwSCfeyhVBlr3eXl hxpWp+/vy+ez8mLFRjR1gt2o2dWcC8pVEUZ94= Received: by 10.103.222.1 with SMTP id z1mr6716184muq.100.1228382322989; Thu, 04 Dec 2008 01:18:42 -0800 (PST) Received: by 10.103.198.2 with HTTP; Thu, 4 Dec 2008 01:18:42 -0800 (PST) Message-ID: <633a82060812040118s4caef5b0n8acac36e780c9345@mail.gmail.com> Date: Thu, 4 Dec 2008 10:18:42 +0100 From: "Jakub Vlasak" To: "Tapestry users" Subject: Re: [T5] 5.0.16 Spanish special characters In-Reply-To: <5258d8d70812040108k5965dd6bnf4d3a46583ba7eef@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4824_30892969.1228382322966" References: <5258d8d70812020631v4480d3c6n88426ec703d97de2@mail.gmail.com> <1228327119.4936c8cf15fc1@www.inbox.lv> <6d5c24d40812031744y1b5d8e45vfcbfd4f71149e258@mail.gmail.com> <5258d8d70812040108k5965dd6bnf4d3a46583ba7eef@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4824_30892969.1228382322966 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, i've had similar problem with slovak character, and I've solved it ba adding the UTF-8 encoding parameter to the java compiler. Edit the pom.xml file, the maven-compiler-plugin like this: org.apache.maven.plugins maven-compiler-plugin 1.5 1.5 true *UTF-8* Hope this will help. On Thu, Dec 4, 2008 at 10:08 AM, Ray wrote: > I've put in logging on the java page when bringing back the message, and > its > coming out incorrectly with ? instead of the special characters, so its > nothing to do with the html I believe. > > I've since learned that the fact that im using Windows may also be having > an > effect as it may be saving the file in a format that is unexpected by > Tapestry, but im only hedging a guess there really. > > Thanks for the feedback so far, its been great. > > > > > On Thu, Dec 4, 2008 at 1:44 AM, dh ning wrote: > > > That's true, native2ascii is unnecessarily any more. > > Try to locate the issue whether it is caused at server side or by html > page > > encoding. > > What's that value in tapestry page.java level? If it is correct, then > this > > should be the html encoding problem. > > 2008/12/4 Thiago H. de Paula Figueiredo > > > > > Em Wed, 03 Dec 2008 14:58:39 -0300, Imants Firsts > > > escreveu: > > > > > > Hi Ray! > > >> > > >> The properties files should be in ascii encoding and the unicode > > >> characters should be escaped with \u, for example "\u0161" for > š > > >> character. JDK comes with native2ascii tool that does the conversion. > > >> > > > > > > That's not correct anymore. Since some Tapestry version I don't recall, > > the > > > property files need to be UTF-8 encoded, so no conversion needs to be > > done. > > > > > > From http://tapestry.apache.org/tapestry5/guide/localization.html: > > > > > > "Properties File Charset > > > > > > Tapestry uses the UTF-8 charset when reading the properties files in a > > > message catalog. This means that you don't have to use the Java > > native2ascii > > > tool." > > > > > > > > > -- > > > Thiago H. de Paula Figueiredo > > > Independent Java consultant, developer, and instructor > > > Consultor, desenvolvedor e instrutor em Java > > > http://www.arsmachina.com.br/thiago > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org > > > For additional commands, e-mail: users-help@tapestry.apache.org > > > > > > > > > ------=_Part_4824_30892969.1228382322966--