FFS!
Rick Murray (539) 13385 posts |
Just spent twenty-odd minutes writing a File format description for Text files – noting some guidelines such as Latin1, not including control codes (think VDU21!), correct line termination (and that Zap/StrongEd cope better than Edit/OS), plus mentioning that smart quotes are not part of the ISO 8859/1 definition so they’re different characters in RISC OS Latin1 and Windows CP-1252. Blah blah. Only for it to throw an application error when I tried to submit. The first time in, the green banner at the top of the screen said: "Page “File formats: Text” does not exist. Please create it now, or hit the “back” button in your browser." Using the back icon (and noting that the entire document has been thrown away), it shows a red banner saying that Javascript and cookies are required. So the documentation cannot be edited on RISC OS using the most common RISC OS native browser? Is this an absolute necessity or can it be fixed? What it is that the scripting does? And why does submitting a document without simply throw this:
? I can use the forum with NetSurf, so why’s the documentation editor so different? As long as this is the case, don’t expect (m)any documentation updates from me. I can’t imagine it would be nice to write documentation on a phone (it’s enough using Google Docs with a bluetooth keyboard), and I don’t tend to turn on the PC much these days. Even for updating my blog, the content (text) is these days written in Zap and simply transfered across to the PC at practically the last minute… |
Chris Hall (132) 3498 posts |
I must say that any long post I write tends to get saved as temp.txt before pressing submit just for this reason! Or at least copied to the clipboard with CTRL-C. |