[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Haderka updated MAGNOLIA-2683:
----------------------------------

    Fix Version/s: 4.3.x
                       (was: 4.3.2)

> FCK with spell check functionality
> ----------------------------------
>
>                 Key: MAGNOLIA-2683
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2683
>             Project: Magnolia
>          Issue Type: New Feature
>          Components: fckeditor
>    Affects Versions: 4.0.1, 3.6.5
>            Reporter: Matteo Pelucco
>            Assignee: Boris Kraft
>            Priority: Minor
>             Fix For: 4.3.x
>
>
> A nice-to-have feature is the FCK spell checking capability, native on fck 
> 2.6.4 with support of online service SpellChecker
> http://dev.fckeditor.net/ticket/2685 (It is free, but the free version 
> displays a banner space while the spell check dialog is open).
> Maybe with EE edition can be found commercial agreements to remove the 
> banner, I don't know...
> There are other possibilities to integrate spell checking with FCK: see 
> http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/Configuration/Spell_Checker.
> I suggest also to consider the new FCK 3.0, near to stable release (Beta 2 
> out at time of writing). It is not on 2.6.x series, but as far as I know 
> there won't be huge limitation on porting Magnolia FCK integration over 3.0 
> release of FCK.
> Sure native spell check can be a good feature for marketing! ;-)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to