haskal
/
Plume
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Plume/po/plume-front/plume-front.pot

54 lines
1.1 KiB
Plaintext
Raw Normal View History

New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid ""
msgstr ""
"Project-Id-Version: plume-front\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-06-15 16:33-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:115
Editor improvements (#486) - Make it possible to insert new paragraphs in the article body - Make it impossible to copy formatted HTML (to make media insertion from markdown code work correctly) TODO: - [x] make it possible to escape draft mode - [x] display errors from the server - [x] button to go back to the "normal" editor - [x] Avoid publishing placeholders
2019-04-06 13:20:12 +00:00
msgid "Open the rich text editor"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:145
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "Title"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:149
msgid "Subtitle, or summary"
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:156
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "Write your article here. Markdown is supported."
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:167
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "Around {} characters left"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:243
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "Tags"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:244
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "License"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:247
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "Cover"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:267
Editor improvements (#486) - Make it possible to insert new paragraphs in the article body - Make it impossible to copy formatted HTML (to make media insertion from markdown code work correctly) TODO: - [x] make it possible to escape draft mode - [x] display errors from the server - [x] button to go back to the "normal" editor - [x] Avoid publishing placeholders
2019-04-06 13:20:12 +00:00
msgid "This is a draft"
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 12:59:03 +00:00
# plume-front/src/editor.rs:274
New editor (#458) With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo: ![peek 05-03-2019 16-12](https://user-images.githubusercontent.com/16254623/53815536-1dc05680-3f62-11e9-94d3-b363ed84eb97.gif) There is still a lot to do, but it is a good first step. Fixes #255
2019-03-15 15:06:10 +00:00
msgid "Publish"
msgstr ""