Received: by 10.236.153.6 with SMTP id e6mr2784791yhk.20.1351930076869;
        Sat, 03 Nov 2012 01:07:56 -0700 (PDT)
X-BeenThere: tiddlywiki@googlegroups.com
Received: by 10.236.142.209 with SMTP id i57ls6171658yhj.2.gmail; Sat, 03 Nov
 2012 01:07:52 -0700 (PDT)
Received: by 10.236.180.134 with SMTP id j6mr319266yhm.15.1351930072183;
        Sat, 03 Nov 2012 01:07:52 -0700 (PDT)
Date: Sat, 3 Nov 2012 01:07:51 -0700 (PDT)
From: Helge <h3l93.ph1l...@gmail.com>
To: tiddlywiki@googlegroups.com
Message-Id: <b9aea75b-57f5-453c-b637-a7165022b928@googlegroups.com>
In-Reply-To: <529f708b-4010-4ddc-84fd-fb651d9dd981@googlegroups.com>
References: <508463B2.4010909@web.de>
 <CAPKKYJbzzb5Yz9eF89fbBUMQ1krP=-JL1McLDbbJ-bEBHS-YTw@mail.gmail.com>
 <907c3c49-9ab8-4823-ba50-27eba652fe96@googlegroups.com>
 <529f708b-4010-4ddc-84fd-fb651d9dd981@googlegroups.com>
Subject: Re: [tw] Unicode-Problems
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1086_7825860.1351930071678"

------=_Part_1086_7825860.1351930071678
Content-Type: multipart/alternative; 
	boundary="----=_Part_1087_29423728.1351930071678"

------=_Part_1087_29423728.1351930071678
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

With the new 2.7.0 beta it did work with the following line of characters:

=C3=AD=C3=A9=C3=A1tio=C3=B8=C3=A7`=C3=B1=E2=80=94=E2=80=A0=C2=BA=E2=81=8B

Thanks again for the advice!

Helge.

Am Mittwoch, 31. Oktober 2012 07:31:01 UTC+1 schrieb Helge:
>
> Ok, while looking at the forum I found your post there, Jeremy - of cours=
e=20
> you already did that! :-)
>
> Well, I'll try adding more unicodey characters and see if it works.
>
> Helge.
>
>
> Am Mittwoch, 31. Oktober 2012 07:26:38 UTC+1 schrieb Helge:
>>
>> Same here, did not work. The Dropbox app just shows different characters=
=20
>> but not the correct ones as Jan already reported.
>>
>> I'll post this in the Dropbox forum, maybe someone there will know how t=
o=20
>> fix it or will even make changes to the DB app to accomodate for unicode=
=20
>> characters.
>>
>> Helge.
>>
>>
>> TiddlyWiki created by Jeremy Ruston, (jeremy [at] osmosoft [dot] com)
>>>
>>> Insert a new line before that one that contains a bunch of random=20
>>> unicode characters. For example:
>>>
>>> =C3=ADnt=C3=A9=C3=A1tio=C3=B8=C3=A7`=C3=B1
>>>
>>> Then save the file and try opening it again from Dropbox. These extra=
=20
>>> characters appearing near the top of the file should cause Dropbox to=
=20
>>> correctly identify the character set. Let me know how you get on,
>>>
>>
------=_Part_1087_29423728.1351930071678
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

With the new 2.7.0 beta it did work with the following line of characters:<=
br><br>=C3=AD=C3=A9=C3=A1tio=C3=B8=C3=A7`=C3=B1=E2=80=94=E2=80=A0=C2=BA=E2=
=81=8B<br><br>Thanks again for the advice!<br><br>Helge.<br><br>Am Mittwoch=
, 31. Oktober 2012 07:31:01 UTC+1 schrieb Helge:<blockquote class=3D"gmail_=
quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;pa=
dding-left: 1ex;">Ok, while looking at the forum I found your post there, J=
eremy - of course you already did that! :-)<div><br></div><div>Well, I'll t=
ry adding more unicodey characters and see if it works.</div><div><br></div=
><div>Helge.</div><div><br><br>Am Mittwoch, 31. Oktober 2012 07:26:38 UTC+1=
 schrieb Helge:<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-l=
eft:0.8ex;border-left:1px #ccc solid;padding-left:1ex">Same here, did not w=
ork. The Dropbox app just shows different characters but not the correct on=
es as Jan already reported.<div><br></div><div>I'll post this in the Dropbo=
x forum, maybe someone there will know how to fix it or will even make chan=
ges to the DB app to accomodate for unicode characters.</div><div><br></div=
><div>Helge.<br><br><br><blockquote class=3D"gmail_quote" style=3D"margin:0=
;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>T=
iddlyWiki created by Jeremy Ruston, (jeremy [at] osmosoft [dot] com)</div>
<div><br></div><div>Insert a new line before that one that contains a bunch=
 of random unicode characters. For example:</div><div><br></div><div>=C3=AD=
nt=C3=A9=C3=A1tio=C3=B8=C3=A7`=C3=B1</div><div><br></div><div>Then save the=
 file and try opening it again from Dropbox. These extra characters appeari=
ng near the top of the file should cause Dropbox to correctly identify the =
character set. Let me know how you get on,</div></div>
</blockquote></div></blockquote></div></blockquote>
------=_Part_1087_29423728.1351930071678--

------=_Part_1086_7825860.1351930071678--