Re: Major, and seemingly random problems with wget 1.8.2
I don't use an Amiga, nor do I have an idea what you mean by a "working Wget setup". Have you tried compiling from source?
Re: Major, and seemingly random problems with wget 1.8.2
Hello Hrvoje, On 07-Oct-03, you wrote: is it possible for someone to e-mail me a working wget setup for amiga to my private mail? Thanks Regards Patrick Robinson
Re: How do you pronounce Hrvoje?
Hi Hrvoje :) * Hrvoje Niksic <[EMAIL PROTECTED]> dixit: > > Can you give us linguistically challenged Americans a phonetic > > rendition of your name? > It's not easy to describe because of the phonems and concepts not > present in the English language. You'll probably regret having asked. [...] Very interesting!. I really didn't know how to pronounce your name, I even had problems writing it at first ;))) Nice to know how to pronounce it. I'm spanish, so I don't exactly know if I got all sounds correctly, but I think I have a pretty good approximation. Thanks ;)) Raúl Núñez de Arenas Coronado -- Linux Registered User 88736 http://www.pleyades.net & http://raul.pleyades.net/
Re: How do you pronounce Hrvoje?
> It's not easy to describe because of the phonems and concepts not > present in the English language. You'll probably regret having asked. > :-) Not at all. Thanks for the detailed explanation. > * The "oh" in "voh" is fairly short, and sounds like how Brits > pronounce "o" in "dog". (So it's not "dawg":-)) I'm not sure if > this phonem exists in American English. I am not sure how the Brits say "dog"; time to watch some British TV, I guess. But I'm sure the phoneme exists; we've got lots of ways to pronounce "o". Perhaps someone who is bilingual in British and American can suggest an alternative. > As you may imagine, living in Munich for two years has taught me > to respond to even the most distorted variants. I think I can utter an approximation that you'd respond to now. :-) Tony
Wget 1.9-beta5 available for testing
This beta includes portability tweaks and minor improvements. Please test it on as many diverse platforms as possible, preferrably with both gcc and non-gcc compilers. If all goes well, I'd like to release 1.9 perhaps as early as tomorrow. Get it from: http://fly.srk.fer.hr/~hniksic/wget/wget-1.9-b5.tar.gz
Re: How do you pronounce Hrvoje?
"Tony Lewis" <[EMAIL PROTECTED]> writes: > Can you give us linguistically challenged Americans a phonetic > rendition of your name? It's not easy to describe because of the phonems and concepts not present in the English language. You'll probably regret having asked. :-) "HUR-voh-yeh" would be the closest approximation you can get without leaving the constraints of English. More specifically: * There are three syllables, with the accent being on the first one, not on the second, which comes natural to most English speakers. It's pronounced as one word, the dashes in "hur-voh-yeh" are just to make the syllables stand out. * The "oh" in "voh" is fairly short, and sounds like how Brits pronounce "o" in "dog". (So it's not "dawg":-)) I'm not sure if this phonem exists in American English. * The "eh" in "yeh" is fairly short and sounds like the "e" in "elm", not like "e" in "default". * "HUR" is the loosest approximation, and arguably the hardest one to get right. The Croatian "r" is as a rolling r, like in Italian or Spanish. The "h" is clearly heard, think of Shaw's Henry Higgins. If you're wondering how three consonants h+r+v coexist next to each other, the answer is that the (rolling) "r" between two consonants takes the role of a vowel. I'm not sure if that makes sense to you, but I guess the truth is that Slavic people are in general much more comfortable with adjacent consonants than Anglo-Saxons. I noticed that Americans have a problem pronouncing "GNU" with a non-silent "g", and often help themselves by saying "guh-noo", which sounds strange to me. For me, saying "gnu" is as natural as saying "glove". Pronuncing my name is an undertaking for most people outside my country, but it's not impossible. I've known Americans with good ear for languages who have gotten it right almost at once. But people are usually *very* confused when they hear it, and probably even more confused when they see it in writing. As you may imagine, living in Munich for two years has taught me to respond to even the most distorted variants. I really ought to get a cheap $2 microphone in the store and record it. :-)
suggestion: rethink retrial and abort behavior
hi, if I observerd correctly, wget behaves this way: errors are classified into two classes:. critical and non-critical errors. when a non critical error (eg time out) occurs wget retries continuing at the byte the last transmission stopped at. (if configured that way) if a critical error (like access denied, file not found) occured, wget stops. I now experienced for the very first time, wget OVERWRITING a partly retrieved file because of a bug. it was a pain in the ass, because I already had been waiting 1:30 hours to download the first half of 600 MB. Wget tried to continue, but the server answered with the remaining file size (I believe) , not the complete file size. So wget got confused and restarted. no, sorry I do not have the logfile any more. but i can get the link (it was a filefront download) This makes me think about another behaviour: - wget may be forced to always retry since yesterday and in the past I experiencend many false stops because of bad server or connection. probably it should delay a retry in the critical case. - if wget decides a continue is not possible due to server limitiation it should NOT delete the file but create a diff, if it seems appropriate (is the diff command able to work on binary files?) Jan
