| 
			
			 | 
		#31 | |
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 4,520 
				Karma: 121692313 
				Join Date: Oct 2009 
				Location: Heemskerk, NL 
				
				
				Device: PRS-T1, Kobo Touch, Kobo Aura 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
  | 
|
| 
		 | 
	
	
| 
			
			 | 
		#32 | 
| 
			
			
			
			 Grand Sorcerer 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,891 
				Karma: 207182180 
				Join Date: Jan 2010 
				
				
				
				Device: Nexus 7, Kindle Fire HD 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Don't get too excited. SInce I'm not very familiar with the codebase, I may have just moved the problem somewhere else.  
		
	
		
		
		
		
		
		
		
		
		
		
		
			  I believe \uXXXX is the preferred way of handling unicode in strings in C/C++/Java, but it sure seems like Microsoft's compiler doesn't like it in this particular case. The hex representations may cause issues, but I doubt it since they're single* unicode codepoints being sought out... in a decidedly utf-8 encoded document. It might be different if you were searching for "fa\u00e7ade" vs "fa\xc3\x87ade" * Yes, I know unicode codepoints/graphemes may not be single "characters." Last edited by DiapDealer; 06-21-2012 at 07:39 AM.  | 
| 
		 | 
	
	
| 
			
			 | 
		#33 | 
| 
			
			
			
			 frumious Bandersnatch 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,570 
				Karma: 20150435 
				Join Date: Jan 2008 
				Location: Spaniard in Sweden 
				
				
				Device: Cybook Orizon, Kobo Aura 
				
				
				 | 
	
	|
| 
		 | 
	
	
| 
			
			 | 
		#34 | 
