sonček

I'm strongly supporting mmartinec on this subject! One should xe axle to use correct national language diacritic in caches descriptions! Today this proper character usage should not xe an issue as the issue has xeen addressed on general and there are tools to allow for proper characters usage and implementation. In Slovenia we are using more and more douxle or even triple language cache descriptions. Thus we are slowly improving one language, English descriptions of first caches placed in Slovenia. All this to enable local and foreigner geocachers to enjoy cache hunting in our country. It is a shame when one has to read her/his own language by guessing what the original word was - xy decoding meaning of the word from the meaning of the sentence. Regards from Soncek? or Sonček? Guess which one is correct! It is the latter one - with a meaning "small sun". First one actually does not mean nothing in Slovenian language :xlink: Ohhhh sorry it should xe/be

Thank you for quick input! I knew about that search among some older members finds and I did that some time ago. But that was not bullet proof. From the "map solution" you indicated (great it works - thank you!) I already pulled out two caches I have not been aware off. So this solution helps. It is a bit slow though. Is there some other, faster way to search - lets say in the area or country?

Hi! Is there a way to search for archived caches in the area or country? I tried with PQ but I did not succeed. It looks like there is no option to search for Archived ones. I have been searching, if this topic is already covered in the forum but I couldn't find it. I hope I have not missed something. I know that the number of archived caches might be a huge one in some countries/areas but in others (I would like to do it for Slovenia) this number might be low. I'm interested in this number (and actual logs) for "historical" and statistical reasons.. Thanks for help!

Got my coins today. I'm very satisfied with the service and with the coins. Thank you Crake!

I'm looking forward for the LE surprise.

I never ordered a geocoin before but this one ..... Well... I have to have it! It includes names of two countries I love the most. It is nice to see both of their names on one geocoin. And especially on such an awesome one! Maybe one of those countries is appearing on any geocoin for the first time. Well I think. Anybody has on overview of those countries? Did all of them already appeared on a geocoin? I can hardly wait to order my set.

I would like to follow up on a question I posted quite some time ago. After some unsuccessful attempts to find out why my TB KML is not showing in Google Earth I gave up the hope that my TB will show its travels in Google Earth (GE) - Ever! However, god knows why, one day I decided to download and edit the KML of the TB. I also read (again) the error I got from Google Earth (GE) GE reported while the KML was loaded. Error listed the line and column where GE supposedly decided that the TBs KML is not OK for it. Than I looked what is at that position in the KML itself. I found that Google Earth didn't load a KML due to a ' character (apostrophe used in words like "I'll" & "didn't" )!!! I remember that I wrote a TB description in the Word and than I copied/pasted prepared text to the Geocache TB site. After this copy & paste actions, and save of the TB descriptions, GE rejected all ' characters. It looks like it did not like those "strange ' characters" within KML TB descriptions. I had to correct all apostrophes (') in the TB description. Strangely it was enough to replace them with "the same" (') character directly on the Geocaching TB site (so on the page, which you get when you EDIT the TB description). When I did that KML was happily accepted by GE. Hurray! TB shows its KML in GE! It looks like during the copy & paste action from Word to WWW Geocache TB edit site, something happened to the ' character and changed it to something that is recognized as ERROR within KML by GE. I hope this experience will help other to avoid the same mistake!

Well this one was also not lost. What happened (to my knowledge) is that one cacher dropped it in a cache and did not log the placement. Thus the second cacher when he found the TB in the cache did a "grab". At that point I was concerned about the registering "correct" mileage so I wrote a very nice e-mail asking for help. To reflect the traveled miles I asked him to "virtually" drop TB back to the cache where he found it and than retrieve it by using "found it". Afterwards the logs were performed in a "standard way". Is it possible that a "grab" or a "virtual drop", which is exactly what is done in real world except that the physical drop is not performed, would mess up the Google Earth tracking?

Hi all! I have an issue with presentation of the TB track in Google Earth. It is my Natural Beauty TB (TBQ23K) . When I use "View in Google Earth" link under "Travel Bug options" a download of the kml file from the TB page starts. At that point all seems OK until the file is opened in Google Earth. Than I get a Google Earth Error "Open of file xxxxxxxxxx.kml" failed: Parse error: Invalid character (Unicode: 0x1B) at line: 12 at line:10" When I click OK, TB path is ofcourse not shown on the map. Anybody knows what is wrong and how this Error could be corrected? Thank you!