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...

89 lines
2.5 KiB
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"
alt="slight_smile"
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
style="width: 3%;"
/>
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"
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
style="width: 3%;"
/>
automatically by Zulip.
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
2. Select the option labeled
**Translate emoticons (convert `:)` to 😃 in messages)**.
## Current emoticon conversions
<table>
<thead>
<tr>
<th align="center">Emoticon</th>
<th align="center">Emoji</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center"><code>:)</code></td>
<td align="center">
<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"
alt="slight_smile"
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
style="width: 30%;">
</td>
</tr>
<tr>
<td align="center"><code>(:</code></td>
<td align="center">
<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"
alt="slight_smile"
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
style="width: 30%;">
</td>
</tr>
<tr>
<td align="center"><code>:(</code></td>
<td align="center">
<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="frown"
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
style="width: 30%;">
</td>
</tr>
<tr>
<td align="center"><code>&lt;3</code></td>
<td align="center">
<img
emoji: Fix some emoji images not loading in missed message emails. `emoji-datasource` package v4.0.4 introduced the concept of qualified and non-qualified emoji codes. As chat programs don't need to use emoji representation selector, so we used migrated our infrastructure to use non-qualified emoji codes. But we missed the fact that the emoji file names in emoji farm are based on emoji data's 'unified' field and the value of this field has changed. Consequently the image file names must also have been changed. We used `emoji_code` while converting the span tags to img tags while processing notifications. But since now `emoji_code` refers to non-qualified code while image file names are based on qualified code, we need to rename images to correctly do the conversion. This commit just fixes this.
2018-08-09 21:06:21 +02:00
src="/static/generated/emoji/images-google-64/2764.png"
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
alt="heart"
style="width: 30%;">
</td>
</tr>
<tr>
<td align="center"><code>:|</code></td>
<td align="center">
<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/1f611.png"
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
alt="expressionless"
style="width: 30%;">
</td>
</tr>
<tr>
<td align="center"><code>:/</code></td>
<td align="center">
<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/1f615.png"
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
alt="confused"
style="width: 30%;">
</td>
</tr>
</tbody>
</table>