MobileRead Forums - View Single Post

Frank Lowney · 04-11-2010, 04:53 PM

In working briefly with Sigil which is new to me, it seems obvious that the WYSIWYG UI is much less capable than the raw code UI. Many of the postings here relate to working with the raw code.

That's all fine and good but I would like to get a handle on what the Sigil WYSIWYG UI can do in relation to all that is possible with the ePub standard. I think that a simple matrix would do. Then, other options such as the expensive Adobe InDesign application could be added.

Knowing what is and isn't currently possible in the WYSIWYG UI might lead to user input for prioritizing what gets incorporated into the UI next. I assume that the goal is for the WYSIWYG UI to grow in capability over time.

04-11-2010, 04:53 PM	#1
Frank Lowney frank.lowney Posts: 13 Karma: 10 Join Date: Apr 2010 Device: iPad	WYSIWYG UI Features Matrix In working briefly with Sigil which is new to me, it seems obvious that the WYSIWYG UI is much less capable than the raw code UI. Many of the postings here relate to working with the raw code. That's all fine and good but I would like to get a handle on what the Sigil WYSIWYG UI can do in relation to all that is possible with the ePub standard. I think that a simple matrix would do. Then, other options such as the expensive Adobe InDesign application could be added. Knowing what is and isn't currently possible in the WYSIWYG UI might lead to user input for prioritizing what gets incorporated into the UI next. I assume that the goal is for the WYSIWYG UI to grow in capability over time.