-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI texts - review and document guidelines #29
Comments
It would be definitely good to have all UI texts following some standard. Feel free to come with an initial proposal either in a Google Doc or here as a comments.
This point goes out of the scope of this issue because here we're not really talking about text (even if we see characters there). This point is related to "iconography" which should be localizable as well. For example, we already do it partially by replacing icons in RTL interfaces. We must go deeper on this and make this aspect locale dependent as well. |
I am just wondering, why is CKeditor capitalising labels like this? Were every first char of a word in the label is capitalised. |
@Bojhan, I was checking MS Word and I see that they capitalize toolbar labels, dialog titles and context menu entries. In-dialog labels are not capitalized though. Much probably we do this in CKEditor following this way. Anyway, we never put our approach on paper, so we're having the chance to review it now and to document it. Your suggestions are welcome. Thanks! |
Cleaning up outdated discussions. See #186 |
There are plenty of issues with CKEditor 4 UI texts that we could improve, like:
We now have, for example, Image, Table, Insert Horizontal Rule, Create Div Container, Insert Special Character, Smiley.
We now have, for example, Image Properties, Select Special Character, Insert Smiley, Code snippet and Mathematics in TeX.
Additionally, we should create rules for this stuff and adhere to them with each new feature that we add.
The text was updated successfully, but these errors were encountered: