Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-20 Thread Jan
Hi Tony, I am happy that you are interested ( by the way, did you check the PHPs i sent to you?). I guess will need some time and help, until the handling is intuitive. At the moment the use is hard to explain because it has still workarrounds which are not really easy. Have you tried to send

Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-19 Thread TonyM
Jan I could not help you character issue but I am very keen on you import text file. Could I please ask when you are ready to document it a little more clearly so us English speaking dummies can understand and make use of it. Thanks in advance Tony -- You received this message because you

Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-19 Thread Jan
Hi Mark, hi Jed...hi anyone interested. the charset issue is quite a drag, I was only able to solve it taking a detour over a .php which does the work. "")); } $url = $_GET['url']; $posturl = $_POST['url']; if (!empty($posturl)) { $url = $posturl ; } $text =

Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-18 Thread Jan
Hi Mark, of course I did. Jed's line of conde is still in the widget on szen.io/test. But I thing what is going wrong is happening before that step. At that point the data already seems to be unreadable. Tschö (another German word with rockdots to say 'see you') Jan Am 18.07.2019 um 03:04

Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-17 Thread 'Mark S.' via TiddlyWiki
But did you try Jed's suggestion: var urltext = decodeURI(client.responseText); ? On Wednesday, July 17, 2019 at 4:58:15 PM UTC-7, Jan wrote: > > Hi Jed, Hi Mark, > thanks for your help, I tried some things before answering: > > stackoverflow says this could help: > >exports.run =

Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-17 Thread Jan
|This at least has an effect...though i doubt it is the right direction... client.overrideMimeType('text/plain; charset=x-user-defined');| Am 18.07.2019 um 01:58 schrieb Jan: Hi Jed, Hi Mark, thanks for your help, I tried some things before answering: stackoverflow says this could

Re: [tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-17 Thread Jan
Hi Jed, Hi Mark, thanks for your help, I tried some things before answering: stackoverflow says this could help: |exports.run = function(url) { var client = new XMLHttpRequest(); client.open('GET', url, false); client.setRequestHeader('Content-type',

[tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-17 Thread Jed Carty
It may be at least partially a browser thing, safari doesn't display the characters, Firefox does. But if it isn't a server thing I am not sure what else to check. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group

[tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-17 Thread 'Mark S.' via TiddlyWiki
If you paste the address into the address bar, it shows the umlauts. To me that suggests that the server knows how to serve them from the text file. On Wednesday, July 17, 2019 at 6:08:55 AM UTC-7, Jed Carty wrote: > > I am not sure what I did but I am glad I was able to help. > > > The

[tw5] Re: Widget to import .txt-File as Tiddler: How do I import umlaute ö ä ü ß an other strange German characters

2019-07-17 Thread Jed Carty
I am not sure what I did but I am glad I was able to help. The problem is almost certainly with encoding, but I am not certain where. One unlikely place is using var urltext = unescape(client.responseText); in the javascript macro, changing that to var urltext =