| 
			
			
			
			 Grand Sorcerer 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,891 
				Karma: 207182180 
				Join Date: Jan 2010 
				
				
				
				Device: Nexus 7, Kindle Fire HD 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			The original source could possibly be utf-16, but at the point the entity substitution happens, Sigil seems to have already homogenized everything to utf-8 (that's an assumption based on the presence of the "QString::fromUtf8" function). Still... it could pose a problem if Sigil does (or chooses to in the future) preserve the underlying utf-8/16-ness of a document. Right now, though, it seems that portion of Sigil's code is confidently expecting utf-8. *shrugs*
		 
		
	
		
		
		
		
		
		
		
		
		
		
		
			Last edited by DiapDealer; 06-21-2012 at 08:51 AM.  | 
| 
		 | 
	
	
| 
			
			 | 
		#35 | 
| 
			
			
			
			 Junior Member 
			
			![]() Posts: 9 
				Karma: 10 
				Join Date: Apr 2012 
				Location: Oxford, England 
				
				
				Device: Kindle 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I have a problem that is worse with the latest betas: 
		
	
		
		
		
		
		
		
		
		
		
		
		
			When working in book view and I want to edit the code I highlight roughly the lines or just place my cursor at the point where I want to work. However when I then switch to Code View I am taken to the very beginning of the document so I've lost my place. Similarly, when I've done editing in Code View and switch back to Book View I'm again taken to the start of the document. It's making it so difficult to work with and it wasn't like this in the non-beta version (although it was always a bit flaky when switching views) I'm in 0.5.902 (although the About still says 0.5.901 - not worried about that though) Last edited by paulhypno; 06-22-2012 at 01:04 PM. Reason: add information  | 
| 
		 | 
	
	
| 
			
			 | 
		#36 | 
| 
			
			
			
			 Sigil developer 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,274 
				Karma: 1101600 
				Join Date: Jan 2011 
				Location: UK 
				
				
				Device: Kindle PW, K4 NT, K3, Kobo Touch 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			There is no syncing of the cursor between views anymore. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	The plan is to leave the cursor where you left it in the specific view (if possible). So if you edit in CV and then switch to BV and move around, when you switch to CV again your cursor should be where you left it. Unfortunately, the cursor position in BV is not working right at this time but will hopefully be fixed before release. Alternatively you can highlight some text in BV and type Ctrl-F, then after switching to CV type Ctrl-G to find the text. Of course, you need to select text that doesn't have any formatting codes in it and have to have your Find & Replace set to current file, etc. so its not great - but its available if you want to use it.  | 
| 
		 | 
	
	
| 
			
			 | 
		#37 | ||
| 
			
			
			
			 Junior Member 
			
			![]() Posts: 9 
				Karma: 10 
				Join Date: Apr 2012 
				Location: Oxford, England 
				
				
				Device: Kindle 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Many thanks for speedy, helpful comments> 
		
	
		
		
		
		
		
		
		
		
		
		
	
	I assume there is a reason for this? I do realise that Sigil isn't a "belt and braces" word processor or html editor but it is otherwise so good, and it IS designed to edit documents so this problem is a big negative. Am I right in thinking that it used to be possible? If so then it's a retrograde move. Please see next comment for what it means in practice: Quote: 
	
 Quote: 
	
  | 
||
| 
		 | 
	
	
| 
			
			 | 
		#38 | |
| 
			
			
			
			 Interested in the matter 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 421 
				Karma: 426094 
				Join Date: Dec 2011 
				Location: Spain, south coast 
				
				
				Device: Pocketbook InkPad 3 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
  | 
|
| 
		 | 
	
	
| 
			
			 | 
		#39 | 
| 
			
			
			
			 Sigil developer 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,274 
				Karma: 1101600 
				Join Date: Jan 2011 
				Location: UK 
				
				
				Device: Kindle PW, K4 NT, K3, Kobo Touch 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			The cursor positioning in Book View is broken at the moment.  When fixed the cursor in BV will be where you left it when you return to BV from CV.
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
| 
			
			 | 
		#40 | |
| 
			
			
			
			 I am what I am 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,625 
				Karma: 62235665 
				Join Date: Sep 2011 
				
				
				
				Device: iPad3, Voyage 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
  | 
|
| 
		 | 
	
	
| 
			
			 | 
		#41 | |
| 
			
			
			
			 Member 
			
			![]() Posts: 23 
				Karma: 10 
				Join Date: Apr 2011 
				
				
				
				Device: none 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 Cheers, thank you for all the work.  | 
|
| 
		 | 
	
	
| 
			
			 | 
		#42 | |
| 
			
			
			
			 Well trained by Cats 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 31,267 
				Karma: 61916422 
				Join Date: Aug 2009 
				Location: The Central Coast of California 
				
				
				Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 BTW 'Insert Chapter Marker' still works after I fixed the shortcut, which had changed from Ctrl-Shift-Enter to Ctrl-Shift-Return (which does not exist on a Win Keyboard)  | 
|
| 
		 | 
	
	
| 
			
			 | 
		#43 | |
| 
			
			
			
			 Evangelist 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 490 
				Karma: 1665031 
				Join Date: Nov 2010 
				Location: Vancouver Island, Nanaimo 
				
				
				Device: K2 (retired), Kobo Touch (passed to the wife), KGlo, Galaxy TabPro 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 ...... Sorry theducks. It's early morning here and I just couldn't resist  
		 | 
|
| 
		 | 
	
	
| 
			
			 | 
		#44 | 
| 
			
			
			
			 Grand Sorcerer 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,891 
				Karma: 207182180 
				Join Date: Jan 2010 
				
				
				
				Device: Nexus 7, Kindle Fire HD 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I've seen at least one reference to: 
		
	
		
		
		
		
		
		
		
		
		
		
		
			Code: 
	<title>Rich text editor, editor, press ALT 0 for help.</title> To consistently recreate the issue (I'm sure there are other ways): 1) Open Sigil 0.5.902 (brand-new empty document) 2) Switch to Code View of "Section0001.xhtml" (note the "<title></title>") 3) Delete the "<p> </p>" line in Code View 4) Switch to Book View 5) Type some text 6) Switch to Code View and note "<title>Rich text editor, editor, press ALT 0 for help.</title>" The text itself comes from a default setting in the language files (en.js) for CKEdit. Thinking it might be connected to the empty title tags... I tried entering a title (in step 2 of the above recreation steps), but no dice. The text I entered is still replaced by "<title>Rich text editor, editor, press ALT 0 for help.</title>" if you complete the steps. Tested on Windows and Linux. Seems like it may be a common thing since I've found evidence of a few live websites with that same distinct title.  
		Last edited by DiapDealer; 06-23-2012 at 01:55 PM.  | 
| 
		 | 
	
	
| 
			
			 | 
		#45 | ||
| 
			
			
			
			 Sigil developer 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,274 
				Karma: 1101600 
				Join Date: Jan 2011 
				Location: UK 
				
				
				Device: Kindle PW, K4 NT, K3, Kobo Touch 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 Quote: 
	
 Made a note to look at the shortcut issue. Yeah, its been seen and noted - but thanks for another way to show it. Makes it much easier to look at something when you can reproduce it as you know...  | 
||
| 
		 | 
	
	
![]()  | 
            
        
            
            
  | 
    
			 
			Similar Threads
		 | 
	||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| 0.5.901 (0.6.0 beta) avaliable | user_none | Sigil | 118 | 06-19-2012 09:59 PM | 
| 0.4.903 (0.5 beta) Avaliable | user_none | Sigil | 77 | 01-03-2012 10:24 PM | 
| 0.4.902 (0.5 beta) Avaliable | user_none | Sigil | 65 | 12-18-2011 12:58 PM | 
| No Avaliable format ? ? ? | Janette55 | Library Management | 5 | 04-16-2011 05:09 PM | 
| Beta 2.0.3 firmware 902 problems | Roos | PocketBook | 15 | 12-15-2010 11:11 AM |