0.5.0 Released

[mrmikel]

Add existing files is no longer under Edit, but a right click at the head of each area, text, images, etc. in the Book Browser.

This is convenient.

[Fabe]

- Implement 245: Unify zoom levels (book, text, image) and store the levels.

For this alone, I thank you. I am sure all other updates will benefit my workflow in Sigil, but maintaining zoom level from chapter to new chapter is primal. You just saved my right index finger 600 clicks on my next project. Thank you. - Fabe

[WS64]

Originally Posted by mrmikel

Add existing files is no longer under Edit, but a right click at the head of each area, text, images, etc. in the Book Browser.

This is convenient.

I did not even know it was in the Edit menu at all, I always used the right click, so this is not a new feature.

[user_none]

Originally Posted by mrmikel

Add existing files is no longer under Edit...

It's moved to menu under File -> New. The thought process is your adding a new file to the ePub.

Originally Posted by cybmole

so it is necessary / recommended to uninstall 0.42 before installing 0.5

If you are installing over a previous version then it is recommend. If you are installing over a beta (some not all but I'll say this as a blanket statement just to be safe) then uninstall is required. If you are installing to a different location than a current install then you can leave that one alone. The current issue (I hope to fix for 0.6) is the installer is not installing all of the files (I believe it's checking the dll version and only overwriting if the one installer is newer).

[ghostyjack]

I've installed the new version but the spell-checker could do with a few improvements.

1. Include a British English dictionary as standard with the install as not a written English is US English. I've manage to source one myself but I've never had to to this with any other program.

2. Have the ability to ignore certain words that don't fall into the chosen language. Very useful for Fantasy and Sci-Fi books.

3. It is flagging as incorrect words that use curly quotes. And where there is an em-dash and no spaces around it, the two words and the em-dash are being flagged as incorrect.

Other than that, no other major issues noted.

[Toxaris]

Originally Posted by ghostyjack

I've installed the new version but the spell-checker could do with a few improvements.

1. Include a British English dictionary as standard with the install as not a written English is US English. I've manage to source one myself but I've never had to to this with any other program.

2. Have the ability to ignore certain words that don't fall into the chosen language. Very useful for Fantasy and Sci-Fi books.

3. It is flagging as incorrect words that use curly quotes. And where there is an em-dash and no spaces around it, the two words and the em-dash are being flagged as incorrect.

Other than that, no other major issues noted.

Ad 1. I think John is an US resident and therefore chosen US English. There are only a few languages available by default, others have to be done manually. It is a choice, probably to keep the file small.
Ad 2. You can use the user dictionary for that. It is easy to add and delete words to it. You can do it manually or right-click on a name in Code View.
Ad 3. This is known and I think a shortcoming of Microspell, but John will know better.

[user_none]

Originally Posted by Toxaris

Ad 1. I think John is an US resident and therefore chosen US English. There are only a few languages available by default, others have to be done manually. It is a choice, probably to keep the file small.

I am in the USA. I'm indeed only including a few default dictionaries to keep the file small and keep the number of places I need to check for updates small. There are also licensing constraints I need to worry about when including dictionaries.

Originally Posted by Toxaris

Ad 2. You can use the user dictionary for that. It is easy to add and delete words to it. You can do it manually or right-click on a name in Code View.

Right now this is the best option. This is not something I want to think about in the short term but it is possible to enhance the misspelling detection by using heuristics on the overall document. I've read about some work in this regard and it allows for things like words in different languages, proper names and words that are found multiple times in the document to be but are not in the dictionary to be excluded from spell check. I don't see it as a priority.

Originally Posted by Toxaris

Ad 3. This is known and I think a shortcoming of Microspell, but John will know better.

I'm using Hunspell for spell check and this is a short coming of the dictionary ghostyjack is using. Basically he's using one without unicode support. The fix is to use a different dictionary that knows that a curly quote is the same as a straight quote.

[mrmikel]

I would love for any program to offer a British and American English dictionary, since I work on programs in both variations. Maybe I can find and install the British English dictionary as well.

[user_none]

Originally Posted by mrmikel

I would love for any program to offer a British and American English dictionary, since I work on programs in both variations. Maybe I can find and install the British English dictionary as well.

You can use any Hunspell dictionary. OpenOffice has a large selection. FYI, an .oxt is just a zip archive with the dictionary files inside of it. You just need the .aff and .dic files. Open Sigil's preferences, go to spelling and click the button on the button to open the user dictionary location. Put the .aff and .dic files there then restart Sigil for them to be available for use.

[ghostyjack]

Originally Posted by user_none

I'm using Hunspell for spell check and this is a short coming of the dictionary ghostyjack is using. Basically he's using one without unicode support. The fix is to use a different dictionary that knows that a curly quote is the same as a straight quote.

You can use any Hunspell dictionary. OpenOffice has a large selection. FYI, an .oxt is just a zip archive with the dictionary files inside of it. You just need the .aff and .dic files. Open Sigil's preferences, go to spelling and click the button on the button to open the user dictionary location. Put the .aff and .dic files there then restart Sigil for them to be available for use.

Well thats annoying as I went to OpenOffice to get my dictionary, this could mean that the GB English dictionary OOo use isn't unicode compatible.

Does anyone know when else you can find GB English dictionaries?

[crutledge]

The editor used for content.opf seems to be different from that used for Code View.

Is it possible to use the same editor?

[user_none]

Originally Posted by crutledge

The editor used for content.opf seems to be different from that used for Code View.

Is it possible to use the same editor?

It's exactly the same editor. The only difference is spell check is not enabled for OPF files.

[bobcdy]

Toxaris - Thanks for the info! Perhaps eventually I might have noticed the red lines and wondered what they mean, but then again...

The spell checker seems to work beautifully - great work user_none!!

[mncowboy]

I have something strange going on. When I am at home, I have 2 additional monitors connected to my laptop. I have the monitors set to extend the desktop, not duplicate. When I was there I opened the meta data window and moved it to a different window.
I am traveling now, and do not have an external monitor to connect to. When I try and view meta data, the window is not visible. It must think that it is still being displayed on another monitor. I can't figure out how to move the window back so it is visible. I have to hit escape to get back to the main application.
Is there a way to get the window moved back, or will I have to connect to an external monitor to move it?

[ElMiko]

The fix is to use a different dictionary that knows that a curly quote is the same as a straight quote.

Understood, but can someone please direct towards a dictionary that works with so-called fancy apostrophes and hyphens and doesn't get tripped up by en and em dashes.

Also, the problem of the cursor jumping from the search box to the body text when one's search goes to a new file (looking in all HTML files) that I described in 4.905 persists.