aitzol/Plume
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
main
Plume/po/plume-front/en.po

64 lines
1.3 KiB
Plaintext
Raw Permalink 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 16:06:10 +01:00
msgid ""
msgstr ""
New Crowdin translations (#479) Enjoy!
2019-04-19 14:59:03 +02:00
"Project-Id-Version: plume\n"
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 16:06:10 +01:00
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-06-15 16:33-0700\n"
Update translation files
2022-01-12 02:24:14 +01:00
"PO-Revision-Date: 2022-01-12 01:20\n"
Update translations
2020-12-18 21:59:58 +01:00
"Last-Translator: \n"
New Crowdin translations (#479) Enjoy!
2019-04-19 14:59:03 +02:00
"Language-Team: English\n"
"Language: en_US\n"
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 16:06:10 +01:00
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
New Crowdin translations (#479) Enjoy!
2019-04-19 14:59:03 +02:00
"X-Crowdin-Project: plume\n"
Update translations
2020-12-18 21:59:58 +01:00
"X-Crowdin-Project-ID: 352097\n"
New Crowdin translations (#479) Enjoy!
2019-04-19 14:59:03 +02:00
"X-Crowdin-Language: en\n"
"X-Crowdin-File: /master/po/plume-front/plume-front.pot\n"
Update translations
2020-12-18 21:59:58 +01:00
"X-Crowdin-File-ID: 12\n"
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 16:06:10 +01:00
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:172
Update translations
2020-12-18 21:59:58 +01:00
msgid "Do you want to load the local autosave last edited at {}?"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:326
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 15:20:12 +02:00
msgid "Open the rich text editor"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:385
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 16:06:10 +01:00
msgid "Title"
New Crowdin translations (#479) Enjoy!
2019-04-19 14:59:03 +02:00
msgstr ""
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 16:06:10 +01:00
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:389
New Crowdin translations (#479) Enjoy!
2019-04-19 14:59:03 +02:00
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 16:06:10 +01:00
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:396
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 16:06:10 +01:00
msgid "Write your article here. Markdown is supported."
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:407
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 16:06:10 +01:00
msgid "Around {} characters left"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:517
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 16:06:10 +01:00
msgid "Tags"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:518
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 16:06:10 +01:00
msgid "License"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:524
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 16:06:10 +01:00
msgid "Cover"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:564
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 15:20:12 +02:00
msgid "This is a draft"
msgstr ""
Update translation files
2022-01-12 02:24:14 +01:00
# plume-front/src/editor.rs:575
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 16:06:10 +01:00
msgid "Publish"
msgstr ""
release Alpha 4 (#709) * Update version numbers * Update translations again * Translations? * This time translations should be here
2019-12-22 15:04:09 +01:00
Reference in New Issue Copy Permalink