TheNextBigWriter Premium → Site Bugs 2
Sol, I have a belated auto-renumbering problem. I didn't catch it earlier, and I can't fix it myself now.
The Sorcerers Progress: Children and Beasts has two Chapter 21's. The second, Lunch at Logchem's, should be number 27. While it might be possible to fiddle with other numbers to make this one accessible, I'm afraid of making things worse. Can you set it right?
The Sorcerers Progress: Children and Beasts has two Chapter 21's. The second, Lunch at Logchem's, should be number 27. While it might be possible to fiddle with other numbers to make this one accessible, I'm afraid of making things worse. Can you set it right?
Why can't you just set it to number 27 yourself?
When I try to get to it, I get the other chapter. Or are you suggesting on the multi-stage dialogue? Okay, yes, it does come up.
Sigh. Your design is based on scenarios first and data second. That means that little-used scenarios are hard to recall. Base it on data that is always used and the scenarios are easy to find and follow. Not the way you design an ATM, but an ATM has a small set of transactions that are shallow to the user.
Anyway, it's done. Thanks for the reminder.
Another oddity: when I enter an in-line comment on an italicized word, the comment shows up italicized. I suspect that you want the comment in the same base font and style as the main text body, but it would be nice to use the base style info from the paragraph as a whole, or from the work as a whole.
Fine-tuning, I know.
In doing inline reviews, I often leave two or more comments for the same selected word or sentence (for separate feedback about the same item). I then write my closing comments, which can be long. Today, I wanted to read those secondary and tertiary comments, so I clicked on x-line to see all of them. My very long closing comments were wiped out. Fortunately, I suspected that might happen, so I copied the closing comments to the clipboard. I was then able to paste them back in. Since x-lines are available when leaving reviews, this could easily burn someone. Not sure if there is an easy fix.
Another issue that may not be easily solvable is foreign fonts. In particular, I'm using some Latin my book, which includes uncommon accents like an e with a horizontal bar over it. It posts as ? on the site when taken from MS Word using Times New Roman. I'll have other Latin words with other uncommon characters, so this will be a pain to deal with. To be honest, I'm not sure CreateSpace or Kindle support them either, so I may have to convert it to something "similiar" using other letters, assuming that's possible (e.g., maybe ae for e+bar).
Please let me know if there is a better solution.
Thanks.
Dirk
Dirk, when using the accents or such, see if that particular letter is available to be inserted as a symbol.
The actual problem with "foreign" fonts is that the tNBW site doesn't support them. I've run across Dirk's problem when I use a Japanese word that has an accent over/with a character. Plus, of course, there is a whole font set devoted to just Japanese pictographs which are not supported here either. To solve that, I write it out, make a screen grab, work on the grab in my photo processing software, crop and then upload it to my web site. Then, I can refer to it as a "picture" in the tNBW edit window. It works, but it sure is cumbersome.
~Tom
Word processors and such work from a standard palette of symbols. There are three basic levels: the 7/8 bit set, the 16 bit set and the 32-bit set. The difference between the 16-bit set and the 32-bit set as that in the smaller set (Unicode/'Basic Multilingual Plane') a number of languages have to share characters in a pool with the Chinese languages ('Unified Han'). There are also ways of coding the longer sets in varying numbers of bytes.
Just about any modern word-processing system should support all the Roman-derived characters as well as Arabic and several other writing systems. (Also Greek symbols.)
I don't recall all the names offhand. Look up Unicode on WikiP and chase links. This is big-time International Standards stuff.
njc, does that mean the different languages map different characters to the same (shared) byte(s), or does each language get its own subset of the total byte pool?
Thanks.
Dirk
Each gets its subset, except in the case of Unified Han. Chase the WikiP links.
In doing inline reviews, I often leave two or more comments for the same selected word or sentence (for separate feedback about the same item). I then write my closing comments, which can be long. Today, I wanted to read those secondary and tertiary comments, so I clicked on x-line to see all of them. My very long closing comments were wiped out. Fortunately, I suspected that might happen, so I copied the closing comments to the clipboard. I was then able to paste them back in. Since x-lines are available when leaving reviews, this could easily burn someone. Not sure if there is an easy fix.
Actually, there is an easy fix. Just go ahead and close your review before checking the x-line. Then your closing comment will be saved. You can always go back and add to your comments even after closing. Take care. Vern
I don't know for sure, Ken. Depending on which machine I'm on, I use either MS Word (2008) or Open Office Writer (latest version). The character renders just fine in my copy on the computer, but changes to either a question mark, or just plain gets ignored when I paste the story into the tMNW editor. I do note that you don't appear to be using Times New Roman, though. What is that font?
I have not tried Janet's solution. That might work. I'll have to see.
~Tom
I use MS Word 2007 with Times New Roman. What WP do you use, K?
EDIT: I just tried four characters (cut directly from MS Word and pasted into the WP here on the site): e with two dots, e with a bar (again), e with a bowl over it (same as your s), and a French e with an accent. e with two dots worked. French e worked. Interestingly, the e with the bowl didn't work, nor did the e with bar.
EDIT: I just tried K's s with a bowl. It works, even though e with a bowl doesn't.
It may be a character missing from the local copy of the character set. It might be an ambiguous coding, which is supposed to be illegal and should be removed to prevent security holes.
Also, MicroSlough uses some characters illegally, including 'smart quotes'. (They also violate the rules for HTML in their HTML encodings.)
Norm d'Plume wrote:In doing inline reviews, I often leave two or more comments for the same selected word or sentence (for separate feedback about the same item). I then write my closing comments, which can be long. Today, I wanted to read those secondary and tertiary comments, so I clicked on x-line to see all of them. My very long closing comments were wiped out. Fortunately, I suspected that might happen, so I copied the closing comments to the clipboard. I was then able to paste them back in. Since x-lines are available when leaving reviews, this could easily burn someone. Not sure if there is an easy fix.
Actually, there is an easy fix. Just go ahead and close your review before checking the x-line. Then your closing comment will be saved. You can always go back and add to your comments even after closing. Take care. Vern
That lends itself to an easy programming fix. The system should auto-save the review before switching over. That way you don't leave it for someone else to trip over.
WordPerfect here. Characters come out fine but paragraph breaks come out as question marks. I guess the ASCII gods had to taketh from somewhere
Not ASCII. Word processors use extended character sets which should fit somewhere under, I think it is, ISO 646.
Sol, ths one's for you and the team. Amy, don't change this until Sol's seen it!
Go to Amy_s`s new Chapter 17, Dictates of Faith. Start an inline review. As the FIRST comment, go to the second paragraph, first two sentences beginning with 'this', the second one italicized. Try to capture the first sentence and the first word of the second sentence for the comment. You will find that the machinery captures the whole of both sentences. Cancel the comment and try again. You will find that you cannot start a new comment until you reload the page.
I suspect that there are at least two bugs at work here, both probably design errors. My distant guess is that there's an XHTML or HTML representation and something is jumping over a -span-. If that's not it, it doesn't matter; it is a bug, and might reveal a lot about the other glitchen people are hitting when selecting text.
The second one, I am guessing, has to do either with cleaning up on the cancel or with something that confuses an empty set (however represented) with no set. Again, distant guess.
Please have a look at this frustrating mmisbehavior. Thanks ....
For the foreign character problem, I found that the word processor here on the site handles the characters just fine. It's only when you save and display the chapter in the posting view that the characters are converted to ?
EDIT: It appears to be a problem with the way the information is stored in the database. Once I open the chapter back up in the word processor here, the character is also a ? So, it displays it correctly the first time I paste it into the word processor. It then saves it as a ?
Sol, time permitting, can you please delete the orphan review reply in my account. My home page shows that I have one review reply waiting for me. It's from Don Chambers. He took the chapter down before I could read his reply to my review, and now I'm unable to read the reply and clear the reply count on my home page. The date on his reply is March 17, 2015.
Thanks.
Dirk
Sol, ths one's for you and the team. Amy, don't change this until Sol's seen it!
Go to Amy_s`s new Chapter 17, Dictates of Faith. Start an inline review. As the FIRST comment, go to the second paragraph, first two sentences beginning with 'this', the second one italicized. Try to capture the first sentence and the first word of the second sentence for the comment. You will find that the machinery captures the whole of both sentences. Cancel the comment and try again. You will find that you cannot start a new comment until you reload the page.
I suspect that there are at least two bugs at work here, both probably design errors. My distant guess is that there's an XHTML or HTML representation and something is jumping over a -span-. If that's not it, it doesn't matter; it is a bug, and might reveal a lot about the other glitchen people are hitting when selecting text.
The second one, I am guessing, has to do either with cleaning up on the cancel or with something that confuses an empty set (however represented) with no set. Again, distant guess.
Please have a look at this frustrating mmisbehavior. Thanks ...
I checked it out and see what you mean with highlighting. This is most likely due to a span or some other html tag interefering with the selection process. I'll pass it along.
I did not have to reload the page though. I'll keep trying to replicate that bug.
In doing inline reviews, I often leave two or more comments for the same selected word or sentence (for separate feedback about the same item). I then write my closing comments, which can be long. Today, I wanted to read those secondary and tertiary comments, so I clicked on x-line to see all of them. My very long closing comments were wiped out. Fortunately, I suspected that might happen, so I copied the closing comments to the clipboard. I was then able to paste them back in. Since x-lines are available when leaving reviews, this could easily burn someone. Not sure if there is an easy fix.
This is odd. Will check it out.
Just a note, even if I don't respond to your comment doesn't mean we won't check it out.
Sol
Once again I have received emails about new writing posted (by Rebecca Vaughn, 3 instances) before the postings are visible on my home page.
TheNextBigWriter Premium → Site Bugs 2
