Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/help/enable-emoticon-translation...

31 lines
607 B
Markdown
Raw Normal View History

emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
# Enable emoticon translation
If you use emoticons like `:)` or `:/`, you can have them translated into
emoji equivalents like
<img
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
src="/static/generated/emoji/images-google-64/1f642.png"
emoji: Rename :slight_smile: to :smile:. Zulip converts :) to the 1F642 Unicode emoji and promotes the same emoji in the popular section of the emoji picker. Previously Zulip has labeled 1F642 as "slight smile". While that name conforms to the Unicode standard (which describes the code point as SLIGHTLY SMILING FACE), it didn't match our use case of the emoji. If a user types :) or selects the first smile in the emoji picker they probably mean to express a regular "smile" and not a "slight smile", which raises the question why they are only smiling slightly. This commit relabels 1F642 as :smile: and our previous :smile: 263A as :smiling_face:. Note that 263A looks different in our three supported emoji sets, so it is not suited to be our "default smile". This change does not require a migration since our emoji system stores both unicode points and names and handles name changes transparently.
2020-06-30 21:16:29 +02:00
alt="smile"
help: Fix styling of emoticons on help pages.
2018-08-16 23:38:15 +02:00
class="emoji-small"
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
/>
or
<img
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
src="/static/generated/emoji/images-google-64/1f641.png"
alt="slight_frown"
help: Fix styling of emoticons on help pages.
2018-08-16 23:38:15 +02:00
class="emoji-small"
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
/>
automatically by Zulip.
help: Update Tools & customization section to conform to style guide.
2019-04-02 23:32:55 +02:00
### Enable emoticon translations
{start_tabs}
help docs: Use {settings_tab|display-settings}.
2018-04-24 19:05:57 +02:00
{settings_tab|display-settings}
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
user docs: Update enable-emoticon-translations.
2018-08-21 04:06:11 +02:00
2. Under **Emoji settings**, select **Convert emoticons before sending**.
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
help: Update Tools & customization section to conform to style guide.
2019-04-02 23:32:55 +02:00
{end_tabs}
## Current emoticon translations
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
help: Generate emoticon translations table dynamically. Closes #8586.
2018-08-15 04:55:36 +02:00
{emoticon_translations}