I could do that, yes, but I think that having it natively, where the user could pick their own preference, for example here on this Discourse forum, would be preferable, I believe.
2 Likes
@Jonathan5 We recently added a new setting that lets you control which editor is shown by default in your community: Choosing the default composer mode for your community
2 Likes
I noticed you mentioned my comment on the original topic, but this new topic doesnât fully address what I was mentioned there. Itâs indeed good that users can pick their default composer mode. My 2 main issues are still:
- The font being used in the markdown
- The constant jumping around of the composer (left to center) when going from markdown to rich text. Maybe some users will never use markdown, but a lot of us will and having the composer changing place all the time, is a bit unnecessary, in my opinion. I rather have markdown where I can see exactly whatâs going on, and having a preview on the right.
That being said, the monospace font is really uncomfortable to the eyes (and Iâm sure other users agree on that, not just by personal choice, but because it seems like a âuniversal ruleâ not to use monospace for reading text).
Maybe some users like it. Iâve seen some crazy color themes for people who code and that hurts my eyes just by looking at them for 5 seconds, let alone spending hours upon hours looking at that screen⊠But, different people have different tastes, so I believe that giving them the option to pick monospace or sans-serif is important. Yes, I could force sans-serif with CSS, but that would prevent people who want to use monospace to really have that option.
So on my behalf and maybe other users as well, consider those 2 options on a future release to make the experience more flexible and pleasant to all users.
Thanks.
3 Likes
At this point, itâd probably be best to have dedicated topics for different issues or ideas.
Hereâs an existing topic about the monospace font you can bring that part of the discussion to: Monospace font in the Markdown-only editor
2 Likes
Hi, in the new composer, I do not see the preview window on the right? How do I get it back for all my members ? Thanks.
2 Likes
Sorry I do not see where to press yes, I donât have this message.
The setting is in âAll site settingsâ 
Sure, itâs somewhere, my question was more and still is, where? 
Thereâs no preview in WYSIWYG mode (for good reason), as you should be seeing what you will get ⊠already 
1 Like
In the new composer isnât any preview, because it is preview already.
Change default back to old one.
4 Likes
Ok thanks for the explanation 
. So the answer I got from @Ethsim2 to press yes somewhere is not related to my concern ?
Useful to now there is no more preview so that I can inform my users to that change in the UI.
There is still a preview if you flick the toggle to change mode to Markdown in the Composer UI. Simples.
2 Likes
Everything is clear now . For administrators who havenât had the opportunity or time to follow the numerous developments regarding this change in the user interface, itâs actually quite simple. There is an administrator setting located here (see screen capture below) that allows you to switch from Rich Text mode to Markdown. Rich Text does not have a preview, because itâs WYSIWYG and itâs is a new feature and Markdown mode has a preview, which corresponds to the old mode our users (and myself) were accustomed to.
The setting: /admin/site_settings/category/all_results?filter=default_composition_mode
2 Likes
Interesting question, acronyms are generally not translated though some use âĂditeur en mode visuelâ instead (which means editor in visual mode).
However, our French-speaking Canadian friends 
are much more sensitive to respect for the French language and have equivalents that, I must say, are rarely used in France, for example:
Common translations in Quebec for WYSIWYG:
"Tel affichage, tel résultat"
â This is the official translation recommended by the OQLF (Office quĂ©bĂ©cois de la langue française).
2 Likes
I see that now this is no longer a âExperimentalâ feature, itâs made it to the official settings since the most recent update. Nice.
Now I just wish the new composer was compatible with the [grid] tag in WYSIWYG mode. Itâll be Iâm told. Canât wait!
4 Likes
2 posts were split to a new topic: Errors when trying to post with rich text editor
Does the Rich Composer have support for System Specs?
I noticed the Composer Component in system specs seems to only provide methods for populating the markdown composer?
1 Like
You can use the same PageObject, you can check some existing examples â prosemirror_editor_spec.rb is the main one.
1 Like
Ah, perfect, thanks @renato !