We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.
The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.
Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.
To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.
Opened 14 years ago
Closed 12 years ago
| Reported by: | eng.melegy | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Core : Output Data | Version: | 3.0 |
| Keywords: | Cc: | eng.melegy@… |
| Description: | modified (diff) |
|---|---|
| Keywords: | Get Plain Text removed |
| Status: | new → confirmed |
| Version: | FCKeditor 2.6.6 → 3.0 |
To get Text from a single element you can use getText() method. Please see here: http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.dom.element.html#getText
If you are talking about getting text from whole page than I think we could create a plug-in that moves down the DOM tree gets text from elements and returns nice plain line of text.
On the other hand I’m not sure if this road is not to slippery. Someone might say that plain line is ok, someone else that ok this is plain text but headers should be in one line a the rest of the text that follows in the other. Someone else might say that when one text ends with a space and the other text begins with it, one of spaces should be removed, someone else might say that they should be felt untouched. Someone might say that some tags should be omitted… and so on.
Perhaps the best solution is to leave this to the user to create a simple plug-in/function which moves down the DOM tree, gets the text from elements and returns it in the form that he/she wants?