Jump to content

pikacu

+Premium Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by pikacu

  1. http://forums.Groundspeak.com/GC/index.php?showforum=8 I think that "Feature Discussions and Suggestions" is better for this type: http://forums.Groundspeak.com/GC/index.php?showforum=139
  2. I have contacted the owner of geocheck.org. Here is his reply: ... Yes, unfortunately, GeoCheck has become so popular, that I have been using too many resources according to my hosting service. Thus, I am in the process of moving the server and hope to have it up and running in the next 12-24 hours.
  3. I just tested the code posted by CDJ Abuser (THANK YOU VERY MUCH ) and it works exactly as written. Please note that you should submit cache description only once (each time something is stripped away). See the description of http://coord.info/GC2VBMY where I use html coding. Summary of using č and Č: 1) In cache description form use č and Č (before submitting again you will have to correct all the codes because they are screwed upon submittion) 2) In log form for cache and trackable item use & #269; and & #268; (one string, no space between & #) 3) In descriptions for trackable items you can use literal characters.
  4. It's related to the HTML validator screwing up the HTML entities. The HTML entity for the character you mentioned (edit: I just saw it actually was someone else who mentioned it) is Č which upon form submission gets translated into the actual character, which then shows up as a plain C. The workaround for now is to enter it as Č (yeah, really like that). Save only once though, if you do it twice it's gonna be screwed up again. It's slightly different behaviour: when we enter characters č and Č literaly (ie by pressing a corresponding keyboard key), they are translated to ASCII c and C after submission. The translation is one way only: when we edit the old record, we don't get back original letters any more. There are two strange things: 1. The other national characters (šŠžŽ) are left untouched, 2. In the first log preview (the single log record which you get just after submittion) you can see untouched characters! But in the log listing on the cache page the charactes are already translated. The translation obviously occurs while writing the record to database. (Please note tha I am referring here to cache logs; when the cache description is submitted you don't get its plain version) The workaround now is like you said: to use html entities & #269; and & #268; which are left untouched after submitting and you can also get them back in editing mode. But this workaround is very cumbersome, I am using it only in descriptions of my caches. BUT... I'm totaly frustrated now! While I was writing the post above and doing some tests I realized that workaround with html entities DOESN'T WORK ANY MORE in the cache descriptions!!!!!! Therefore no more national characters in our cache descriptions . Hey guys what are wrong with you????? Don't you realize that you have international audience here and not only ASCII reading/writing people? Please make full Unicode support for cache descriptions ASAP. I believe that this is a more urgent issue than inventing some fancy lists like last visited caches... The unicode support issue is here for a long time now (it had its own vote entry in former voting mechanism which was quietly removed recently), and as I heared not only Slovenian (Croatian, Bosnian, etc..) characters are affected but some other nations' too. In the meantime, please bring back the workaround with html entities for national characters.
  5. Yes, please full Unicode support! I can't understand how it's possible that you still don't fully support Unicode (there is no charge for using it as is the case for google maps) Domo!!! +1 for that. Unicode support!!! I vill ask one more time. Vhj there is no ansver from Groundspeak about this "little" issue about unicode support. Vhj are some characters filtered out? Can some admin please ansver to this oustion. p.s. This tekst is intentionallj vritten vithout "special" english letters. This is hov description of our Slovenian caches looks like. Thank jou! +1 I also think It vould be great, if Unicode for the Slovenian letters vould be enabled. Othervise it is realli annoing to read the tekst. Please enable it, Thank jou I also don't understand this really bizzare thing: Slovenian letters (I don't know for other languages) DO WORK in descriptions and logs for TBs and GCs!!! It seems that there are two uncoordinated teams of programmers...
  6. Yes, please full Unicode support! I can't understand how it's possible that you still don't fully support Unicode (there is no charge for using it as is the case for google maps)
  7. I have a pocket query running every day. Today I have got an email that PQ has been generated. When I clicked on link to zip file on PQ download page I didn't get anything but message "Sorry, the requested Pocket Query download is no longer available." And it is no longer listed in the list of available PQs. This are the times: Current server time: Saturday, 14 January 2012 03:08:15 PQ generated time: 14/01/2012 02:45:23 My time zone is CET, current time: 14/01/2012 12:23 This has already happened once before but I thought then thet I made some mistake... Anybody else with this problem?
  8. I can't download pocket query. Today I have got mail notice that PQ is ready for download. But there is no PQ available in the list!
  9. Oddmund, thanx for the solution, it works! I have just got answer from the owner: "My service provider has just moved me to a new server. Unfortunately, this generates some problems, but we are working on it."
  10. I have just got answer from the owner: "My service provider has just moved me to a new server. Unfortunately, this generates some problems, but we are working on it."
  11. Agree 100% with that. There are numerous requests for changes which we wote for them. Why those are not solved? How avatars and vague dates got prioritized over requests from geocachers?
  12. The problem was solved! I tested and I didn't recieve any notification. Thanks!
  13. I tried but doesn't work. When the caches were on the new list, I was getting double notifications.
  14. I have created a new bookmark list with "notify" option turned off, and included all caches that were on the old list. The notifications are still comming.
  15. I have no other bookmark list. When I click on the last in the email, I get the message "The bookmark list you are trying to view has been deleted." Yes, I have deleted the bookmark list, but still getting emails which I don't need any more
  16. I had a bookmark list with enabled the "Notify me when items on this list are logged" option. I have deleted this list few days ago but I am still recieving logs from caches from this list (on my email). How could I disable getting these logs? (These caches are not on my watch list).
×
×
  • Create New...