geowas

I also logged one EC by plane. Not my own plane, though http://www.geocaching.com/seek/log.aspx?LUID=e8404571-1150-4eac-a903-35a4a90dbdbb&IID=4adfe1f8-0848-483d-9327-3cfd42b4067d

<removed - double entry>

I found GC43 - Europe's First this summer. My favourite oldie is for sure GC443 - The Rhine View Stash, still having the original container, logbook, etc!

Right. I have not yet seen any / not so many caches in Greece that are (only) in Greek. So why should ECs be? Also in many countries foreigners are the biggest group of people who geocache. So why exclude them from the fun? There are 20 caches total in Albania. 5 of them are ECs. How many cachers might there be in AL? And how many visitors do speak Albanian?

Two ECs in English in Arabia? Bad, bad... they would have to be in Arabic now. Lucky German cachers that the caches were placed in time.

Hi geoaware, just to say that also to me this is a sad and silly decision. Things have been said by cezanne, trevorh7000 and others already, so I won't add more, but I very much hope that this rule change will be reverted. Thanks. geowas

<unauthorized links removed by moderator> ... and no need to "buy" them.

<unauthorized links removed by moderator> Here you can create your own trackable (that means trackable on the respective website) free of charge. Maybe this can help for now?

Not to complain, it is definitively an o.k. step to have the website in different languages now, and I must say (for the German part) the translation is good, so fine with that. As a veteran German geocacher I'm indifferent about the change, though, not happy, because I used the site for years in English, which is ok for me. And for now I'll keep it in English to avoid the mix of German and English texts (yes, I understand, work in progress). BUT.... if I recall correctly the discussions from earlier this year (and from before that), there were more voices asking for internationalisation than for localisation. What does it help a Czech cacher if he can now get the menus and some pages in Czech language, but if he/she is still not able to log in his language, due to missing Unicode support in that place?!?

Isn't the same true for Google?! So many countries are not seriously covered by Google, having just the major highways. And for the accuracy: since Google started to add smaller roads/tracks they become more and more wrong (new roads added where there are buildings for > 10 years). I vote for having boths. Each of the two, Google Maps and OSM, have their strengths and weaknesses. Why not combine them.

<removed>

Compare OSM vs Google... Move the transparency slider and see. http://sautter.com/map/ I think OSM would be a big + for many countries where Google has almost nothing. And for many regions where Google has maps, the OSM maps can offer more. So to have the possibility to switch would be excellent.

I am wondering whether someone here by chance knows a good free online multi-lingual source for geological terms (not nessarily as complete as a dictionary). It seems good old LEO has quite some geology terms included, too. At least for de<->en. dict.leo.org

Thanks for the clarification! But can't you just add it to the guidelines? Then it should be clear for everybody. Because asking for a picture of "this educational thing next to the coordinates" could also be "specific content"....

To me it's all not clear. Is a "hard" photo requirement ok if it's not requiring faces and/or other parts of the finders' bodies on it? Yes or no? When reading previous posts - and answers from geoaware - I read this here and that there... Creating ECs is hard work* (for me). I have only made one so far and I find it a pity if people didn't have to prove that they have been there. And I'm not asking for a picture only - it's just one out of several tasks/questions to answer. I have been there to create it - so I think people should be able to prove they've been there as well. The rest has been said before. To me the picture in an EC is what signing the logbook is in a Traditional/Multi/... cache. Thanks geowas * but fun!

You are correct! However, we will not tolerate logs being deleted because a person did not meet a specific content requirement in a photograph (for example the requirement to show a face). Those requests are now optional only! Is it ok to have a "hard" requirement that asks for a photo of the geological thing the cache is about (leaving out faces, GPSrs, etc.)?

Maybe I'm wrong, but isn't it internalisation, not localisation, most people are asking for? Nate used the proper term in the quote above. Localization is creating a culture-specific version of the site. Internationalization is modifying the site to allow localization. Users want localization, software architects want internationalization. Ok, let this be right. What I wanted to say is: I think most people want support for internationalisation (yes!) like full Unicode support, support for multiple cache descriptions in different languages, most recently search options for available languages in the cache description and so on, not localisation of the UI and "common pages".

Maybe I'm wrong, but isn't it internalisation, not localisation, most people are asking for?

No. If you want to put in longer text you need more space, not less as we have it now with all the white space.

Yes, but for the UI as I read it - not the topic here. Right, so let's conspirate on THIS is in fact something I'm afraid of, too.

Now a 1920x1200 screen accomodates only 50% of the Hide & Seek a Cache page. Intended?

Good idea! But additionally - an old request - it would be very helpful to be able to print only one out of several descriptions for caches available in more than one language. Hint for the developers: look at geocaching.de, they have a nice implementation of this. The language topic (with all it's different aspects) comes up here again and again. I really don't understand why there is no reaction on it by the Groundspeak people.

Today I finished a cache in Vienna which I started yesterday and which I had to continue today because I had to look up an Austrian word first (unfortunately the English translation didn't help in this case). So yes, additional cache descriptions in English (or any other bigger language) I do support! And, Groundspeak, please give us some technical solution to make different translations printable separately. geowas

Hi eagsc7. I take that you mean what you write. ... and CONTINUED in other countries. 1) Being taught a language hardly means you are able to write or speak it, especially if it was taught in school 2) "IF a cache is placed in another country in which English is NOT taught in schools, then cache description can be in native language." I) IF...? Should it not? II) Let me rephrase: "Whenever a cache is placed by an owner who speaks other languages than his native language, then cache description should/can be in his native language, local language and in English/French/Spanish/Swedish/Turkish/Chinese/Russian/Suaheli/..., whatever language(s) the owner speaks." How about that? I doubt that all 46 Mio. are able to speak (or write) it. Maybe so many technically were taught it in school (see above). And: the translation works as well the other way around. Good?! BTW, how many of the caches in the US are bilingual in English and Spanish? Wikipedia says: "Spanish, spoken by 12% of the population at home, is the second most common language and the most widely taught second language." geowas p.s. hi hzoi!

I would also like to see some more internationalisation at gc.com 1) personalised date/time format 2) full Unicode support 3) possibility to have multiple cache descriptions in different languages NOT on one page (geocaching.de has a nice implementation for that...) Hope this can be implemented some day...