Release 2.7 (#2364)

Change french translator author.

.github/ISSUE_TEMPLATE/bug-report.md

@@ -10,7 +10,15 @@ Please also check if an issue already exists on this problem.
 Please provide a description covering the following points, if applicable:
 
 * A clear and concise description of what the bug is.
-* Steps to reproduce the behaviour
+* Steps to reproduce the behaviour.
 * A clear and concise description of what you expected to happen.
 * If applicable, add screenshots to help explain your problem.
 * If the error dialog popped up, copy/paste the content here.
+
+Please also *always* include the following information:
+
+* The operating system you are using, and if Linux, also the distro.
+* The version of novelWriter you are using.
+* How and from where you installed novelWriter.
+
+Issues without this required information will be closed.

.github/pull_request_template.md

@@ -19,6 +19,6 @@ Please check the following before you make a pull request:
 * [ ] The header of all files contain a reference to the repository license
 * [ ] The overall test coverage is increased or remains the same as before
 * [ ] All tests are passing
-* [ ] All flake8 checks are passing and the style guide is followed
+* [ ] All linting checks are passing and the style guide is followed
 * [ ] Documentation (as docstrings) is complete and understandable
 * [ ] Only files that have been actively changed are committed

.github/workflows/build_assets.yml

@@ -9,7 +9,7 @@ jobs:
       - name: Python Setup
         uses: actions/setup-python@v5
         with:
-          python-version: "3.12"
+          python-version: "3.13"
           architecture: x64
 
       - name: Install Packages (apt)
@@ -21,7 +21,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Install Packages (pip)
-        run: pip install -r docs/source/requirements.txt
+        run: pip install -U -r requirements.txt -r docs/requirements.txt
 
       - name: Build Assets
         run: |
@@ -32,7 +32,7 @@ jobs:
         with:
           name: nw-assets
           path: |
-            novelwriter/assets/manual.pdf
+            novelwriter/assets/manual*.pdf
             novelwriter/assets/sample.zip
             novelwriter/assets/i18n/*.qm
           if-no-files-found: error

.github/workflows/build_linux.yml

@@ -10,13 +10,13 @@ jobs:
     needs: buildAssets
     runs-on: ubuntu-latest
     env:
-      PYTHON_VERSION: "3.12"
+      PYTHON_VERSION: "3.13"
       LINUX_TAG: "manylinux_2_28_x86_64"
     steps:
       - name: Python Setup
         uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
           architecture: x64
 
       - name: Install Packages (pip)

.github/workflows/build_mac.yml

@@ -8,10 +8,9 @@ jobs:
 
   buildMac-AMD64:
     needs: buildAssets
-    # Stay on macos-12 due to https://github.com/create-dmg/create-dmg/issues/143
-    runs-on: macos-12
+    runs-on: macos-latest
     env:
-      PYTHON_VERSION: "3.12"
+      PYTHON_VERSION: "3.13"
       PACKAGE_ARCH: x86_64
       MINICONDA_ARCH: x86_64
     steps:
@@ -40,9 +39,9 @@ jobs:
 
   buildMac-M1:
     needs: buildAssets
-    runs-on: macos-14
+    runs-on: macos-latest
     env:
-      PYTHON_VERSION: "3.12"
+      PYTHON_VERSION: "3.13"
       PACKAGE_ARCH: aarch64
       MINICONDA_ARCH: arm64
     steps:

.github/workflows/build_win.yml

@@ -13,13 +13,13 @@ jobs:
       - name: Python Setup
         uses: actions/setup-python@v5
         with:
-          python-version: "3.12"
+          python-version: "3.13"
           architecture: x64
 
       - name: Checkout Source
         uses: actions/checkout@v4
 
-      - name: Download Artifacts
+      - name: Download Assets
         uses: actions/download-artifact@v4
         with:
           name: nw-assets

.github/workflows/build_win_launcher.yml

@@ -0,0 +1,45 @@
+name: BuildWindowsLauncher
+
+on: workflow_dispatch
+
+jobs:
+  buildLauncherWin64:
+    runs-on: windows-latest
+    steps:
+      - name: Checkout Source
+        uses: actions/checkout@v4
+
+      - name: Build Launcher
+        id: build
+        run: |
+          Set-Location setup\windows
+          .\make.ps1
+
+      - name: Upload Unsigned Artifacts
+        id: upload-unsigned-artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: launcher
+          path: setup/windows/novelWriter.exe
+          if-no-files-found: error
+          retention-days: 14
+
+      - name: Submit Signing Request
+        uses: signpath/github-action-submit-signing-request@v1
+        with:
+          api-token: "${{ secrets.SIGNPATH_API_TOKEN }}"
+          organization-id: "0471e52c-66fa-4e9a-bfb9-36167095ca3f"
+          project-slug: "novelWriter"
+          signing-policy-slug: "release-signing"
+          artifact-configuration-slug: "launcher"
+          github-artifact-id: "${{ steps.upload-unsigned-artifact.outputs.artifact-id }}"
+          wait-for-completion: true
+          output-artifact-directory: "."
+
+      - name: Upload Signed Artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: launcher-signed
+          path: novelWriter.exe
+          if-no-files-found: error
+          retention-days: 14

.github/workflows/i18n.yml

@@ -12,7 +12,7 @@ jobs:
       - name: Python Setup
         uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
           architecture: x64
       - name: Install Packages (apt)
         run: |

.github/workflows/lock_threads.yml

@@ -0,0 +1,34 @@
+name: LockThreads
+
+on:
+  schedule:
+    - cron: "14 3 */3 * *"
+
+permissions:
+  issues: write
+  pull-requests: write
+
+concurrency:
+  group: lock-threads
+
+jobs:
+  action:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: dessant/lock-threads@v5
+        with:
+          github-token: ${{ github.token }}
+          issue-inactive-days: 120
+          issue-comment: >
+            This issue has been automatically locked since there has not been
+            any recent activity after it was closed. Please open a new issue
+            for related bugs or feature requests.
+          issue-lock-reason: "resolved"
+          pr-inactive-days: 120
+          # pr-comment: >
+          #   This pull request thread has been automatically locked since there
+          #   has not been any recent activity after it was closed. Please open
+          #   an issue for any related bugs or feature requests.
+          pr-lock-reason: "resolved"
+          process-only: "issue, pr"
+          log-output: true

.github/workflows/syntax.yml

@@ -1,4 +1,4 @@
-name: Flake8
+name: Linting
 
 on:
   push:
@@ -21,10 +21,17 @@ jobs:
           architecture: x64
       - name: Checkout Source
         uses: actions/checkout@v4
-      - name: Install flake8
-        run: pip install -r requirements-dev.txt
-      - name: Syntax Check
+      - name: Install Dependencies
+        run: pip install -r requirements.txt -r requirements-dev.txt
+      - name: Ruff Check
         run: |
-          flake8 --version
-          flake8 novelwriter --count --show-source --statistics
-          flake8 tests --count --show-source --statistics --extend-ignore ANN
+          ruff --version
+          ruff check
+      - name: Pyright Check
+        run: |
+          pyright --version
+          pyright
+      - name: Isort Check
+        run: |
+          isort --version
+          isort --check .

.github/workflows/test_linux.yml

@@ -14,7 +14,7 @@ jobs:
   testLinux:
     strategy:
       matrix:
-        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
       fail-fast: false
     runs-on: ubuntu-latest
     steps:
@@ -26,7 +26,7 @@ jobs:
       - name: Install Packages (apt)
         run: |
           sudo apt update
-          sudo apt install libenchant-2-dev qttools5-dev-tools aspell-en
+          sudo apt install libenchant-2-dev qttools5-dev-tools
       - name: Checkout Source
         uses: actions/checkout@v4
       - name: Install Dependencies (pip)
@@ -41,6 +41,6 @@ jobs:
           export QT_QPA_PLATFORM=offscreen
           python -m pytest -v --cov=novelwriter --timeout=60
       - name: Upload to Codecov
-        uses: codecov/codecov-action@v4
+        uses: codecov/codecov-action@v5
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/test_mac.yml

@@ -17,7 +17,7 @@ jobs:
       - name: Python Setup
         uses: actions/setup-python@v5
         with:
-          python-version: "3.12"
+          python-version: "3.13"
           architecture: x64
       - name: Install Packages (brew)
         run: |
@@ -32,6 +32,6 @@ jobs:
           export QT_QPA_PLATFORM=offscreen
           python -m pytest -v --cov=novelwriter --timeout=60
       - name: Upload to Codecov
-        uses: codecov/codecov-action@v4
+        uses: codecov/codecov-action@v5
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/test_win.yml

@@ -17,7 +17,7 @@ jobs:
       - name: Python Setup
         uses: actions/setup-python@v5
         with:
-          python-version: "3.12"
+          python-version: "3.13"
           architecture: x64
       - name: Checkout Source
         uses: actions/checkout@v4
@@ -28,6 +28,6 @@ jobs:
         run: |
           python -m pytest -v --cov=novelwriter --timeout=60
       - name: Upload to Codecov
-        uses: codecov/codecov-action@v4
+        uses: codecov/codecov-action@v5
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.gitignore

@@ -1,6 +1,7 @@
 # Setup/Install
 /MANIFEST
 /build/
+/build_*/
 /deploy/
 /dist/
 /dist_*/
@@ -10,6 +11,7 @@ setup.iss
 /novelwriter.desktop
 /novelWriter.pyw
 /setup/macos/Info.plist
+/setup/windows/build
 .venv
 
 # Translations
@@ -20,8 +22,9 @@ i18n/*.qph
 
 # Documentation
 /docs/build/
+/docs/source/locales/**/*.mo
 /novelwriter/assets/help/
-/novelwriter/assets/manual.pdf
+/novelwriter/assets/manual*.pdf
 *.qch
 *.qhc
 .~lock.*
@@ -53,3 +56,10 @@ ToC.txt
 
 # Other
 /test.py
+.config
+.local
+*.patch
+
+# IDE
+.vscode
+.ruff_cache

CHANGELOG.md

@@ -1,5 +1,375 @@
 # novelWriter Changelog
 
+## Version 2.7 [2025-06-01]
+
+### Release Notes
+
+The 2.7 release updates the 2.7 RC 1 release and makes an improvement to the build settings tool.
+It also updates most translations and updates the French version of the documentation.
+
+See the website for complete [Release Notes](https://novelwriter.io/releases/release_2_7.html).
+
+### Detailed Changelog
+
+**Improvement**
+
+* The Manuscript Build Settings dialog now works on a copy of the settings so that if the dialog
+  box is closed without saving, all changes are discarded. It should also now detect any change
+  made to properly raise a confirmation prompt when closing without saving. Issue #2350. PR #2351.
+
+**Documentation**
+
+* The user documentation has been restructured, and the Getting Started section has been made less
+  technical. The install instructions have been moved out and into the main website. The technical
+  and in-depth parts of the documentation have been kept, but moved further back so that the
+  documentation can be read from the start and to the point where the user has enough information.
+  The larger sections have also been split up so that it should be easier to find the wanted
+  information directly from the menu. Issue #2345. PR #2355.
+
+**Internationalisation**
+
+* Updated US English, Japanese, Norwegian. German, Italian, Polish, Brazilian Portuguese and
+  Chinese translation files. PR #2353.
+* French documentation updated by @Karduin. Issue #2360. PR #2361.
+
+----
+
+## Version 2.7 RC 1 [2025-05-19]
+
+### Release Notes
+
+This is a release candidate of the next release version, and is intended for testing purposes.
+Please be careful when using this version on live writing projects, and make sure you take frequent
+backups.
+
+### Detailed Changelog
+
+**New Features**
+
+* It is now possible to set character count as the main statistics displayed on the GUI instead of
+  word count. The setting is available under the "Appearance" section in Preferences. Issue #1657.
+  PR #2323.
+* Comments can now be marked as "Manuscript Notes" with the `%Note.term:` syntax. The term is a
+  free form value that is displayed alongside the note when exported to the manuscript. Each term
+  is also added as a column in exports from the Outline View. Issue #1133. PR #2346.
+* A completer drop down menu has been added to comments as well in the editor. It is triggered when
+  a new line starts with `%`. It will show the options of Synopsis, Short, Story and Note, and when
+  a period is added after the latter two, show a list of previously used Story and Note keys.
+  Issue #1784. PR #2290.
+
+**Improvements**
+
+* The dialogue colour of the Snazzy Light syntax theme has changed from yellow to blue, which
+  should make it easier to read. PR #2336.
+* The Snazzy Light theme has also been added as a GUI theme. PR #2334.
+* The auto-generated title page for new projects should now make a little more sense in terms of
+  default values filled in for the author. PR #2333.
+* The new project form on the Welcome dialog now remembers the previous author name filled in, so
+  there should be no need to type it again every time. PR #2333.
+* Project name and author name values are now also used for new example projects. PR #2333.
+* The narrator break symbol settings for dialogue have been changed from a free text field to a
+  dropdown list of dashes. This helps to avoid misunderstandings where the field was populated with
+  other symbols, like quote symbols (see #2320). Issue #2324. PR #2327.
+* A splash screen is now shown at startup, providing some information about the initialisation
+  steps the startup script is running before the GUI is launched. Since loading system fonts can be
+  quote heavy, this at least gives some user feedback to users running on systems where there is a
+  significant delay. In particular, there is a long delay when loading fonts with poor Unicode
+  support, in which case the Qt library will look for replacement glyphs when the symbols are first
+  encountered. Previously, the delay happened when the Welcome dialog was being drawn, since this
+  is the first time a non-Ascii Unicode character is used. Now these Unicode characters are probed
+  when the config is loaded, with progress output on the splash screen. Issue #2315. PR #2316.
+
+**Bugfixes**
+
+* Moving a note between root folders of a different type will now update the class the tags defined
+  within the note are associated with. This association is used to populate the tag auto-completion
+  in the editor. Issue #2330. PR #2343.
+* The story structure comments now appear under the correct column when exported to CSV from the
+  Outline View. Issue #2313. PR #2343.
+* A new unique ID is now assigned to new example projects. Creating multiple example projects would
+  previously retain the original ID, causing the Welcome dialog to override them rather than list
+  them as unique projects. PR #2333.
+* In Qt6, or probably in PyQt6, the datetime type from Python was truncated to a date variable when
+  localising it. This has been fixed by explicitly converting the Python datetime to a QDateTime
+  before passing it to the PyQt wrapper. This is probably a bug in PyQt6. Issue #2325. PR #2326.
+* A missing Remix icon for project copy has been added. Issue #2314. PR #2317.
+
+**Accessibility**
+
+* Trees and lists on the GUI have been assigned names so that screen readers can more easily
+  identify them. Switches on the GUI have also been associated with their labels so the screen
+  reader can pick up the label text. Icons on the project tree also have an accessibility label.
+  Issues #2106 and #2107. PR #2337.
+* Switches should now show a highlighted border when they have focus, and the toggle animation also
+  now works properly when a switch is toggled using the keyboard. This should improve keyboard
+  navigation. PR #2337.
+* The default status and importance labels for new projects now use shapes for icons, to make the
+  defaults more accessible for people with reduced colour vision. Issue #2332. PR #2333.
+
+**Code Improvements**
+
+* New tests have been added for the custom data models, using the Qt model tester framework that
+  ensures the models have all the virtual methods implemented. PR #2331.
+
+----
+
+## Version 2.7 Beta 1 [2025-04-20]
+
+### Release Notes
+
+This is a beta release of the next release version, and is intended for testing purposes. Please be
+careful when using this version on live writing projects, and make sure you take frequent backups.
+
+### Detailed Changelog
+
+**New Features**
+
+* The TypIcons icon set has been dropped and all individual icon files removed. Instead, three new
+  icon themes have been added in a total of nine different variations. These icon themes are kept
+  in single files and generated from official sources. They are also colourised at runtime using
+  the GUI theme colours for consistency. Issue #2159. PRs #2171, #2174, #2177, #2178 and #2203.
+* Support for Story Structure comments have been added. These are special in-text comments that can
+  be used for analysing the story structure using various writing techniques. The comments are
+  indexed by novelWriter and can be included in manuscripts as well as exported to CSV files from
+  the Outline View for use with spread sheet software. Idea and documentation by Alan Langford
+  (@instancezero). Issues #1784, #2288, #2289 and #2296. PRs #2255, #2284, #2293, #2295 and #2298.
+
+**Improvements**
+
+* The thickness of the editor cursor can now be set in Preferences. Issue #2219. PR #2230.
+* The Novel View has been rewritten from scratch using a model/view framework. Several minor issues
+  were resolved in the process. Issues #942 and #2253. PR #2272.
+* The logic of where new documents are added in the project tree has been rewritten and improved.
+  The algorithm should now avoid adding chapters within chapters when a scene inside a chapter is
+  selected. Otherwise the behaviour should be similar to before, but it will now also apply the
+  same logic when new documents are created from templates. Issue #2260. PR #2302.
+* Dialogue highlighting should now work a little better for single quoted dialogue when it
+  encounters apostrophes in the same text. Issue #2271. PR #2300.
+* Quoted text is no longer highlighted as dialogue in the editor when the document is a project
+  note. This is consistent with how the viewer and manuscript tool work. Issue #2297. PR #2299.
+
+**Documentation**
+
+* Internationalisation for the documentation is now properly supported in the code base, and new
+  contributions are possible. Discussion #1834. PRs #2224 and #2227.
+
+**Internationalisation**
+
+* French translation files for the documentation were added by @Karduin. PR #2226.
+
+**Packaging and Installation**
+
+* The move to Qt6 is complete, and the new minimum requirement is Qt 6.4. Issues #864, #1142,
+  #2192, #2193, #2194 and #2195. PRs #2184, #2187, #2190, #2191, #2196, #2204, #2301 and #2306.
+* Support for Python 3.9 has been dropped. Due to the Qt6 change, older distros are no longer
+  supported. The oldest Ubuntu release still supported is 24.04. PR #2182.
+* The Windows release now uses a custom novelWriter.exe launcher rather than calling the Python exe
+  directly with novelWriter.pyw as an argument. This means novelWriter can also be launched from
+  its install folder, and desktop shortcuts created directly. It also simplifies the registry
+  entries. PRs #2197, #2198 and #2199.
+* The Appdata XML files used with AppImage releases has been updated and broken links fixed.
+  PR #2229.
+* RPM packages are now available for the 2.6.3 release on Fedora 41 and 42. Several minor
+  adjustments to the code base has been made to make the packaging process easier for the 2.7
+  release. The Fedora releases are maintained by Benson Muite (@bkmgit). Issues #907, #2276 and
+  #2303. PRs #2305 and #2307.
+* The shebang from the launch script on Windows has been removed. Issue #1284. PR #2280.
+
+**Code Improvements**
+
+* The log output now obeys the `NO_COLOR` and `FORCE_COLOR` environment variables. PR #2228.
+* The CI/CD pipeline now runs type checking on the code base using Pyright. PR #2279.
+* The CI/CD pipeline now uses Ruff to check code style and format. PRs #2281, #2282 and #2287.
+* The code base has been updated to conform to new linting rules. PR #2201.
+
+----
+
+## Version 2.6.3 [2025-02-16]
+
+### Release Notes
+
+This is a patch release that fixes a translation issue that affected several labels on the user
+interface where the wrong or no translation was used. The bug affected all languages except for
+English.
+
+### Detailed Changelog
+
+**Bugfixes**
+
+* Fix retrieval of translation string for stats and shape constants. This particularly affected the
+  details panel below the project tree, some labels on the outline, the statics panel on the
+  Manuscript tool and the status icon shape menu in Project Settings. It also affected the
+  statistics submenu in the Insert menu. Issue #2246. PRs #2247 and #2249.
+
+----
+
+## Version 2.6.2 [2025-02-16]
+
+### Release Notes
+
+This is a patch release that fixes a few issues with the project tree: The Empty Trash option in
+the menu now works again, and it is no longer possible to accidentally drag and drop project items
+onto the root of the project tree.
+
+In addition, a Czech translation has been added by Tomáš Zmek, and the Italian, Polish and
+Brazilian Portuguese translations have been updated.
+
+### Detailed Changelog
+
+**Bugfixes**
+
+* Fixed a bug where alternative scene formats were ignored when splitting a document. Issue #2233.
+  PR #2234.
+* Fixed the Empty Trash menu entry in the Project menu. It was not connected to the project tree
+  and therefore selecting it did nothing. Issue #2239. PR #2242.
+* Fixed a bug where it was possible to drag items to the root levels as long as they were dropped
+  between existing root items. This action is now properly blocked. PR #2242.
+
+**Improvements**
+
+* Added an extra check in the project tree item model that can prevent a crash in certain
+  circumstances when moving multiple project items. It is probably a corner case caused by
+  competing garbage collectors in Python and Qt, but the additional check should handle. PR #2242.
+
+**Internationalisation**
+
+* Add Czech translation by Tomáš Zmek. PR #2244.
+* Updated Italian, Polish and Brazilian Portuguese translations. PR #2244.
+
+See the [translation activity stream](https://crowdin.com/project/novelwriter/activity-stream) for
+more details.
+
+----
+
+## Version 2.6.1 [2025-02-02]
+
+### Release Notes
+
+This is a patch release that fixes an issue with creating new notes from the editor context menu,
+adds an option to turn off the confirmation box that pops up when closing novelWriter, and improves
+the recent project list on the Welcome dialog.
+
+A French version of the user guide is now also available when the localisation is set to French,
+and the French, Latin American Spanish, Norwegian, US English, German and Japanese translations of
+the application have been updated.
+
+### Detailed Changelog
+
+**Bugfixes**
+
+* Fixed an issue where the "Create Note from Tag" would also show up for `@story` references. These
+  should not create new novel documents. The same menu entry was also removed for `@mention`
+  references, as it is not known what category the would belong to. Issue #2212. PR #2215.
+
+**Improvements**
+
+* A setting was added to Preferences to disable the dialog box when exiting novelWriter. It is
+  available under the "Behaviour" section. Issue #2209. PR#2213.
+* Recent projects on the Welcome dialog box are now tracked using their unique ID as well as their
+  path. This means that if a project is moved, it should not show up twice in the list, but the
+  path should be updated. Issue #2217. PR #2218.
+
+**Documentation**
+
+* A French version of the user guide is nov available from the Help menu if the GUi language is set
+  to French. The French translation was contributed by @Karduin. It is currently directly added to
+  the source, but from 2.7 it will be generated automatically in the same way the English user
+  guide is. Discussion #1834. PR #2220.
+
+**Internationalisation**
+
+* French translations are available up to the 2.6 release. That is, the new exit dialog setting is
+  not translated yet. PR #2214.
+* Latin American Spanish, Norwegian, US English, German and Japanese translations are fully
+  updated. PR #2214.
+
+See the [translation activity stream](https://crowdin.com/project/novelwriter/activity-stream) for
+more details.
+
+----
+
+## Version 2.6 [2025-01-26]
+
+### Release Notes
+
+The 2.6 release fixes a few minor issues from the RC 1 pre-release, and updates most translations.
+
+See the website for complete [Release Notes](https://novelwriter.io/releases/release_2_6.html).
+
+### Detailed Changelog
+
+**Bugfixes**
+
+* Fixed a bug in the novel selector dropdown used a few places that would clear the selection if
+  the novel list was refreshed. PR #2179.
+* Fixed a bug that would crash the app if the project tree was clicked without any project having
+  been loaded. The selection model does not exist prior to a project load. Issue #2173. PR #2181.
+* Replaced a broken link on the dictionary install tool available on Windows. PR #2189.
+* Backported a few code fixes from 2.7 related to freeing memory from closed dialogs and one
+  instance of a potentially uninitialised variable. PR #2202.
+* Fixed word wrapping in the item details panel for status and importance labels with very long
+  names. PR #2202.
+* Fixed the project tree context menu so that it is not opened when right-clicking on an empty area
+  of the tree widget. PR #2202.
+
+**Improvements**
+
+* Chapter headings are now level 1 headings in all manuscript output formats, not just HTML like
+  before. Most applications that post-processes output will assume chapters are level 1.
+  Correspondingly, scenes are now level 2 and sections are level 3. Notes headings remain
+  unchanged. Issue #2205. PR #2206.
+
+**Internationalisation**
+
+* German, US English, Italian, Japanese, Norwegian and Polish have been updated in full. Brazilian
+  Portuguese and Chinese have been partially updated. PR #2207.
+
+**Documentation**
+
+* Documentation has been updated with 2.6 features. PR #2210.
+
+----
+
+## Version 2.6 RC 1 [2025-01-09]
+
+### Release Notes
+
+This is a release candidate of the next release version, and is intended for testing purposes.
+Please be careful when using this version on live writing projects, and make sure you take frequent
+backups.
+
+### Detailed Changelog
+
+**New Features**
+
+* The session timer in the status bar can now be hidden by clicking on it. Issue #1029. PR #2149.
+* Status and importance labels can now be exported and imported. Issue #1847. PRs #2152 and #2153.
+
+**Bugfixes**
+
+* Fix a beta release bug where it was not possible to change the status or importance flag on
+  folders in the project tree. Issue #2145. PR #2147.
+* Fix an issue where the word counter would override the selection counter in the editor. This was
+  caused by the selection counter being on a much shorter timer than the word counter, so in some
+  cases the latter result came in after the former even if the user actions where the other way
+  around. The selection counter now takes precedence, always. Issue #2155. PRs #2156 and #2157.
+* Fix a minor issue where the search panel header background would not update colour when the theme
+  was changed. Issue #2162. PR #2167.
+
+**Improvements**
+
+* It is no longer necessary to click the "Apply" button when making changes to status and
+  importance labels, or auto-replace settings, in Project Settings. The changes are applied
+  directly to the listed items. They are not applied to the project until the Project Settings are
+  accepted. This is a more intuitive approach. Issue #2150. PR #2151.
+
+**Packaging and Installation**
+
+* MacOS packages are now built on the latest MacOS image available on GitHub. The x86_64 build was
+  previously locked to MacOS 12, which is no loner available. PR #2141.
+
+----
+
 ## Version 2.6 Beta 2 [2024-12-23]
 
 ### Release Notes
@@ -117,7 +487,7 @@ careful when using this version on live writing projects, and make sure you take
   markup processing and syntax highlighting. It is both slightly faster, and there are issues with
   text encoding in at least some versions of Qt6 or PyQt6. PRs #2028 and #2043.
 * Preparation for Qt6: Added a wrapper function for connecting signals to slots that has a
-  different function signature. Python lambdas generate warnings inn Qt6. PR #2075.
+  different function signature. Python lambdas generate warnings in Qt6. PR #2075.
 * Refactored manuscript formats and moved most of the processing to the Tokenizer class to simplify
   the format classes and also make them more consistent. PRs #2060, #2061 and #2062.
 * The document builder has been refactored to support more generalised format classes. PR #2047.
@@ -987,7 +1357,7 @@ _These Release Notes also include the changes from the 2.2 Beta 1 and 2.2 RC 1 r
 **Usability**
 
 * Use `Ctrl+K, H` for inserting short description comments (alias to synopsis), drop the space
-  after the `%` symbol when inserting special comments, add a browse icon to the open open project
+  after the `%` symbol when inserting special comments, add a browse icon to the open project
   dialog, and remove the popup warning for Alpha releases. PR #1626.
 * Menu entries no longer clear the status bar message when they are hovered. This was caused by a
   status tip feature in Qt, which prints a blank message to the status bar. PR #1630.
@@ -997,7 +1367,7 @@ _These Release Notes also include the changes from the 2.2 Beta 1 and 2.2 RC 1 r
   of 1 second. PR #1634.
 * The document viewer panel now shows the importance label next to each entry, and double-clicking
   an entry will open it in the viewer. All entries also now show the content in tooltips so that
-  the columns can be shrunk to only view the icon if there is too little space. Issue #16220.
+  the columns can be shrunk to only view the icon if there is too little space. Issue #1620.
   PR #1639.
 * The editor toolbar no longer uses the same buttons for markdown and shortcodes style formatting.
   They have each received their separate buttons. Some additional space has been added between the

CONTRIBUTING.md

@@ -1,5 +1,7 @@
 # Contributing Guide
 
+See also [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md).
+
 When contributing to this repository, please first discuss the change you wish to make with the
 owner. Either via the issue tracker or on the discussions page. Especially if it is regarding new
 features. If you just want to make a minor correction, like fix a typo or similar, feel free to
@@ -11,7 +13,7 @@ just make a pull request directly.
   also provide a fix. It makes it easier to keep track of what has been fixed and when.
 * Translations made via the [Crowdin project page](https://crowdin.com/project/novelwriter).
 * Improvements to the documentation. Particularly if the documentation is unclear. Please don't
-  make any larger changes to the documentation without discussing if with the maintainer first.
+  make any larger changes to the documentation without discussing them with the maintainer first.
 * Adaptations, installation or packaging features targeting specific operating systems.
 
 **Please do not:**
@@ -22,19 +24,22 @@ just make a pull request directly.
 
 ## Picking the Correct Branch for a Pull Request
 
-The `main` branch is the default branch. For general changes, please make a new branch in your own
-fork from the current `main` branch. Do not make pull requests from your copy of the `main` branch.
+Pre-releases are made from the `main` branch, and full releases are made from the `release` branch.
+If you are submitting a fix to a current release you must do so from the `release` branch. If you
+make such a fix on the `main` branch, **it cannot be included in a patch release**. This also
+applies to the documentation for the latest release published on the main website.
 
-As of April 2024, releases are made from the `release` branch. If you are submitting a fix to a
-current release you must do so from the `release` branch. If you make such a fix on the `main`
-branch, **it cannot be included in a patch release**. This also applies to the documentation for
-the latest release published on the main website.
+New features are only accepted on full releases, so a feature pull request must be made to the
+`main` branch. However, if the `main` branch is very close to a new full release, pull requests may
+not be merged until the release is completed.
 
-**Also check the following:**
+## Pull Request Check List
 
-* Make sure your code passes all tests and conforms to the style guide. You can check that the
-  code generally conforms by running the Python linting tool `flake8` from the root of the project
-  folder, although it doesn't check everything. The same check is also run on pull requests.
+Make sure the pull request follows these rules:
+
+* The `main` branch is the default branch. For general changes, please make a new branch in your
+  own fork from the current `main` branch. Do not make pull requests from your copy of the `main`
+  branch.
 * Please provide a description of the changes in the pull request under the summary section of the
   pull request template, and reference any related issues by providing the issue number.
 * Do not change the version number.
@@ -42,90 +47,63 @@ the latest release published on the main website.
   mostly an issue with translation files. The language tool may update all files in the `i18n`
   folder.
 
-## Code of Conduct
+## General Rules
 
-There is a code of conduct. Please follow it in all your interactions with the project.
+These are the guidelines for the project. The source code of novelWriter broadly follows the
+[PEP8](https://www.python.org/dev/peps/pep-0008) style guide, but with a few exceptions.
 
-### Our Pledge
+### Tests
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers
-pledge to making participation in our project and our community a harassment-free experience for
-everyone, regardless of age, body size, disability, ethnicity, gender identity and expression,
-level of experience, nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+* New code must not break any existing tests.
+* New code must come with tests that cover the code in full. If the code has branches that only
+  runs on some OSes, they must be covered when test are run on that OS. The test suite runs on
+  Linux, Windows and MacOS.
 
-Please see the [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) file for the full text.
+### Code Formatting
 
-## Code Style Guide
+* Do not run automatic formatting tools like `black` or `ruff` on the code. Auto-formatting using
+  `ruff` is planned, but there are a couple of features missing in it, so it is currently only used
+  for linting. Auto-formatting with `isort` is configured in `pyproject.toml` and can be used.
+* The pull request code *must* pass the `ruff` linting rules specified in `pyproject.toml`.
+* In general, do not make large scale formatting changes to the code.
 
-The source code of novelWriter broadly follows the [PEP8](https://www.python.org/dev/peps/pep-0008)
-style guide, but with a few exceptions. Some key points are listed below.
+### Type Annotations
 
-**Line Length:**
+* All functions and parameters must be type annotated, and so must variables and attributes if the
+  type cannot be inferred from the initial value. Typing rules are set in `pyproject.toml` and a
+  pull request must pass `pyright` with these settings.
+* Do not use the `Any` type when an actual type exists. `Any` is allowed for functions that
+  actually handles any kind of input and returns a standard type.
+* Do not use deprecated capitalised annotations like `Dict`, `List`, `Tuple`, etc.
+* Type annotated code must be runnable on all supported Python versions.
 
-* Source code lines can extend to the upper limit of 99 characters allowed by PEP8. 79 characters
-  is the recommended line length in PEP8, but this is often too restrictive. 99 characters are
-  acceptable when that is more practical. Readability has priority. Generally, if a code statement
+### Internationalisation
+
+* All comments and docstrings in the code must be in English.
+* All text presented to the user must be wrapped in calls to Qt's translation framework, and the
+  spelling of this text *must* be UK English. US English spelling is not allowed for these strings.
+* Commit descriptions and pull requests must also be in English.
+
+### Line Length
+
+* Source code lines can extend to the upper limit of 99 characters. Generally, if a code statement
   requires multiple lines, the lines should wrap at 79 characters if possible. If wrapping can be
-  avoided by going to 99, then that is generally preferable.
-* For text files, the text should be wrapped at 99 character. The exception is markdown image tags
-  and urls which can run past that limit.
+  avoided by going to 99, then that is generally preferable. Readability has priority.
+* For text files, the text should be wrapped at 99 character. The exception is Markdown image tags
+  and URLs which can run past that limit.
 
-**Variable and Function Names**
-
-* PEP8 allows for camelCase for consistency with existing code. The Qt library uses camelCase, so
-  the novelWriter source code does too.
-* The exception to the above is for constants. They should always be in upper snake case, like PEP8
-  states.
-
-**Spaces, Indentation and Alignment**
+### Spaces, Indentation and Alignment
 
 * Only indentation by multiples of 4 spaces is allowed.
 * No trailing spaces should occur on any line in the source code, including empty lines.
-* All common line wrapping methods are allowed in the code, but avoid deep indentations.
+* Common line wrapping methods are allowed in the code except `\`, but avoid deep indentations.
 * Aligning operators and attributes in columns with multiple spaces is not allowed by PEP8. The
   rule is relaxed a bit here. Alignment is allowed when populating large dictionaries or setting
   many class attributes. It does improve readability in such cases, but should not be overused.
 
-**Type Annotation**
+### General Code Rules
 
-* All functions must be properly type annotated, and a return type stated in all cases.
-* Do not use `List`, `Dict`, `Tuple`, etc, annotations that were deprecated in Python 3.9. You can
-  install the `flake8-pep585` extension to make sure you don't forget. This is also checked by the
-  syntax action run on pull requests.
-* If annotations require a more recent Python version than the minimum version stated in the
-  project's `pyproject.toml`, hide it under an `if TYPE_CHECKING` condition so that the code can
-  still run on older versions. It's OK to require a more recent version for development.
-
-### Linting with `flake8`
-
-A good tool for checking Python code for errors and code style is `flake8`. The documentation is
-available [here](https://flake8.pycqa.org/en/latest/).
-
-The `.flake8` file in the root of this project has the following settings for that matches the
-required code style:
-
-```conf
-[flake8]
-ignore = E133,E221,E226,E228,E241,W503
-max-line-length = 99
-exclude = docs/*
-```
-
-The command line equivalent, with reporting, is:
-```bash
-flake8 . --count --ignore E133,E221,E226,E228,E241,W503 --max-line-length=99 --show-source --statistics
-```
-
-Passing this check is required before contributions are merged. This is checked automatically when
-you make a pull request. You can run the `flake8` command locally to check beforehand. The full
-command will give you a detailed description of the code lines that do not conform to the standard.
-
-Two of the ignored errors are due to the relaxed restriction on column alignment, these are the
-E221 and E241 error codes.
-
-The code E226 is ignored because it doesn't actually follow the
-[PEP8 recommendation](https://www.python.org/dev/peps/pep-0008/#other-recommendations)
-of grouping longer equations by operator precedence like `2*a + 3*b` instead of `a * a + 3 * b`.
-Generally, don't use spaces around `*`, `/` and `**`, but _do_ use spaces around `+` and `-`.
-The same applies to the modulo operator `%`, hence E228 is also ignored.
+* Use f-string style for string formatting as the first choice, and `.format` functions if there is
+  a good reason for it. Do not use `%` style formatting except for logging output. For logging, `%`
+  must be used (it's a limitation in the logging library unfortunately).
+* Functions should be on camelCase form for consistency with the Qt library code.

CREDITS.md

@@ -21,6 +21,7 @@ The artwork on the Welcome dialog was created by Louis Durrant.
 The default language is English (UK) with English (US) as an option. These are the original
 translators for the languages currently available:
 
+* **Czech:** Tomáš Zmek (perteus)
 * **Dutch:** Martijn van der Kleijn (mvdkleijn)
 * **French:** Jan Lüdke (jyhelle)
 * **German:** Myian (HeyMyian)
@@ -38,6 +39,10 @@ Additional larger translation contributions:
 * **French:** Albert Aribaud (aaribaud)
 * **Portuguese:** Oli Maia (olimaia)
 
+Translations of the documentation:
+
+* **French:** Jean-Michel Heras (Karduin)
+
 Translations are managed on [Crowdin](https://crowdin.com/project/novelwriter), and more
 contributions are listed on the project's Members page.
 
@@ -45,8 +50,8 @@ contributions are listed on the project's Members page.
 
 The following libraries are dependencies of novelWriter:
 
-* **Qt5** by Qt Company
-* **PyQt5** by Riverbank Computing
+* **Qt6** by Qt Company
+* **PyQt6** by Riverbank Computing
 * **Enchant** by Dom Lachowicz
 * **PyEnchant** by Dimitri Merejkowsky
 
@@ -54,7 +59,9 @@ The following libraries are dependencies of novelWriter:
 
 Some of the assets bundled with novelWriter were adapted from the following sources:
 
-* **Typicons** icons by Stephen Hutchings (CC BY-SA 4.0)
+* **Material Symbols** icons by Google Inc (Apache 2.0)
+* **Remix** icons by RemixIcon (Apache 2.0)
+* **Font Awesome** icons by Fonticons Inc (CC BY 4.0)
 * **Tomorrow** syntax themes by Chris Kempson (MIT License)
 * **Owl** syntax themes by Sarah Drasner (MIT License)
 * **Solarized** themes by Ethan Schoonover (MIT License)
@@ -64,11 +71,9 @@ Some of the assets bundled with novelWriter were adapted from the following sour
 
 ## Fonts
 
-The font used for the main novelWriter logo, mimetype and text banners is Pridi. Other fonts are
-used on buttons and icons.
+The font used for the main novelWriter logo, mimetype and text banners is Pridi.
 
 * **Pridi** by Cadson Demak (Open Font License, Version 1.1)
-* **Source Sans Pro** by Paul D. Hunt (SIL Open Font License)
 
 ## Special Mentions
 

README.md

@@ -1,9 +1,9 @@
 # novelWriter
 
-[![Linux](https://github.com/vkbo/novelWriter/actions/workflows/test_linux.yml/badge.svg?branch=main)](https://github.com/vkbo/novelWriter/actions/workflows/test_linux.yml)
-[![Windows](https://github.com/vkbo/novelWriter/actions/workflows/test_win.yml/badge.svg?branch=main)](https://github.com/vkbo/novelWriter/actions/workflows/test_win.yml)
-[![MacOS](https://github.com/vkbo/novelWriter/actions/workflows/test_mac.yml/badge.svg?branch=main)](https://github.com/vkbo/novelWriter/actions/workflows/test_mac.yml)
-[![Flake8](https://github.com/vkbo/novelWriter/workflows/flake8/badge.svg)](https://github.com/vkbo/novelWriter/actions)
+[![Linux](https://github.com/vkbo/novelWriter/actions/workflows/test_linux.yml/badge.svg)](https://github.com/vkbo/novelWriter/actions/workflows/test_linux.yml)
+[![Windows](https://github.com/vkbo/novelWriter/actions/workflows/test_win.yml/badge.svg)](https://github.com/vkbo/novelWriter/actions/workflows/test_win.yml)
+[![MacOS](https://github.com/vkbo/novelWriter/actions/workflows/test_mac.yml/badge.svg)](https://github.com/vkbo/novelWriter/actions/workflows/test_mac.yml)
+[![Linting](https://github.com/vkbo/novelWriter/actions/workflows/syntax.yml/badge.svg)](https://github.com/vkbo/novelWriter/actions/workflows/syntax.yml)
 [![CodeCov](https://codecov.io/gh/vkbo/novelWriter/branch/main/graph/badge.svg)](https://codecov.io/gh/vkbo/novelWriter)
 
 <img align="left" style="margin: 0 0 4px 0;" src="https://raw.githubusercontent.com/vkbo/novelWriter/main/setup/novelwriter_readme.png">
@@ -40,16 +40,20 @@ documentation.
 
 ## Implementation
 
-novelWriter is written with Python 3 (3.9+) using Qt5 and PyQt5 (5.15 only), and is released on
-Linux, Windows and macOS. It can in principle run on any Operating System that also supports Qt,
-PyQt and Python.
+novelWriter is written with Python and Qt6 with PyQt6 Python binding. It is released on Linux,
+Windows and MacOS. It can in principle run on any Operating System that also supports Qt, PyQt and
+Python.
+
+<p align="center">
+  <img width="80%" src="https://raw.githubusercontent.com/vkbo/novelWriter/main/setup/screenshot.png">
+</p>
 
 ## Project Contributions
 
 Please don't make feature pull requests without first having discussed them with the maintainer.
-You can make a feature request in the issue tracker, or if the idea isn't fully formed, start a
-discussion on the discussion page. Please also don't make pull requests to reformat or rewrite
-existing code unless there is a very good reason for doing so.
+You can make a feature request in the [issues tracker](https://github.com/vkbo/novelWriter/issues),
+or if the idea isn't fully formed, start a [discussion](https://github.com/vkbo/novelWriter/discussions).
+Please also don't make pull requests to reformat or rewrite existing code unless there is a very good reason for doing so.
 
 Fixes and patches are welcome. Contributions related to packaging and installing novelWriter will
 also be appreciated, but please make an issue or a discussion topic first. Before contributing any
@@ -58,9 +62,9 @@ code, please also read the full
 
 Project credits are available in [CREDITS.md](https://github.com/vkbo/novelWriter/blob/main/CREDITS.md).
 
-**Note:** As of April 2024 only pre-releases are made from the `main` branch. Full releases are
-made from the `release` branch. So if you're submitting a fix to a current release, **including
-changes to documentation**, they must be made to the `release` branch.
+**Note:** New features and pre-releases are made on the `main` branch. Full releases are made from
+the `release` branch. So if you're submitting a fix to a current release, **including changes to
+documentation**, they must be made to the `release` branch.
 
 ### Translations
 
@@ -69,9 +73,6 @@ can contribute translations at the [Crowdin project page](https://crowdin.com/pr
 If you have any questions, feel free to post them to the
 [Translations of novelWriter](https://github.com/vkbo/novelWriter/issues/93) issue thread.
 
-For more details, and how to use Qt Linguist for translations, see the
-[i18n instructions](https://github.com/vkbo/novelWriter/blob/main/i18n/README.md).
-
 ## Licence
 
 This is Open Source software, and novelWriter is licenced under GPLv3. See the

docs/requirements.txt

@@ -1,6 +1,8 @@
-sphinx-book-theme
-sphinx>=5.0
-sphinx-favicon
-sphinx-design
-pygments>=2.7
 docutils>=0.17.1
+pygments>=2.7
+sphinx-book-theme
+sphinx-copybutton
+sphinx-design
+sphinx-favicon
+sphinx-intl
+sphinx>=5.0

docs/source/conf.py

@@ -5,21 +5,26 @@ Documentation: http://www.sphinx-doc.org/en/master/config
 
 # -- Imports -----------------------------------------------------------------
 
+import datetime
 import os
 import time
-import datetime
 
 # -- Project Information -----------------------------------------------------
 
 project = "novelWriter"
-copyright = f"{datetime.date.today().year}"
-author = "Veronica Berglyd Olsen"
+copyright = f"{datetime.date.today().year}"  # noqa: A001
+
+tmp_authors = ["Veronica Berglyd Olsen"]
+if additional := os.environ.get("SPHINX_I18N_AUTHORS"):
+    tmp_authors.extend(a.strip() for a in additional.split(","))
+
+author = ", ".join(tmp_authors)
 
 initFile = os.path.join(
     os.path.dirname(__file__), os.pardir, os.pardir,
     "novelwriter", "__init__.py"
 )
-with open(initFile) as inFile:
+with open(initFile, encoding="utf-8") as inFile:
     for aLine in inFile:
         if aLine.startswith("__version__"):
             release = aLine.split('"')[1].strip()
@@ -35,12 +40,14 @@ os.environ["TZ"] = "Europe/Oslo"
 time.tzset()
 
 needs_sphinx = "5.0"
-extensions = ["sphinx_design"]
+extensions = ["sphinx_design", "sphinx_copybutton"]
 templates_path = ["_templates"]
 source_suffix = ".rst"
 master_doc = "index"
 today_fmt = "%A, %d %B %Y at %H:%M"
 language = "en"
+locale_dirs = ["locales/"]
+gettext_compact = False
 exclude_patterns = []
 
 # -- Options for HTML Output -------------------------------------------------
@@ -80,5 +87,5 @@ latex_elements = {
 }
 latex_logo = "_static/novelwriter-pdf.png"
 latex_documents = [(
-    master_doc, "manual.tex", "User Guide", author, "manual"
+    master_doc, "manual.tex", None, author, "manual"
 )]

docs/source/features/dialogue.rst

@@ -0,0 +1,92 @@
+.. _docs_features_dialogue:
+
+*********************
+Dialogue Highlighting
+*********************
+
+Dialogue recognition and colour highlighting is available both while you're writing and in
+generated manuscript documents.
+
+The default language settings in novelWriter are for English. That includes the dialogue
+highlighting settings. But many dialogue styles are supported. You can tune a number of settings
+to fit your language and style preferences in the "Text Highlighting" section in **Preferences**.
+You can mix and match these settings.
+
+.. figure:: images/fig_dialogue_highlighting.png
+
+   The **Text Highlighting** section of **Preferences**.
+
+
+Quoted Dialogue
+===============
+
+By default, dialogue highlighting is enabled for the double quote symbols you have defined in the
+**Quotation Style** section of **Preferences**.
+
+.. figure:: images/fig_dialogue_quote_styles.png
+
+   The **Quotation Style** section of **Preferences**.
+
+You can change which quote symbols are highlighted by selecting one of "None", "Single", "Double",
+or "Both" from the "Highlight dialogue" setting under **Text Highlighting**.
+
+You can also enable or disable the "Allow open-ended dialogue" setting to allow for the style where
+multi-paragraph dialogue is not closed until the last paragraph.
+
+.. admonition:: Limitations
+
+   Dialogue highlighting for single quotes is difficult to process when the same single quote
+   symbol is also used for apostrophes. There isn't a good solution to this. Your best option in
+   the cases where the highlighting is wrong is to insert an alternative apostrophe symbol instead.
+   See :ref:`docs_more_typographical_symbols_apostrophe` for more details.
+
+
+Alternative Dialogue
+====================
+
+You can use the "Alternative dialogue symbols" setting for custom dialogue wrapper symbols. These
+are highlighted in a different colour than regular dialogue.
+
+The intended use case here is if you use an alternative style to distinguish a different style of
+communication. The feature idea came from a science fiction series where mind-to-mind communication
+used a different quotation style.
+
+
+Dialogue Line Symbols
+=====================
+
+In some languages, a single symbol at the start of a paragraph can indicate that the whole
+paragraph is dialogue. For instance, this symbol can be a short dash (en dash).
+
+.. figure:: images/fig_dialogue_line.png
+
+   An example of dialogue starting with a short dash.
+
+You can enable this feature by adding the symbols to the "Dialogue line symbols" setting. Multiple
+symbols are allowed.
+
+
+Dialogue with Narrator Break
+============================
+
+The dialogue symbol setting will not detect if the dialogue ends in the paragraph. In some styles
+there is no way to actually indicate the switch from dialogue to narration; in others there are.
+These a narrator break symbols are usually dashes. You can select one of the supported dash symbols
+for narrator breaks. These can be used with any of the above dialogue recognition settings.
+
+.. figure:: images/fig_dialogue_narrator_break.png
+
+   An example of dialogue starting with a short dash and a long dash narrator break.
+
+
+Alternating Dialogue and Narration
+==================================
+
+The alternating dialogue and narration style is supported with the "Alternating dialogue/narration
+symbol" setting. It can be set to one of the supported dashes. This style will switch into dialogue
+mode when it first encounters the selected dash in a paragraph, and switch back out when it sees
+the next one, and so forth.
+
+.. figure:: images/fig_dialogue_alternating.png
+
+   An example of alternating dialogue and narration using a long dash.

docs/source/features/shortcuts.rst

@@ -1,4 +1,4 @@
-.. _a_kb:
+.. _docs_features_shortcuts:
 
 ******************
 Keyboard Shortcuts
@@ -8,11 +8,10 @@ Most features in novelWriter are available as keyboard shortcuts. This is a refe
 shortcuts. Most of them are also listed in the application's user interface.
 
 .. note::
+
    On MacOS, replace :kbd:`Ctrl` with :kbd:`Cmd`.
 
 
-.. _a_kb_main:
-
 Main Window Shortcuts
 =====================
 
@@ -38,8 +37,6 @@ Main Window Shortcuts
    ":kbd:`Shift+F6`",     "Open the **Project Details** dialog"
 
 
-.. _a_kb_tree:
-
 Project Tree Shortcuts
 ======================
 
@@ -62,8 +59,6 @@ Project Tree Shortcuts
    ":kbd:`Ctrl+Shift+Del`", "Move the selected item to Trash"
 
 
-.. _a_kb_editor:
-
 Document Editor Shortcuts
 =========================
 
@@ -120,7 +115,7 @@ Other Editor Shortcuts
    ":kbd:`Ctrl+.`",         "Open the context menu at the current cursor location"
    ":kbd:`Ctrl+A`",         "Select all text in the document"
    ":kbd:`Ctrl+C`",         "Copy selected text to clipboard"
-   ":kbd:`Ctrl+K`",         "Activate the insert commands (see list in :ref:`a_kb_ins`)"
+   ":kbd:`Ctrl+K`",         "Activate the insert commands (see list in :ref:`docs_features_shortcuts_insert`)"
    ":kbd:`Ctrl+R`",         "Open or reload the current document in the viewer"
    ":kbd:`Ctrl+S`",         "Save the current document"
    ":kbd:`Ctrl+V`",         "Paste text from clipboard to cursor position"
@@ -135,7 +130,7 @@ Other Editor Shortcuts
    ":kbd:`Ctrl+Shift+A`",   "Select all text in the current paragraph"
 
 
-.. _a_kb_ins:
+.. _docs_features_shortcuts_insert:
 
 Insert Shortcuts
 ----------------
@@ -184,8 +179,6 @@ a key or key combination for the inserted content.
    ":kbd:`Ctrl+K`, :kbd:`Shift+Space`", "Insert a thin space"
 
 
-.. _a_kb_viewer:
-
 Document Viewer Shortcuts
 =========================
 

docs/source/features/story_comments.rst

@@ -0,0 +1,110 @@
+.. _docs_features_story:
+
+**************
+Story Comments
+**************
+
+A special set of comment styles allow for annotating your text with structure information. There
+are two styles of comments available. They are an extension to regular comments as described in
+:ref:`docs_usage_comments`.
+
+.. versionadded:: 2.7
+
+
+Story Structure Comments
+========================
+
+You can annotate story structure by using the ``%Story`` style of comment. To use the feature,
+make the first word of a comment ``Story``, followed by a period, a structure term, a colon, a
+space and the text for that term.
+
+
+Usage
+-----
+
+The story term can be anything that you want to track in the manuscript. This construct is intended
+to make it easier to extract metadata from a work to perform a structural analysis of the story.
+
+There are probably as many ways to examine story structure as there are authors and editors
+combined. For this reason the story tag is flexible. You can use any terms you want and track any
+aspect of the story that serves your purposes.
+
+An example method has been advanced by Shawn Coyne in *The Story Grid*. This method asserts that a
+story is composed of "beats", and that each beat has an inciting incident, a complication, a
+crisis, and a resolution. One might capture these elements of a beat where a character overcomes
+their fear of giving a speech as:
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ### Scene
+
+   %Synopsis: Carol overcomes her fear of giving a speech.
+
+   %Story.incite: Carol is pleased to be invited to a conference to see her boss deliver a keynote.
+   %Story.complication: Carol's boss calls in sick and asks her to deliver a big speech.
+   %Story.crisis: Carol has a fear of appearing on stage.
+   %Story.resolution: Carol engages the help of a coach who helps her overcome her fears and delivers a great speech.
+
+Other analytical models propose tracking a scene's pace, how it affects the mood of the story, or
+which element(s) of the story's genre are being satisfied. An author can use this mechanism to
+track any element of a scene. Some examples include time of day, how much time passes in the scene,
+or even the physical form of a shape-shifting character. If a story involves magic, one could track
+which wand a main character has in hand. It's up to tha author.
+
+When the story and other scene metadata is extracted into a tabular form, it is possible to get a
+comprehensive overview of the story and to identify possible issues. For example, so many
+fast-paced scenes without a break that readers might become fatigued or over-stimulated.
+
+
+Output
+------
+
+The story structure comments can be included in the manuscript, and are formatted similarly to
+the synopsis comments:
+
+.. figure:: images/fig_story_structure_manuscript.png
+
+   A set of story structure comments as shown in the Manuscript tool.
+
+When you export your project data from the Outline View, all story structure terms are added as
+columns to the exported file, which can then be opened in the spread sheet software of your choice.
+
+
+Story Notes
+===========
+
+Story notes are similar to story structure comments, but have no predefined meaning. Essentially
+they are a generalisation of the story structure comment, and the only point of having this
+additional format is to allow you do filter them in and out of your manuscript independently.
+
+You can annotate story notes by using the ``%Note`` style of comment. To use the feature,
+make the first word of a comment ``Note``, followed by a period, a term, a colon, a space and the
+text for the note.
+
+
+Usage
+-----
+
+These notes are free form, but one intended use case is to add consistency annotations to your text
+to remind yourself where you have described something that must be checked against other parts of
+your text later on.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ### Scene
+
+   %Synopsis: Carol overcomes her fear of giving a speech.
+
+   %Note.consistency: This is the first time in the story Carol gives a speech.
+
+
+Output
+------
+
+Story notes are included in the manuscript in exactly the same way story structure comments are,
+but has a separate inclusion setting in the build settings. They are also included in CSV exports
+from the **Outline View**.

docs/source/index.rst

@@ -1,6 +1,6 @@
-######################
-novelWriter User Guide
-######################
+##########
+User Guide
+##########
 
 | **Release Version:** |release|
 | **Updated:** |today|
@@ -16,14 +16,6 @@ storage for robustness.
    :align: center
    :width: 500
 
-The project storage is suitable for version control software, and also well suited for file
-synchronisation tools. All text is saved as plain text files, and your project data as standard
-data formats in XML and JSON. See :ref:`a_storage` for more details.
-
-Any operating system that has Python 3 and the Qt 5 libraries should be able to run novelWriter.
-It runs fine on Linux, Windows and MacOS, and users have tested it on other platforms as well.
-See :ref:`a_started` for more details.
-
 **Useful Links**
 
 * Website: https://novelwriter.io
@@ -40,56 +32,58 @@ See :ref:`a_started` for more details.
 .. toctree::
    :hidden:
 
-   Main Page <self>
+   self
+   More Documents <https://novelwriter.io/more/>
 
 .. toctree::
-   :maxdepth: 1
-   :caption: Introduction
+   :caption: Getting Started
    :hidden:
 
-   int_introduction
-   int_overview
-   int_started
-   int_howto
-   int_glossary
+   usage/introduction
+   usage/organising_project
+   usage/chapters_and_scenes
+   usage/basic_formatting
+   usage/comments
+   usage/tags_and_references
+   usage/alignment_and_indent
+   usage/advanced_formatting
+   usage/front_back_matter
+   usage/howto
 
 .. toctree::
-   :maxdepth: 1
-   :caption: Using novelWriter
+   :caption: The User Interface
    :hidden:
 
-   usage_breakdown
-   usage_project
-   usage_writing
-   usage_format
-   usage_shortcuts
-   usage_typography
+   user_interface/main_window
+   user_interface/projects
+   user_interface/editor_viewer
+   user_interface/split_and_merge
+   user_interface/manuscript
+   user_interface/statistics
 
 .. toctree::
-   :maxdepth: 1
-   :caption: Organising Your Project
+   :caption: Other Features
    :hidden:
 
-   project_overview
-   project_structure
-   project_references
-   project_manuscript
+   features/dialogue
+   features/story_comments
+   features/shortcuts
 
 .. toctree::
-   :maxdepth: 1
-   :caption: Additional Details
+   :caption: In-Depth Topics
    :hidden:
 
-   more_customise
-   more_projectformat
-   more_counting
+   more/counting
+   more/typography
+   more/customise
+   more/handling_errors
+   more/project_format
 
 .. toctree::
-   :maxdepth: 1
    :caption: Technical Topics
    :hidden:
 
-   tech_locations
-   tech_storage
-   tech_source
-   tech_tests
+   technical/locations
+   technical/storage
+   technical/source
+   technical/tests

docs/source/int_glossary.rst

@@ -1,64 +0,0 @@
-.. _a_glossary:
-
-********
-Glossary
-********
-
-.. glossary::
-   :sorted:
-
-   Root Folder
-      A "Root Folder" is a top level folder of the project tree in novelWriter. Each type of root
-      folder has a specific icon to identify it. For an overview of available root folder types,
-      see :ref:`a_proj_roots`.
-
-   Novel Documents
-      These are documents that are created under a "Novel" :term:`root folder`. They behave
-      differently than :term:`Project Notes`, and have some more restrictions. For instance, they
-      can not exist in folders intended only for project notes. See the :ref:`a_struct` chapter for
-      more details.
-
-   Project Notes
-      Project Notes are unrestricted documents that can be placed anywhere in your project. You
-      should not use these documents for story elements, only for notes. Project notes are the
-      source files used by the Tags and References system. See the :ref:`a_references` chapter for
-      more details on how to use them.
-
-   Tag
-      A tag is a user defined value assigned as a tag to a section of your :term:`Project Notes`.
-      It is optional, and can be defined once per heading. It is set using the :term:`keyword`
-      syntax ``@tag: value``, where ``value`` is the user defined part. Each tag can be referenced
-      in another file using one of the :term:`reference` keywords. See :ref:`a_references` chapter
-      for more details.
-
-   Reference
-      A reference is one of a set of :term:`keywords<keyword>` that can be used to link to a
-      :term:`tag` in another document. The reference keywords are specific to the different
-      :term:`root folder` types. A full overview is available in the :ref:`a_references` chapter.
-
-   Project Index
-      The project index is a record of all headings in a project, with all their meta data like
-      synopsis comments, :term:`tags<tag>` and :term:`references<reference>`. The project index is
-      kept up to date automatically, but can also be regenerated manually from the
-      :guilabel:`Tools` menu or by pressing :kbd:`F9`.
-
-   Context Menu
-      A context menu is a menu that pops up when you right click something in the user interface.
-      In novelWriter, you can often also open a context menu by pressing the keyboard shortcut
-      :kbd:`Ctrl+.`.
-
-   Headings
-      Each level of headings in :term:`Novel Documents` have a specific meaning in terms of the
-      structure of the story. That is, they determine what novelWriter considers a partition, a
-      chapter, a scene or a text section. For :term:`Project Notes`, the heading levels don't
-      matter. For more details on headings in novel documents, see :ref:`a_struct_heads`.
-
-   Keyword
-      A keyword in novelWriter is a special command you put in the text of your documents. They are
-      not standard Markdown, but are used in novelWriter to add information that is interpreted by
-      the application. For instance, keywords are used for :term:`tags<tag>` and
-      :term:`references<reference>`.
-
-      Keywords must always be on their own line, and the first character of the line must always be
-      the ``@`` character. The keyword must also always be followed by a ``:`` character, and the
-      values passed to the command are added after this, separated by commas.

docs/source/int_introduction.rst

@@ -1,128 +0,0 @@
-.. _a_intro:
-
-********
-Overview
-********
-
-.. _Snowflake: https://www.advancedfictionwriting.com/articles/snowflake-method/
-.. _Markdown: https://en.wikipedia.org/wiki/Markdown
-
-At its core, novelWriter is a multi-document plain text editor. The idea is to let you edit your
-text without having to deal with formatting until you generate a draft document or manuscript.
-Instead, you can focus on the writing right from the start.
-
-Of course, you probably need *some* formatting for your text. At the very least you need emphasis.
-Most people are familiar with adding emphasis using ``_underscores_`` and ``**asterisks**``. This
-formatting standard comes from Markdown_ and is supported by novelWriter. It also uses Markdown
-formatting for defining document headings. If you need more specialised formatting, additional
-formatting options are available using a shortcode format. See :ref:`a_fmt_shortcodes` for more
-details.
-
-.. admonition:: Limitations
-
-   novelWriter is designed for writing fiction, so the formatting features available are limited to
-   those relevant for this purpose. It is *not* suitable for technical writing, and it is *not* a
-   full-featured Markdown editor.
-
-   It is also not intended as a tool for organising research for writing, and therefore lacks
-   formatting features you may need for this purpose. The notes feature in novelWriter is mainly
-   intended for character profiles and plot outlines.
-
-Your novel project in novelWriter is organised as a collection of separate plain text documents
-instead of a single, large document. The idea is to make it easier to reorganise your project
-structure without having to cut and paste text between chapters and scenes.
-
-There are two kinds of documents in your project: :term:`Novel Documents` are documents that are
-part of your story. The other kind of documents are :term:`Project Notes`, which are intended for
-your notes about your characters, your world building, and so on.
-
-You can at any point split the individual documents by their headings up into multiple documents,
-or merge multiple documents into a single document. This makes it easier to use variations of the
-Snowflake_ method for writing. You can start by writing larger structure-focused documents, like
-for instance one document per act, and later effortlessly split these up into chapters or scenes.
-
-
-.. _a_intro_features:
-
-Key Features
-============
-
-Below are some key features of novelWriter.
-
-**Focus on writing**
-   The aim of the user interface is to let you focus on writing instead of spending time formatting
-   text. Formatting is therefore limited to a small set of formatting tags for simple things like
-   text emphasis and paragraph alignment. Additional shortcodes are available for special
-   formatting cases.
-
-   When you really want to focus on just writing, you can switch the editor into **Focus Mode**
-   where only the text editor panel itself is visible, and the project structure view is hidden
-   away.
-
-**Keep an eye on your notes**
-   The main window can optionally show a document viewer to the right of the editor. The viewer
-   is intended for displaying another scene document, your character notes, plot notes, or any
-   other document you may need to reference while writing. It is not intended as a preview panel
-   for the document you're editing, but if you wish, you can also use it for this purpose.
-
-**Organise your documents how you like**
-   You can split your novel project up into as many individual documents as you want to. When you
-   build the project into a manuscript, they are all glued together in the top-to-bottom order in
-   which they appear in the project tree. You can use as few text documents as you like, but
-   splitting the project up into chapters and scenes means you can easily reorder them using the
-   drag-and-drop feature of the project tree. You can also start out with fewer documents and then
-   later split them into multiple documents based on chapter and scene headings.
-
-**Multi-novel project support**
-   The main parts of your project is split up into top level special folders called "Root" folders.
-   Your main story text lives in the "Novel" root folder. You can have multiple such folders in a
-   project, and rename them to whatever you want. This allows you to keep a series of individual
-   novels with the same characters and world building in the same project, and create manuscripts
-   for them individually.
-
-**Keep track of your story elements**
-   All notes in your project can be assigned a :term:`tag` that you can then :term:`reference` from
-   any other document or note. In fact, you can add a new tag under each heading of a note if you
-   need to be able to reference specific sections of it, or you want to keep several topics in the
-   same note.
-
-**Get an overview of your story**
-   It is not the documents themselves that define the chapters and scenes of your story, but the
-   headings that separate them. In the **Outline View** on the main window you can see an outline
-   of all the chapter and scene headings of each novel root folder in your project. If they have
-   any references in them, like which character is in what chapter and scene, these are listed in
-   additional columns.
-
-   You can also add a synopsis to each chapter or scene, which can be listed here as well. You have
-   the option to add or remove columns of information from this outline. A subset of the outline
-   information is also available in the **Novel View** as an alternative view to the project tree.
-
-**Get an overview of your story elements**
-   Under the document viewer panel you will find a series of tabs that show the different story
-   elements you have created tags for. The tabs are sorted into **Characters**, **Plots**, etc,
-   depending on which categories you are using in your story. This panel can be hidden to free up
-   space when you don't need it.
-
-**Assembling your manuscript**
-   Whether you want to assemble a manuscript, or export all your notes, or generate an outline of
-   your chapters and scenes with a synopsis included, you can use the **Build Manuscript** tool to
-   do so. The tool lets you select what information you want to include in the generated document,
-   and how it is formatted. You can send the result to a printer or PDF, or generate an Open
-   Document file that can be opened by most office type word processors. You can also generate the
-   result as HTML, or Markdown, both suitable for further conversion to other formats.
-
-
-.. _a_intro_screenshots:
-
-Screenshots
-===========
-
-.. figure:: images/screenshot_light.png
-   :class: dark-light
-
-   novelWriter with light colour theme
-
-.. figure:: images/screenshot_dark.png
-   :class: dark-light
-
-   novelWriter with dark colour theme

docs/source/int_overview.rst

@@ -1,88 +0,0 @@
-.. _a_reading:
-
-******************
-What to Read First
-******************
-
-The documentation of novelWriter is quite extensive. There are a lot of features to get used to,
-but you don't need all of them to get started.
-
-The chapters below labelled "Essential Information" are the ones you need to know to use the
-application correctly. By "correctly", it is meant: in a way so novelWriter understands the basic
-structure of your text. It collects a lot of information from your text and uses it to display the
-structure of it in various ways to help you get an overview of your writing.
-
-The chapters labelled "Recommended Reading" includes additional information on how the different
-parts if the application work and what the features do. 
-
-The "Optional" and "Lookup" chapters contain additional information or lookup tables that are not
-essential for using the application.
-
-
-Using novelWriter
-=================
-
-In order to use novelWriter effectively, you need to know the basics of how it works. The following
-chapters will explain the main principles. It starts with the basics, and gets more detailed as you
-read on.
-
-:ref:`a_breakdown` – Essential Information
-   This chapter explains the basics of how the application works and what it can and cannot do.
-
-:ref:`a_ui_project` – Recommended Reading
-   This chapter will give you a more detailed explanation of how you can use the user interface
-   components to organise and view your project work.
-
-:ref:`a_ui_writing` – Recommended Reading
-   This chapter will give you a more detailed explanation of how the text editor and viewer work.
-
-:ref:`a_fmt` – Essential Information
-   This chapter covers how you should format your text. The editor is plain text, so text
-   formatting requires some basic markup. The structure of your novel is also inferred from how you
-   use headings. Tags and references are implemented by special keywords.
-
-:ref:`a_kb` – Optional / Lookup
-   This chapter lists all the keyboard shortcuts in novelWriter and what they do. Most of the
-   shortcuts are also listed next to their menu entries inside the app, or in tool tips. This
-   chapter is mostly for reference.
-
-:ref:`a_typ` – Optional
-   This chapter gives you an overview of the special typographical symbols available in
-   novelWriter. The auto-replace feature can handle the insertion of standard quote symbols for
-   your language, and other special characters. If you use any symbols aside from these, their
-   intended use is explained here.
-
-
-Organising Your Projects
-========================
-
-In addition to managing a collection of plain text files, novelWriter can interpret and map the
-structure of your novel and show you additional information about its flow and content. In order
-to take advantage of these features, you must structure your text in a specific way and add some
-meta data for it to extract.
-
-:ref:`a_proj` – Essential Information
-   This chapter explains how you organise the content of your project, and how to set up automated
-   backups of your work.
-
-:ref:`a_struct` – Essential Information
-   This chapter covers the way your novel's structure is encoded into the text documents. It
-   explains how the different levels of headings are used, and some special formatting for
-   different kinds of headings.
-
-:ref:`a_references` - Recommended Reading
-   This chapter explains how you organise your notes, and how the Tags and References system works.
-   This system lets you cross-link your documents in your project, and display these references in
-   the application interface.
-
-:ref:`a_manuscript` - Recommended Reading
-   This chapter explains how the **Manuscript Build** tool works, how you can control the way
-   chapter titles are formatted, and how scene and section breaks are handled.
-
-
-Additional Details & Technical Topics
-=====================================
-
-The Additional Details and the Technical Topics sections contain more in-depth information about
-how various bits of novelWriter works. This information is not essential to getting started using
-novelWriter.

docs/source/int_started.rst

@@ -1,180 +0,0 @@
-.. _a_started:
-
-**********************
-Setup and Installation
-**********************
-
-.. _Enchant: https://abiword.github.io/enchant/
-.. _GitHub: https://github.com/vkbo/novelWriter
-.. _Downloads page: https://download.novelwriter.io
-.. _PPA: https://launchpad.net/~vkbo/+archive/ubuntu/novelwriter
-.. _Pre-Release PPA: https://launchpad.net/~vkbo/+archive/ubuntu/novelwriter-pre
-.. _PyPi: https://pypi.org/project/novelWriter/
-.. _python.org: https://www.python.org/downloads/
-.. _Releases: https://github.com/vkbo/novelWriter/releases
-.. _AppImage: https://appimage.org/
-
-Ready-made packages and installers for novelWriter are available for all major platforms, including
-Linux, Windows and MacOS, from the `Downloads page`_. See below for install additional instructions
-for each platform.
-
-You can also install novelWriter from the Python Package Index (PyPi_). See :ref:`a_started_pip`.
-Installing from PyPi does not set up icon launchers, so you will either have to do this yourself,
-or start novelWriter from the command line.
-
-Spell checking in novelWriter is provided by a third party library called Enchant_. Generally, it
-should pull dictionaries from your operating system automatically. However, on Windows they must be
-installed manually. See :ref:`a_custom_dict` for more details.
-
-
-.. _a_started_windows:
-
-Installing on Windows
-=====================
-
-You can install novelWriter with both Python and library dependencies embedded using the Windows
-Installer (setup.exe) file from the `Downloads page`_, or from the Releases_ page on GitHub_.
-Installing it should be straightforward.
-
-If you have any issues, try uninstalling the previous version and making a fresh install. If you
-already had a version installed via a different method, you should uninstall that first as having
-multiple installations has been known to cause problems.
-
-.. note::
-   The novelWriter installer is not signed because Microsoft doesn't currently provide a way for
-   non-profit open source projects to properly sign their installers. The novelWriter project
-   doesn't have the funding to pay for commercial software signing certificates. You will therefore
-   see an additional warning about this when you download and run the installer.
-
-
-.. _a_started_linux:
-
-Installing on Linux
-===================
-
-A Debian package can be downloaded from the `Downloads page`_, or from the Releases_ page on
-GitHub_. This package should work on both Debian, Ubuntu and Linux Mint, at least.
-
-If you prefer, you can also add the novelWriter repository on Launchpad to your package manager.
-The Launchpad packages `are signed by the author <https://launchpad.net/~vkbo>`__.
-
-
-Ubuntu
-------
-
-You can add the Ubuntu PPA_ and install novelWriter with the following commands.
-
-.. code-block:: bash
-
-   sudo add-apt-repository ppa:vkbo/novelwriter
-   sudo apt update
-   sudo apt install novelwriter
-
-If you want the `Pre-Release PPA`_ instead, add the ``ppa:vkbo/novelwriter-pre`` repository.
-
-
-Debian and Mint
----------------
-
-Since this is a pure Python package, the Launchpad PPA can in principle also be used on Debian or
-Mint. However, the above command will fail to add the signing key, as it is Ubuntu-specific.
-
-Instead, run the following commands to add the repository and key:
-
-.. code-block:: bash
-
-   sudo gpg --no-default-keyring --keyring /usr/share/keyrings/novelwriter-ppa-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys F19F1FCE50043114
-   echo "deb [signed-by=/usr/share/keyrings/novelwriter-ppa-keyring.gpg] http://ppa.launchpad.net/vkbo/novelwriter/ubuntu noble main" | sudo tee /etc/apt/sources.list.d/novelwriter.list
-
-Then run the update and install commands as for Ubuntu:
-
-.. code-block:: bash
-
-   sudo apt update
-   sudo apt install novelwriter
-
-.. note::
-   You may need to use the Ubuntu 20.04 (focal) packages for Debian 11 or earlier. The newer Ubuntu
-   packages use a different compression algorithm that may not be supported.
-
-.. tip::
-   If you get an error message like ``gpg: failed to create temporary file`` when importing the key
-   from the Ubuntu keyserver, try creating the folder it fails on, and import the key again:
-
-   .. code-block:: bash
-
-      sudo mkdir /root/.gnupg/
-
-
-AppImage Releases
------------------
-
-For other Linux distros than the ones mentioned above, the primary option is AppImage_. These are
-completely standalone images for the app that include the necessary environment to run novelWriter.
-They can of course be run on any Linux distro, if you prefer this to native packages.
-
-.. note::
-   novelWriter generally doesn't support Python versions that have reached end of life. If your
-   Linux distro still uses older Python versions and novelWriter won't run, you may want to try the
-   AppImage instead.
-
-
-.. _a_started_macos:
-
-Installing on MacOS
-===================
-
-You can install novelWriter with both its Python and library dependencies embedded using the DMG
-application image file from the `Downloads page`_, or from the Releases_ page on GitHub_.
-Installing it should be straightforward.
-
-* Download the DMG file and open it. Then drag the novelWriter icon to the :guilabel:`Applications`
-  folder on the right. This will install it into your :guilabel:`Applications`.
-* The first time you try to launch it, it will say that the bundle cannot be verified, simply press
-  the :guilabel:`Open` button to add an exception.
-* If you are not presented with an :guilabel:`Open` button in the dialog, launch the application
-  again by right clicking on the application in Finder and selecting :guilabel:`Open` from the
-  context menu.
-
-The context menu can also be accessed by option-clicking if you have a one button mouse. This is
-done by holding down the option key on your keyboard and clicking on the application in Finder.
-
-.. note::
-   The novelWriter DMG is not signed because Apple doesn't currently provide a way for non-profit
-   open source projects to properly sign their installers. The novelWriter project doesn't have the
-   funding to pay for commercial software signing certificates.
-
-
-.. _a_started_pip:
-
-Installing from PyPi
-====================
-
-novelWriter is also available on the Python Package Index, or PyPi_. This install method works on
-all supported operating systems with a suitable Python environment.
-
-To install from PyPi you must first have the ``python`` and ``pip`` commands available on your
-system. You can download Python from `python.org`_. It is recommended that you install the latest
-version. If you are on Windows, also make sure to select the "Add Python to PATH" option during
-installation.
-
-To install novelWriter from PyPi, use the following command:
-
-.. code-block:: bash
-
-   pip install novelwriter
-
-To upgrade an existing installation, use:
-
-.. code-block:: bash
-
-   pip install --upgrade novelwriter
-
-When installing via pip, novelWriter can be launched from command line with:
-
-.. code-block:: bash
-
-   novelwriter
-
-Make sure the install location for pip is in your PATH variable. This is not always the case by
-default, and then you may get a "Not Found" error when running the ``novelwriter`` command.

docs/source/locales/authors_fr.conf

@@ -0,0 +1,2 @@
+# French translation authors, one name per line
+Jean-Michel Heras

docs/source/locales/fr/LC_MESSAGES/features/dialogue.po

@@ -0,0 +1,223 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 22:09+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/features/dialogue.rst:5
+msgid "Dialogue Highlighting"
+msgstr "Mise en évidence du dialogue"
+
+#: ../../source/features/dialogue.rst:7
+msgid ""
+"Dialogue recognition and colour highlighting is available both while "
+"you're writing and in generated manuscript documents."
+msgstr ""
+"La reconnaissance des dialogues et le surlignage des couleurs sont "
+"disponibles à la fois pendant que vous écrivez et dans les documents "
+"manuscrits générés."
+
+#: ../../source/features/dialogue.rst:10
+msgid ""
+"The default language settings in novelWriter are for English. That "
+"includes the dialogue highlighting settings. But many dialogue styles "
+"are supported. You can tune a number of settings to fit your language "
+"and style preferences in the \"Text Highlighting\" section in "
+"**Preferences**. You can mix and match these settings."
+msgstr ""
+"Les paramètres linguistiques par défaut de novelWriter sont ceux de "
+"l'anglais. Cela inclut les paramètres de mise en évidence des dialogues. "
+"Mais de nombreux styles de dialogue sont pris en charge. Vous pouvez "
+"ajuster un certain nombre de paramètres en fonction de vos préférences "
+"linguistiques et stylistiques dans la section « Surlignage du texte » "
+"des **Préférences**. Vous pouvez combiner ces paramètres.\n"
+"\n"
+"Traduit avec DeepL.com (version gratuite)"
+
+#: ../../source/features/dialogue.rst:17
+msgid "The **Text Highlighting** section of **Preferences**."
+msgstr "La section **Mise en évidence du texte** des **Préférences**."
+
+#: ../../source/features/dialogue.rst:21
+msgid "Quoted Dialogue"
+msgstr "Dialogue entre guillemets"
+
+#: ../../source/features/dialogue.rst:23
+msgid ""
+"By default, dialogue highlighting is enabled for the double quote "
+"symbols you have defined in the **Quotation Style** section of "
+"**Preferences**."
+msgstr ""
+"Par défaut, la mise en évidence du dialogue est activée pour les "
+"symboles de guillemets doubles que vous avez définis dans la section "
+"**Style de guillemets** des **Préférences**."
+
+#: ../../source/features/dialogue.rst:28
+msgid "The **Quotation Style** section of **Preferences**."
+msgstr "La section **Style de guillemets** des **Préférences**."
+
+#: ../../source/features/dialogue.rst:30
+msgid ""
+"You can change which quote symbols are highlighted by selecting one of "
+"\"None\", \"Single\", \"Double\", or \"Both\" from the \"Highlight "
+"dialogue\" setting under **Text Highlighting**."
+msgstr ""
+"Vous pouvez modifier les symboles de guillemets mis en évidence en "
+"sélectionnant « Aucun », « Simple », « Double » ou « Les deux » dans le "
+"paramètre « Mettre les dialogues en évidence » sous **Surlignage du "
+"texte**."
+
+#: ../../source/features/dialogue.rst:33
+msgid ""
+"You can also enable or disable the \"Allow open-ended dialogue\" setting "
+"to allow for the style where multi-paragraph dialogue is not closed "
+"until the last paragraph."
+msgstr ""
+"Vous pouvez également activer ou désactiver le paramètre « Autoriser les "
+"dialogues ouverts » pour autoriser le style dans lequel les dialogues à "
+"plusieurs paragraphes ne sont pas clos avant le dernier paragraphe."
+
+#: ../../source/features/dialogue.rst:36
+msgid "Limitations"
+msgstr "Restrictions"
+
+#: ../../source/features/dialogue.rst:38
+msgid ""
+"Dialogue highlighting for single quotes is difficult to process when the "
+"same single quote symbol is also used for apostrophes. There isn't a "
+"good solution to this. Your best option in the cases where the "
+"highlighting is wrong is to insert an alternative apostrophe symbol "
+"instead. See :ref:`docs_more_typographical_symbols_apostrophe` for more "
+"details."
+msgstr ""
+"La mise en évidence du dialogue pour les guillemets simples est "
+"difficile à traiter lorsque le même symbole de guillemet simple est "
+"également utilisé pour les apostrophes. Il n'existe pas de bonne "
+"solution à ce problème. Votre meilleure option dans les cas où la mise "
+"en évidence est erronée est d'insérer un symbole d'apostrophe alternatif "
+"à la place. Voir :ref:`docs_more_typographical_symbols_apostrophe` pour "
+"plus de détails."
+
+#: ../../source/features/dialogue.rst:45
+msgid "Alternative Dialogue"
+msgstr "Dialogue alternatif"
+
+#: ../../source/features/dialogue.rst:47
+msgid ""
+"You can use the \"Alternative dialogue symbols\" setting for custom "
+"dialogue wrapper symbols. These are highlighted in a different colour "
+"than regular dialogue."
+msgstr ""
+"Vous pouvez utiliser le paramètre « Symboles de dialogue alternatifs » "
+"pour les symboles de dialogue personnalisés. Ceux-ci sont mis en "
+"évidence dans une couleur différente de celle des dialogues normaux."
+
+#: ../../source/features/dialogue.rst:50
+msgid ""
+"The intended use case here is if you use an alternative style to "
+"distinguish a different style of communication. The feature idea came "
+"from a science fiction series where mind-to-mind communication used a "
+"different quotation style."
+msgstr ""
+"Le cas d'utilisation prévu ici est celui où vous utilisez un style "
+"alternatif pour distinguer un style de communication différent. L'idée "
+"est venue d'une série de science-fiction dans laquelle la communication "
+"d'esprit à esprit utilisait un style de citation différent."
+
+#: ../../source/features/dialogue.rst:56
+msgid "Dialogue Line Symbols"
+msgstr "Symboles des lignes de dialogue"
+
+#: ../../source/features/dialogue.rst:58
+msgid ""
+"In some languages, a single symbol at the start of a paragraph can "
+"indicate that the whole paragraph is dialogue. For instance, this symbol "
+"can be a short dash (en dash)."
+msgstr ""
+"Dans certaines langues, un seul symbole au début d'un paragraphe peut "
+"indiquer que tout le paragraphe est un dialogue. Par exemple, ce symbole "
+"peut être un tiret demi-cadratin."
+
+#: ../../source/features/dialogue.rst:63
+msgid "An example of dialogue starting with a short dash."
+msgstr "Exemple de dialogue commençant par un tiret demi-cadratin."
+
+#: ../../source/features/dialogue.rst:65
+msgid ""
+"You can enable this feature by adding the symbols to the \"Dialogue line "
+"symbols\" setting. Multiple symbols are allowed."
+msgstr ""
+"Vous pouvez activer cette fonction en ajoutant les symboles au paramètre "
+"« Symboles de la ligne de dialogue ». Plusieurs symboles sont autorisés."
+
+#: ../../source/features/dialogue.rst:70
+msgid "Dialogue with Narrator Break"
+msgstr "Dialogue avec incise"
+
+#: ../../source/features/dialogue.rst:72
+msgid ""
+"The dialogue symbol setting will not detect if the dialogue ends in the "
+"paragraph. In some styles there is no way to actually indicate the "
+"switch from dialogue to narration; in others there are. These a narrator "
+"break symbols are usually dashes. You can select one of the supported "
+"dash symbols for narrator breaks. These can be used with any of the "
+"above dialogue recognition settings."
+msgstr ""
+"Le réglage du symbole de dialogue ne détecte pas si le dialogue se "
+"termine dans le paragraphe. Dans certains styles, il n'y a aucun moyen "
+"d'indiquer le passage du dialogue à la narration ; dans d'autres, il y "
+"en a un. Ces symboles de rupture avec le narrateur sont généralement des "
+"tirets. Vous pouvez sélectionner l'un des symboles de tirets pris en "
+"charge pour les ruptures de narration. Ces symboles peuvent être "
+"utilisés avec n'importe lequel des paramètres de reconnaissance de "
+"dialogue ci-dessus."
+
+#: ../../source/features/dialogue.rst:79
+msgid ""
+"An example of dialogue starting with a short dash and a long dash "
+"narrator break."
+msgstr ""
+"Exemple de dialogue commençant par un tiret demi-cadratin, une incise "
+"par un tiret cadratin."
+
+#: ../../source/features/dialogue.rst:83
+msgid "Alternating Dialogue and Narration"
+msgstr "Dialogue et narration alternés"
+
+#: ../../source/features/dialogue.rst:85
+msgid ""
+"The alternating dialogue and narration style is supported with the "
+"\"Alternating dialogue/narration symbol\" setting. It can be set to one "
+"of the supported dashes. This style will switch into dialogue mode when "
+"it first encounters the selected dash in a paragraph, and switch back "
+"out when it sees the next one, and so forth."
+msgstr ""
+"Le style de dialogue et de narration alternés est pris en charge par le "
+"paramètre « Symbole de dialogue/narration alternés ». Il peut être "
+"défini sur l'un des tirets pris en charge. Ce style passe en mode "
+"dialogue lorsqu'il rencontre pour la première fois le tiret sélectionné "
+"dans un paragraphe, et revient en mode dialogue lorsqu'il rencontre le "
+"tiret suivant, et ainsi de suite."
+
+#: ../../source/features/dialogue.rst:92
+msgid "An example of alternating dialogue and narration using a long dash."
+msgstr ""
+"Exemple d'alternance de dialogue et de narration à l'aide d'un tiret "
+"cadratin."

docs/source/locales/fr/LC_MESSAGES/features/shortcuts.po

@@ -0,0 +1,978 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 22:50+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/features/shortcuts.rst:5
+msgid "Keyboard Shortcuts"
+msgstr "Raccourcis clavier"
+
+#: ../../source/features/shortcuts.rst:7
+msgid ""
+"Most features in novelWriter are available as keyboard shortcuts. This "
+"is a reference list of those shortcuts. Most of them are also listed in "
+"the application's user interface."
+msgstr ""
+"La plupart des fonctionnalités de novelWriter sont disponibles sous "
+"forme de raccourcis clavier. Il s'agit d'une liste de référence de ces "
+"raccourcis. La plupart d'entre eux sont également listés dans "
+"l'interface utilisateur de l'application."
+
+#: ../../source/features/shortcuts.rst:12
+msgid "On MacOS, replace :kbd:`Ctrl` with :kbd:`Cmd`."
+msgstr "Sous MacOS, remplacez :kbd:`Ctrl` par :kbd:`Cmd`."
+
+#: ../../source/features/shortcuts.rst:16
+msgid "Main Window Shortcuts"
+msgstr "Raccourcis de la fenêtre principale"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Shortcut"
+msgstr "Raccourci"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Description"
+msgstr "Description"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F1`"
+msgstr ":kbd:`F1`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the online user manual"
+msgstr "Ouvrir le manuel d'utilisation en ligne"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F5`"
+msgstr ":kbd:`F5`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Build Manuscript** tool"
+msgstr "Ouvrir l'outil **Compiler le manuscrit**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F6`"
+msgstr ":kbd:`F6`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Writing Statistics** tool"
+msgstr "Ouvrir l'outil **Statistiques d'écriture**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F8`"
+msgstr ":kbd:`F8`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Toggle **Focus Mode**"
+msgstr "Basculer **Mode sans distraction**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F9`"
+msgstr ":kbd:`F9`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Re-build the project's index"
+msgstr "Reconstruire l'index du projet"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F11`"
+msgstr ":kbd:`F11`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Toggle full screen mode"
+msgstr "Basculer en mode plein écran"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+,`"
+msgstr ":kbd:`Ctrl+,`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Preferences** dialog"
+msgstr "Ouvrir la boîte de dialogue **Préférences**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+E`"
+msgstr ":kbd:`Ctrl+E`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Switch or toggle focus for the editor or viewer"
+msgstr ""
+"Changement ou basculement du focus de l'éditeur ou du visualisateur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+T`"
+msgstr ":kbd:`Ctrl+T`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Switch or toggle focus for the project tree or novel view"
+msgstr ""
+"Changement de focalisation de l'arborescence du projet ou de la vue du "
+"roman"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Q`"
+msgstr ":kbd:`Ctrl+Q`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Exit novelWriter"
+msgstr "Quitter novelWriter"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+,`"
+msgstr ":kbd:`Ctrl+Maj+,`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Project Settings** dialog"
+msgstr "Ouvrir la boîte de dialogue **Paramètres du projet**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+O`"
+msgstr ":kbd:`Ctrl+Maj+O`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the Welcome dialog to open or create a project"
+msgstr ""
+"Ouvrir la boîte de dialogue de bienvenue pour ouvrir ou créer un projet"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+S`"
+msgstr ":kbd:`Ctrl+Maj+S`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Save the current project"
+msgstr "Enregistrer le projet en cours"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+T`"
+msgstr ":kbd:`Ctrl+Maj+T`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Switch focus to the outline view"
+msgstr "Basculer vers la vue d'ensemble"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+W`"
+msgstr ":kbd:`Ctrl+Maj+W`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Close the current project"
+msgstr "Fermer le projet en cours"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Shift+F1`"
+msgstr ":kbd:`Maj+F1`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the local user manual (PDF) if it is available"
+msgstr "Ouvrir le manuel d'utilisation local (PDF) s'il est disponible"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Shift+F6`"
+msgstr ":kbd:`Maj+F6`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Project Details** dialog"
+msgstr "Ouvrir la boîte de dialogue **Détails du projet**"
+
+#: ../../source/features/shortcuts.rst:41
+msgid "Project Tree Shortcuts"
+msgstr "Raccourcis de l'arborescence du projet"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F2`"
+msgstr ":kbd:`F2`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Edit the label of the selected item"
+msgstr "Modifier le libellé de l'élément sélectionné"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Return`"
+msgstr ":kbd:`Retour`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the selected document in the editor"
+msgstr "Ouvrir le document sélectionné dans l'éditeur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Alt+Up`"
+msgstr ":kbd:`Alt+Haut`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Jump or go to the previous item at same level in the tree"
+msgstr ""
+"Sauter ou aller à l'élément précédent au même niveau dans 'l'arborescence"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Alt+Down`"
+msgstr ":kbd:`Alt+Bas`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Jump or go to the next item at same level in the tree"
+msgstr ""
+"Sauter ou aller à l'élément suivant au même niveau dans l'arborescence"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Alt+Left`"
+msgstr ":kbd:`Alt+Gauche`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Jump to the parent item in the tree"
+msgstr "Sauter à l'élément parent dans l'arborescence"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Alt+Right`"
+msgstr ":kbd:`Alt+Droite`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Jump to the first child item in the project tree"
+msgstr "Sauter au premier élément enfant dans l'arborescence du projet"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+.`"
+msgstr ":kbd:`Ctrl+.`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the context menu on the selected item"
+msgstr "Ouvrir le menu contextuel de l'élément sélectionné"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+L`"
+msgstr ":kbd:`Ctrl+L`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Quick Links** menu"
+msgstr "Ouvrir le menu **Liens rapides**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+N`"
+msgstr ":kbd:`Ctrl+N`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the **Create New Item** menu"
+msgstr "Ouvrir le menu **Créer un nouvel élément**"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+O`"
+msgstr ":kbd:`Ctrl+O`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+R`"
+msgstr ":kbd:`Ctrl+R`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the selected document in the viewer"
+msgstr "Ouvrir le document sélectionné dans le visualisateur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Up`"
+msgstr ":kbd:`Ctrl+Haut`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Move selected item one step up in the tree"
+msgstr "Déplacer l'élément sélectionné d'un cran dans l'arborescence"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Down`"
+msgstr ":kbd:`Ctrl+Bas`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Move selected item one step down in the tree"
+msgstr "Déplacer l'élément sélectionné d'un cran dans l'arborescence"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+Del`"
+msgstr ":kbd:`Ctrl+Maj+Suppr`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Move the selected item to Trash"
+msgstr "Déplacer l'élément sélectionné vers la corbeille"
+
+#: ../../source/features/shortcuts.rst:63
+msgid "Document Editor Shortcuts"
+msgstr "Raccourcis de l'éditeur de documents"
+
+#: ../../source/features/shortcuts.rst:67
+msgid "Text Search Shortcuts"
+msgstr "Raccourcis de recherche de texte"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F3`"
+msgstr ":kbd:`F3`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Find the next occurrence of the search word"
+msgstr "Trouver la prochaine occurrence du mot recherché"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+F`"
+msgstr ":kbd:`Ctrl+F`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open search and look for the selected word"
+msgstr "Ouvrir la recherche et rechercher le mot sélectionné"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+G`"
+msgstr ":kbd:`Ctrl+G`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+H`"
+msgstr ":kbd:`Ctrl+H`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open replace and look for the selected word (Mac :kbd:`Cmd+=`)"
+msgstr ""
+"Ouvrir remplacer et rechercher le mot sélectionné (Mac :kbd:`Cmd+=`)"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+1`"
+msgstr ":kbd:`Ctrl+Maj+1`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Replace selected occurrence, and move to the next"
+msgstr "Remplacer l'occurrence sélectionnée et passer à la suivante"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+G`"
+msgstr ":kbd:`Ctrl+Maj+G`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Find the previous occurrence of the search word"
+msgstr "Trouver l'occurrence précédente du mot recherché"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+F`"
+msgstr ":kbd:`Ctrl+Maj+F`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open project search and look for the selected word"
+msgstr "Ouvrir la recherche de projet et recherchez le mot sélectionné"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Shift+F3`"
+msgstr ":kbd:`Maj+F3`"
+
+#: ../../source/features/shortcuts.rst:83
+msgid "Text Formatting Shortcuts"
+msgstr "Raccourcis de mise en forme du texte"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+'`"
+msgstr ":kbd:`Ctrl+'`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Wrap selected text, or word under cursor, in single quotes"
+msgstr ""
+"Mettre le texte sélectionné, ou le mot sous le curseur, entre guillemets "
+"simples"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+\"`"
+msgstr ":kbd:`Ctrl+\"`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Wrap selected text, or word under cursor, in double quotes"
+msgstr ""
+"Mettre le texte sélectionné, ou le mot sous le curseur, entre guillemets"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+/`"
+msgstr ":kbd:`Ctrl+/`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Toggle comment format for block or selected text"
+msgstr ""
+"Modifier le format des commentaires pour le bloc ou le texte sélectionné"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+0`"
+msgstr ":kbd:`Ctrl+0`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Remove format for block or selected text"
+msgstr "Supprimer le format d'un bloc ou d'un texte sélectionné"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+1`"
+msgstr ":kbd:`Ctrl+1`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block format to heading level 1"
+msgstr "Modifier le format du bloc au niveau de titre 1"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+2`"
+msgstr ":kbd:`Ctrl+2`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block format to heading level 2"
+msgstr "Modifier le format du bloc en titre de niveau 2"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+3`"
+msgstr ":kbd:`Ctrl+3`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block format to heading level 3"
+msgstr "Modifier le format du bloc en titre de niveau 3"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+4`"
+msgstr ":kbd:`Ctrl+4`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block format to heading level 4"
+msgstr "Modifier le format du bloc en titre de niveau 4"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+5`"
+msgstr ":kbd:`Ctrl+5`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block alignment to left-aligned"
+msgstr "Aligner le bloc à gauche"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+6`"
+msgstr ":kbd:`Ctrl+6`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block alignment to centred"
+msgstr "Aligner le bloc au centre"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+7`"
+msgstr ":kbd:`Ctrl+7`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Change block alignment to right-aligned"
+msgstr "Aligner le bloc à droite"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+8`"
+msgstr ":kbd:`Ctrl+8`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Add a left margin to the block"
+msgstr "Ajouter une marge gauche au bloc"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+9`"
+msgstr ":kbd:`Ctrl+9`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Add a right margin to the block"
+msgstr "Ajouter une marge droite au bloc"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+B`"
+msgstr ":kbd:`Ctrl+B`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Format selected text, or word under cursor, with bold"
+msgstr "Formater le texte sélectionné, ou le mot sous le curseur, en gras"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+D`"
+msgstr ":kbd:`Ctrl+D`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Format selected text, or word under cursor, with strike through"
+msgstr ""
+"Formater le texte sélectionné, ou le mot sous le curseur, en le barrant"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+I`"
+msgstr ":kbd:`Ctrl+I`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Format selected text, or word under cursor, with italic"
+msgstr ""
+"Formater le texte sélectionné, ou le mot sous le curseur, avec de "
+"l'italique"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+/`"
+msgstr ":kbd:`Ctrl+Maj+/`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+D`"
+msgstr ":kbd:`Ctrl+Maj+D`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Toggle ignored text format for block or selected text"
+msgstr ""
+"Basculer le format de texte ignoré pour le bloc ou le texte sélectionné"
+
+#: ../../source/features/shortcuts.rst:109
+msgid "Other Editor Shortcuts"
+msgstr "Autres raccourcis de l'éditeur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`F7`"
+msgstr ":kbd:`F7`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Re-run the spell checker on the document"
+msgstr "Ré-exécuter le correcteur orthographique sur le document"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the context menu at the current cursor location"
+msgstr "Ouvrir le menu contextuel à l'emplacement actuel du curseur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+A`"
+msgstr ":kbd:`Ctrl+A`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Select all text in the document"
+msgstr "Sélectionner tout le texte dans le document"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+C`"
+msgstr ":kbd:`Ctrl+C`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Copy selected text to clipboard"
+msgstr "Copier le texte sélectionné dans le presse-papiers"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`"
+msgstr ":kbd:`Ctrl+K`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ""
+"Activate the insert commands (see list in :ref:"
+"`docs_features_shortcuts_insert`)"
+msgstr ""
+"Activer les commandes d'insertion (voir la liste dans :ref:"
+"`docs_features_shortcuts_insert`)"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open or reload the current document in the viewer"
+msgstr "Ouvrir ou recharger le document en cours dans le visualisateur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+S`"
+msgstr ":kbd:`Ctrl+S`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Save the current document"
+msgstr "Enregistrer le document en cours"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+V`"
+msgstr ":kbd:`Ctrl+V`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Paste text from clipboard to cursor position"
+msgstr "Coller le texte du presse-papiers à la position du curseur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+W`"
+msgstr ":kbd:`Ctrl+W`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Close the current document"
+msgstr "Fermer le document en cours"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+X`"
+msgstr ":kbd:`Ctrl+X`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Cut selected text to clipboard"
+msgstr "Couper le texte sélectionné dans le presse-papiers"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Y`"
+msgstr ":kbd:`Ctrl+Y`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Redo latest undo"
+msgstr "Rétablir la dernière annulation"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Z`"
+msgstr ":kbd:`Ctrl+Z`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Undo latest changes"
+msgstr "Annuler les dernières modifications"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Backspace`"
+msgstr ":kbd:`Ctrl+Retour arrière`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Delete the word before the cursor"
+msgstr "Supprimer le mot précédant le curseur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Del`"
+msgstr ":kbd:`Ctrl+Suppr`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Delete the word after the cursor"
+msgstr "Supprimer le mot après le curseur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+F7`"
+msgstr ":kbd:`Ctrl+F7`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Toggle spell checking"
+msgstr "Vérifier l'orthographe"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Return`"
+msgstr ":kbd:`Ctrl+Retour`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Open the tag or reference under the cursor in the viewer"
+msgstr ""
+"Ouvrir la balise ou la référence sous le curseur dans le visualiseur"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+A`"
+msgstr ":kbd:`Ctrl+Maj+A`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Select all text in the current paragraph"
+msgstr "Sélectionner tout le texte du paragraphe en cours"
+
+#: ../../source/features/shortcuts.rst:136
+msgid "Insert Shortcuts"
+msgstr "Raccourcis d'insertion"
+
+#: ../../source/features/shortcuts.rst:138
+msgid ""
+"A set of insert features are also available through shortcuts, but they "
+"require a double combination of key sequences. The insert feature is "
+"activated with :kbd:`Ctrl+K`, followed by a key or key combination for "
+"the inserted content."
+msgstr ""
+"Un ensemble de fonctions d'insertion sont également disponibles par le "
+"biais de raccourcis, mais elles nécessitent une double combinaison de "
+"séquences de touches. La fonction d'insertion est activée avec :kbd:"
+"`Ctrl+K`, suivi d'une touche ou d'une combinaison de touches pour le "
+"contenu inséré."
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Space`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Espace`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a non-breaking space"
+msgstr "Insérer un espace insécable"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`_`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`_`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a long dash (em dash)"
+msgstr "Insérer un tiret long"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`.`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`.`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert an ellipsis"
+msgstr "Insérer un point de suspension"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`'`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`'`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a modifier apostrophe"
+msgstr "Insérer une apostrophe"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`*`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`*`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a list bullet"
+msgstr "Insérer une puce de liste"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`%`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`%`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a per mille symbol"
+msgstr "Insérer un symbole pour mille"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`~`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`~`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a figure dash (same width as a number)"
+msgstr "Insérer un tiret (de la même largeur qu'un chiffre)"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`−`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`−`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a short dash (en dash)"
+msgstr "Insérer un tiret court"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`1`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`1`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a left single quote"
+msgstr "Insérer un guillemet simple gauche"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`2`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`2`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a right single quote"
+msgstr "Insérer un guillemet simple à droite"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`3`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`3`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a left double quote"
+msgstr "Insérer un double guillemet gauche"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`4`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`4`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a right double quote"
+msgstr "Insérer un double guillemet droit"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`C`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`C`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@char`` keyword"
+msgstr "Insérer un mot-clé ``@char``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`E`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`E`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert an ``@entity`` keyword"
+msgstr "Insérer un mot-clé ``@entity``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`F`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`F`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@focus`` keyword"
+msgstr "Insérer un mot-clé ``@focus``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`G`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`G`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@tag`` keyword"
+msgstr "Insérer un mot-clé ``@tag``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`H`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`H`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a short description comment"
+msgstr "Insérer un bref commentaire de description"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`L`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`L`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@location`` keyword"
+msgstr "Insérer un mot-clé ``@location``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`M`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`M`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@mention`` keyword"
+msgstr "Insérer un mot-clé ``@mention``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`O`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`O`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert an ``@object`` keyword"
+msgstr "Insérer un mot-clé ``@object``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`P`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`P`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@plot`` keyword"
+msgstr "Insérer un mot-clé `@plot``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`S`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`S`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a synopsis comment"
+msgstr "Insérer un commentaire de synopsis"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`T`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`T`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@time`` keyword"
+msgstr "Insérer un mot-clé ``@time``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`V`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`V`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@pov`` keyword"
+msgstr "Insérer un mot-clé ``@pov``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`X`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`X`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a ``@custom`` keyword"
+msgstr "Insérer un mot-clé ``@custom``"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+Space`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+Espace`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a thin non-breaking space"
+msgstr "Insérer un espace fin insécable"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+_`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+_`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a horizontal bar (quotation dash)"
+msgstr "Insérer une barre horizontale"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+'`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+'`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a prime"
+msgstr "Insérer une prime"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+\"`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+\"`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a double prime"
+msgstr "Insérer une double prime"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+*`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+*`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a flower mark (alternative bullet)"
+msgstr "Insérer une fleur (puce alternative)"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+−`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+−`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a hyphen bullet (alternative bullet)"
+msgstr "Insérer une puce à tiret (puce alternative)"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+D`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+D`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a division sign"
+msgstr "Insérer un signe de division"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+O`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+O`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a degree symbol"
+msgstr "Insérer un symbole de degré"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+X`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+X`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a times sign"
+msgstr "Insert a times sign"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Shift+Space`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Maj+Espace`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Insert a thin space"
+msgstr "Insérer un espace fin"
+
+#: ../../source/features/shortcuts.rst:183
+msgid "Document Viewer Shortcuts"
+msgstr "Raccourcis de la fenêtre de visualisation des documents"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Move backward in the view history"
+msgstr "Reculer dans l'historique des vues"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Move forward in the view history"
+msgstr "Avancer dans l'historique des vues"
+
+#: ../../source/features/shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+R`"
+msgstr ":kbd:`Ctrl+Maj+R`"
+
+#: ../../source/features/shortcuts.rst:1
+msgid "Close the document viewer"
+msgstr "Fermer l'afficheur de documents"

docs/source/locales/fr/LC_MESSAGES/features/story_comments.po

@@ -0,0 +1,221 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 22:28+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/features/story_comments.rst:5
+msgid "Story Comments"
+msgstr "Commentaires sur l'histoire"
+
+#: ../../source/features/story_comments.rst:7
+msgid ""
+"A special set of comment styles allow for annotating your text with "
+"structure information. There are two styles of comments available. They "
+"are an extension to regular comments as described in :ref:"
+"`docs_usage_comments`."
+msgstr ""
+"Un ensemble spécial de styles de commentaires permet d'annoter votre "
+"texte avec des informations sur la structure. Deux styles de "
+"commentaires sont disponibles. Ils sont une extension des commentaires "
+"normaux tels que décrits dans :ref:`docs_usage_comments`."
+
+#: ../../source/features/story_comments.rst:15
+msgid "Story Structure Comments"
+msgstr "Commentaires sur la structure de l'histoire"
+
+#: ../../source/features/story_comments.rst:17
+msgid ""
+"You can annotate story structure by using the ``%Story`` style of "
+"comment. To use the feature, make the first word of a comment ``Story``, "
+"followed by a period, a structure term, a colon, a space and the text "
+"for that term."
+msgstr ""
+"Vous pouvez annoter la structure de l'histoire en utilisant le style de "
+"commentaire ``%Story``. Pour utiliser cette fonctionnalité, le premier "
+"mot du commentaire doit être ``Story``, suivi d'un point, d'un terme de "
+"structure, de deux points, d'un espace et du texte correspondant à ce "
+"terme."
+
+#: ../../source/features/story_comments.rst:23
+#: ../../source/features/story_comments.rst:88
+msgid "Usage"
+msgstr "Utilisation"
+
+#: ../../source/features/story_comments.rst:25
+msgid ""
+"The story term can be anything that you want to track in the manuscript. "
+"This construct is intended to make it easier to extract metadata from a "
+"work to perform a structural analysis of the story."
+msgstr ""
+"Le terme de l'histoire peut être n'importe quoi que vous voulez suivre "
+"dans le manuscrit. Cette construction est destinée à faciliter "
+"l'extraction des métadonnées d'une œuvre afin d'effectuer une analyse "
+"structurelle de l'histoire."
+
+#: ../../source/features/story_comments.rst:28
+msgid ""
+"There are probably as many ways to examine story structure as there are "
+"authors and editors combined. For this reason the story tag is flexible. "
+"You can use any terms you want and track any aspect of the story that "
+"serves your purposes."
+msgstr ""
+"Il y a probablement autant de façons d'examiner la structure d'une "
+"histoire qu'il y a d'auteurs et d'éditeurs réunis. C'est la raison pour "
+"laquelle l'étiquette « histoire » est flexible. Vous pouvez utiliser les "
+"termes de votre choix et suivre tous les aspects de l'histoire qui vous "
+"intéressent."
+
+#: ../../source/features/story_comments.rst:32
+msgid ""
+"An example method has been advanced by Shawn Coyne in *The Story Grid*. "
+"This method asserts that a story is composed of \"beats\", and that each "
+"beat has an inciting incident, a complication, a crisis, and a "
+"resolution. One might capture these elements of a beat where a character "
+"overcomes their fear of giving a speech as:"
+msgstr ""
+"Un exemple de méthode a été proposé par Shawn Coyne dans *The Story "
+"Grid*. Cette méthode affirme qu'une histoire est composée de « temps » "
+"et que chaque temps comporte un incident déclencheur, une complication, "
+"une crise et une résolution. On pourrait saisir les éléments d'un temps "
+"où un personnage surmonte sa peur de faire un discours comme suit :"
+
+#: ../../source/features/story_comments.rst:37
+#: ../../source/features/story_comments.rst:94
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/features/story_comments.rst:50
+msgid ""
+"Other analytical models propose tracking a scene's pace, how it affects "
+"the mood of the story, or which element(s) of the story's genre are "
+"being satisfied. An author can use this mechanism to track any element "
+"of a scene. Some examples include time of day, how much time passes in "
+"the scene, or even the physical form of a shape-shifting character. If a "
+"story involves magic, one could track which wand a main character has in "
+"hand. It's up to tha author."
+msgstr ""
+"D'autres modèles analytiques proposent de suivre le rythme d'une scène, "
+"la façon dont il affecte l'ambiance de l'histoire ou les éléments du "
+"genre de l'histoire qui sont satisfaits. Un auteur peut utiliser ce "
+"mécanisme pour suivre n'importe quel élément d'une scène. Il peut "
+"s'agir, par exemple, de l'heure, du temps qui s'écoule dans la scène ou "
+"même de la forme physique d'un personnage qui change de forme. Si "
+"l'histoire fait appel à la magie, il est possible de savoir quelle "
+"baguette le personnage principal tient en main. C'est à l'auteur de "
+"décider."
+
+#: ../../source/features/story_comments.rst:56
+msgid ""
+"When the story and other scene metadata is extracted into a tabular "
+"form, it is possible to get a comprehensive overview of the story and to "
+"identify possible issues. For example, so many fast-paced scenes without "
+"a break that readers might become fatigued or over-stimulated."
+msgstr ""
+"Lorsque les métadonnées de l'histoire et d'autres scènes sont extraites "
+"sous forme de tableau, il est possible d'obtenir une vue d'ensemble de "
+"l'histoire et d'identifier les problèmes éventuels. Par exemple, un si "
+"grand nombre de scènes au rythme rapide, sans pause, que les lecteurs "
+"risquent de se fatiguer ou d'être trop stimulés."
+
+#: ../../source/features/story_comments.rst:62
+#: ../../source/features/story_comments.rst:106
+msgid "Output"
+msgstr "Production"
+
+#: ../../source/features/story_comments.rst:64
+msgid ""
+"The story structure comments can be included in the manuscript, and are "
+"formatted similarly to the synopsis comments:"
+msgstr ""
+"Les commentaires sur la structure de l'histoire peuvent être inclus dans "
+"le manuscrit et sont formatés de la même manière que les commentaires "
+"sur le synopsis :"
+
+#: ../../source/features/story_comments.rst:69
+msgid "A set of story structure comments as shown in the Manuscript tool."
+msgstr ""
+"Une série de commentaires sur la structure de l'histoire, tels qu'ils "
+"apparaissent dans l'outil Manuscrit."
+
+#: ../../source/features/story_comments.rst:71
+msgid ""
+"When you export your project data from the Outline View, all story "
+"structure terms are added as columns to the exported file, which can "
+"then be opened in the spread sheet software of your choice."
+msgstr ""
+"Lorsque vous exportez les données de votre projet à partir de la vue en "
+"plan, tous les termes de la structure du récit sont ajoutés en tant que "
+"colonnes au fichier exporté, qui peut ensuite être ouvert dans le "
+"logiciel de feuille de calcul de votre choix."
+
+#: ../../source/features/story_comments.rst:76
+msgid "Story Notes"
+msgstr "Notes sur l'histoire"
+
+#: ../../source/features/story_comments.rst:78
+msgid ""
+"Story notes are similar to story structure comments, but have no "
+"predefined meaning. Essentially they are a generalisation of the story "
+"structure comment, and the only point of having this additional format "
+"is to allow you do filter them in and out of your manuscript "
+"independently."
+msgstr ""
+"Les notes de récit sont similaires aux commentaires de structure de "
+"récit, mais n'ont pas de signification prédéfinie. Il s'agit "
+"essentiellement d'une généralisation du commentaire de structure, et le "
+"seul intérêt de ce format supplémentaire est de vous permettre de les "
+"filtrer dans et hors de votre manuscrit de manière indépendante."
+
+#: ../../source/features/story_comments.rst:82
+msgid ""
+"You can annotate story notes by using the ``%Note`` style of comment. To "
+"use the feature, make the first word of a comment ``Note``, followed by "
+"a period, a term, a colon, a space and the text for the note."
+msgstr ""
+"Vous pouvez annoter les notes d'articles en utilisant le style de "
+"commentaire ``%Note``. Pour utiliser cette fonctionnalité, le premier "
+"mot du commentaire doit être « Note », suivi d'un point, d'un terme, de "
+"deux points, d'un espace et du texte de la note."
+
+#: ../../source/features/story_comments.rst:90
+msgid ""
+"These notes are free form, but one intended use case is to add "
+"consistency annotations to your text to remind yourself where you have "
+"described something that must be checked against other parts of your "
+"text later on."
+msgstr ""
+"Ces notes sont libres, mais l'une des utilisations prévues est d'ajouter "
+"des annotations de cohérence à votre texte pour vous rappeler où vous "
+"avez décrit quelque chose qui doit être vérifié ultérieurement par "
+"rapport à d'autres parties de votre texte."
+
+#: ../../source/features/story_comments.rst:108
+msgid ""
+"Story notes are included in the manuscript in exactly the same way story "
+"structure comments are, but has a separate inclusion setting in the "
+"build settings. They are also included in CSV exports from the **Outline "
+"View**."
+msgstr ""
+"Les notes de récit sont incluses dans le manuscrit de la même manière "
+"que les commentaires sur la structure du récit, mais elles ont un "
+"paramètre d'inclusion distinct dans les paramètres de construction. "
+"Elles sont également incluses dans les exportations CSV à partir de la "
+"**Vue d'ensemble**."

docs/source/locales/fr/LC_MESSAGES/index.po

@@ -0,0 +1,121 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-27 20:56+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/index.rst:32
+msgid "More Documents"
+msgstr "Plus d'informations"
+
+#: ../../source/index.rst:38
+msgid "Getting Started"
+msgstr "Pour commencer"
+
+#: ../../source/index.rst:53
+msgid "The User Interface"
+msgstr "Interface utilisateur"
+
+#: ../../source/index.rst:64
+msgid "Other Features"
+msgstr "Autres fonctionnalités"
+
+#: ../../source/index.rst:72
+msgid "In-Depth Topics"
+msgstr "En détail"
+
+#: ../../source/index.rst:82
+msgid "Technical Topics"
+msgstr "Rubriques techniques"
+
+#: ../../source/index.rst:3
+msgid "User Guide"
+msgstr "Guide d'utilisation"
+
+#: ../../source/index.rst:5
+msgid "**Release Version:** |release|"
+msgstr "**Version :** |release|"
+
+#: ../../source/index.rst:6
+msgid "**Updated:** |today|"
+msgstr "**Mise à jour :** |today|"
+
+#: ../../source/index.rst:8
+msgid ""
+"novelWriter is an open source plain text editor designed for writing "
+"novels assembled from individual text documents. It uses a minimal "
+"formatting syntax inspired by Markdown, and adds a meta data syntax for "
+"comments, synopsis, and cross-referencing. It is designed to be a simple "
+"text editor that allows for easy organisation of text and notes, using "
+"human readable text files as storage for robustness."
+msgstr ""
+"novelWriter est un éditeur de texte brut open source conçu pour écrire "
+"des romans assemblés à partir de documents texte individuels. Il utilise "
+"une syntaxe de formatage minimale inspirée de Markdown, et ajoute une "
+"syntaxe de métadonnées pour les commentaires, les synopsis et les "
+"références croisées. Il est conçu pour être un éditeur de texte simple "
+"qui permet d'organiser facilement le texte et les notes, en utilisant des "
+"fichiers texte lisibles par l'homme comme stockage pour plus de "
+"robustesse."
+
+#: ../../source/index.rst:19
+msgid "**Useful Links**"
+msgstr "**Liens utiles**"
+
+#: ../../source/index.rst:21
+msgid "Website: https://novelwriter.io"
+msgstr "Site web : https://novelwriter.io"
+
+#: ../../source/index.rst:22
+msgid "Documentation: https://docs.novelwriter.io"
+msgstr "Documentation: https://docs.novelwriter.io"
+
+#: ../../source/index.rst:23
+msgid "Public Releases: https://releases.novelwriter.io"
+msgstr "Public Releases: https://releases.novelwriter.io"
+
+#: ../../source/index.rst:24
+msgid "Internationalisation: https://crowdin.com/project/novelwriter"
+msgstr "Internationalisation: https://crowdin.com/project/novelwriter"
+
+#: ../../source/index.rst:25
+msgid "Source Code: https://github.com/vkbo/novelWriter"
+msgstr "Code source : https://github.com/vkbo/novelWriter"
+
+#: ../../source/index.rst:26
+msgid "Source Releases: https://github.com/vkbo/novelWriter/releases"
+msgstr "Source Releases: https://github.com/vkbo/novelWriter/releases"
+
+#: ../../source/index.rst:27
+msgid "Issue Tracker: https://github.com/vkbo/novelWriter/issues"
+msgstr "Issue Tracker: https://github.com/vkbo/novelWriter/issues"
+
+#: ../../source/index.rst:28
+msgid "Feature Discussions: https://github.com/vkbo/novelWriter/discussions"
+msgstr ""
+"Feature Discussions: https://github.com/vkbo/novelWriter/discussions"
+
+#: ../../source/index.rst:29
+msgid "PyPi Project: https://pypi.org/project/novelWriter"
+msgstr "PyPi Project: https://pypi.org/project/novelWriter"
+
+#: ../../source/index.rst:30
+msgid "Social Media: https://fosstodon.org/@novelwriter"
+msgstr "Social Media: https://fosstodon.org/@novelwriter"

docs/source/locales/fr/LC_MESSAGES/more/counting.po

@@ -0,0 +1,321 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 23:00+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/more/counting.rst:5
+msgid "Word and Text Counts"
+msgstr "Décompte des mots et des textes"
+
+#: ../../source/more/counting.rst:7
+msgid ""
+"This is an overview of how words and other counts of your text are performed. "
+"The counting rules should be relatively standard, and are comparable to Libre "
+"Office Writer rules."
+msgstr ""
+"Il s'agit d'une vue d'ensemble de la manière dont les mots et autres comptages "
+"de votre texte sont effectués. Les règles de comptage devraient être "
+"relativement standard, et sont comparables aux règles de Libre Office Writer."
+
+#: ../../source/more/counting.rst:10
+msgid ""
+"The counts provided in the app on the raw text are meant to be approximate. For "
+"more accurate counts, you need to build your manuscript in the **Manuscript "
+"Tool** and check the counts on the generated preview."
+msgstr ""
+"Les décomptes fournis dans l'application sur le texte brut sont approximatifs. "
+"Pour des décomptes plus précis, vous devez compiler votre manuscrit avec "
+"**Compiler le manuscrit** et vérifier les décomptes sur l'aperçu généré."
+
+#: ../../source/more/counting.rst:16
+msgid "Text Word Counts and Stats"
+msgstr "Décompte des mots du texte et statistiques"
+
+#: ../../source/more/counting.rst:18
+msgid ""
+"These are the rules for the main counts available for for each document in a "
+"project."
+msgstr ""
+"Il s'agit des règles relatives aux principaux décomptes disponibles pour chaque "
+"document d'un projet."
+
+#: ../../source/more/counting.rst:20
+msgid "For all counts, the following rules apply."
+msgstr "Pour tous les décomptes, les règles suivantes s'appliquent."
+
+#: ../../source/more/counting.rst:22 ../../source/more/counting.rst:56
+msgid "Short (–) and long (—) dashes are considered word separators."
+msgstr ""
+"Les tirets demi-cadratin (–) et cadratin (—) sont considérés comme des "
+"séparateurs de mots."
+
+#: ../../source/more/counting.rst:23
+msgid "Any line starting with ``%`` or ``@`` is ignored."
+msgstr "Toute ligne commençant par ``%`` ou ``@`` est ignorée."
+
+#: ../../source/more/counting.rst:24
+msgid "Trailing white spaces are ignored, including line breaks."
+msgstr ""
+"Les espaces blancs de fin de ligne sont ignorés, y compris les sauts de ligne."
+
+#: ../../source/more/counting.rst:25
+msgid "Leading ``>`` and trailing ``<`` are ignored with any spaces next to them."
+msgstr ""
+"Les ``>`` de début et les ``<`` de fin sont ignorés, de même que les espaces "
+"qui les accompagnent."
+
+#: ../../source/more/counting.rst:26
+msgid ""
+"Valid shortcodes and other commands wrapped in brackets ``[]`` are ignored."
+msgstr ""
+"Les shortcodes valides et les autres commandes entre crochets ``[]`` sont "
+"ignorés."
+
+#: ../../source/more/counting.rst:27
+msgid "In-line Markdown syntax in text paragraphs is treated as part of the text."
+msgstr ""
+"La syntaxe Markdown en ligne dans les paragraphes de texte est traitée comme "
+"faisant partie du texte."
+
+#: ../../source/more/counting.rst:29
+msgid ""
+"After the above preparation of the text, the following counts are available."
+msgstr "Après la préparation du texte, les chiffres suivants sont disponibles."
+
+#: ../../source/more/counting.rst:31
+msgid "**Character Count**"
+msgstr "**Décompte des caractères**"
+
+#: ../../source/more/counting.rst:32
+msgid ""
+"The character count is the sum of characters per line, including leading and in-"
+"text white space characters, but excluding trailing white space characters. "
+"Shortcodes in the text are not included, but Markdown codes are. Only headings "
+"and text are counted."
+msgstr ""
+"Le nombre de caractères est la somme des caractères par ligne, y compris les "
+"caractères d'en-tête et les caractères d'espacement dans le texte, mais pas les "
+"caractères d'espacement de fin. Les Shortcodes dans le texte ne sont pas "
+"inclus, mais les codes Markdown le sont. Seuls les en-têtes et le texte sont "
+"pris en compte."
+
+#: ../../source/more/counting.rst:36
+msgid "**Word Count**"
+msgstr "**Décompte des mots**"
+
+#: ../../source/more/counting.rst:37
+msgid ""
+"The words count is the sum of blocks of continuous character per line separated "
+"by any number of white space characters or dashes. Only headings and text are "
+"counted."
+msgstr ""
+"Le nombre de mots est la somme des blocs de caractères continus par ligne, "
+"séparés par un nombre quelconque de caractères d'espacement ou de tirets. Seuls "
+"les titres et le texte sont comptés."
+
+#: ../../source/more/counting.rst:40
+msgid "**Paragraph Count**"
+msgstr "**Décompte des paragraphes**"
+
+#: ../../source/more/counting.rst:41
+msgid ""
+"The paragraph count is the number of text blocks separated by one or more empty "
+"line. A line consisting only of white spaces is considered empty."
+msgstr ""
+"Le nombre de paragraphes est le nombre de blocs de texte séparés par une ou "
+"plusieurs lignes vides. Une ligne constituée uniquement d'espaces blancs est "
+"considérée comme vide."
+
+#: ../../source/more/counting.rst:46
+msgid "Manuscript Counts"
+msgstr "Décompte du manuscrit"
+
+#: ../../source/more/counting.rst:48
+msgid ""
+"These are the rules for the counts available for a manuscript in the "
+"**Manuscript Tool**. The rules have been tuned to agree with LibreOffice "
+"Writer, but will vary slightly depending on the content of your text. "
+"LibreOffice Writer also counts the text in the page header, which the "
+"**Manuscript Tool** does not."
+msgstr ""
+"Voici les règles pour les décomptes disponibles pour un manuscrit dans l'outil "
+"**Outil Manuscrit**. Les règles ont été ajustées pour correspondre à "
+"LibreOffice Writer, mais varieront légèrement en fonction du contenu de votre "
+"texte. LibreOffice Writer compte également le texte dans l'en-tête de la page, "
+"ce que ne fait pas l'outil **Outil Manuscrit**."
+
+#: ../../source/more/counting.rst:53
+msgid ""
+"The content of each line is counted after all formatting has been processed, so "
+"the result will be more accurate than the counts for text documents elsewhere "
+"in the app. The following rules apply:"
+msgstr ""
+"Le contenu de chaque ligne est compté après le traitement de toutes les mises "
+"en forme, de sorte que le résultat sera plus précis que les décomptes pour les "
+"documents textuels dans d'autres parties de l'application. Les règles suivantes "
+"s'appliquent :"
+
+#: ../../source/more/counting.rst:57
+msgid ""
+"Leading and trailing white spaces are generally included, but paragraph breaks "
+"are not."
+msgstr ""
+"Les espaces blancs de début et de fin sont généralement inclus, mais les sauts "
+"de paragraphe ne le sont pas."
+
+#: ../../source/more/counting.rst:58
+msgid "Hard line breaks within paragraph are considered white space characters."
+msgstr ""
+"Les retours à la ligne dans un paragraphe sont considérés comme des caractères "
+"d'espacement."
+
+#: ../../source/more/counting.rst:59
+msgid ""
+"All formatting codes are ignored, including shortcodes, commands and Markdown."
+msgstr ""
+"Tous les codes de formatage sont ignorés, y compris les shortcodes, les "
+"commandes et Markdown."
+
+#: ../../source/more/counting.rst:60
+msgid "Scene and section separators are counted."
+msgstr "Les séparateurs de scène et de section sont pris en compte."
+
+#: ../../source/more/counting.rst:61
+msgid "Comments and meta data lines are counted after they are formatted."
+msgstr ""
+"Les lignes de commentaires et de métadonnées sont comptées après leur mise en "
+"forme."
+
+#: ../../source/more/counting.rst:62
+msgid "Headers are counted after they are formatted with custom formats."
+msgstr ""
+"Les en-têtes sont comptés après avoir été formatés avec des formats "
+"personnalisés."
+
+#: ../../source/more/counting.rst:64
+msgid "The following counts are available:"
+msgstr "Les décomptes suivants sont disponibles :"
+
+#: ../../source/more/counting.rst:66
+msgid "**Headings**"
+msgstr "**En-têtes**"
+
+#: ../../source/more/counting.rst:67
+msgid "The number of headings in the manuscript."
+msgstr "Le nombre d'entêtes dans le manuscrit."
+
+#: ../../source/more/counting.rst:69
+msgid "**Paragraphs**"
+msgstr "**Paragraphes**"
+
+#: ../../source/more/counting.rst:70
+msgid "The number of body text paragraphs in the manuscript."
+msgstr "Le nombre de paragraphes dans le manuscrit."
+
+#: ../../source/more/counting.rst:72
+msgid "**Words**"
+msgstr "**Mots**"
+
+#: ../../source/more/counting.rst:73
+msgid ""
+"The number of words in the manuscript, including any comments and meta data "
+"text."
+msgstr ""
+"Le nombre de mots du manuscrit, y compris les commentaires et les métadonnées."
+
+#: ../../source/more/counting.rst:75
+msgid "**Words in Text**"
+msgstr "**Mots dans le texte**"
+
+#: ../../source/more/counting.rst:76
+msgid "The number of words in body text paragraphs, excluding all other text."
+msgstr "Nombre de mots dans les paragraphes, à l'exclusion de tout autre texte."
+
+#: ../../source/more/counting.rst:78
+msgid "**Words in Headings**"
+msgstr "**Mots dans les entêtes**"
+
+#: ../../source/more/counting.rst:79
+msgid ""
+"The number of words in headings, including inserted formatting like chapter "
+"numbers, etc."
+msgstr ""
+"Le nombre de mots dans les entêtes, y compris le formatage inséré comme les "
+"numéros de chapitre, etc."
+
+#: ../../source/more/counting.rst:81
+msgid "**Characters**"
+msgstr "**Caractères**"
+
+#: ../../source/more/counting.rst:82
+msgid ""
+"The number of characters in all lines, including any comments and meta data "
+"text. Paragraph breaks are not counted, but in-paragraph hard line breaks are."
+msgstr ""
+"Le nombre de caractères de toutes les lignes, y compris les commentaires et le "
+"texte des métadonnées. Les sauts de paragraphe ne sont pas comptés, mais les "
+"sauts de ligne dans les paragraphes le sont."
+
+#: ../../source/more/counting.rst:85
+msgid "**Character in Text**"
+msgstr "**Caractères dans le texte**"
+
+#: ../../source/more/counting.rst:86
+msgid ""
+"The number of characters in body text paragraphs. Paragraph breaks are not "
+"counted, but in-paragraph hard line breaks are."
+msgstr ""
+"Nombre de caractères dans les paragraphes. Les sauts de paragraphe ne sont pas "
+"comptés, mais les sauts de ligne dans les paragraphes le sont."
+
+#: ../../source/more/counting.rst:89
+msgid "**Characters in Headings**"
+msgstr "**Caractères dans les entêtes**"
+
+#: ../../source/more/counting.rst:90
+msgid "The number of characters in headings."
+msgstr "Le nombre de caractères dans les en-têtes."
+
+#: ../../source/more/counting.rst:92
+msgid "**Character in Text, No Spaces**"
+msgstr "**Caractères dans le texte, sans les espaces**"
+
+#: ../../source/more/counting.rst:93
+msgid ""
+"The number of characters in body text paragraphs considered part of a word or "
+"punctuation. That is, white space characters are not counted."
+msgstr ""
+"Le nombre de caractères dans les paragraphes considérés comme faisant partie "
+"d'un mot ou d'une ponctuation. En d'autres termes, les caractères d'espacement "
+"ne sont pas pris en compte."
+
+#: ../../source/more/counting.rst:96
+msgid "**Character in Headings, No Spaces**"
+msgstr "**Caractères dans les en-têtes, sans les espaces**"
+
+#: ../../source/more/counting.rst:97
+msgid ""
+"The number of characters in headings considered part of a word or punctuation. "
+"That is, white space characters are not counted."
+msgstr ""
+"Le nombre de caractères dans les en-têtes considérés comme faisant partie d'un "
+"mot ou de la ponctuation. En d'autres termes, les caractères d'espacement ne "
+"sont pas pris en compte."

docs/source/locales/fr/LC_MESSAGES/more/customise.po

@@ -0,0 +1,359 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:05+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/more/customise.rst:5
+msgid "Customisations"
+msgstr "Personnalisations"
+
+#: ../../source/more/customise.rst:10
+msgid ""
+"There are a few ways you can customise novelWriter yourself. Currently, "
+"you can add new GUI themes, your own syntax themes, and install additional "
+"dictionaries."
+msgstr ""
+"Vous pouvez personnaliser novelWriter de plusieurs façons. Actuellement, "
+"vous pouvez ajouter de nouveaux thèmes d'interface graphique, vos propres "
+"thèmes de syntaxe et installer des dictionnaires supplémentaires."
+
+#: ../../source/more/customise.rst:17
+msgid "Spell Check Dictionaries"
+msgstr "Dictionnaires de vérification orthographique"
+
+#: ../../source/more/customise.rst:19
+msgid ""
+"novelWriter uses Enchant_ as the spell checking tool. Depending on your "
+"operating system, it may or may not load all installed spell check "
+"dictionaries automatically."
+msgstr ""
+"novelWriter utilise Enchant_ comme outil de vérification orthographique. "
+"Selon votre système d'exploitation, il peut ou non charger automatiquement "
+"tous les dictionnaires de vérification orthographique installés."
+
+#: ../../source/more/customise.rst:24
+msgid "Linux and MacOS"
+msgstr "Linux et MacOS"
+
+#: ../../source/more/customise.rst:26
+msgid ""
+"On Linux and MacOS, you generally only have to install hunspell, aspell or "
+"myspell dictionaries on your system like you do for other applications. "
+"See your distro or OS documentation for how to do this. These dictionaries "
+"should show up as available spell check languages in novelWriter."
+msgstr ""
+"Sous Linux et MacOS, il vous suffit généralement d'installer les "
+"dictionnaires hunspell, aspell ou myspell sur votre système, comme vous le "
+"faites pour d'autres applications. Consultez la documentation de votre "
+"distro ou de votre système d'exploitation pour savoir comment procéder. "
+"Ces dictionnaires devraient apparaître comme des langues de vérification "
+"orthographique disponibles dans novelWriter."
+
+#: ../../source/more/customise.rst:32
+msgid "Windows"
+msgstr "Windows"
+
+#: ../../source/more/customise.rst:34
+msgid ""
+"For Windows, English is included with the installation. For other "
+"languages you have to download and add dictionaries yourself."
+msgstr ""
+"Pour Windows, l'anglais est inclus dans l'installation. Pour les autres "
+"langues, vous devez télécharger et ajouter les dictionnaires vous-même."
+
+#: ../../source/more/customise.rst:37
+msgid "**Install Tool**"
+msgstr "**Outil d'installation**"
+
+#: ../../source/more/customise.rst:39
+msgid ""
+"A small tool to assist with this can be found under **Tools > Add "
+"Dictionaries**. It will import spell checking dictionaries from Free "
+"Office or Libre Office extensions. The dictionaries are then installed in "
+"the install location for the Enchant library and should thus work for any "
+"application that uses Enchant for spell checking."
+msgstr ""
+"Un petit outil pour vous aider se trouve sous **Outils > Ajouter des "
+"dictionnaires**. Il importera des dictionnaires de vérification "
+"orthographique à partir des extensions Free Office ou Libre Office. Les "
+"dictionnaires sont alors installés dans l'emplacement d'installation de la "
+"bibliothèque Enchant et devraient donc fonctionner pour toute application "
+"qui utilise Enchant pour la vérification orthographique."
+
+#: ../../source/more/customise.rst:44
+msgid "**Manual Install**"
+msgstr "**Installation manuelle**"
+
+#: ../../source/more/customise.rst:46
+msgid ""
+"If you prefer to do this manually or want to use a different source than "
+"the ones mentioned above, You need to get compatible dictionary files for "
+"your language. You need two files files ending with ``.aff`` and ``.dic``. "
+"These files must then be copied to the following location:"
+msgstr ""
+"Si vous préférez le faire manuellement ou si vous voulez utiliser une "
+"source différente de celles mentionnées ci-dessus, vous devez obtenir des "
+"fichiers de dictionnaires compatibles avec votre langue. Vous avez besoin "
+"de deux fichiers se terminant par ``.aff`` et ``.dic``. Ces fichiers "
+"doivent ensuite être copiés à l'emplacement suivant :"
+
+#: ../../source/more/customise.rst:50
+msgid "``C:\\Users\\<USER>\\AppData\\Local\\enchant\\hunspell``"
+msgstr "``C:\\Users\\<USER>\\AppData\\Local\\enchant\\hunspell``"
+
+#: ../../source/more/customise.rst:52
+msgid ""
+"This assumes your user profile is stored at ``C:\\Users\\<USER>``. The "
+"last one or two folders may not exist, so you may need to create them."
+msgstr ""
+"Cela suppose que votre profil d'utilisateur est stocké dans ``C:"
+"\\Users\\<USER>``. Le dernier ou les deux derniers dossiers peuvent ne pas "
+"exister, vous devrez donc les créer."
+
+#: ../../source/more/customise.rst:55
+msgid "You can find the various dictionaries on the `Free Desktop`_ website."
+msgstr ""
+"Vous pouvez trouver les différents dictionnaires sur le site web `Free "
+"Desktop`_."
+
+#: ../../source/more/customise.rst:58
+msgid ""
+"The Free Desktop link points to a repository, and what may look like file "
+"links inside the dictionary folder are actually links to web pages. If you "
+"right-click and download those, you get HTML files, not dictionaries!"
+msgstr ""
+"Le lien Free Desktop pointe vers un référentiel, et ce qui peut ressembler "
+"à des liens de fichiers à l'intérieur du dossier du dictionnaire sont en "
+"fait des liens vers des pages web. Si vous cliquez avec le bouton droit de "
+"la souris et que vous les téléchargez, vous obtiendrez des fichiers HTML, "
+"pas des dictionnaires !"
+
+#: ../../source/more/customise.rst:62
+msgid ""
+"In order to download the actual dictionary files, right-click the "
+"\"plain\" label at the end of each line and download that."
+msgstr ""
+"Pour télécharger les fichiers du dictionnaire, cliquez avec le bouton "
+"droit de la souris sur l'étiquette « plain » à la fin de chaque ligne et "
+"téléchargez-la."
+
+#: ../../source/more/customise.rst:69
+msgid "Syntax and GUI Themes"
+msgstr "Syntaxe et thèmes de l'interface graphique"
+
+#: ../../source/more/customise.rst:71
+msgid ""
+"Adding your own GUI and syntax themes is relatively easy, although it "
+"requires that you manually edit config files with colour values. The "
+"themes are defined by simple plain text config files with meta data and "
+"colour settings."
+msgstr ""
+"L'ajout de vos propres thèmes d'interface graphique et de syntaxe est "
+"relativement facile, bien qu'il soit nécessaire d'éditer manuellement les "
+"fichiers de configuration avec les valeurs de couleur. Les thèmes sont "
+"définis par de simples fichiers de configuration en texte brut contenant "
+"des métadonnées et des paramètres de couleur."
+
+#: ../../source/more/customise.rst:75
+msgid ""
+"In order to make your own versions, first copy one of the existing files "
+"to your local computer and modify it as you like."
+msgstr ""
+"Pour créer vos propres versions, copiez d'abord l'un des fichiers "
+"existants sur votre ordinateur local et modifiez-le à votre guise."
+
+#: ../../source/more/customise.rst:78
+msgid ""
+"The existing syntax themes are stored in `novelwriter/assets/syntax "
+"<https://github.com/vkbo/novelWriter/tree/main/novelwriter/assets/"
+"syntax>`_."
+msgstr ""
+"Les thèmes syntaxiques existants sont stockés dans `novelwriter/assets/"
+"syntax <https://github.com/vkbo/novelWriter/tree/main/novelwriter/assets/"
+"syntax>`_."
+
+#: ../../source/more/customise.rst:80
+msgid ""
+"The existing GUI themes are stored in `novelwriter/assets/themes <https://"
+"github.com/vkbo/novelWriter/tree/main/novelwriter/assets/themes>`_."
+msgstr ""
+"Les thèmes GUI existants sont stockés dans `novelwriter/assets/themes "
+"<https://github.com/vkbo/novelWriter/tree/main/novelwriter/assets/"
+"themes>`_."
+
+#: ../../source/more/customise.rst:82
+msgid ""
+"The existing icon themes are stored in `novelwriter/assets/icons <https://"
+"github.com/vkbo/novelWriter/tree/main/novelwriter/assets/icons>`_."
+msgstr ""
+"Les thèmes d'icônes existants sont stockés dans `novelwriter/assets/icons "
+"<https://github.com/vkbo/novelWriter/tree/main/novelwriter/assets/icons>`_."
+
+#: ../../source/more/customise.rst:85
+msgid ""
+"Remember to also change the name of your theme by modifying the ``name`` "
+"setting at the top of the file, otherwise you may not be able to "
+"distinguish them in **Preferences**."
+msgstr ""
+"N'oubliez pas de changer également le nom de votre thème en modifiant le "
+"paramètre ``name`` en haut du fichier, sinon vous ne pourrez pas les "
+"distinguer dans les **Préférences**."
+
+#: ../../source/more/customise.rst:88
+msgid ""
+"For novelWriter to be able to locate the custom theme files, you must copy "
+"them to the :ref:`docs_technical_locations_data` location in your home or "
+"user area. There should be a folder there named ``syntax`` for syntax "
+"themes, just ``themes`` for GUI themes, and ``icons`` for icon themes. "
+"These folders are created the first time you start novelWriter."
+msgstr ""
+"Pour que novelWriter puisse localiser les fichiers de thèmes "
+"personnalisés, vous devez les copier dans l'emplacement :ref:"
+"`docs_technical_locations_data` dans votre espace personnel ou "
+"utilisateur. Il devrait y avoir un dossier nommé ``syntax`` pour les "
+"thèmes de syntaxe, juste ``themes`` pour les thèmes GUI, et ``icons`` pour "
+"les thèmes d'icônes. Ces dossiers sont créés la première fois que vous "
+"démarrez novelWriter.\n"
+"\n"
+"Traduit avec DeepL.com (version gratuite)"
+
+#: ../../source/more/customise.rst:93
+msgid ""
+"Once the files are copied there, they should show up in **Preferences** "
+"with the label you set as ``name`` inside the file."
+msgstr ""
+"Une fois les fichiers copiés, ils devraient apparaître dans les "
+"**Préférences** avec le nom que vous avez défini dans le fichier."
+
+#: ../../source/more/customise.rst:98
+msgid ""
+"The theme file formats change regularly in new releases. It is up to you "
+"to keep custom theme files up to date."
+msgstr ""
+"Les formats des fichiers de thème changent régulièrement dans les "
+"nouvelles versions. C'est à vous qu'il incombe de mettre à jour les "
+"fichiers des thèmes personnalisés."
+
+#: ../../source/more/customise.rst:103
+msgid "Custom GUI and Icons Theme"
+msgstr "Thème d'interface graphique et d'icônes personnalisé"
+
+#: ../../source/more/customise.rst:105
+msgid "A GUI theme ``.conf`` file consists of the following settings:"
+msgstr ""
+"Le fichier ``.conf`` d'un thème GUI est constitué des paramètres suivants :"
+
+#: ../../source/more/customise.rst:159
+msgid "In the Main section you must at least define the ``name`` settings."
+msgstr ""
+"Dans la section Main, vous devez au moins définir les paramètres ``name``."
+
+#: ../../source/more/customise.rst:161
+msgid ""
+"The Palette values correspond to the Qt enum values for ``QPalette::"
+"ColorRole``, see the `Qt documentation <https://doc.qt.io/qt-6/qpalette."
+"html#ColorRole-enum>`_ for more details. The colour values are RGB numbers "
+"on the format ``r, g, b`` where each is an integer from ``0`` to ``255``. "
+"Omitted values are not loaded and will use default values. If the "
+"``helptext`` colour is not defined, it is computed as a colour between the "
+"``window`` and ``windowtext`` colour. Additional shades of some of the "
+"colours are also computed. These are mainly used for 3D effects."
+msgstr ""
+"Les valeurs de la palette correspondent aux valeurs de l'enum Qt pour "
+"``QPalette::ColorRole``, voir la documentation Qt <https://doc.qt.io/qt-6/"
+"qpalette.html#ColorRole-enum>`_ pour plus de détails. Les valeurs de "
+"couleur sont des nombres RVB au format ``r, g, b`` où chacun est un entier "
+"de ``0`` à ``255``. Les valeurs omises ne sont pas chargées et utilisent "
+"les valeurs par défaut. Si la couleur ``helptext`` n'est pas définie, elle "
+"est calculée comme une couleur comprise entre les couleurs ``window`` et "
+"``windowtext``. Des nuances supplémentaires de certaines couleurs sont "
+"également calculées. Elles sont principalement utilisées pour les effets "
+"3D."
+
+#: ../../source/more/customise.rst:168
+msgid "The ``fadedtext`` and ``errortext`` theme colour entries were added."
+msgstr ""
+"Les entrées de couleur des thèmes ``fadedtext`` et ``errortext`` ont été "
+"ajoutées."
+
+#: ../../source/more/customise.rst:171
+msgid ""
+"The ``icontheme`` setting was dropped as the icon theme is now its own "
+"setting. The ``[Icons]`` and ``[Project]`` sections were added, and the "
+"``status*`` settings removed."
+msgstr ""
+"Le paramètre ``icontheme`` a été supprimé car le thème des icônes a "
+"maintenant son propre paramètre. Les sections ``[Icons]`` et ``[Project]`` "
+"ont été ajoutées, et le paramètre ``status*`` a été supprimé."
+
+#: ../../source/more/customise.rst:177
+msgid "Custom Syntax Theme"
+msgstr "Syntaxe des thèmes personnalisés"
+
+#: ../../source/more/customise.rst:179
+msgid "A syntax theme ``.conf`` file consists of the following settings:"
+msgstr ""
+"Un fichier ``.conf`` de thème est constitué des paramètres suivants :"
+
+#: ../../source/more/customise.rst:213
+msgid ""
+"In the Main section, you must define at least the ``name`` setting. The "
+"Syntax colour values are RGB(A) numbers of the format ``r, g, b, a`` where "
+"each is an integer from ``0`` to ``255``. The fourth value is the alpha "
+"channel, which can be omitted."
+msgstr ""
+"Dans la section Main, vous devez définir au moins le paramètre ``name``. "
+"Les valeurs de couleur de la syntaxe sont des nombres RVB(A) du format "
+"``r, g, b, a`` où chacun est un entier de ``0`` à ``255``. La quatrième "
+"valeur est le canal alpha, qui peut être omis."
+
+#: ../../source/more/customise.rst:217
+msgid ""
+"Omitted syntax colours default to black, except ``background`` which "
+"defaults to white, and ``texthighlight`` which defaults to white with half "
+"transparency."
+msgstr ""
+"Les couleurs omises dans la syntaxe prennent par défaut la couleur noire, "
+"à l'exception de ``background`` qui prend par défaut la couleur blanche, "
+"et de ``texthighlight`` qui prend par défaut la couleur blanche avec une "
+"demi-transparence."
+
+#: ../../source/more/customise.rst:220
+msgid "The ``shortcode`` syntax colour entry was added."
+msgstr "Le paramètre de couleur ``shortcode`` a été ajouté."
+
+#: ../../source/more/customise.rst:223
+msgid "The ``optional`` syntax colour entry was added."
+msgstr "Le paramètre de couleur ``optional`` a été ajouté."
+
+#: ../../source/more/customise.rst:226
+msgid "The ``texthighlight`` syntax colour entry was added."
+msgstr "Le paramètre de couleur ``texthighlight`` a été ajouté."
+
+#: ../../source/more/customise.rst:229
+msgid ""
+"The ``dialog``, ``altdialog``, ``note`` and ``tag`` syntax colour entries "
+"were added. ``straightquotes``, ``doublequotes`` and ``singlequotes`` were "
+"removed."
+msgstr ""
+"Les paramètres de couleur ``dialog``, ``altdialog``, ``note`` et ``tag`` "
+"ont été ajoutés. Les paramètres ``guillemets droits``, ``guillemets "
+"doubles`` et ``guillemets simples`` ont été supprimés."

docs/source/locales/fr/LC_MESSAGES/more/handling_errors.po

@@ -0,0 +1,159 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:11+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/more/handling_errors.rst:5
+msgid "Handling Errors"
+msgstr "Traitement des erreurs"
+
+#: ../../source/more/handling_errors.rst:7
+msgid ""
+"In case something goes wrong, novelWriter has a few built-in features to "
+"reduce the chance your work is lost. In case of a crash, it will also "
+"try to save whatever changes you have made before exiting, if this is at "
+"all possible."
+msgstr ""
+"En cas de problème, novelWriter dispose de quelques fonctions intégrées "
+"pour réduire le risque de perte de votre travail. En cas de panne, il "
+"essaiera également d'enregistrer les modifications que vous avez "
+"apportées avant de quitter, si cela est possible."
+
+#: ../../source/more/handling_errors.rst:11
+msgid ""
+"The storage solution is designed to save each text document "
+"independently, so only the document you're working on is actually at a "
+"risk of losing data in the event of a crash."
+msgstr ""
+"La solution de stockage est conçue pour sauvegarder chaque document "
+"texte indépendamment, de sorte que seul le document sur lequel vous "
+"travaillez risque de perdre des données en cas de panne."
+
+#: ../../source/more/handling_errors.rst:18
+msgid "Recovered Documents"
+msgstr "Documents récupérés"
+
+#: ../../source/more/handling_errors.rst:20
+msgid ""
+"If novelWriter crashes or otherwise exits without saving the project "
+"state, or if you're using a file synchronisation tool that runs out of "
+"sync, there may be files in the project storage folder that aren't "
+"tracked in the core project file. These files, when discovered, are "
+"recovered and added back into the project when a project is opened."
+msgstr ""
+"Si novelWriter se plante ou se termine sans sauvegarder l'état du "
+"projet, ou si vous utilisez un outil de synchronisation de fichiers qui "
+"se désynchronise, il peut y avoir des fichiers dans le dossier de "
+"stockage du projet qui ne sont pas suivis dans le fichier de base du "
+"projet. Ces fichiers, lorsqu'ils sont découverts, sont récupérés et "
+"ajoutés au projet lorsqu'un projet est ouvert."
+
+#: ../../source/more/handling_errors.rst:25
+msgid ""
+"The discovered files are scanned for metadata that give clues as to "
+"where the document may previously have been located in the project. The "
+"project loading routine will try to put them back as close as possible "
+"to this location, if it still exists. Generally, it will be appended to "
+"the end of the folder where it previously was located. If that folder "
+"doesn't exist, it will try to add it to the correct root folder type. If "
+"it cannot figure out which root folder is correct, the document will be "
+"added to the **Novel** root folder. Finally, if a **Novel** does not "
+"exist, one will be created."
+msgstr ""
+"Les fichiers découverts sont analysés à la recherche de métadonnées qui "
+"donnent des indices sur l'emplacement antérieur du document dans le "
+"projet. La routine de chargement du projet essaiera de les replacer "
+"aussi près que possible de cet emplacement, s'il existe toujours. En "
+"général, le document sera ajouté à la fin du dossier où il se trouvait "
+"auparavant. Si ce dossier n'existe pas, il essaiera de l'ajouter au type "
+"de dossier racine correct. S'il ne parvient pas à déterminer quel est le "
+"bon dossier racine, le document sera ajouté au dossier racine "
+"**Nouveau**. Enfin, si un **Nouveau** n'existe pas, il en sera créé un."
+
+#: ../../source/more/handling_errors.rst:33
+msgid ""
+"If the title of the document can be recovered, the word \"Recovered:\" "
+"will be added as a prefix to indicate that it may need further "
+"attention. If the title cannot be determined, the document will be named "
+"after its internal key, which is a string of characters and numbers."
+msgstr ""
+"Si le titre du document peut être récupéré, le mot « Récupéré : » sera "
+"ajouté comme préfixe pour indiquer qu'il peut nécessiter une attention "
+"supplémentaire. Si le titre ne peut être déterminé, le document sera "
+"nommé d'après sa clé interne, qui est une chaîne de caractères et de "
+"chiffres."
+
+#: ../../source/more/handling_errors.rst:41
+msgid "Project Lockfile"
+msgstr "Fichier de verrouillage du projet"
+
+#: ../../source/more/handling_errors.rst:43
+msgid ""
+"To prevent data loss caused by file conflicts when novelWriter projects "
+"are synchronised via file synchronisation tools, a project lockfile is "
+"written to the project storage folder when a project is open. If you try "
+"to open a project that already has such a file present, you will be "
+"presented with a warning, and some information about where else "
+"novelWriter thinks the project is also open. You will be given the "
+"option to ignore this warning, and continue opening the project at your "
+"own risk."
+msgstr ""
+"Pour éviter la perte de données causée par des conflits de fichiers "
+"lorsque les projets novelWriter sont synchronisés via des outils de "
+"synchronisation de fichiers, un fichier de verrouillage de projet est "
+"écrit dans le dossier de stockage du projet lorsqu'un projet est ouvert. "
+"Si vous essayez d'ouvrir un projet dans lequel un tel fichier est déjà "
+"présent, vous recevrez un avertissement et des informations sur "
+"l'endroit où novelWriter pense que le projet est également ouvert. Vous "
+"aurez la possibilité d'ignorer cet avertissement et de continuer à "
+"ouvrir le projet à vos risques et périls."
+
+#: ../../source/more/handling_errors.rst:52
+msgid ""
+"If, for some reason, novelWriter or your computer crashes, the lock file "
+"may remain even if there are no other instances keeping the project "
+"open. In such a case it is safe to ignore the lock file warning when re-"
+"opening the project."
+msgstr ""
+"Si, pour une raison quelconque, novelWriter ou votre ordinateur tombe en "
+"panne, le fichier de verrouillage peut subsister même si aucune autre "
+"instance ne maintient le projet ouvert. Dans ce cas, il est prudent "
+"d'ignorer l'avertissement relatif au fichier de verrouillage lors de la "
+"réouverture du projet."
+
+#: ../../source/more/handling_errors.rst:58
+msgid ""
+"If you choose to ignore the warning and continue opening the project, "
+"and multiple instances of the project are in fact open, you are likely "
+"to cause inconsistencies and create diverging project files, potentially "
+"resulting in loss of data and orphaned files. You are not likely to lose "
+"any actual text unless both instances have the same document open in the "
+"editor, and novelWriter will try to resolve project inconsistencies the "
+"next time you open the project."
+msgstr ""
+"Si vous choisissez d'ignorer l'avertissement et de continuer à ouvrir le "
+"projet, et que plusieurs instances du projet sont en fait ouvertes, vous "
+"risquez de provoquer des incohérences et de créer des fichiers de projet "
+"divergents, ce qui peut entraîner une perte de données et des fichiers "
+"orphelins. Il est peu probable que vous perdiez du texte à moins que les "
+"deux instances aient le même document ouvert dans l'éditeur, et "
+"novelWriter essaiera de résoudre les incohérences du projet la prochaine "
+"fois que vous l'ouvrirez."

docs/source/locales/fr/LC_MESSAGES/more/project_format.po

@@ -0,0 +1,298 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:21+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/more/project_format.rst:5
+msgid "Project Format Changes"
+msgstr "Modifications du format des projets"
+
+#: ../../source/more/project_format.rst:7
+msgid ""
+"Most of the changes to the file formats over the history of novelWriter "
+"have no impact on the user side of things. The project files are "
+"generally updated automatically. However, some of the changes require "
+"minor actions from the user."
+msgstr ""
+"La plupart des modifications apportées aux formats de fichiers au cours "
+"de l'histoire de novelWriter n'ont pas d'impact sur l'utilisateur. Les "
+"fichiers de projet sont généralement mis à jour automatiquement. "
+"Cependant, certains changements nécessitent des actions mineures de la "
+"part de l'utilisateur."
+
+#: ../../source/more/project_format.rst:11
+msgid ""
+"The key changes in the formats are listed in this chapter, as well as "
+"the user actions required, where applicable."
+msgstr ""
+"Les principales modifications apportées aux formats sont énumérées dans "
+"ce chapitre, ainsi que les actions requises de la part de l'utilisateur, "
+"le cas échéant."
+
+#: ../../source/more/project_format.rst:14
+msgid ""
+"A full project file format specification is available under \"More "
+"Documents\"."
+msgstr ""
+"Une spécification complète du format de fichier du projet est disponible "
+"sous « Plus d'informations »."
+
+#: ../../source/more/project_format.rst:18
+msgid ""
+"When you update a project from one format version to the next, the "
+"project can no longer be opened by a version of novelWriter prior to the "
+"version where the new file format was introduced. You will get a "
+"notification about any updates to your project file format and will have "
+"the option to decline the upgrade."
+msgstr ""
+"Lorsque vous mettez à jour un projet d'une version de format à la "
+"suivante, le projet ne peut plus être ouvert par une version de "
+"novelWriter antérieure à la version où le nouveau format de fichier a "
+"été introduit. Vous recevrez une notification concernant toute mise à "
+"jour du format de fichier de votre projet et vous aurez la possibilité "
+"de refuser la mise à jour."
+
+#: ../../source/more/project_format.rst:27
+msgid "Format 1.5 Changes"
+msgstr "Format 1.5 Modifications"
+
+#: ../../source/more/project_format.rst:29
+msgid "This project format was introduced in novelWriter version 2.0 RC 2."
+msgstr ""
+"Ce format de projet a été introduit dans la version 2.0 RC 2 de "
+"novelWriter."
+
+#: ../../source/more/project_format.rst:31
+msgid ""
+"This is a modification of the 1.4 format. It makes the XML more "
+"consistent in that meta data have been moved to their respective section "
+"nodes as attributes, and key/value settings now have a consistent "
+"format. Logical flags are saved as yes/no instead of Python True/False, "
+"and the main heading of the document is now saved to the item rather "
+"than in the index. The conversion is done automatically the first time a "
+"project is loaded. No user action is required."
+msgstr ""
+"Il s'agit d'une modification du format 1.4. Il rend le XML plus cohérent "
+"en ce sens que les métadonnées ont été déplacées vers leurs nœuds de "
+"section respectifs en tant qu'attributs, et que les paramètres clé/"
+"valeur ont désormais un format cohérent. Les indicateurs logiques sont "
+"sauvegardés sous forme de oui/non au lieu de True/False de Python, et le "
+"titre principal du document est désormais sauvegardé dans l'article "
+"plutôt que dans l'index. La conversion est effectuée automatiquement "
+"lors du premier chargement d'un projet. Aucune action de l'utilisateur "
+"n'est nécessaire."
+
+#: ../../source/more/project_format.rst:41
+msgid "Format 1.4 Changes"
+msgstr "Format 1.4 Modifications"
+
+#: ../../source/more/project_format.rst:43
+msgid ""
+"This project format was introduced in novelWriter version 2.0 RC 1. "
+"Since this was a release candidate, it is unlikely that your project "
+"uses it, but it may be the case if you've installed a pre-release."
+msgstr ""
+"Ce format de projet a été introduit dans la version 2.0 RC 1 de "
+"novelWriter. Comme il s'agissait d'une version candidate, il est peu "
+"probable que votre projet l'utilise, mais c'est peut-être le cas si vous "
+"avez installé une préversion."
+
+#: ../../source/more/project_format.rst:47
+msgid ""
+"This format changes the way project items (folders, documents and notes) "
+"are stored. It is a more compact format that is simpler and faster to "
+"parse, and easier to extend. The conversion is done automatically the "
+"first time a project is loaded. No user action is required."
+msgstr ""
+"Ce format modifie la manière dont les éléments du projet (dossiers, "
+"documents et notes) sont stockés. Il s'agit d'un format plus compact, "
+"plus simple et plus rapide à analyser, et plus facile à étendre. La "
+"conversion se fait automatiquement lors du premier chargement d'un "
+"projet. Aucune action de l'utilisateur n'est nécessaire."
+
+#: ../../source/more/project_format.rst:55
+msgid "Format 1.3 Changes"
+msgstr "Format 1.3 Modifications"
+
+#: ../../source/more/project_format.rst:57
+msgid "This project format was introduced in novelWriter version 1.5."
+msgstr ""
+"Ce format de projet a été introduit dans la version 1.5 de novelWriter."
+
+#: ../../source/more/project_format.rst:59
+msgid ""
+"With this format, the number of document layouts was reduced from eight "
+"to two. The conversion of document layouts is performed automatically "
+"when the project is opened."
+msgstr ""
+"Avec ce format, le nombre de présentations de documents a été réduit de "
+"huit à deux. La conversion des présentations de documents s'effectue "
+"automatiquement lors de l'ouverture du projet."
+
+#: ../../source/more/project_format.rst:62
+msgid ""
+"Due to the reduction of layouts, some features that were previously "
+"controlled by these layouts will be lost. These features are instead now "
+"controlled by syntax codes, so to recover these features, some minor "
+"modification must be made to select documents by the user."
+msgstr ""
+"En raison de la réduction des présentations, certaines caractéristiques "
+"qui étaient auparavant contrôlées par ces présentations seront perdues. "
+"Ces fonctionnalités sont désormais contrôlées par des codes syntaxiques. "
+"Pour les récupérer, l'utilisateur doit donc apporter quelques "
+"modifications mineures aux documents sélectionnés."
+
+#: ../../source/more/project_format.rst:66
+msgid ""
+"The manual changes the user must make should be very few as they apply "
+"to document layouts that should be used only a few places in any given "
+"project. These are as follows:"
+msgstr ""
+"Les modifications manuelles que l'utilisateur doit apporter sont très "
+"peu nombreuses car elles s'appliquent à des mises en page de documents "
+"qui ne doivent être utilisées qu'à quelques endroits dans un projet "
+"donné. Ces modifications sont les suivantes :"
+
+#: ../../source/more/project_format.rst:69
+msgid "**Title Pages**"
+msgstr "**Pages de titres**"
+
+#: ../../source/more/project_format.rst:71
+msgid ""
+"The formatting of the level one title on the title page must be changed "
+"from ``# Title Text`` to ``#! Title Text`` in order to retain the "
+"previous functionality. See :ref:`docs_usage_headings_levels`."
+msgstr ""
+"Le formatage du titre de niveau 1 sur la page de titre doit être modifié "
+"de ``# Title Text`` à ``# ! Title Text`` afin de conserver la "
+"fonctionnalité précédente. Voir :ref:`docs_usage_headings_levels`."
+
+#: ../../source/more/project_format.rst:74
+msgid ""
+"Any text that was previously centred on the page must be manually "
+"centred using the text alignment feature. See :ref:"
+"`docs_usage_align_indent`."
+msgstr ""
+"Tout texte qui était précédemment centré sur la page doit être centré "
+"manuellement en utilisant la fonction d'alignement du texte. Voir :ref:"
+"`docs_usage_align_indent`."
+
+#: ../../source/more/project_format.rst:77
+msgid "**Unnumbered Chapters**"
+msgstr "**Chapitres non numérotés**"
+
+#: ../../source/more/project_format.rst:79
+msgid ""
+"Since the specific layout for unnumbered chapters has been dropped, such "
+"chapters must all use the ``##! Chapter Name`` formatting code instead "
+"of ``## Chapter Name``. This also includes chapters marked by an "
+"asterisk: ``## *Chapter Name``, as this feature has also been dropped. "
+"See :ref:`docs_usage_headings_levels`."
+msgstr ""
+"La mise en page spécifique pour les chapitres non numérotés ayant été "
+"abandonnée, ces chapitres doivent tous utiliser le code de formatage "
+"``# ! Nom du chapitre`` au lieu de `## Nom du chapitre``. Cela inclut "
+"également les chapitres marqués d'un astérisque : `## *Nom de "
+"chapitre``, car cette fonctionnalité a également été abandonnée. Voir :"
+"ref:`docs_usage_headings_levels`."
+
+#: ../../source/more/project_format.rst:84
+msgid "**Plain Pages**"
+msgstr "**Pages vierges**"
+
+#: ../../source/more/project_format.rst:86
+msgid ""
+"The layout named \"Plain Page\" has also been removed. The only feature "
+"of this layout was that it ensured that the content always started on a "
+"fresh page. In the new format, fresh pages can be set anywhere in the "
+"text with the ``[new page]`` code. See :ref:"
+"`docs_usage_formatting_breaks`."
+msgstr ""
+"La mise en page appelée « page simple » a également été supprimée. La "
+"seule caractéristique de cette mise en page était qu'elle garantissait "
+"que le contenu commençait toujours sur une nouvelle page. Dans le "
+"nouveau format, les nouvelles pages peuvent être placées n'importe où "
+"dans le texte avec le code ``[new page]``. Voir :ref:"
+"`docs_usage_formatting_breaks`."
+
+#: ../../source/more/project_format.rst:94
+msgid "Format 1.2 Changes"
+msgstr "Format 1.2 Modifications"
+
+#: ../../source/more/project_format.rst:96
+msgid "This project format was introduced in novelWriter version 0.10."
+msgstr ""
+"Ce format de projet a été introduit dans la version 0.10 de novelWriter."
+
+#: ../../source/more/project_format.rst:98
+msgid ""
+"With this format, the way auto-replace entries were stored in the main "
+"project XML file changed. Conversion from this format is done "
+"automatically."
+msgstr ""
+"Avec ce format, la façon dont les entrées de remplacement automatique "
+"étaient stockées dans le fichier XML du projet principal a changé. La "
+"conversion de ce format se fait automatiquement."
+
+#: ../../source/more/project_format.rst:105
+msgid "Format 1.1 Changes"
+msgstr "Format 1.1 Modifications"
+
+#: ../../source/more/project_format.rst:107
+msgid "This project format was introduced in novelWriter version 0.7."
+msgstr ""
+"Ce format de projet a été introduit dans la version 0.7 de novelWriter."
+
+#: ../../source/more/project_format.rst:109
+msgid ""
+"With this format, the ``content`` folder was introduced in the project "
+"storage. Previously, all novelWriter documents were saved in a series of "
+"folders numbered from ``data_0`` to ``data_f``."
+msgstr ""
+"Avec ce format, le dossier ``content`` a été introduit dans le stockage "
+"du projet. Auparavant, tous les documents de novelWriter étaient "
+"sauvegardés dans une série de dossiers numérotés de ``data_0`` à "
+"``data_f``."
+
+#: ../../source/more/project_format.rst:112
+msgid ""
+"It also reduces the number of meta data and cache files. These files are "
+"automatically deleted if an old project is opened. This was also when "
+"the Table of Contents file was introduced. Conversion from this format "
+"is done automatically."
+msgstr ""
+"Il réduit également le nombre de métadonnées et de fichiers de cache. "
+"Ces fichiers sont automatiquement supprimés lorsqu'un ancien projet est "
+"ouvert. C'est également à cette époque que le fichier de table des "
+"matières a été introduit. La conversion de ce format se fait "
+"automatiquement."
+
+#: ../../source/more/project_format.rst:120
+msgid "Format 1.0 Changes"
+msgstr "Format 1.0 Modifications"
+
+#: ../../source/more/project_format.rst:122
+msgid ""
+"This is the original file format and project structure. It was in use up "
+"to version 0.6.3."
+msgstr ""
+"Il s'agit du format de fichier et de la structure de projet d'origine. "
+"Il a été utilisé jusqu'à la version 0.6.3."

docs/source/locales/fr/LC_MESSAGES/more/typography.po

@@ -0,0 +1,267 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 23:17+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/more/typography.rst:5
+msgid "Typographical Notes"
+msgstr "Notes typographiques"
+
+#: ../../source/more/typography.rst:12
+msgid ""
+"novelWriter has some support for typographical symbols that are not usually "
+"easily available in many text editors. This includes for instance the "
+"proper unicode quotation marks, dashes, ellipsis, thin spaces, etc. All "
+"these symbols are available from the **Insert** menu, and via keyboard "
+"shortcuts. See :ref:`docs_features_shortcuts_insert`."
+msgstr ""
+"novelWriter prend en charge certains symboles typographiques qui ne sont "
+"généralement pas disponibles dans de nombreux éditeurs de texte. Cela "
+"inclut par exemple les guillemets unicode, les tirets, les ellipses, les "
+"espaces fins, etc. Tous ces symboles sont disponibles dans le menu "
+"**Insérer**, et via des raccourcis clavier. Voir :ref:"
+"`docs_features_shortcuts_insert`."
+
+#: ../../source/more/typography.rst:17
+msgid ""
+"This chapter provides some additional information on how novelWriter "
+"handles these symbols."
+msgstr ""
+"Ce chapitre fournit des informations supplémentaires sur la manière dont "
+"novelWriter gère ces symboles."
+
+#: ../../source/more/typography.rst:21
+msgid "Dashes and Ellipsis"
+msgstr "Tirets et points de suspension"
+
+#: ../../source/more/typography.rst:23
+msgid ""
+"With the auto-replace feature enabled (see :ref:`docs_ui_edit_view_auto`), "
+"two and three hyphens are converted automatically to short and long dashes, "
+"four hyphens to a horizontal bar, and three dots to ellipsis."
+msgstr ""
+"Lorsque la fonction de remplacement automatique est activée (voir :ref:"
+"`docs_ui_edit_view_auto`), les deux et trois traits d'union sont "
+"automatiquement convertis en tirets demi-cadratin et cadratin, les quatre "
+"traits d'union en barre horizontale et les trois points en points de "
+"suspension."
+
+#: ../../source/more/typography.rst:29
+msgid ""
+"The last auto-replace can always be reverted with the undo command :kbd:"
+"`Ctrl+Z`, reverting the text to what you typed before the automatic "
+"replacement occurred."
+msgstr ""
+"Le dernier remplacement automatique peut toujours être annulé avec la "
+"commande d'annulation :kbd:`Ctrl+Z`, rétablissant le texte tel qu'il était "
+"avant le remplacement automatique."
+
+#: ../../source/more/typography.rst:32
+msgid ""
+"In addition, \"Figure Dash\" is available. The Figure Dash is a dash that "
+"has the same width as the numbers of the same font, for most fonts. It "
+"helps to align numbers nicely in columns when you need to use a dash in "
+"them."
+msgstr ""
+"En outre, le « tiret chiffré » est disponible. Il s'agit d'un tiret de la "
+"même largeur que les chiffres de la même police, pour la plupart des "
+"polices. Il permet de bien aligner les chiffres dans les colonnes lorsque "
+"vous devez utiliser un tiret."
+
+#: ../../source/more/typography.rst:38
+msgid "Single and Double Quotes"
+msgstr "Guillemets simples et doubles"
+
+#: ../../source/more/typography.rst:40
+msgid ""
+"All the different quotation marks listed on the `Quotation Mark`_ Wikipedia "
+"page are available, and can be selected as auto-replaced symbols for "
+"straight single and double quote key strokes. The settings can be found in "
+"**Preferences**."
+msgstr ""
+"Tous les différents guillemets listés sur la page Wikipedia `Quotation "
+"Mark`_ sont disponibles, et peuvent être sélectionnés comme symboles auto-"
+"remplacés pour les touches de guillemets simples et doubles. Les réglages "
+"se trouvent dans les **Préférences**."
+
+#: ../../source/more/typography.rst:44
+msgid ""
+"If your text contains straight single and double quotes, there are two "
+"convenience functions in the **Format** menu that can be used to re-format "
+"a selected section of text with the correct quote symbols."
+msgstr ""
+"Si votre texte contient des guillemets simples et doubles, deux fonctions "
+"pratiques du menu **Format** permettent de reformater une section de texte "
+"sélectionnée avec les symboles de guillemets corrects."
+
+#: ../../source/more/typography.rst:48
+msgid ""
+"You can enable dialogue recognition and colour highlighting for novel "
+"documents. See :ref:`docs_features_dialogue` for more details."
+msgstr ""
+"Vous pouvez activer la reconnaissance du dialogue et la mise en évidence "
+"des couleurs pour les nouveaux documents. Voir :ref:"
+"`docs_features_dialogue` pour plus de détails."
+
+#: ../../source/more/typography.rst:53
+msgid "Single and Double Prime"
+msgstr "Simple et double prime"
+
+#: ../../source/more/typography.rst:55
+msgid ""
+"Both single and double prime symbols are available in the **Insert** menu. "
+"These symbols are the correct symbols to use for unit symbols for feet, "
+"inches, minutes, and seconds. The usage of these is described in more "
+"detail on the Wikipedia Prime_ page. They look very similar to single and "
+"double straight quotes, and may be rendered similarly by the font, but they "
+"have different codes. Using these correctly will also prevent the auto-"
+"replace and dialogue highlighting features misunderstanding their meaning "
+"in the text."
+msgstr ""
+"Les symboles de prime simple et double sont disponibles dans le menu "
+"**Insérer**. Ces symboles sont les symboles corrects à utiliser pour les "
+"symboles d'unités pour les pieds, les pouces, les minutes et les secondes. "
+"L'utilisation de ces symboles est décrite plus en détail sur la page Prime_ "
+"de Wikipedia. Ils ressemblent beaucoup aux guillemets simples et doubles et "
+"peuvent être rendus de la même manière par la police, mais ils ont des "
+"codes différents. En les utilisant correctement, vous éviterez que les "
+"fonctions de remplacement automatique et de mise en évidence des dialogues "
+"ne se méprennent sur leur signification dans le texte."
+
+#: ../../source/more/typography.rst:66
+msgid "Modifier Letter Apostrophe"
+msgstr "Modificateur Lettre Apostrophe"
+
+#: ../../source/more/typography.rst:68
+msgid ""
+"The auto-replace feature will consider any right-facing single straight "
+"quote as a quote symbol, even if it is intended as an apostrophe. This also "
+"includes the syntax highlighter, which may assume the first following "
+"apostrophe is the closing symbol of a single quoted region of text."
+msgstr ""
+"La fonction de remplacement automatique considère tout guillemet droit "
+"simple orienté vers la droite comme un symbole de guillemet, même s'il "
+"s'agit d'une apostrophe. Cela s'applique également à l'outil de mise en "
+"évidence de la syntaxe, qui peut supposer que la première apostrophe qui "
+"suit est le symbole de fermeture d'une région de texte entre guillemets."
+
+#: ../../source/more/typography.rst:72
+msgid ""
+"To get around this, an alternative apostrophe is available. It is a special "
+"Unicode character that is not categorised as punctuation, but as a "
+"modifier. It is usually rendered the same way as the right single quotation "
+"marks, depending on the font. There is a Wikipedia article for the "
+"`Modifier letter apostrophe`_ with more details."
+msgstr ""
+"Pour contourner ce problème, il existe une apostrophe alternative. Il "
+"s'agit d'un caractère Unicode spécial qui n'est pas considéré comme une "
+"ponctuation, mais comme un modificateur. Il est généralement rendu de la "
+"même manière que les guillemets simples de droite, en fonction de la police "
+"de caractères. Il existe un article de Wikipédia sur la `lettre "
+"modificatrice apostrophe`_ avec plus de détails."
+
+#: ../../source/more/typography.rst:79
+msgid ""
+"On export with the **Build Manuscript** tool, these apostrophes will be "
+"replaced automatically with the corresponding right hand single quote "
+"symbol as is generally recommended. Therefore it doesn't really matter if "
+"you only use them to correct syntax highlighting in some places, and not "
+"others."
+msgstr ""
+"Lors de l'exportation à l'aide de l'outil **Compiler le manuscrit**, ces "
+"apostrophes seront automatiquement remplacées par le symbole de guillemet "
+"simple de droite correspondant, comme cela est généralement recommandé. Par "
+"conséquent, il importe peu que vous les utilisiez uniquement pour corriger "
+"la coloration syntaxique à certains endroits, et pas à d'autres."
+
+#: ../../source/more/typography.rst:86
+msgid "White Space Symbols"
+msgstr "Symboles de l'espace"
+
+#: ../../source/more/typography.rst:88
+msgid ""
+"A few variations of the regular space character is supported. The correct "
+"typographical way to separate a number from its unit is with a `thin "
+"space`_. It is usually 2/3 the width of a regular space. For numbers and "
+"units, this should in addition be a non-breaking space, that is, the text "
+"wrapping should not add a line break on this particular space."
+msgstr ""
+"Quelques variations du caractère espace régulier sont prises en charge. La "
+"manière typographique correcte de séparer un nombre de son unité est "
+"d'utiliser une `espace fine`_. Sa largeur est généralement égale aux deux "
+"tiers de celle d'une espace normale. Pour les nombres et les unités, il "
+"doit en outre s'agir d'un espace insécable, c'est-à-dire que l'habillage du "
+"texte ne doit pas ajouter de saut de ligne sur cet espace particulier."
+
+#: ../../source/more/typography.rst:93
+msgid "A regular space can also be made into a non-breaking space if needed."
+msgstr ""
+"Un espace régulier peut également être transformé en espace insécable si "
+"nécessaire."
+
+#: ../../source/more/typography.rst:95
+msgid ""
+"All non-breaking spaces are highlighted with a differently coloured "
+"background to make it easier to spot them in the text. The colour will "
+"depend on the selected colour theme."
+msgstr ""
+"Tous les espaces insécables sont mis en évidence par un arrière-plan de "
+"couleur différente pour faciliter leur repérage dans le texte. La couleur "
+"dépend du thème de couleur sélectionné."
+
+#: ../../source/more/typography.rst:98
+msgid ""
+"You can insert these spaces in your text using the following keyboard "
+"combinations:"
+msgstr ""
+"Vous pouvez insérer ces espaces dans votre texte en utilisant les "
+"combinaisons de clavier suivantes :"
+
+#: ../../source/more/typography.rst:100
+msgid "A non-breaking space can be inserted with :kbd:`Ctrl+K`, :kbd:`Space`."
+msgstr ""
+"Un espace insécable peut être inséré avec :kbd:`Ctrl+K`, :kbd:`Espace`."
+
+#: ../../source/more/typography.rst:101
+msgid ""
+"Thin spaces are also supported, and can be inserted with :kbd:`Ctrl+K`, :"
+"kbd:`Shift+Space`."
+msgstr ""
+"Les espaces courtes sont également supportés, et peuvent être insérés avec :"
+"kbd:`Ctrl+K`, :kbd:`Maj+Espace`."
+
+#: ../../source/more/typography.rst:102
+msgid ""
+"Non-breaking thin space can be inserted with :kbd:`Ctrl+K`, :kbd:"
+"`Ctrl+Space`."
+msgstr ""
+"Une espace courte insécable peut être insérée avec :kbd:`Ctrl+K`, :kbd:"
+"`Ctrl+Espace`."
+
+#: ../../source/more/typography.rst:104
+msgid ""
+"These are all insert features, and the **Insert** menu has more. The "
+"keyboard shortcuts for them are also listed in :ref:"
+"`docs_features_shortcuts`."
+msgstr ""
+"Ce sont toutes des fonctions d'insertion, et le menu **Insérer** en propose "
+"d'autres. Les raccourcis clavier sont également listés dans :ref:"
+"`docs_features_shortcuts`."

docs/source/locales/fr/LC_MESSAGES/technical/locations.po

@@ -0,0 +1,158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:25+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/technical/locations.rst:5
+msgid "File Locations"
+msgstr "Emplacement des fichiers"
+
+#: ../../source/technical/locations.rst:9
+msgid ""
+"novelWriter will create a few files on your system outside of the "
+"application folder itself. These file locations are described in this "
+"chapter."
+msgstr ""
+"novelWriter créera quelques fichiers sur votre système en dehors du "
+"dossier de l'application elle-même. L'emplacement de ces fichiers est "
+"décrit dans ce chapitre."
+
+#: ../../source/technical/locations.rst:16
+msgid "Configuration"
+msgstr "Configuration"
+
+#: ../../source/technical/locations.rst:18
+msgid ""
+"The general configuration of novelWriter, including everything that is "
+"in **Preferences**, is saved in one central configuration file. The "
+"location of this file depends on your operating system. The system paths "
+"are provided by the Qt QStandardPaths_ class and its ``ConfigLocation`` "
+"value."
+msgstr ""
+"La configuration générale de novelWriter, y compris tout ce qui se "
+"trouve dans les **Préférences**, est enregistrée dans un fichier de "
+"configuration central. L'emplacement de ce fichier dépend de votre "
+"système d'exploitation. Les chemins d'accès au système sont fournis par "
+"la classe Qt QStandardPaths_ et sa valeur ``ConfigLocation``."
+
+#: ../../source/technical/locations.rst:22
+#: ../../source/technical/locations.rst:45
+msgid "The standard paths are:"
+msgstr "Les chemins standard sont les suivants :"
+
+#: ../../source/technical/locations.rst:24
+msgid "Linux: ``~/.config/novelwriter/novelwriter.conf``"
+msgstr "Linux : ``~/.config/novelwriter/novelwriter.conf``"
+
+#: ../../source/technical/locations.rst:25
+msgid "MacOS: ``~/Library/Preferences/novelwriter/novelwriter.conf``"
+msgstr "MacOS: ``~/Library/Preferences/novelwriter/novelwriter.conf``"
+
+#: ../../source/technical/locations.rst:26
+msgid ""
+"Windows: ``C:\\Users\\<USER>\\AppData\\Local\\novelwriter\\novelwriter."
+"conf``"
+msgstr ""
+"Windows: ``C:\\Users\\<USER>\\AppData\\Local\\novelwriter\\novelwriter."
+"conf``"
+
+#: ../../source/technical/locations.rst:28
+#: ../../source/technical/locations.rst:51
+msgid ""
+"Here, ``~`` corresponds to the user's home directory on Linux and MacOS, "
+"and ``<USER>`` is the user's username on Windows."
+msgstr ""
+"Ici, ``~`` correspond au répertoire personnel de l'utilisateur sous "
+"Linux et MacOS, et ``<USER>`` est le nom d'utilisateur de l'utilisateur "
+"sous Windows."
+
+#: ../../source/technical/locations.rst:32
+#: ../../source/technical/locations.rst:55
+msgid ""
+"These are the standard operating system defined locations. If your "
+"system has been set up in a different way, these locations may also be "
+"different."
+msgstr ""
+"Il s'agit des emplacements standard définis par le système "
+"d'exploitation. Si votre système a été configuré différemment, ces "
+"emplacements peuvent également être différents."
+
+#: ../../source/technical/locations.rst:39
+msgid "Application Data"
+msgstr "Données d'application"
+
+#: ../../source/technical/locations.rst:41
+msgid ""
+"novelWriter also stores a bit of data that is generated by the user's "
+"actions. This includes the list of recent projects form the **Welcome** "
+"dialog. Custom themes should also be saved here. The system paths are "
+"provided by the Qt QStandardPaths_ class and its ``AppDataLocation`` "
+"value."
+msgstr ""
+"novelWriter stocke également un certain nombre de données générées par "
+"les actions de l'utilisateur. Cela inclut la liste des projets récents "
+"de la boîte de dialogue **Bienvenue**. Les thèmes personnalisés "
+"devraient également être sauvegardés ici. Les chemins d'accès au système "
+"sont fournis par la classe Qt QStandardPaths_ et sa valeur "
+"``AppDataLocation``."
+
+#: ../../source/technical/locations.rst:47
+msgid "Linux: ``~/.local/share/novelwriter/``"
+msgstr "Linux: ``~/.local/share/novelwriter/``"
+
+#: ../../source/technical/locations.rst:48
+msgid "MacOS: ``~/Library/Application Support/novelwriter/``"
+msgstr "MacOS: ``~/Library/Application Support/novelwriter/``"
+
+#: ../../source/technical/locations.rst:49
+msgid "Windows: ``C:\\Users\\<USER>\\AppData\\Roaming\\novelwriter\\``"
+msgstr "Windows: ``C:\\Users\\<USER>\\AppData\\Roaming\\novelwriter\\``"
+
+#: ../../source/technical/locations.rst:58
+msgid "The Application Data location also holds several folders:"
+msgstr ""
+"L'emplacement des données d'application contient également plusieurs "
+"dossiers :"
+
+#: ../../source/technical/locations.rst:60
+msgid "``cache``"
+msgstr "``cache``"
+
+#: ../../source/technical/locations.rst:61
+msgid ""
+"This folder is used to save the preview data for the **Manuscript "
+"Build** tool."
+msgstr ""
+"Ce dossier est utilisé pour enregistrer les données de prévisualisation "
+"pour l'outil **Compilation de manuscrit**."
+
+#: ../../source/technical/locations.rst:63
+msgid "``icons``, ``syntax`` and ``themes``"
+msgstr "``icons``, ``syntax`` and ``themes``"
+
+#: ../../source/technical/locations.rst:64
+msgid ""
+"These folders are empty by default, but this is where the user can store "
+"custom theme files. See :ref:`docs_more_custom` for more details."
+msgstr ""
+"Ces dossiers sont vides par défaut, mais c'est là que l'utilisateur peut "
+"stocker des fichiers de thèmes personnalisés. Voir :ref:"
+"`docs_more_custom` pour plus de détails."

docs/source/locales/fr/LC_MESSAGES/technical/source.po

@@ -0,0 +1,283 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:39+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/technical/source.rst:5
+msgid "Running from Source"
+msgstr "Exécuter depuis la source"
+
+#: ../../source/technical/source.rst:11
+msgid ""
+"This chapter describes various ways of running novelWriter directly from "
+"the source code, and how to build the various components like the "
+"translation files and documentation."
+msgstr ""
+"Ce chapitre décrit les différentes façons d'exécuter novelWriter "
+"directement à partir du code source, et comment construire les "
+"différents composants tels que les fichiers de traduction et la "
+"documentation."
+
+#: ../../source/technical/source.rst:16
+msgid ""
+"The text below assumes the command ``python`` corresponds to a Python 3 "
+"executable. Python 2 is now deprecated, but on many systems the command "
+"``python3`` may be needed instead. Likewise, ``pip`` may need to be "
+"replaced with ``pip3``."
+msgstr ""
+"Le texte ci-dessous suppose que la commande ``python`` correspond à un "
+"exécutable Python 3. Python 2 est maintenant déprécié, mais sur de "
+"nombreux systèmes, la commande ``python3`` peut être utilisée à la "
+"place. De même, ``pip`` peut être remplacé par ``pip3``."
+
+#: ../../source/technical/source.rst:20
+msgid ""
+"Most of the custom commands for building packages of novelWriter, or "
+"building assets, are contained in the ``pkgutils.py`` script in the root "
+"of the source code. You can list the available commands by running:"
+msgstr ""
+"La plupart des commandes personnalisées pour construire des paquets de "
+"novelWriter, ou pour construire des actifs, sont contenues dans le "
+"script ``pkgutils.py`` à la racine du code source. Vous pouvez lister "
+"les commandes disponibles en lançant :"
+
+#: ../../source/technical/source.rst:32
+msgid "Dependencies"
+msgstr "Dépendances"
+
+#: ../../source/technical/source.rst:34
+msgid ""
+"novelWriter has been designed to rely on as few dependencies as "
+"possible. Only the Python wrapper for the Qt GUI libraries is required. "
+"The package for spell checking is optional, but recommended. Everything "
+"else is handled with standard Python libraries."
+msgstr ""
+"novelWriter a été conçu pour s'appuyer sur le moins de dépendances "
+"possible. Seul le wrapper Python pour les bibliothèques Qt GUI est "
+"nécessaire. Le paquetage pour la vérification orthographique est "
+"optionnel, mais recommandé. Tout le reste est géré par les bibliothèques "
+"Python standard."
+
+#: ../../source/technical/source.rst:38
+msgid ""
+"The following Python packages are needed to run all features of "
+"novelWriter:"
+msgstr ""
+"Les paquets Python suivants sont nécessaires pour exécuter toutes les "
+"fonctionnalités de novelWriter :"
+
+#: ../../source/technical/source.rst:40
+msgid "``PyQt6`` – needed for connecting with the Qt6 libraries."
+msgstr "``PyQt6`` - nécessaire pour se connecter aux bibliothèques Qt6."
+
+#: ../../source/technical/source.rst:41
+msgid "``PyEnchant`` – needed for spell checking (optional)."
+msgstr ""
+"``PyEnchant`` - nécessaire pour la vérification orthographique "
+"(optionnel)."
+
+#: ../../source/technical/source.rst:43
+msgid ""
+"If you want spell checking, you must install the ``PyEnchant`` package. "
+"The spell check library must be at least 3.0 to work with Windows. On "
+"Linux, 2.0 also works fine."
+msgstr ""
+"Si vous voulez un correcteur orthographique, vous devez installer le "
+"paquet ``PyEnchant``. La bibliothèque de vérification orthographique "
+"doit être au moins en version 3.0 pour fonctionner sous Windows. Sous "
+"Linux, la version 2.0 fonctionne également très bien."
+
+#: ../../source/technical/source.rst:46
+msgid ""
+"If you install from PyPi, these dependencies should be installed "
+"automatically. If you install from source, dependencies can still be "
+"installed from PyPi with:"
+msgstr ""
+"Si vous installez à partir de PyPi, ces dépendances devraient être "
+"installées automatiquement. Si vous installez à partir des sources, les "
+"dépendances peuvent toujours être installées à partir de PyPi avec :"
+
+#: ../../source/technical/source.rst:55
+msgid ""
+"On Linux distros, the Qt library is usually split up into multiple "
+"packages. In some cases, secondary dependencies may not be installed "
+"automatically. For novelWriter, the library files for rendering the SVG "
+"icons may be left out and needs to be installed manually. This is the "
+"case on for instance Arch Linux."
+msgstr ""
+"Sur les distributions Linux, la bibliothèque Qt est généralement divisée "
+"en plusieurs paquets. Dans certains cas, des dépendances secondaires "
+"peuvent ne pas être installées automatiquement. Pour novelWriter, les "
+"fichiers de la bibliothèque pour le rendu des icônes SVG peuvent être "
+"omis et doivent être installés manuellement. C'est le cas, par exemple, "
+"sous Arch Linux."
+
+#: ../../source/technical/source.rst:64
+msgid "Build and Install from Source"
+msgstr "Compiler et installer à partir des sources"
+
+#: ../../source/technical/source.rst:66
+msgid ""
+"If you want to install novelWriter directly from the source available on "
+"GitHub_, you must first build the package using the Python Packaging "
+"Authority's build tool. It can be installed with:"
+msgstr ""
+"Si vous souhaitez installer novelWriter directement à partir des sources "
+"disponibles sur GitHub_, vous devez d'abord construire le paquet à "
+"l'aide de l'outil de construction de la Python Packaging Authority. Il "
+"peut être installé avec :"
+
+#: ../../source/technical/source.rst:73
+msgid "On Debian-based systems the tool can also be installed with:"
+msgstr ""
+"Sur les systèmes basés sur Debian, l'outil peut également être installé "
+"avec :"
+
+#: ../../source/technical/source.rst:79
+msgid ""
+"With the tool installed, run the following command from the root of the "
+"novelWriter source code:"
+msgstr ""
+"Une fois l'outil installé, exécutez la commande suivante à partir de la "
+"racine du code source de novelWriter :"
+
+#: ../../source/technical/source.rst:85
+msgid ""
+"This should generate a ``.whl`` file in the ``dist/`` folder at your "
+"current location. The wheel file can then be installed on your system. "
+"Here with example version number 2.0.7, but yours may be different:"
+msgstr ""
+"Cela devrait générer un fichier ``.whl`` dans le dossier ``dist/`` de "
+"votre emplacement actuel. Le fichier wheel peut alors être installé sur "
+"votre système. Ici avec l'exemple de la version numéro 2.0.7, mais la "
+"vôtre peut être différente :"
+
+#: ../../source/technical/source.rst:97
+msgid "Building the Translation Files"
+msgstr "Création des fichiers de traduction"
+
+#: ../../source/technical/source.rst:99
+msgid ""
+"If you installed novelWriter from a package, the translation files "
+"should be pre-built and included. If you're running novelWriter from the "
+"source code, you will need to generate the files yourself. The files you "
+"need will be written to the ``novelwriter/assets/i18n`` folder, and will "
+"have the ``.qm`` file extension."
+msgstr ""
+"Si vous avez installé novelWriter à partir d'un paquetage, les fichiers "
+"de traduction devraient être préconstruits et inclus. Si vous exécutez "
+"novelWriter à partir du code source, vous devrez générer les fichiers "
+"vous-même. Les fichiers dont vous avez besoin seront écrits dans le "
+"dossier ``novelwriter/assets/i18n``, et auront l'extension ``.qm``."
+
+#: ../../source/technical/source.rst:104
+msgid "You can build the ``.qm`` files with:"
+msgstr "Vous pouvez construire les fichiers ``.qm`` avec :"
+
+#: ../../source/technical/source.rst:110
+msgid ""
+"This requires that the Qt Linguist tool is installed on your system. On "
+"Ubuntu and Debian, the needed package is called ``qttools5-dev-tools``."
+msgstr ""
+"Cela nécessite que l'outil Qt Linguist soit installé sur votre système. "
+"Sur Ubuntu et Debian, le paquet nécessaire s'appelle ``qttools5-dev-"
+"tools``."
+
+#: ../../source/technical/source.rst:115
+msgid ""
+"If you want to improve novelWriter with translation files for another "
+"language, or update an existing translation, instructions for how to "
+"contribute can be found in the ``README.md`` file in the ``i18n`` folder "
+"of the source code."
+msgstr ""
+"Si vous voulez améliorer novelWriter avec des fichiers de traduction "
+"pour une autre langue, ou mettre à jour une traduction existante, les "
+"instructions pour contribuer peuvent être trouvées dans le fichier "
+"``README.md`` dans le dossier ``i18n`` du code source."
+
+#: ../../source/technical/source.rst:123
+msgid "Building the Example Project"
+msgstr "Construction du projet d'exemple"
+
+#: ../../source/technical/source.rst:125
+msgid ""
+"In order to be able to create new projects from example files, you need "
+"a ``sample.zip`` file in the ``assets`` folder of the source. This file "
+"can be built from the ``pkgutils.py`` script by running:"
+msgstr ""
+"Afin de pouvoir créer de nouveaux projets à partir des fichiers "
+"d'exemple, vous avez besoin d'un fichier ``sample.zip`` dans le dossier "
+"``assets`` de la source. Ce fichier peut être construit à partir du "
+"script ``pkgutils.py`` en exécutant :"
+
+#: ../../source/technical/source.rst:137
+msgid "Building the Documentation"
+msgstr "Élaboration de la documentation"
+
+#: ../../source/technical/source.rst:139
+msgid ""
+"A local copy of this documentation can be generated as HTML. This "
+"requires installing some Python packages from PyPi:"
+msgstr ""
+"Une copie locale de cette documentation peut être générée au format "
+"HTML. Cela nécessite l'installation de certains paquets Python à partir "
+"de PyPi :"
+
+#: ../../source/technical/source.rst:146
+msgid ""
+"The documentation can then be built from the root folder in the source "
+"code by running:"
+msgstr ""
+"La documentation peut ensuite être créée à partir du dossier racine du "
+"code source en lançant le programme :"
+
+#: ../../source/technical/source.rst:152
+msgid ""
+"If successful, the documentation should be available in the ``docs/build/"
+"html`` folder and you can open the ``index.html`` file in your browser."
+msgstr ""
+"En cas de succès, la documentation devrait être disponible dans le "
+"dossier `docs/build/html` et vous pouvez ouvrir le fichier `index.html` "
+"dans votre navigateur."
+
+#: ../../source/technical/source.rst:155
+msgid ""
+"You can also build a PDF manual from the documentation using the "
+"``pkgutils.py`` script:"
+msgstr ""
+"Vous pouvez également créer un manuel PDF à partir de la documentation "
+"en utilisant le script ``pkgutils.py`` :"
+
+#: ../../source/technical/source.rst:161
+msgid ""
+"This will build the English documentation as a PDF using LaTeX. The file "
+"will then be copied into the assets folder and made available in the "
+"**Help** menu in novelWriter. Replace ``en`` with ``all`` to build for "
+"all languages. The Sphinx build system has a few extra dependencies when "
+"building the PDF. Please check the `Sphinx Docs`_ for more details."
+msgstr ""
+"Cela permettra de créer la documentation anglaise au format PDF en "
+"utilisant LaTeX. Le fichier sera ensuite copié dans le dossier assets et "
+"rendu disponible dans le menu **Aide** de novelWriter. Remplacez ``en`` "
+"par ``all`` pour construire pour toutes les langues. Le système de "
+"construction Sphinx a quelques dépendances supplémentaires lors de la "
+"construction du PDF. Veuillez consulter la `Docs Sphinx`_ pour plus de "
+"détails."

docs/source/locales/fr/LC_MESSAGES/technical/storage.po

@@ -0,0 +1,501 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:33+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/technical/storage.rst:5
+msgid "How Data is Stored"
+msgstr "Comment les données sont stockées"
+
+#: ../../source/technical/storage.rst:9
+msgid ""
+"This chapter contains details of how novelWriter stores and handles the "
+"project data."
+msgstr ""
+"Ce chapitre contient des détails sur la manière dont novelWriter stocke "
+"et gère les données du projet."
+
+#: ../../source/technical/storage.rst:13
+msgid "Overview"
+msgstr "Présentation générale"
+
+#: ../../source/technical/storage.rst:15
+msgid ""
+"The files of a novelWriter project are stored in a dedicated project "
+"folder. The project structure is kept in a file at the root of this "
+"folder called ``nwProject.nwx``. All the document files and associated "
+"meta data are stored in other folders below the project folder."
+msgstr ""
+"Les fichiers d'un projet novelWriter sont stockés dans un dossier dédié "
+"au projet. La structure du projet est conservée dans un fichier à la "
+"racine de ce dossier appelé ``nwProject.nwx``. Tous les fichiers de "
+"documents et les métadonnées associées sont stockés dans d'autres "
+"dossiers sous le dossier du projet."
+
+#: ../../source/technical/storage.rst:19
+msgid "This way of storing data was chosen for several reasons."
+msgstr ""
+"Ce mode de stockage des données a été choisi pour plusieurs raisons."
+
+#: ../../source/technical/storage.rst:21
+msgid ""
+"Firstly, all the text you add to your project is saved directly to your "
+"project folder in separate files. Only the project structure and the "
+"text you are currently editing is stored in memory at any given time, "
+"which means there is a smaller risk of losing data if the application or "
+"your computer crashes."
+msgstr ""
+"Tout d'abord, tout le texte que vous ajoutez à votre projet est "
+"enregistré directement dans le dossier de votre projet, dans des "
+"fichiers séparés. Seule la structure du projet et le texte que vous êtes "
+"en train d'éditer sont stockés en mémoire à un moment donné, ce qui "
+"signifie qu'il y a moins de risque de perdre des données si "
+"l'application ou votre ordinateur tombe en panne."
+
+#: ../../source/technical/storage.rst:26
+msgid ""
+"Secondly, having multiple small files means it is very easy to "
+"synchronise them between computers with standard file synchronisation "
+"tools."
+msgstr ""
+"Deuxièmement, le fait d'avoir plusieurs petits fichiers signifie qu'il "
+"est très facile de les synchroniser entre ordinateurs à l'aide d'outils "
+"de synchronisation de fichiers standard."
+
+#: ../../source/technical/storage.rst:29
+msgid ""
+"Thirdly, if you use `version control`_ software to track the changes to "
+"your project, the file formats used for the files are well suited. All "
+"the JSON documents have line breaks and indents as well, which makes it "
+"easier to track them with version control software."
+msgstr ""
+"Troisièmement, si vous utilisez un logiciel de `contrôle de version`_ "
+"pour suivre les modifications apportées à votre projet, les formats "
+"utilisés pour les fichiers sont bien adaptés. Tous les documents JSON "
+"comportent des sauts de ligne et des retraits, ce qui facilite leur "
+"suivi avec un logiciel de contrôle de version."
+
+#: ../../source/technical/storage.rst:35
+msgid ""
+"Since novelWriter has to keep track of a bunch of files and folders when "
+"a project is open, it may not run well on some virtual file systems. A "
+"file or folder must be accessible with exactly the path it was saved or "
+"created with. An example where this is not the case is the way Google "
+"Drive is mapped on Linux Gnome desktops using gvfs/gio."
+msgstr ""
+"Comme novelWriter doit garder la trace d'un grand nombre de fichiers et "
+"de dossiers lorsqu'un projet est ouvert, il peut ne pas fonctionner "
+"correctement sur certains systèmes de fichiers virtuels. Un fichier ou "
+"un dossier doit être accessible avec exactement le chemin avec lequel il "
+"a été sauvegardé ou créé. Un exemple où ce n'est pas le cas est la façon "
+"dont Google Drive est mappé sur les bureaux Linux Gnome en utilisant "
+"gvfs/gio."
+
+#: ../../source/technical/storage.rst:42
+msgid ""
+"You should not add additional files to the project folder yourself. Nor "
+"should you, as a rule, manually edit files within it. If you really must "
+"manually edit the text files, e.g. with some automated task you want to "
+"perform, you need to rebuild the Project Index when you open the project "
+"again."
+msgstr ""
+"Vous ne devez pas ajouter vous-même des fichiers supplémentaires au "
+"dossier du projet. En règle générale, vous ne devez pas non plus "
+"modifier manuellement les fichiers qui s'y trouvent. Si vous devez "
+"vraiment modifier manuellement les fichiers texte, par exemple dans le "
+"cadre d'une tâche automatisée, vous devez reconstruire l'index du projet "
+"lorsque vous ouvrez à nouveau le projet."
+
+#: ../../source/technical/storage.rst:47
+msgid ""
+"Editing text files in the ``content`` folder is less risky as these are "
+"just plain text. Editing the main project XML file, however, may make "
+"the project file unreadable and you may crash novelWriter and lose "
+"project structure information and project settings."
+msgstr ""
+"L'édition de fichiers texte dans le dossier ``content`` est moins "
+"risquée car il s'agit de texte simple. Cependant, éditer le fichier XML "
+"du projet principal peut rendre le fichier du projet illisible et vous "
+"risquez de planter novelWriter et de perdre les informations sur la "
+"structure et les paramètres du projet."
+
+#: ../../source/technical/storage.rst:53
+msgid "Project Structure"
+msgstr "Structure du projet"
+
+#: ../../source/technical/storage.rst:55
+msgid ""
+"All novelWriter files are written with utf-8 encoding. Since Python "
+"automatically converts Unix line endings to Windows line endings on "
+"Windows systems, novelWriter does not make any adaptations to the "
+"formatting on Windows systems. This is handled entirely by the Python "
+"standard library. Python also handles this when working on the same "
+"files on both Windows and Unix-based operating systems."
+msgstr ""
+"Tous les fichiers novelWriter sont écrits avec l'encodage utf-8. Comme "
+"Python convertit automatiquement les fins de ligne Unix en fins de ligne "
+"Windows sur les systèmes Windows, novelWriter ne fait aucune adaptation "
+"au formatage sur les systèmes Windows. Ceci est entièrement géré par la "
+"bibliothèque standard de Python. Python s'en occupe également lorsqu'il "
+"travaille sur les mêmes fichiers sur les systèmes d'exploitation Windows "
+"et Unix."
+
+#: ../../source/technical/storage.rst:63
+msgid "Main Project File"
+msgstr "Fichier principal du projet"
+
+#: ../../source/technical/storage.rst:65
+msgid ""
+"The project itself requires a dedicated folder for storing its files, "
+"where novelWriter will create its own \"file system\" where the "
+"project's folder and file hierarchy is described in a project XML file. "
+"This is the main project file in the project's root folder with the name "
+"``nwProject.nwx``. This file also contains all the meta data required "
+"for the project (except the index data), and a number of related project "
+"settings."
+msgstr ""
+"Le projet lui-même nécessite un dossier dédié pour stocker ses fichiers, "
+"où novelWriter créera son propre « système de fichiers » où la "
+"hiérarchie des dossiers et des fichiers du projet est décrite dans un "
+"fichier XML du projet. C'est le fichier principal du projet dans le "
+"dossier racine du projet avec le nom ``nwProject.nwx``. Ce fichier "
+"contient également toutes les métadonnées requises pour le projet (à "
+"l'exception des données d'index), ainsi qu'un certain nombre de "
+"paramètres liés au projet."
+
+#: ../../source/technical/storage.rst:71
+msgid ""
+"If this file is lost or corrupted, the structure of the project is lost, "
+"although not the text itself. It is important to keep this file backed "
+"up, either through the built-in backup tool, or your own backup solution."
+msgstr ""
+"Si ce fichier est perdu ou corrompu, la structure du projet est perdue, "
+"mais pas le texte lui-même. Il est important de sauvegarder ce fichier, "
+"soit à l'aide de l'outil de sauvegarde intégré, soit à l'aide de votre "
+"propre solution de sauvegarde."
+
+#: ../../source/technical/storage.rst:75
+msgid ""
+"The project XML file is indent-formatted, and is suitable for diff tools "
+"and version control since most of the file will stay static, although a "
+"timestamp is set in the meta section on line 2, and various meta data "
+"entries incremented, on each save."
+msgstr ""
+"Le fichier XML du projet est formaté en indentation et convient aux "
+"outils de comparaison et de contrôle de version, car la majeure partie "
+"du fichier reste statique, bien qu'un horodatage soit défini dans la "
+"section méta à la ligne 2 et que diverses entrées de données méta soient "
+"incrémentées à chaque enregistrement."
+
+#: ../../source/technical/storage.rst:79
+msgid ""
+"A full project file format specification is available under \"More "
+"Documents\"."
+msgstr ""
+"Une spécification complète du format de fichier du projet est disponible "
+"sous « Plus d'informations »."
+
+#: ../../source/technical/storage.rst:83
+msgid "Project Documents"
+msgstr "Documents de projet"
+
+#: ../../source/technical/storage.rst:85
+msgid ""
+"All the project documents are saved in a subfolder of the main project "
+"folder named ``content``. Each document has a file handle based on a 52 "
+"bit random number, represented as a hexadecimal string. The documents "
+"are saved with a filename assembled from this handle and the file "
+"extension ``.nwd``."
+msgstr ""
+"Tous les documents du projet sont enregistrés dans un sous-dossier du "
+"dossier principal du projet nommé ``content``. Chaque document possède "
+"un identifiant de fichier basé sur un nombre aléatoire de 52 bits, "
+"représenté sous la forme d'une chaîne hexadécimale. Les documents sont "
+"enregistrés avec un nom de fichier assemblé à partir de cet identifiant "
+"et de l'extension ``.nwd``."
+
+#: ../../source/technical/storage.rst:90
+msgid ""
+"If you wish to find the file system location of a document in the "
+"project, you can either look it up in the project XML file, select "
+"**Show File Details** from the **Document** menu when having the "
+"document open in the editor, or look in the ``ToC.txt`` file in the root "
+"of the project folder. The ``ToC.txt`` file has a list of all documents "
+"in the project, referenced by their label, and where they are saved."
+msgstr ""
+"Si vous souhaitez trouver l'emplacement du système de fichiers d'un "
+"document dans le projet, vous pouvez soit le rechercher dans le fichier "
+"XML du projet, soit sélectionner **Afficher les détails du fichier** "
+"dans le menu **Document** lorsque le document est ouvert dans l'éditeur, "
+"soit rechercher dans le fichier ``ToC.txt`` à la racine du dossier du "
+"projet. Le fichier ``ToC.txt`` contient une liste de tous les documents "
+"du projet, référencés par leur étiquette, et l'endroit où ils sont "
+"sauvegardés."
+
+#: ../../source/technical/storage.rst:96
+msgid ""
+"The reason for this cryptic file naming is to avoid issues with file "
+"naming conventions and restrictions on different operating systems, and "
+"also to have a file name that does not depend on what you name the "
+"document within the project, or changes it to. This is particularly "
+"useful when using a versioning system."
+msgstr ""
+"La raison de ce nom de fichier cryptique est d'éviter les problèmes liés "
+"aux conventions de dénomination des fichiers et aux restrictions sur les "
+"différents systèmes d'exploitation, et aussi d'avoir un nom de fichier "
+"qui ne dépend pas du nom que vous donnez au document dans le projet, ou "
+"des modifications que vous lui apportez. Ceci est particulièrement utile "
+"lors de l'utilisation d'un système de gestion des versions."
+
+#: ../../source/technical/storage.rst:101
+msgid ""
+"Each document file contains a plain text version of the text from the "
+"editor. The file can in principle be edited in any text editor, and is "
+"suitable for diffing and version control if so desired. Just make sure "
+"the file remains in utf-8 encoding, otherwise unicode characters may "
+"become mangled when the file is opened in novelWriter again."
+msgstr ""
+"Chaque fichier de document contient une version en texte brut du texte "
+"de l'éditeur. Le fichier peut en principe être édité dans n'importe quel "
+"éditeur de texte, et convient pour le diffing et le contrôle de version "
+"si on le souhaite. Assurez-vous simplement que le fichier reste en "
+"encodage utf-8, sinon les caractères unicode risquent d'être altérés "
+"lorsque le fichier est ouvert dans novelWriter."
+
+#: ../../source/technical/storage.rst:106
+msgid ""
+"Editing these files is generally not recommended. The reason for this is "
+"that the index will not be automatically updated when doing so, which "
+"means novelWriter doesn't know you've altered the file. If you *do* edit "
+"a file in this manner, you should rebuild the index when you next open "
+"the project in novelWriter."
+msgstr ""
+"Il est généralement déconseillé de modifier ces fichiers. La raison en "
+"est que l'index ne sera pas automatiquement mis à jour, ce qui signifie "
+"que novelWriter ne sait pas que vous avez modifié le fichier. Si vous "
+"modifiez un fichier de cette manière, vous devez reconstruire l'index "
+"lorsque vous ouvrez le projet dans novelWriter."
+
+#: ../../source/technical/storage.rst:111
+#, python-format
+msgid ""
+"The first lines of the file may contain some meta data starting with the "
+"characters ``%%~``. These lines are mainly there to restore some "
+"information if the file is lost from the main project file, and the "
+"information may be helpful if you do open the file in an external editor "
+"as it contains the document label and the document class and layout. The "
+"lines can be deleted without any consequences to the rest of the content "
+"of the file, and will be added back the next time the document is saved "
+"in novelWriter."
+msgstr ""
+"Les premières lignes du fichier peuvent contenir des métadonnées "
+"commençant par les caractères ``%%~``. Ces lignes sont principalement là "
+"pour restaurer certaines informations si le fichier est perdu dans le "
+"fichier principal du projet, et ces informations peuvent être utiles si "
+"vous ouvrez le fichier dans un éditeur externe car elles contiennent "
+"l'étiquette du document ainsi que la classe et la mise en page du "
+"document. Les lignes peuvent être supprimées sans conséquences pour le "
+"reste du contenu du fichier, et seront ajoutées la prochaine fois que le "
+"document sera sauvegardé dans novelWriter."
+
+#: ../../source/technical/storage.rst:120
+msgid "The File Saving Process"
+msgstr "Le processus d'enregistrement des fichiers"
+
+#: ../../source/technical/storage.rst:122
+msgid ""
+"When saving the project file, or any of the documents, the data is first "
+"saved to a temporary file. If successful, the old data file is then "
+"removed, and the temporary file replaces it. This ensures that the "
+"previously saved data is only replaced when the new data has been "
+"successfully saved to the storage medium."
+msgstr ""
+"Lors de l'enregistrement du fichier de projet ou de l'un des documents, "
+"les données sont d'abord enregistrées dans un fichier temporaire. En cas "
+"de succès, l'ancien fichier de données est alors supprimé et remplacé "
+"par le fichier temporaire. Cela garantit que les données précédemment "
+"enregistrées ne sont remplacées que lorsque les nouvelles données ont "
+"été enregistrées avec succès sur le support de stockage."
+
+#: ../../source/technical/storage.rst:129
+msgid "Project Meta Data"
+msgstr "Métadonnées du projet"
+
+#: ../../source/technical/storage.rst:131
+msgid ""
+"The project folder contains a subfolder named ``meta``, containing a "
+"number of files. The meta folder contains semi-important files. That is, "
+"they can be lost with only minor impact to the project. All files in "
+"this folder are JSON or JSON Lines files, although some other files may "
+"remain from earlier versions of novelWriter as they haven't all been "
+"JSON files in the past."
+msgstr ""
+"Le dossier du projet contient un sous-dossier nommé ``meta``, contenant "
+"un certain nombre de fichiers. Le dossier meta contient des fichiers "
+"semi-importants. C'est-à-dire qu'ils peuvent être perdus avec un impact "
+"mineur sur le projet. Tous les fichiers de ce dossier sont des fichiers "
+"JSON ou JSON Lines, bien que certains autres fichiers puissent provenir "
+"de versions antérieures de novelWriter, car ils n'ont pas tous été des "
+"fichiers JSON dans le passé."
+
+#: ../../source/technical/storage.rst:136
+msgid ""
+"If you use version control software on your project, you can exclude "
+"this folder, although you may want to track the session log file and the "
+"custom words list."
+msgstr ""
+"Si vous utilisez un logiciel de contrôle de version pour votre projet, "
+"vous pouvez exclure ce dossier, même si vous souhaitez suivre le fichier "
+"journal de la session et la liste des mots personnalisés."
+
+#: ../../source/technical/storage.rst:141
+msgid "The Project Index"
+msgstr "L'index des projets"
+
+#: ../../source/technical/storage.rst:143
+msgid ""
+"Between writing sessions, the project index is saved in a JSON file in "
+"``meta/index.json``. This file is not critical. If it is lost, it can be "
+"completely rebuilt from within novelWriter from the **Tools** menu."
+msgstr ""
+"Entre les sessions d'écriture, l'index du projet est sauvegardé dans un "
+"fichier JSON dans ``meta/index.json``. Ce fichier n'est pas critique. "
+"S'il est perdu, il peut être complètement reconstruit à partir de "
+"novelWriter dans le menu **Outils**."
+
+#: ../../source/technical/storage.rst:147
+msgid ""
+"The index is maintained and updated whenever a document or note is saved "
+"in the editor. It contains all references and tags in documents and "
+"notes, as well as the location of all headers in the project, and the "
+"word counts within each header section."
+msgstr ""
+"L'index est maintenu et mis à jour chaque fois qu'un document ou une "
+"note est enregistré dans l'éditeur. Il contient toutes les références et "
+"les balises des documents et des notes, ainsi que l'emplacement de tous "
+"les en-têtes dans le projet et le nombre de mots dans chaque section de "
+"l'en-tête."
+
+#: ../../source/technical/storage.rst:151
+msgid ""
+"The integrity of the index is checked when the file is loaded. It is "
+"possible to corrupt the index if the file is manually edited and "
+"manipulated, so the check is important to avoid sudden crashes of "
+"novelWriter. If the file contains errors, novelWriter will automatically "
+"build it anew. If the check somehow fails and novelWriter keeps "
+"crashing, you can delete the file manually and rebuild the index. If "
+"this too fails, you have likely encountered a bug."
+msgstr ""
+"L'intégrité de l'index est vérifiée lorsque le fichier est chargé. Il "
+"est possible de corrompre l'index si le fichier est édité et manipulé "
+"manuellement, c'est pourquoi cette vérification est importante pour "
+"éviter les plantages soudains de novelWriter. Si le fichier contient des "
+"erreurs, novelWriter le reconstruira automatiquement. Si la vérification "
+"échoue d'une manière ou d'une autre et que novelWriter continue à se "
+"bloquer, vous pouvez supprimer le fichier manuellement et reconstruire "
+"l'index. Si cela échoue également, vous avez probablement rencontré un "
+"bogue."
+
+#: ../../source/technical/storage.rst:159
+msgid "Build Definitions"
+msgstr "Définitions des compilations"
+
+#: ../../source/technical/storage.rst:161
+msgid ""
+"The build definitions from the **Manuscript Build** tool are kept in the "
+"``meta/builds.json`` file. If this file is lost, all custom build "
+"definitions are lost too."
+msgstr ""
+"Les définitions de construction de l'outil **Compilation du manuscrit** "
+"sont conservées dans le fichier ``meta/builds.json``. Si ce fichier est "
+"perdu, toutes les définitions de construction personnalisées sont "
+"également perdues."
+
+#: ../../source/technical/storage.rst:166
+msgid "Cached GUI Options"
+msgstr "Options de l'interface graphique mises en cache"
+
+#: ../../source/technical/storage.rst:168
+msgid ""
+"A file named ``meta/options.json`` contains the latest state of various "
+"GUI buttons, switches, dialog window sizes, column sizes, etc, from the "
+"GUI. These are the GUI settings that are specific to the project. Global "
+"GUI settings are stored in the main config file."
+msgstr ""
+"Un fichier nommé ``meta/options.json`` contient le dernier état des "
+"différents boutons de l'interface graphique, des commutateurs, de la "
+"taille des fenêtres de dialogue, de la taille des colonnes, etc, de "
+"l'interface graphique. Ce sont les paramètres de l'interface graphique "
+"qui sont spécifiques au projet. Les paramètres globaux de l'interface "
+"graphique sont stockés dans le fichier de configuration principal."
+
+#: ../../source/technical/storage.rst:172
+msgid ""
+"The file is not critical, but if it is lost, all such GUI options will "
+"revert back to their default settings."
+msgstr ""
+"Le fichier n'est pas critique, mais s'il est perdu, toutes les options "
+"de l'interface graphique reviendront à leurs paramètres par défaut."
+
+#: ../../source/technical/storage.rst:177
+msgid "Custom Word List"
+msgstr "Liste des mots personnalisés"
+
+#: ../../source/technical/storage.rst:179
+msgid ""
+"A file named ``meta/userdict.json`` contains all the custom words you've "
+"added to the project for spell checking purposes. The content of the "
+"file can be edited from the **Tools** menu. If you lose this file, all "
+"your custom spell check words will be lost too."
+msgstr ""
+"Un fichier nommé ``meta/userdict.json`` contient tous les mots "
+"personnalisés que vous avez ajoutés au projet à des fins de vérification "
+"orthographique. Le contenu de ce fichier peut être édité à partir du "
+"menu **Outils**. Si vous perdez ce fichier, tous vos mots personnalisés "
+"pour la vérification orthographique seront également perdus."
+
+#: ../../source/technical/storage.rst:185
+msgid "Session Stats"
+msgstr "Statistiques de la session"
+
+#: ../../source/technical/storage.rst:187
+msgid ""
+"The writing progress is saved in the ``meta/sessions.jsonl`` file. This "
+"file records the length and word counts of each writing session on the "
+"given project. The file is used by the **Writing Statistics** tool. If "
+"this file is lost, the history it contains is also lost, but it has "
+"otherwise no impact on the project."
+msgstr ""
+"La progression de l'écriture est sauvegardée dans le fichier ``meta/"
+"sessions.jsonl``. Ce fichier enregistre la durée et le nombre de mots de "
+"chaque session d'écriture sur le projet donné. Ce fichier est utilisé "
+"par l'outil **Statistiques d'écriture**. Si ce fichier est perdu, "
+"l'historique qu'il contient est également perdu, mais cela n'a par "
+"ailleurs aucun impact sur le projet."
+
+#: ../../source/technical/storage.rst:192
+msgid ""
+"Each session is recorded as a JSON object on a single line of the file. "
+"Each session record is appended tot he file."
+msgstr ""
+"Chaque session est enregistrée sous la forme d'un objet JSON sur une "
+"seule ligne du fichier. Chaque enregistrement de session est ajouté au "
+"fichier."

docs/source/locales/fr/LC_MESSAGES/technical/tests.po

@@ -0,0 +1,160 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 11:41+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/technical/tests.rst:5
+msgid "Running Tests"
+msgstr "Exécution des tests"
+
+#: ../../source/technical/tests.rst:7
+msgid ""
+"The novelWriter source code is well covered by tests. The test framework used "
+"for the development is ``pytest`` with the use of an extension for Qt."
+msgstr ""
+"Le code source de novelWriter est bien couvert par des tests. Le cadre de test "
+"utilisé pour le développement est ``pytest`` avec l'utilisation d'une extension "
+"pour Qt."
+
+#: ../../source/technical/tests.rst:12
+msgid "Dependencies"
+msgstr "Dépendances"
+
+#: ../../source/technical/tests.rst:14
+msgid "The dependencies for running the tests can be installed with:"
+msgstr ""
+"Les dépendances nécessaires à l'exécution des tests peuvent être installées "
+"avec :"
+
+#: ../../source/technical/tests.rst:20
+msgid ""
+"This will install a couple of extra packages for coverage and test management. "
+"The minimum requirement is ``pytest`` and ``pytest-qt``."
+msgstr ""
+"Cela installera quelques paquets supplémentaires pour la couverture et la "
+"gestion des tests. Le minimum requis est ``pytest`` et ``pytest-qt``."
+
+#: ../../source/technical/tests.rst:25
+msgid "Simple Test Run"
+msgstr "Test simple"
+
+#: ../../source/technical/tests.rst:27
+msgid ""
+"To run the tests, you simply need to execute the following from the root of the "
+"source folder:"
+msgstr ""
+"Pour exécuter les tests, il suffit d'exécuter ce qui suit à partir de la racine "
+"du dossier source :"
+
+#: ../../source/technical/tests.rst:33
+msgid ""
+"Since several of the tests involve opening up the novelWriter GUI, you may want "
+"to disable the GUI for the duration of the test run. Moving your mouse while "
+"the tests are running may otherwise interfere with the execution of some tests."
+msgstr ""
+"Puisque plusieurs des tests impliquent l'ouverture de l'interface graphique de "
+"novelWriter, vous pouvez désactiver l'interface graphique pour la durée de "
+"l'exécution du test. Si vous déplacez votre souris pendant que les tests sont "
+"en cours d'exécution, vous risquez d'interférer avec l'exécution de certains "
+"tests."
+
+#: ../../source/technical/tests.rst:37
+msgid ""
+"You can disable the renderring of the GUI by setting the flag "
+"``QT_QPA_PLATFORM=offscreen``:"
+msgstr ""
+"Vous pouvez désactiver le rendu de l'interface graphique en définissant le "
+"drapeau ``QT_QPA_PLATFORM=offscreen`` :"
+
+#: ../../source/technical/tests.rst:45
+msgid "Advanced Options"
+msgstr "Options avancées"
+
+#: ../../source/technical/tests.rst:47
+msgid ""
+"Adding the flag ``-v`` to the ``pytest`` command will increase verbosity of the "
+"test execution."
+msgstr ""
+"L'ajout du drapeau ``-v`` à la commande ``pytest`` augmente la verbosité de "
+"l'exécution du test."
+
+#: ../../source/technical/tests.rst:49
+msgid "You can also add coverage report generation. For instance to HTML:"
+msgstr ""
+"Vous pouvez également ajouter la génération de rapports de couverture. Par "
+"exemple en HTML :"
+
+#: ../../source/technical/tests.rst:55
+msgid "Other useful report formats are ``xml``, and ``term`` for terminal output."
+msgstr ""
+"D'autres formats de rapport utiles sont ``xml``, et ``term`` pour la sortie "
+"terminal."
+
+#: ../../source/technical/tests.rst:57
+msgid ""
+"You can also run tests per subpackage of novelWriter with the ``-m`` command. "
+"The available subpackage groups are ``base``, ``core``, and ``gui``. Consider "
+"for instance:"
+msgstr ""
+"Vous pouvez aussi lancer des tests par sous-paquet de novelWriter avec la "
+"commande ``-m``. Les groupes de sous-paquetages disponibles sont ``base``, "
+"``core``, et ``gui``. Prenons un exemple :"
+
+#: ../../source/technical/tests.rst:64
+msgid ""
+"This will only run the tests of the \"core\" package, that is, all the classes "
+"that deal with the project data of a novelWriter project. The \"gui\" tests, "
+"likewise, will run the tests for the GUI components, and the \"base\" tests "
+"cover the bits in-between."
+msgstr ""
+"Ceci n'exécutera que les tests du paquet « core », c'est-à-dire toutes les "
+"classes qui traitent les données d'un projet novelWriter. Les tests « gui », de "
+"même, exécuteront les tests des composants de l'interface graphique, et les "
+"tests « base » couvriront les éléments intermédiaires."
+
+#: ../../source/technical/tests.rst:68
+msgid ""
+"You can also filter the tests with the ``-k`` switch. The following will do the "
+"same as ``-m core``:"
+msgstr ""
+"Vous pouvez également filtrer les tests avec le commutateur ``-k``. Ce qui suit "
+"fera la même chose que ``-m core`` :"
+
+#: ../../source/technical/tests.rst:75
+msgid ""
+"All tests are named in such a way that you can filter them by adding more bits "
+"of the test names. They all start with the word \"test\". Then comes the group: "
+"\"Core\", \"Base\", \"Dlg\", \"Tool\", or \"Gui\". Finally comes the name of "
+"the class or module, which generally corresponds to a single source code file. "
+"For instance, running the following will run all tests for the document editor:"
+msgstr ""
+"Tous les tests sont nommés de manière à ce que vous puissiez les filtrer en "
+"ajoutant d'autres éléments aux noms des tests. Ils commencent tous par le mot « "
+"test ». Vient ensuite le groupe : « Core », “Base”, “Dlg”, “Tool” ou “Gui”. "
+"Enfin, vient le nom de la classe ou du module, qui correspond généralement à un "
+"seul fichier de code source. Par exemple, l'exécution de ce qui suit lancera "
+"tous les tests pour l'éditeur de documents :"
+
+#: ../../source/technical/tests.rst:84
+msgid "To run a single test, simply add the full test name to the ``-k`` switch."
+msgstr ""
+"Pour lancer un seul test, il suffit d'ajouter le nom complet du test au "
+"commutateur ``-k``."

docs/source/locales/fr/LC_MESSAGES/usage/advanced_formatting.po

@@ -0,0 +1,392 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 16:04+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/advanced_formatting.rst:5
+msgid "Advanced Formatting"
+msgstr "Mise en forme avancée"
+
+#: ../../source/usage/advanced_formatting.rst:7
+msgid ""
+"Standard Markdown formatting is somewhat limited, so novelWriter has some "
+"additional formatting codes for special use cases. These codes are all based "
+"on brackets, and some allow an additional value to be set after a colon."
+msgstr ""
+"Le formatage Markdown standard est quelque peu limité, c'est pourquoi "
+"novelWriter dispose de quelques codes de formatage supplémentaires pour des "
+"cas d'utilisation particuliers. Ces codes sont tous basés sur les crochets, et "
+"certains permettent de définir une valeur supplémentaire après les deux points."
+
+#: ../../source/usage/advanced_formatting.rst:11
+msgid "This section covers all these formatting codes."
+msgstr "Cette section couvre tous ces codes de formatage."
+
+#: ../../source/usage/advanced_formatting.rst:17
+msgid "Formatting with Shortcodes"
+msgstr "Mise en forme avec les shortcodes"
+
+#: ../../source/usage/advanced_formatting.rst:19
+msgid ""
+"For basic formatting, like emphasis, you should use the standard Markdown "
+"style formatting tags descried in :ref:`docs_usage_basics_emphasis` whenever "
+"possible."
+msgstr ""
+"Pour le formatage de base, comme la mise en valeur, vous devriez utiliser les "
+"balises de formatage standard du style Markdown décrites dans :ref:"
+"`docs_usage_basics_emphasis` chaque fois que possible."
+
+#: ../../source/usage/advanced_formatting.rst:22
+msgid ""
+"For additional formatting options, you can use shortcodes. Shortcodes is a "
+"form of in-line codes that wrap the section of text to be formatted. "
+"Shortcodes can be nested to apply multiple formats to the same piece of text."
+msgstr ""
+"Pour des options de formatage supplémentaires, vous pouvez utiliser des "
+"shortcodes. Les shortcodes sont une forme de codes en ligne qui enveloppent la "
+"section de texte à mettre en forme. Les shortcodes peuvent être imbriqués pour "
+"appliquer plusieurs formats à la même partie de texte."
+
+#: ../../source/usage/advanced_formatting.rst:26
+msgid ""
+"These shortcodes are intended for special formatting cases, or more complex "
+"cases that cannot be solved with simple Markdown-like formatting codes. "
+"Available shortcodes are listed below."
+msgstr ""
+"Ces shortcodes sont destinés à des cas de formatage spéciaux ou à des cas plus "
+"complexes qui ne peuvent pas être résolus avec de simples codes de formatage "
+"de type Markdown. Les shortcodes disponibles sont énumérés ci-dessous."
+
+#: ../../source/usage/advanced_formatting.rst:29
+msgid "Shortcodes Formats"
+msgstr "Formats des shortcodes"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Syntax"
+msgstr "Syntaxe"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Description"
+msgstr "Description"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[b]text[/b]``"
+msgstr "``[b]texte[/b]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as bold text."
+msgstr "Le texte est affiché en gras."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[i]text[/i]``"
+msgstr "``[i]texte[/i]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as italicised text."
+msgstr "Le texte est affiché en italique."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[s]text[/s]``"
+msgstr "``[s]texte[/s]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as strike through text."
+msgstr "Le texte est affiché sous forme de texte barré."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[u]text[/u]``"
+msgstr "``[u]texte[/u]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as underlined text."
+msgstr "Le texte est affiché sous forme de texte souligné."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[m]text[/m]``"
+msgstr "``[m]texte[/m]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as highlighted text."
+msgstr "Le texte est affiché en surbrillance."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[sup]text[/sup]``"
+msgstr "``[sup]texte[/sup]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as superscript text."
+msgstr "Le texte est affiché en exposant."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[sub]text[/sub]``"
+msgstr "``[sub]texte[/sub]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Text is displayed as subscript text."
+msgstr "Le texte est affiché en indice."
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[footnote:key]``"
+msgstr "``[footnote:clé]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "A reference to a :ref:`footnote comment <docs_usage_comments_footnotes>`."
+msgstr ""
+"Une référence à un :ref:`commentaire de note de bas de page "
+"<docs_usage_comments_footnotes>`."
+
+#: ../../source/usage/advanced_formatting.rst:43
+msgid ""
+"Unlike Markdown style codes, these can be used anywhere within a paragraph. "
+"Even in the middle of a word if you need to. You can also freely combine them "
+"to form more complex formatting."
+msgstr ""
+"Contrairement aux codes de style Markdown, ces codes peuvent être utilisés "
+"n'importe où dans un paragraphe. Même au milieu d'un mot si nécessaire. Vous "
+"pouvez également les combiner librement pour obtenir une mise en forme plus "
+"complexe."
+
+#: ../../source/usage/advanced_formatting.rst:46
+msgid ""
+"The shortcodes are available from the **Format** menu and in the editor "
+"toolbar, which can be activated by clicking the left-most icon button in the "
+"editor header."
+msgstr ""
+"Les shortcodes sont disponibles dans le menu **Format** et dans la barre "
+"d'outils de l'éditeur, qui peut être activée en cliquant sur l'icône la plus à "
+"gauche dans l'en-tête de l'éditeur."
+
+#: ../../source/usage/advanced_formatting.rst:51
+msgid ""
+"Shortcodes are not processed until you generate a preview or generate a "
+"manuscript document. So there is no highlighting of the text between the "
+"formatting markers. There is also no check that your markers make sense. You "
+"must ensure that you have both the opening and closing formatting markers "
+"where you want them."
+msgstr ""
+"Les shortcodes ne sont pas traités tant que vous n'avez pas généré un aperçu "
+"ou un document manuscrit. Il n'y a donc pas de mise en évidence du texte entre "
+"les marqueurs de formatage. Il n'y a pas non plus de vérification de la "
+"logique de vos marqueurs. Vous devez vous assurer que les marqueurs de "
+"formatage d'ouverture et de fermeture se trouvent à l'endroit voulu."
+
+#: ../../source/usage/advanced_formatting.rst:62
+msgid "Vertical Space and Page Breaks"
+msgstr "Espace vertical et sauts de page"
+
+#: ../../source/usage/advanced_formatting.rst:64
+msgid ""
+"You can apply page breaks to partition, chapter and scene headings for novel "
+"documents from the **Manuscript Build** tool. If you need to add a page break "
+"or additional vertical spacing in other places, there are special codes "
+"available for this purpose."
+msgstr ""
+"Vous pouvez appliquer des sauts de page aux en-têtes de partition, de chapitre "
+"et de scène pour les documents de roman à partir de l'outil **Compiler le "
+"manuscrit**. Si vous avez besoin d'ajouter un saut de page ou un espacement "
+"vertical supplémentaire à d'autres endroits, il existe des codes spéciaux à "
+"cet effet."
+
+#: ../../source/usage/advanced_formatting.rst:68
+msgid ""
+"Adding more than one line break between paragraphs will **not** increase the "
+"space between those paragraphs when generating a manuscript document. To add "
+"additional space between paragraphs, add the text ``[vspace]`` on a line of "
+"its own, and the **Manuscript Build** tool will insert a blank paragraph in "
+"its place."
+msgstr ""
+"L'ajout de plus d'un saut de ligne entre les paragraphes n'augmentera **pas** "
+"l'espace entre ces paragraphes lors de la génération d'un document manuscrit. "
+"Pour ajouter de l'espace entre les paragraphes, ajoutez le texte ``[vspace]`` "
+"sur une ligne distincte, et l'outil **Compilation du manuscrit** insérera un "
+"paragraphe vide à sa place."
+
+#: ../../source/usage/advanced_formatting.rst:73
+msgid ""
+"If you need multiple blank paragraphs just add a colon and a number to the "
+"above code. For instance, writing ``[vspace:3]`` will insert three blank "
+"paragraphs."
+msgstr ""
+"Si vous avez besoin de plusieurs paragraphes vides, il suffit d'ajouter deux "
+"points et un chiffre au code ci-dessus. Par exemple, en écrivant "
+"``[vspace:3]``, vous insérerez trois paragraphes vides."
+
+#: ../../source/usage/advanced_formatting.rst:76
+msgid ""
+"If you need to add a page break somewhere, put the text ``[new page]`` on a "
+"line by itself before the text you wish to start on a new page."
+msgstr ""
+"Si vous devez ajouter un saut de page quelque part, placez le texte ``[ new "
+"page]`` sur une ligne isolée avant le texte que vous souhaitez faire commencer "
+"sur une nouvelle page."
+
+#: ../../source/usage/advanced_formatting.rst:81
+msgid ""
+"The page break code is applied to the text that follows it. It adds a \"page "
+"break before\" mark to the text when exporting to HTML or Open Document. This "
+"means that a ``[new page]`` code which has no text following it will not "
+"result in a page break."
+msgstr ""
+"Le code de saut de page est appliqué au texte qui le suit. Il ajoute une "
+"marque de « saut de page avant » au texte lors de l'exportation vers HTML ou "
+"Open Document. Cela signifie qu'un code ``[ new page]`` qui n'est suivi "
+"d'aucun texte n'entraînera pas de saut de page."
+
+#: ../../source/usage/advanced_formatting.rst:85
+#: ../../source/usage/advanced_formatting.rst:132
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/usage/advanced_formatting.rst:104
+msgid "Inserting Word Counts in the Text"
+msgstr "Insérer le nombre de mots dans le texte"
+
+#: ../../source/usage/advanced_formatting.rst:106
+msgid ""
+"The cover page of a manuscript normally has the word count stated on it. Any "
+"statistics value collected by novelWriter can be inserted into any document "
+"using a special shortcode. You can insert the code for any of the available "
+"statistics values from the **Insert** menu under **Word/Character Count**."
+msgstr ""
+"La page de couverture d'un manuscrit indique normalement le nombre de mots. "
+"Toute valeur statistique collectée par novelWriter peut être insérée dans "
+"n'importe quel document à l'aide d'un shortcode spécial. Vous pouvez insérer "
+"le code pour n'importe quelle valeur statistique disponible dans le menu "
+"**Insérer** sous **Nombre de mots/caractères**."
+
+#: ../../source/usage/advanced_formatting.rst:111
+msgid ""
+"The value inserted is the actual count for your entire manuscript, so it is "
+"not populated until you run the **Manuscript Build** tool. Until then they "
+"will show up as \"0\" in the viewer panel."
+msgstr ""
+"La valeur insérée est le nombre réel pour l'ensemble de votre manuscrit, elle "
+"n'est donc pas renseignée tant que vous n'avez pas exécuté l'outil "
+"**Compilation du manuscrit**. Jusqu'à ce moment-là, ils apparaîtront sous la "
+"forme d'un « 0 » dans le panneau de visualisation."
+
+#: ../../source/usage/advanced_formatting.rst:114
+msgid "The available codes are:"
+msgstr "Les codes disponibles sont les suivants :"
+
+#: ../../source/usage/advanced_formatting.rst:116
+msgid "Stats Shortcodes"
+msgstr "Shortcodes de statistiques"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Code"
+msgstr "Code"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:allChars]``"
+msgstr "``[field:allChars]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Characters"
+msgstr "Personnages"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:textChars]``"
+msgstr "``[field:textChars]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Characters in Text"
+msgstr "Caractères dans un texte"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:titleChars]``"
+msgstr "``[field:titleChars]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Characters in Headings"
+msgstr "Caractères dans les titres"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:paragraphCount]``"
+msgstr "``[field:paragraphCount]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Paragraphs"
+msgstr "Paragraphes"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:titleCount]``"
+msgstr "``[field:titleCount]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Headings"
+msgstr "En-têtes"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:allWordChars]``"
+msgstr "``[field:allWordChars]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Characters, No Spaces"
+msgstr "Caractères, sans les espaces"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:textWordChars]``"
+msgstr "``[field:textWordChars]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Characters in Text, No Spaces"
+msgstr "Caractères dans le texte, sans les espaces"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:titleWordChars]``"
+msgstr "``[field:titleWordChars]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Characters in Headings, No Spaces"
+msgstr "Caractères dans les titres, sans les espaces"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:allWords]``"
+msgstr "``[field:allWords]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Words"
+msgstr "Mots"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:textWords]``"
+msgstr "``[field:textWords]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Words in Text"
+msgstr "Mots dans le texte"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "``[field:titleWords]``"
+msgstr "``[field:titleWords]``"
+
+#: ../../source/usage/advanced_formatting.rst:1
+msgid "Words in Headings"
+msgstr "Mots dans les entêtes"
+
+#: ../../source/usage/advanced_formatting.rst:134
+msgid ""
+"This is an example cover page. A similar page is automatically generated when "
+"you create a new project."
+msgstr ""
+"Il s'agit d'un exemple de page de couverture. Une page similaire est "
+"automatiquement générée lorsque vous créez un nouveau projet."

docs/source/locales/fr/LC_MESSAGES/usage/alignment_and_indent.po

@@ -0,0 +1,185 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 14:45+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/alignment_and_indent.rst:5
+msgid "Alignment and Indentation"
+msgstr "Alignement et indentation"
+
+#: ../../source/usage/alignment_and_indent.rst:7
+msgid ""
+"The Markdown standard doesn't have commands for aligning text, so "
+"novelWriter adds its own syntax for this. It also has syntax for "
+"indentation, which is similar to Markdown block quotes."
+msgstr ""
+"Le standard Markdown n'a pas de commandes pour aligner le texte, donc "
+"novelWriter ajoute sa propre syntaxe pour cela. Il dispose également "
+"d'une syntaxe pour l'indentation, qui est similaire aux guillemets de "
+"bloc de Markdown."
+
+#: ../../source/usage/alignment_and_indent.rst:12
+msgid "Paragraph Alignment and Indentation"
+msgstr "Alignement et indentation des paragraphes"
+
+#: ../../source/usage/alignment_and_indent.rst:14
+msgid ""
+"All documents have the text by default aligned to the left or justified, "
+"depending on your setting in **Preferences**."
+msgstr ""
+"Le texte de tous les documents est par défaut aligné à gauche ou "
+"justifié, selon les paramètres définis dans les **Préférences**."
+
+#: ../../source/usage/alignment_and_indent.rst:17
+msgid ""
+"You can override the default text alignment on individual paragraphs by "
+"specifying alignment tags. These tags are double angle brackets. Either "
+"``>>`` or ``<<``. You put them either before or after the paragraph, and "
+"they will \"push\" the text towards the edge the brackets point towards. "
+"This should be fairly intuitive."
+msgstr ""
+"Vous pouvez remplacer l'alignement par défaut du texte sur des "
+"paragraphes individuels en spécifiant des balises d'alignement. Ces "
+"balises sont des doubles chevrons. Il peut s'agir de ``>>`` ou de "
+"``<<``. Vous les placez avant ou après le paragraphe, et elles « "
+"pousseront » le texte vers le bord vers lequel les crochets pointent. "
+"Cela devrait être assez intuitif."
+
+#: ../../source/usage/alignment_and_indent.rst:22
+msgid ""
+"Indentation uses a similar syntax. But here you use a single ``>`` or "
+"``<`` to \"push\" the text away from the edge."
+msgstr ""
+"L'indentation utilise une syntaxe similaire. Mais ici, vous utilisez un "
+"seul ``>`` ou ``<`` pour éloigner le texte du bord."
+
+#: ../../source/usage/alignment_and_indent.rst:25
+#: ../../source/usage/alignment_and_indent.rst:52
+#: ../../source/usage/alignment_and_indent.rst:69
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/usage/alignment_and_indent.rst:27
+msgid "Text Alignment and Indentation"
+msgstr "Alignement et indentation du texte"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "Syntax"
+msgstr "Syntaxe"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "Description"
+msgstr "Description"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "``>> Right aligned text``"
+msgstr "``>> Texte aligné à droite``"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "The text paragraph is right-aligned."
+msgstr "Le paragraphe est aligné à droite."
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "``Left aligned text <<``"
+msgstr "``Texte aligné à gauche <<``"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "The text paragraph is left-aligned."
+msgstr "Le paragraphe est aligné à gauche."
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "``>> Centred text <<``"
+msgstr "``>> Texte centré <<``"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "The text paragraph is centred."
+msgstr "Le paragraphe est centré."
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "``> Left indented text``"
+msgstr "``> Texte en retrait à gauche``"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "The text has an increased left margin."
+msgstr "Le texte a une marge gauche plus importante."
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "``Right indented text <``"
+msgstr "``Texte en retrait à droite <``"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "The text has an increased right margin."
+msgstr "Le texte a une marge droite plus importante."
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "``> Left/right indented text <``"
+msgstr "``> Texte indenté gauche/droite <```"
+
+#: ../../source/usage/alignment_and_indent.rst:1
+msgid "The text has both margins increased."
+msgstr "Les deux marges du texte ont été augmentées."
+
+#: ../../source/usage/alignment_and_indent.rst:41
+msgid ""
+"The text editor will not show the alignment and indentation live. But "
+"the viewer will show them when you open the document there. It will of "
+"course also be reflected in the document generated from the **Manuscript "
+"Build** tool as long as the format supports paragraph alignment."
+msgstr ""
+"L'éditeur de texte n'affiche pas l'alignement et l'indentation en "
+"direct. Mais l'afficheur les affichera lorsque vous y ouvrirez le "
+"document. Ils seront bien sûr également reflétés dans le document généré "
+"par l'outil de compilation de manuscrits, à condition que le format "
+"prenne en charge l'alignement des paragraphes."
+
+#: ../../source/usage/alignment_and_indent.rst:47
+msgid "Alignment with Line Breaks"
+msgstr "Alignement avec les sauts de ligne"
+
+#: ../../source/usage/alignment_and_indent.rst:49
+msgid ""
+"If you have line breaks in the paragraph, the markers for all the lines "
+"are combined and used for the entire paragraph. For the following text, "
+"all lines will be centred:"
+msgstr ""
+"Si le paragraphe comporte des retours à la ligne, les marqueurs de "
+"toutes les lignes sont combinés et utilisés pour l'ensemble du "
+"paragraphe. Pour le texte suivant, toutes les lignes seront centrées :"
+
+#: ../../source/usage/alignment_and_indent.rst:63
+msgid "Alignment with First Line Indent"
+msgstr "Alignement sur le retrait de la première ligne"
+
+#: ../../source/usage/alignment_and_indent.rst:65
+msgid ""
+"If you have first line indent enabled in your manuscript build settings, "
+"you probably want to disable it for text in verses. Adding any alignment "
+"tags will cause the first line indent to be switched off for that "
+"paragraph."
+msgstr ""
+"Si vous avez activé le retrait de première ligne dans les paramètres de "
+"compilation de votre Manuscrit, vous voudrez probablement le désactiver "
+"pour le texte en vers. L'ajout de balises d'alignement entraînera la "
+"désactivation du retrait de première ligne pour ce paragraphe."
+
+#: ../../source/usage/alignment_and_indent.rst:71
+msgid "The following text will always be aligned against the left margin:"
+msgstr "Le texte suivant sera toujours aligné sur la marge de gauche :"

docs/source/locales/fr/LC_MESSAGES/usage/basic_formatting.po

@@ -0,0 +1,219 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 10:44+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/basic_formatting.rst:5
+msgid "Basic Formatting"
+msgstr "Mise en forme de base"
+
+#: ../../source/usage/basic_formatting.rst:9
+msgid ""
+"The basic text formatting syntax of novelWriter is based on Markdown_. "
+"It is only a subset of the Markdown syntax though. Lists, images, and "
+"links are not supported."
+msgstr ""
+"La syntaxe de formatage de texte de base de novelWriter est basée sur "
+"Markdown_. Il ne s'agit toutefois que d'un sous-ensemble de la syntaxe "
+"Markdown. Les listes, les images et les liens ne sont pas pris en charge."
+
+#: ../../source/usage/basic_formatting.rst:12
+msgid ""
+"That said, URLs in the text should automatically be highlighted and "
+"become clickable. However, only URLs starting with \"http\" or \"https\" "
+"are recognised. In the editor, you must hold down the :kbd:`Ctrl` key "
+"when clicking a URL to follow it."
+msgstr ""
+"Cela dit, les URL dans le texte devraient automatiquement être mis en "
+"évidence et devenir cliquables. Cependant, seules les URL commençant par "
+"« http » ou « https » sont reconnues. Dans l'éditeur, vous devez "
+"maintenir la touche :kbd:`Ctrl` enfoncée lorsque vous cliquez sur une "
+"URL pour la suivre."
+
+#: ../../source/usage/basic_formatting.rst:20
+msgid "Text Paragraphs"
+msgstr "Paragraphes du texte"
+
+#: ../../source/usage/basic_formatting.rst:22
+msgid ""
+"A text paragraph is indicated by a blank line. That is, you need two "
+"line breaks to separate two fragments of text into two paragraphs. "
+"Single line breaks are treated as line breaks within a paragraph."
+msgstr ""
+"Un paragraphe de texte est indiqué par une ligne blanche. En d'autres "
+"termes, il faut deux sauts de ligne pour séparer deux fragments de texte "
+"en deux paragraphes. Les sauts de ligne simples sont traités comme des "
+"sauts de ligne à l'intérieur d'un paragraphe."
+
+#: ../../source/usage/basic_formatting.rst:26
+msgid ""
+"It is important that you actually follow this rule. You should not, for "
+"instance, mimic indented paragraphs manually in the editor. This, and a "
+"lot of other formatting options that can be applied to text paragraphs "
+"in the :ref:`Manuscript Tool <docs_ui_manuscript>` depend on paragraphs "
+"being separated by blank lines."
+msgstr ""
+"Il est important de respecter cette règle. Vous ne devez pas, par "
+"exemple, imiter les paragraphes indentés manuellement dans l'éditeur. "
+"Ceci, ainsi que beaucoup d'autres options de formatage qui peuvent être "
+"appliquées aux paragraphes de texte dans l'outil :ref:`Manuscript Tool "
+"<docs_ui_manuscript>`, dépendent du fait que les paragraphes sont "
+"séparés par des lignes vides."
+
+#: ../../source/usage/basic_formatting.rst:31
+msgid ":bdg-success:`Correct`"
+msgstr ":bdg-success:`Correct`"
+
+#: ../../source/usage/basic_formatting.rst:41
+msgid ":bdg-danger:`Incorrect`"
+msgstr ":bdg-danger:`Incorrect`"
+
+#: ../../source/usage/basic_formatting.rst:50
+msgid ""
+"If you do as shown in the \"Incorrect\" example, novelWriter will "
+"understand this as a single paragraph with two lines."
+msgstr ""
+"Si vous procédez comme dans l'exemple « Incorrect », novelWriter "
+"comprendra qu'il s'agit d'un seul paragraphe de deux lignes."
+
+#: ../../source/usage/basic_formatting.rst:57
+msgid "Text Emphasis with Markdown"
+msgstr "Mise en valeur du texte avec Markdown"
+
+#: ../../source/usage/basic_formatting.rst:59
+msgid ""
+"A minimal set of Markdown text emphasis styles are supported for text "
+"paragraphs."
+msgstr ""
+"Un ensemble minimal de styles d'accentuation de texte Markdown est pris "
+"en charge pour les paragraphes de texte."
+
+#: ../../source/usage/basic_formatting.rst:61
+msgid "``_text_``"
+msgstr "``_texte_``"
+
+#: ../../source/usage/basic_formatting.rst:62
+msgid "The text is rendered as emphasised text (italicised)."
+msgstr "Le texte est rendu en italique."
+
+#: ../../source/usage/basic_formatting.rst:64
+msgid "``**text**``"
+msgstr "``**texte**``"
+
+#: ../../source/usage/basic_formatting.rst:65
+msgid "The text is rendered as strongly emphasised text (bold)."
+msgstr "Le texte est rendu en gras."
+
+#: ../../source/usage/basic_formatting.rst:67
+msgid "``~~text~~``"
+msgstr "``~~texte~~``"
+
+#: ../../source/usage/basic_formatting.rst:68
+msgid "Strike through text."
+msgstr "Barrer le texte."
+
+#: ../../source/usage/basic_formatting.rst:70
+msgid ""
+"In Markdown guides it is often recommended to differentiate between "
+"strong emphasis and emphasis by using ``**`` for strong and ``_`` for "
+"emphasis, although Markdown generally also supports ``__`` for strong "
+"and ``*`` for emphasis. However, since the differentiation makes the "
+"highlighting and conversion significantly simpler and faster, in "
+"novelWriter this is a rule, not just a recommendation."
+msgstr ""
+"Dans les guides Markdown, il est souvent recommandé de différencier le "
+"gras de l'italique en utilisant ``**`` pour le gras et ``_`` pour "
+"l'italique, bien que Markdown supporte également ``__`` pour le gras et "
+"``*`` pour l'italique. Cependant, puisque la différenciation rend la "
+"mise en évidence et la conversion significativement plus simple et plus "
+"rapide, dans novelWriter il s'agit d'une règle et non d'une simple "
+"recommandation."
+
+#: ../../source/usage/basic_formatting.rst:76
+msgid "In addition, the following rules apply:"
+msgstr "En outre, les règles suivantes s'appliquent :"
+
+#: ../../source/usage/basic_formatting.rst:78
+msgid ""
+"The emphasis and strike through formatting tags do not allow spaces "
+"between the words and the tag itself. That is, ``**text**`` is valid, "
+"``**text **`` is not."
+msgstr ""
+"Les balises de mise en valeur et de biffage n'autorisent pas les espaces "
+"entre les mots et la balise elle-même. Autrement dit, ``**texte**`` est "
+"valide, ``**texte **`` ne l'est pas."
+
+#: ../../source/usage/basic_formatting.rst:80
+msgid ""
+"More generally, the delimiters must be on the outer edge of words. That "
+"is, ``some **text in bold** here`` is valid, ``some** text in bold** "
+"here`` is not."
+msgstr ""
+"Plus généralement, les délimiteurs doivent se trouver aux bords des "
+"mots. Autrement dit, « certains **textes en gras** ici » sont valides, « "
+"certains** textes en gras** ici » ne le sont pas."
+
+#: ../../source/usage/basic_formatting.rst:82
+msgid ""
+"If using both ``**`` and ``_`` to wrap the same text, the underscore "
+"must be the **inner** wrapper. This is due to the underscore also being "
+"a valid word character, so if they are on the outside, they violate rule "
+"2."
+msgstr ""
+"Si vous utilisez à la fois ``**`` et ``_`` pour envelopper le même "
+"texte, le trait de soulignement doit être à **l'intérieure**. Ceci est "
+"dû au fait que le trait de soulignement est également un caractère "
+"verbal valide, donc s'il est à l'extérieur, il viole la règle 2."
+
+#: ../../source/usage/basic_formatting.rst:85
+msgid ""
+"Text emphasis does not span past line breaks. If you need to add "
+"emphasis to multiple lines or paragraphs, you must apply it to each of "
+"them in turn."
+msgstr ""
+"L'accentuation du texte ne s'étend pas au-delà des sauts de ligne. Si "
+"vous devez ajouter une emphase à plusieurs lignes ou paragraphes, vous "
+"devez l'appliquer à chacun d'entre eux à tour de rôle."
+
+#: ../../source/usage/basic_formatting.rst:87
+msgid ""
+"Text emphasis can only be used in comments and paragraphs. Headings and "
+"meta data tags don't allow for formatting, and any formatting markup "
+"will be displayed as-is."
+msgstr ""
+"Cette mise en valeur du texte ne peut être utilisée que dans les "
+"commentaires et les paragraphes. Les titres et les balises de "
+"métadonnées ne permettent pas la mise en forme, et toute marque de mise "
+"en forme sera affichée telle quelle."
+
+#: ../../source/usage/basic_formatting.rst:92
+msgid ""
+"novelWriter supports standard escape syntax for the emphasis markup "
+"characters in case the editor misunderstands your intended usage of "
+"them. That is, ``\\*``, ``\\_`` and ``\\~`` will generate a plain ``*``, "
+"``_`` and ``~``, respectively, without interpreting them as part of the "
+"markup."
+msgstr ""
+"novelWriter supporte la syntaxe d'échappement standard pour les "
+"caractères d'accentuation au cas où l'éditeur ne comprendrait pas "
+"l'usage que vous voulez en faire. C'est-à-dire que ``\\*``, ``\\_`` et "
+"``\\~`` généreront respectivement un ``*``, ``_`` et ``~``, sans les "
+"interpréter comme faisant partie du balisage."

docs/source/locales/fr/LC_MESSAGES/usage/chapters_and_scenes.po

@@ -0,0 +1,261 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-29 14:27+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/chapters_and_scenes.rst:5
+msgid "Chapters and Scenes"
+msgstr "Chapitres et scènes"
+
+#: ../../source/usage/chapters_and_scenes.rst:9
+msgid ""
+"Since novelWriter uses a plain text format, the structure of your novel must "
+"follow a certain set of simple rules. For documents in a **Novel** type root "
+"folder, it is the heading that determines if the document is a chapter or a "
+"scene."
+msgstr ""
+"Comme novelWriter utilise un format de texte brut, la structure de votre "
+"roman doit suivre un certain nombre de règles simples. Pour les documents "
+"situés dans un dossier racine de type **Roman**, c'est le titre qui détermine "
+"s'il s'agit d'un chapitre ou d'une scène."
+
+#: ../../source/usage/chapters_and_scenes.rst:13
+msgid ""
+"The formatting of headings is based on Markdown_. A heading is indicated by a "
+"line starting with one or more ``#`` characters. It accepts up to four of "
+"these. You can use multiple headings in the same document, but it is the "
+"first heading that determines which icon and information is displayed in the "
+"project tree."
+msgstr ""
+"Le formatage des titres est basé sur Markdown_. Un titre est indiqué par une "
+"ligne commençant par un ou plusieurs caractères ``#``. Il en accepte jusqu'à "
+"quatre. Vous pouvez utiliser plusieurs titres dans le même document, mais "
+"c'est le premier titre qui détermine l'icône et les informations affichées "
+"dans l'arborescence du projet."
+
+#: ../../source/usage/chapters_and_scenes.rst:20
+msgid ""
+"You can use the same heading levels for your notes in the other root folders, "
+"but they aren't treated as chapters or scenes, so there you are free to use "
+"them as you want."
+msgstr ""
+"Vous pouvez utiliser les mêmes niveaux de titres pour vos notes dans les "
+"autres dossiers racines, mais ils ne sont pas traités comme des chapitres ou "
+"des scènes, et vous êtes donc libre de les utiliser comme vous le souhaitez."
+
+#: ../../source/usage/chapters_and_scenes.rst:27
+msgid "Heading Levels"
+msgstr "Niveaux d'en-tête"
+
+#: ../../source/usage/chapters_and_scenes.rst:31
+msgid "An illustration of how heading levels correspond to the novel structure."
+msgstr ""
+"Illustration de la correspondance entre les niveaux d'en-tête et la structure "
+"du roman."
+
+#: ../../source/usage/chapters_and_scenes.rst:33
+msgid ""
+"Four levels of headings are understood for novel documents. You can pick and "
+"choose from these as you want, but if your story has chapters, you should use "
+"these headings to indicate them. If you also add scene headings, you have "
+"better control of how your scene separators are formatted in your manuscript. "
+"The chapter and scenes headings are also displayed in the :ref:`Novel View "
+"<docs_ui_main_novel>` and :ref:`Outline View <docs_ui_main_outline>`."
+msgstr ""
+"Quatre niveaux d'en-têtes sont prévus pour les documents de roman. Vous "
+"pouvez les choisir à votre guise, mais si votre histoire comporte des "
+"chapitres, vous devez utiliser ces titres pour les indiquer. Si vous ajoutez "
+"également des titres de scènes, vous pourrez mieux contrôler la façon dont "
+"vos séparateurs de scènes sont formatés dans votre manuscrit. Les titres de "
+"chapitres et de scènes sont également affichés dans les vues :ref:`Novel View "
+"<docs_ui_main_novel>` et :ref:`Outline View <docs_ui_main_outline>`."
+
+#: ../../source/usage/chapters_and_scenes.rst:39
+msgid "``# Title Text``"
+msgstr "``# Texte de titre``"
+
+#: ../../source/usage/chapters_and_scenes.rst:40
+msgid ""
+"This is a heading level one. This heading indicates the start of a new "
+"partition. Partitions are for when you want to split your story into \"Part "
+"1\", \"Part 2\", etc. You can also choose to use them for splitting the text "
+"up into acts, and then hide these headings in your manuscript so that they "
+"are not included in the output."
+msgstr ""
+"Il s'agit d'une en-tête de niveau un. Ce titre indique le début d'une "
+"nouvelle partie. Les parties sont utilisées lorsque vous souhaitez diviser "
+"votre histoire en « Partie 1 », « Partie 2 », etc. Vous pouvez également "
+"choisir de les utiliser pour diviser le texte en actes, puis de masquer ces "
+"titres dans votre manuscrit afin qu'ils ne soient pas inclus dans la sortie."
+
+#: ../../source/usage/chapters_and_scenes.rst:45
+msgid "``## Chapter Title``"
+msgstr "``## Titre de chapitre``"
+
+#: ../../source/usage/chapters_and_scenes.rst:46
+msgid ""
+"This is a heading level two. This heading indicates the start of a new "
+"chapter. Chapter numbers can be inserted automatically when building the "
+"manuscript, so you don't have to do this in the title. See :ref:"
+"`docs_ui_manuscript_head_numbers` for more details."
+msgstr ""
+"Il s'agit d'une en-tête de niveau deux. Ce titre indique le début d'un "
+"nouveau chapitre. Les numéros de chapitre peuvent être insérés "
+"automatiquement lors de la construction du manuscrit, de sorte que vous "
+"n'avez pas à le faire dans le titre. Voir :ref:"
+"`docs_ui_manuscript_head_numbers` pour plus de détails."
+
+#: ../../source/usage/chapters_and_scenes.rst:50
+msgid "``### Scene Title``"
+msgstr "``### Titre de scène``"
+
+#: ../../source/usage/chapters_and_scenes.rst:51
+msgid ""
+"This is a heading level three. This heading indicates the start of a new "
+"scene. Scene numbers or scene separators can be inserted automatically when "
+"building the manuscript, so you can use the title field as a working title "
+"for your scenes if you wish, but you must provide a minimal title."
+msgstr ""
+"Il s'agit d'une en-tête de niveau trois. Ce titre indique le début d'une "
+"nouvelle scène. Des numéros de scène ou des séparateurs de scène peuvent être "
+"insérés automatiquement lors de la construction du manuscrit. Vous pouvez "
+"donc utiliser le champ titre comme titre de travail pour vos scènes si vous "
+"le souhaitez, mais vous devez fournir un titre minimal."
+
+#: ../../source/usage/chapters_and_scenes.rst:56
+msgid "``#### Section Title``"
+msgstr "``#### Titre de section``"
+
+#: ../../source/usage/chapters_and_scenes.rst:57
+msgid ""
+"This is a heading level four. This heading indicates the start of a new "
+"section. Section titles can be replaced by separators or ignored completely "
+"when building the manuscript. The meaning of a section is really whatever you "
+"want it to be. You can use it to split your scenes up into chunks, or into "
+"separate documents."
+msgstr ""
+"Il s'agit d'une en-tête de niveau quatre. Ce titre indique le début d'une "
+"nouvelle section. Les titres de section peuvent être remplacés par des "
+"séparateurs ou ignorés complètement lors de la construction du manuscrit. La "
+"signification d'une section est en fait celle que vous voulez lui donner. "
+"Vous pouvez l'utiliser pour diviser vos scènes en morceaux ou en documents "
+"distincts."
+
+#: ../../source/usage/chapters_and_scenes.rst:62
+msgid ""
+"For headings level one through three, adding a ``!`` modifies the meaning of "
+"the heading. The alternative meaning of the heading is only relevant when you "
+"generate your manuscript, but you may want to keep the use cases in mind "
+"while writing."
+msgstr ""
+"Pour les en-têtes de niveau un à trois, l'ajout d'un ``!`` modifie la "
+"signification de l'en-tête. La signification alternative de l'en-tête n'est "
+"pertinente que lorsque vous générez votre manuscrit, mais vous pouvez garder "
+"à l'esprit les cas d'utilisation lors de la rédaction."
+
+#: ../../source/usage/chapters_and_scenes.rst:66
+msgid "``#! Title Text``"
+msgstr "``#! Texte de titre``"
+
+#: ../../source/usage/chapters_and_scenes.rst:67
+msgid ""
+"This tells the **Manuscript Build** tool that the level one heading is "
+"intended to be used for the novel or notes folder's main title, like for "
+"instance the novel title on the cover page. When building the manuscript, "
+"this will use a different styling of the title, which you can modify "
+"independently from how partition titles are styled. See :ref:"
+"`docs_usage_front_back_matter_title` for more details."
+msgstr ""
+"Cela indique à l'outil **Compiler le manuscrit** que l'en-tête de niveau un "
+"est destiné à être utilisé pour le titre principal du roman ou du dossier de "
+"notes, comme par exemple le titre du roman sur la page de couverture. Lors de "
+"la compilation du manuscrit, l'outil utilisera un style différent pour le "
+"titre, que vous pouvez modifier indépendamment de la façon dont les titres "
+"des parties sont stylisés. Voir :ref:`docs_usage_front_back_matter_title` "
+"pour plus de détails."
+
+#: ../../source/usage/chapters_and_scenes.rst:73
+msgid "``##! Chapter Title``"
+msgstr "``## ! Titre de chapitre``"
+
+#: ../../source/usage/chapters_and_scenes.rst:74
+msgid ""
+"This tells the **Manuscript Build** tool to not assign a chapter number to "
+"this chapter title if automatic chapter numbers are enabled. Such titles are "
+"useful for prologues and epilogues for instance. See :ref:"
+"`docs_usage_front_back_matter_unnumbered` for more details."
+msgstr ""
+"Cette option indique à l'outil **Compilation du manuscrit** de ne pas "
+"attribuer de numéro de chapitre à ce titre de chapitre si la numérotation "
+"automatique des chapitres est activée. De tels titres sont utiles pour les "
+"prologues et les épilogues par exemple. Voir :ref:"
+"`docs_usage_front_back_matter_unnumbered` pour plus de détails."
+
+#: ../../source/usage/chapters_and_scenes.rst:78
+msgid "``###! Scene Title``"
+msgstr "``###! Titre de scène``"
+
+#: ../../source/usage/chapters_and_scenes.rst:79
+msgid ""
+"This is an alternative scene heading that can be formatted differently in the "
+"**Manuscript Build** tool. It is intended for separating \"soft\" and "
+"\"hard\" scene breaks. Aside from this, it behaves identically to a regular "
+"scene heading. See :ref:`docs_ui_manuscript_head_hard_soft` for more details."
+msgstr ""
+"Il s'agit d'un titre de scène alternatif qui peut être formaté différemment "
+"dans l'outil **Compilation du manuscrit**. Il est destiné à séparer les "
+"coupures de scène « douces » et « dures ». A part cela, il se comporte de la "
+"même manière qu'un titre de scène normal. Voir :ref:"
+"`docs_ui_manuscript_head_hard_soft` pour plus de détails."
+
+#: ../../source/usage/chapters_and_scenes.rst:84
+msgid ""
+"The formatting of these headings can be customised quite extensively in the :"
+"ref:`Manuscript Tool <docs_ui_manuscript>`, which is covered in a separate "
+"part of the documentation."
+msgstr ""
+"Le formatage de ces en-têtes peut être personnalisé de manière assez poussée "
+"dans l'outil :ref:`Manuscript Tool <docs_ui_manuscript>`, qui fait l'objet "
+"d'une partie distincte de la documentation."
+
+#: ../../source/usage/chapters_and_scenes.rst:90
+msgid ""
+"The space after the ``#`` or ``!`` character is mandatory. The editor will "
+"change colour and font size when the heading is correctly formatted."
+msgstr ""
+"L'espace après le caractère ``#`` ou ``!`` est obligatoire. L'éditeur "
+"changera de couleur et de taille de police lorsque le titre sera correctement "
+"formaté."
+
+#: ../../source/usage/chapters_and_scenes.rst:93
+msgid ""
+"Page breaks can be automatically added before titles, partition, chapter and "
+"scene headings from the **Manuscript Build** tool when you build your project "
+"to a format that supports page breaks. If you want page breaks in other "
+"places, you have to specify them manually. See :ref:"
+"`docs_usage_formatting_breaks` for more details."
+msgstr ""
+"Les sauts de page peuvent être automatiquement ajoutés avant les titres, les "
+"parties, les chapitres et les scènes à partir de l'outil **Compilation du "
+"manuscrit** lorsque vous créez votre projet dans un format qui prend en "
+"charge les sauts de page. Si vous voulez des sauts de page à d'autres "
+"endroits, vous devez les spécifier manuellement. Voir :ref:"
+"`docs_usage_formatting_breaks` pour plus de détails."

docs/source/locales/fr/LC_MESSAGES/usage/comments.po

@@ -0,0 +1,254 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 11:20+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/comments.rst:5
+msgid "Comments and Notes"
+msgstr "Commentaires et notes"
+
+#: ../../source/usage/comments.rst:7
+msgid ""
+"You can add comments to your text that are not a part of the story. "
+"Regular comments are intended for you to add notes to yourself inside "
+"the text, which may be useful when you revise your drafts. However, "
+"there are several types of comments you can use."
+msgstr ""
+"Vous pouvez ajouter à votre texte des commentaires qui ne font pas "
+"partie de l'histoire. Les commentaires ordinaires sont destinés à vous "
+"permettre d'ajouter des notes à l'intérieur du texte, ce qui peut "
+"s'avérer utile lorsque vous révisez vos projets. Cependant, il existe "
+"plusieurs types de commentaires que vous pouvez utiliser."
+
+#: ../../source/usage/comments.rst:11
+msgid ""
+"This section covers the basic comment types. There are a couple of "
+"advanced features that use comment syntax too, but they are covered "
+"later."
+msgstr ""
+"Cette section couvre les types de commentaires de base. Il existe "
+"quelques fonctions avancées qui utilisent également la syntaxe des "
+"commentaires, mais elles sont abordées plus loin."
+
+#: ../../source/usage/comments.rst:18
+msgid "Plain Comments"
+msgstr "Commentaires simples"
+
+#: ../../source/usage/comments.rst:20
+msgid ""
+"A plain comment is a line or paragraph that starts with the character "
+"``%`` as its first character. You can put them wherever you like in your "
+"documents, and you can choose to include or exclude them from your "
+"manuscript."
+msgstr ""
+"Un commentaire simple est une ligne ou un paragraphe qui commence par le "
+"caractère ``%``. Vous pouvez les placer où vous le souhaitez dans vos "
+"documents, et vous pouvez choisir de les inclure ou de les exclure de "
+"votre manuscrit."
+
+#: ../../source/usage/comments.rst:24
+msgid ""
+"For the most part, novelWriter completely ignores these comments. They "
+"are not included in your word or character counts either, and are only "
+"displayed in the document viewer panel if you enable them."
+msgstr ""
+"La plupart du temps, novelWriter ignore complètement ces commentaires. "
+"Ils ne sont pas non plus inclus dans le décompte des mots ou des "
+"caractères, et ne sont affichés dans le panneau de visualisation du "
+"document que si vous les activez."
+
+#: ../../source/usage/comments.rst:28 ../../source/usage/comments.rst:63
+#: ../../source/usage/comments.rst:80 ../../source/usage/comments.rst:128
+#: ../../source/usage/comments.rst:156
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/usage/comments.rst:44
+msgid "Synopsis or Description Comments"
+msgstr "Commentaires Synopsis ou Description"
+
+#: ../../source/usage/comments.rst:46
+msgid ""
+"A special kind of comments are **Synopsis** and **Short Description** "
+"comments. They are different from plain comments in that they can be "
+"displayed alongside other information about a scene or a character or "
+"other story element described in a note. As with plain comments, they "
+"can be included in your manuscript, but they are formatted differently "
+"than plain comments."
+msgstr ""
+"Les commentaires **Synopsis** et **Description courte** constituent un "
+"type particulier de commentaires. Ils se distinguent des commentaires "
+"ordinaires par le fait qu'ils peuvent être affichés à côté d'autres "
+"informations concernant une scène, un personnage ou un autre élément de "
+"l'histoire décrit dans une note. Comme les commentaires ordinaires, ils "
+"peuvent être inclus dans votre manuscrit, mais leur format est différent "
+"de celui des commentaires ordinaires."
+
+#: ../../source/usage/comments.rst:53
+msgid ""
+"A summary or description comment can be used once, and only once, for "
+"each heading as they are considered a description of the content of the "
+"text under that heading. If you add two such comments under the same "
+"heading, the last one will be used."
+msgstr ""
+"Un commentaire de résumé ou de description peut être utilisé une fois, "
+"et une seule, pour chaque rubrique, car il est considéré comme une "
+"description du contenu du texte de cette rubrique. Si vous ajoutez deux "
+"commentaires de ce type sous la même rubrique, c'est le dernier qui sera "
+"utilisé."
+
+#: ../../source/usage/comments.rst:59
+msgid "Synopsis"
+msgstr "Synopsis"
+
+#: ../../source/usage/comments.rst:61
+msgid ""
+"A **Synopsis** comment is intended for adding a summary of your chapters "
+"and scenes."
+msgstr ""
+"Un commentaire **Synopsis** est destiné à ajouter un résumé de vos "
+"chapitres et scènes."
+
+#: ../../source/usage/comments.rst:75
+msgid "Short Description"
+msgstr "Brève description"
+
+#: ../../source/usage/comments.rst:77
+msgid ""
+"A **Short Description** comment behaves exactly the same as a synopsis "
+"comment, but is intended as a description of a story element, like a "
+"character."
+msgstr ""
+"Un commentaire **Brève description** se comporte exactement de la même "
+"manière qu'un commentaire de synopsis, mais il est destiné à décrire un "
+"élément de l'histoire, tel qu'un personnage."
+
+#: ../../source/usage/comments.rst:100
+msgid ""
+"The ``%Synopsis:`` and ``%Short:`` comment prefixes are interchangeable, "
+"but when you include them in the manuscript, they are labelled based on "
+"the prefix, so the latter may make more sense for a Character note than "
+"the former."
+msgstr ""
+"Les préfixes de commentaire ``%Synopsis:`` et ``%Short:`` sont "
+"interchangeables, mais lorsque vous les incluez dans le manuscrit, ils "
+"sont étiquetés en fonction du préfixe, de sorte que ce dernier peut "
+"avoir plus de sens pour une note de caractère que le premier."
+
+#: ../../source/usage/comments.rst:108
+msgid "Footnote Comments"
+msgstr "Commentaires de note de bas de page"
+
+#: ../../source/usage/comments.rst:110
+msgid ""
+"Footnotes are added with a shortcode, paired with a matching comment for "
+"the actual footnote text. The matching is done with a key that links the "
+"two. If you insert a footnote from the **Insert** menu, a unique key is "
+"generated for you. Shortcodes in general are covered in more detail in :"
+"ref:`docs_usage_formatting_shortcodes`."
+msgstr ""
+"Les notes de bas de page sont ajoutées à l'aide d'un shortcode, associé "
+"à un commentaire correspondant au texte de la note de bas de page. La "
+"correspondance est assurée par une clé qui lie les deux. Si vous insérez "
+"une note de bas de page à partir du menu **Insérer**, une clé unique est "
+"générée pour vous. Les shortcodes en général sont couverts plus en "
+"détail dans :ref:`docs_usage_formatting_shortcodes`."
+
+#: ../../source/usage/comments.rst:115
+msgid ""
+"The insert footnote feature will add the footnote shortcode marker at "
+"the position of your cursor in the editor panel, and create the "
+"associated footnote comment right after the paragraph. It will then move "
+"the cursor there so you can immediately start typing the footnote text."
+msgstr ""
+"La fonction d'insertion d'une note de bas de page ajoute le marqueur de "
+"shortcode de note de bas de page à l'emplacement de votre curseur dans "
+"le panneau de l'éditeur et crée le commentaire de note de bas de page "
+"associé juste après le paragraphe. Elle déplacera ensuite le curseur à "
+"cet endroit afin que vous puissiez immédiatement commencer à taper le "
+"texte de la note de bas de page."
+
+#: ../../source/usage/comments.rst:119
+msgid ""
+"The footnote comment can be anywhere in the document, so if you wish to "
+"move them to, say, the bottom of the text, you are free to do so."
+msgstr ""
+"Le commentaire de la note de bas de page peut se trouver n'importe où "
+"dans le document, de sorte que si vous souhaitez le placer, par exemple, "
+"au bas du texte, vous êtes libre de le faire."
+
+#: ../../source/usage/comments.rst:122
+msgid ""
+"Footnote keys are only required to be unique within a document, so if "
+"you copy, move or merge text, you must make sure the keys are not "
+"duplicated. If you use the automatically generated keys from the "
+"**Insert** menu, they are unique among all indexed documents. They are "
+"not guaranteed to be unique against footnotes in the **Archive** or "
+"**Trash** folder though, but the chance of accidentally generating the "
+"same key twice in a project is relatively small."
+msgstr ""
+"Les clés de notes de bas de page ne doivent être uniques qu'à "
+"l'intérieur d'un document. Par conséquent, si vous copiez, déplacez ou "
+"fusionnez du texte, vous devez vous assurer que les clés ne sont pas "
+"dupliquées. Si vous utilisez les clés générées automatiquement à partir "
+"du menu **Insérer**, elles sont uniques parmi tous les documents "
+"indexés. Il n'est pas garanti qu'elles soient uniques par rapport aux "
+"notes de bas de page du dossier Archives ou Corbeille, mais le risque de "
+"générer accidentellement la même clé deux fois dans un projet est "
+"relativement faible."
+
+#: ../../source/usage/comments.rst:144
+msgid "Ignored Text"
+msgstr "Texte ignoré"
+
+#: ../../source/usage/comments.rst:146
+msgid ""
+"If you want to completely ignore some of the text in your documents, but "
+"are not ready to delete it, you can add ``%~`` before the text paragraph "
+"or line. This will cause novelWriter to skip the text entirely when "
+"generating previews or building manuscripts."
+msgstr ""
+"Si vous souhaitez ignorer complètement une partie du texte dans vos "
+"documents, mais que vous n'êtes pas prêt à l'effacer, vous pouvez "
+"ajouter ``%~`` devant le paragraphe ou la ligne de texte. Cela permettra "
+"à novelWriter d'ignorer complètement le texte lors de la génération "
+"d'aperçus ou de la construction de manuscrits."
+
+#: ../../source/usage/comments.rst:150
+msgid ""
+"This is a better way of removing text than converting them to regular "
+"comments, as you may want to include regular comments in your previews "
+"or draft manuscript."
+msgstr ""
+"Il s'agit d'un meilleur moyen de supprimer le texte que de le convertir "
+"en commentaires normaux, car vous souhaiterez peut-être inclure des "
+"commentaires normaux dans vos prévisualisations ou votre projet de "
+"manuscrit."
+
+#: ../../source/usage/comments.rst:153
+msgid ""
+"You can toggle the ignored text feature on and off for a paragraph by "
+"pressing :kbd:`Ctrl+Shift+D` on your keyboard with your cursor somewhere "
+"in the paragraph."
+msgstr ""
+"Vous pouvez activer ou désactiver la fonction de texte ignoré pour un "
+"paragraphe en appuyant sur :kbd:`Ctrl+Maj+D` sur votre clavier avec "
+"votre curseur quelque part dans le paragraphe."

docs/source/locales/fr/LC_MESSAGES/usage/front_back_matter.po

@@ -0,0 +1,146 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 16:13+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/front_back_matter.rst:5
+msgid "Front and Back Matter"
+msgstr "Premières et dernières pages"
+
+#: ../../source/usage/front_back_matter.rst:7
+msgid ""
+"Front and back matter documents are documents that go before and after "
+"your main story text. They can include pages like your cover page, "
+"content tables, prologues, epilogues, etc. These special pages and "
+"sections are supported to some extent by novelWriter."
+msgstr ""
+"Les documents de début et de fin sont des documents qui précèdent et "
+"suivent le texte principal de l'histoire. Il peut s'agir de pages comme "
+"la page de couverture, de tables des matières, de prologues, "
+"d'épilogues, etc. Ces pages et sections spéciales sont prises en charge "
+"dans une certaine mesure par novelWriter."
+
+#: ../../source/usage/front_back_matter.rst:15
+msgid "The Title Page"
+msgstr "La page de titre"
+
+#: ../../source/usage/front_back_matter.rst:17
+msgid ""
+"It is recommended that you add a document at the very top of each "
+"**Novel** root folder with the novel title in it. You should modify the "
+"level 1 heading format code with an ``!`` in order to render it as a "
+"document title that is excluded from any automatic Table of Content in a "
+"manuscript build document."
+msgstr ""
+"Il est recommandé d'ajouter un document au premier niveau de chaque "
+"dossier racine **Roman** avec le titre du roman. Vous devez modifier le "
+"code de format de l'en-tête de niveau un avec un ``!`` afin de le rendre "
+"comme un titre de document qui est exclu de toute table des matières "
+"automatique lors de la compilation du manuscrit."
+
+#: ../../source/usage/front_back_matter.rst:22
+msgid ""
+"You can also add the author name and address above this if this is "
+"required by the manuscript format you use, and additional space added "
+"before the title."
+msgstr ""
+"Vous pouvez également ajouter le nom et l'adresse de l'auteur au-dessus "
+"de ce titre si le format de manuscrit que vous utilisez l'exige, et "
+"ajouter un espace supplémentaire avant le titre."
+
+#: ../../source/usage/front_back_matter.rst:25
+#: ../../source/usage/front_back_matter.rst:73
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/usage/front_back_matter.rst:27
+msgid ""
+"This is the title page novelWriter generates automatically for a new "
+"project as of version 2.6:"
+msgstr ""
+"Il s'agit de la page de titre que novelWriter génère automatiquement "
+"pour un nouveau projet à partir de la version 2.6 :"
+
+#: ../../source/usage/front_back_matter.rst:43
+msgid ""
+"The title is by default centred on the page. You can add more text to "
+"the page as you wish, like for instance the author's name and details."
+msgstr ""
+"Le titre est par défaut centré sur la page. Vous pouvez ajouter plus de "
+"texte à la page si vous le souhaitez, comme par exemple le nom de "
+"l'auteur et ses coordonnées."
+
+#: ../../source/usage/front_back_matter.rst:46
+msgid ""
+"The default title page inserts the word count for text only, but you can "
+"add other counts too. See :ref:`docs_usage_formatting_counts` for more "
+"details."
+msgstr ""
+"La page de titre par défaut insère le nombre de mots pour le texte "
+"uniquement, mais vous pouvez également ajouter d'autres décomptes. Voir :"
+"ref:`docs_usage_formatting_counts` pour plus de détails."
+
+#: ../../source/usage/front_back_matter.rst:53
+msgid "Additional Pages"
+msgstr "Pages additionnelles"
+
+#: ../../source/usage/front_back_matter.rst:55
+msgid ""
+"If you want an additional page of text after the title page, starting on "
+"a fresh page, you can add ``[new page]`` on a line by itself, and "
+"continue the text after it. This will insert a page break before the "
+"text. See :ref:`docs_usage_formatting_breaks` for more details."
+msgstr ""
+"Si vous voulez une page de texte supplémentaire après la page de titre, "
+"commençant sur une nouvelle page, vous pouvez ajouter ``[ new page]`` "
+"sur une ligne à part, et continuer le texte après elle. Cela insérera un "
+"saut de page avant le texte. Voir :ref:`docs_usage_formatting_breaks` "
+"pour plus de détails."
+
+#: ../../source/usage/front_back_matter.rst:63
+msgid "Unnumbered Chapters"
+msgstr "Chapitres non numérotés"
+
+#: ../../source/usage/front_back_matter.rst:65
+msgid ""
+"If you use the automatic numbering feature for your chapters, but you "
+"want to keep some special chapters separate from this, you can add an ``!"
+"`` to the level 2 heading formatting code to tell the build tool to skip "
+"these chapters when adding numbers."
+msgstr ""
+"Si vous utilisez la numérotation automatique pour vos chapitres, mais "
+"que vous voulez garder certains chapitres spéciaux séparés, vous pouvez "
+"ajouter un `!` au code de formatage des titres de niveau deux pour "
+"indiquer à l'outil de compilation d'ignorer ces chapitres lors de "
+"l'ajout des numéros."
+
+#: ../../source/usage/front_back_matter.rst:69
+msgid ""
+"Unnumbered chapters are useful for prologue and epilogue chapters, and "
+"also for interlude chapters if you use those in your text. There is a "
+"separate formatting feature for such chapter titles in the **Manuscript "
+"Build** tool. See the :ref:`docs_ui_manuscript` page for more details."
+msgstr ""
+"Les chapitres non numérotés sont utiles pour les prologues et les "
+"épilogues, ainsi que pour les interludes si vous en utilisez dans votre "
+"texte. Il existe une fonction de formatage séparée pour ces titres de "
+"chapitre dans l'outil **Compilation du manuscrit**. Voir la page :ref:"
+"`docs_ui_manuscript` pour plus de détails."

docs/source/locales/fr/LC_MESSAGES/usage/howto.po

@@ -0,0 +1,285 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 16:22+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/howto.rst:5
+msgid "Tips & Tricks"
+msgstr "Trucs et astuces"
+
+#: ../../source/usage/howto.rst:9
+msgid ""
+"This is a list of hopefully helpful little tips on how to get the most out of "
+"novelWriter."
+msgstr ""
+"Il s'agit d'une liste de petits conseils, que nous espérons utiles, sur la "
+"façon de tirer le meilleur parti de novelWriter."
+
+#: ../../source/usage/howto.rst:12
+msgid ""
+"This section will be expanded over time. If you would like to have something "
+"added, feel free to contribute, or start a discussion on the project's "
+"`Discussions Page`_."
+msgstr ""
+"Cette section sera développée au fil du temps. Si vous souhaitez que quelque "
+"chose soit ajouté, n'hésitez pas à contribuer, ou à lancer une discussion sur "
+"la `Page des discussions`_ du projet."
+
+#: ../../source/usage/howto.rst:17
+msgid "Managing the Project"
+msgstr "Gestion du projet"
+
+#: ../../source/usage/howto.rst
+msgid "How do I create a project from a template?"
+msgstr "Comment créer un projet à partir d'un modèle ?"
+
+#: ../../source/usage/howto.rst:22
+msgid ""
+"On the Welcome dialog's **Create New Project** form, you can select to "
+"\"Prefill Project\" from the content of a different project. This feature is "
+"most useful if you copy a project you have dedicated to be a template project. "
+"If you have a structure and settings you want to use for every new project, "
+"this is the best solution."
+msgstr ""
+"Dans le formulaire **Créer un nouveau projet** de la boîte de dialogue "
+"d'accueil, vous pouvez choisir de « pré-remplir le projet » à partir du contenu "
+"d'un autre projet. Cette fonction est particulièrement utile si vous copiez un "
+"projet que vous avez dédié à être un projet modèle. Si vous avez une structure "
+"et des paramètres que vous souhaitez utiliser pour chaque nouveau projet, c'est "
+"la meilleure solution."
+
+#: ../../source/usage/howto.rst
+msgid "How do I merge multiple documents into one?"
+msgstr "Comment fusionner plusieurs documents en un seul ?"
+
+#: ../../source/usage/howto.rst:30
+msgid ""
+"If you need to merge a selection of documents in your project into a single "
+"document, you can achieve this by first making a new folder for just that "
+"purpose, and drag all the documents you want merged into this folder. Then you "
+"can right click the folder, select :guilabel:`Transform` and :guilabel:`Merge "
+"Documents in Folder`."
+msgstr ""
+"Si vous avez besoin de fusionner une sélection de documents dans votre projet "
+"en un seul document, vous pouvez le faire en créant un nouveau dossier à cet "
+"effet, et en faisant glisser tous les documents que vous voulez fusionner dans "
+"ce dossier. Ensuite, vous pouvez faire un clic droit sur le dossier, "
+"sélectionner :guilabel:`Transformer` et :guilabel:`Fusionner les documents du "
+"dossier`."
+
+#: ../../source/usage/howto.rst:35
+msgid ""
+"In the dialog that pops up, the documents will be in the same order as in the "
+"folder, but you can rearrange them here of you wish. See :ref:"
+"`docs_ui_split_merge` for more details."
+msgstr ""
+"Dans la boîte de dialogue qui s'ouvre, les documents seront dans le même ordre "
+"que dans le dossier, mais vous pouvez les réorganiser ici si vous le souhaitez. "
+"Voir :ref:`docs_ui_split_merge` pour plus de détails."
+
+#: ../../source/usage/howto.rst
+msgid "How do I share status or importance labels between projects?"
+msgstr ""
+"Comment puis-je partager des étiquettes d'état ou d'importance entre les "
+"projets ?"
+
+#: ../../source/usage/howto.rst:41
+msgid ""
+"The status or importance labels you have defined in a project can be exported "
+"from **Project Settings** from the respective configuration tabs. You can then "
+"import these labels in another project."
+msgstr ""
+"Les étiquettes d'état ou d'importance que vous avez définies dans un projet "
+"peuvent être exportées à partir de **Paramètres du projet** dans les onglets de "
+"configuration respectifs. Vous pouvez ensuite importer ces étiquettes dans un "
+"autre projet."
+
+#: ../../source/usage/howto.rst:47
+msgid "Layout Tricks"
+msgstr "Astuces de mise en page"
+
+#: ../../source/usage/howto.rst
+msgid "How do I create a table?"
+msgstr "Comment créer un tableau ?"
+
+#: ../../source/usage/howto.rst:52
+msgid ""
+"The formatting tools available in novelWriter don't allow for complex "
+"structures like tables. However, the editor does render tabs in a similar way "
+"that regular word processors do. You can set the width of a tab in "
+"**Preferences**."
+msgstr ""
+"Les outils de formatage disponibles dans novelWriter ne permettent pas de créer "
+"des structures complexes telles que des tableaux. Cependant, l'éditeur rend les "
+"tabulations de la même manière que les traitements de texte classiques. Vous "
+"pouvez définir la largeur d'un onglet dans les **Préférences**."
+
+#: ../../source/usage/howto.rst:56
+msgid ""
+"The tab key should have the same distance in the editor as in the viewer, so "
+"you can align text in columns using the tab key, and it should look the same "
+"when viewed next to the editor."
+msgstr ""
+"La touche de tabulation doit avoir la même distance dans l'éditeur que dans "
+"l'afficheur, de sorte que vous puissiez aligner du texte en colonnes à l'aide "
+"de la touche de tabulation, et que l'aspect soit le même lorsque vous regardez "
+"à côté de l'éditeur."
+
+#: ../../source/usage/howto.rst:59
+msgid ""
+"This is most suitable for your notes, as the result in exported documents "
+"cannot be guaranteed to match. Especially if you don't use the same font in "
+"your manuscript as in the editor."
+msgstr ""
+"Cette méthode convient surtout à vos notes, car il n'est pas garanti que le "
+"résultat dans les documents exportés corresponde à la réalité. Surtout si vous "
+"n'utilisez pas la même police dans votre manuscrit que dans l'éditeur."
+
+#: ../../source/usage/howto.rst
+msgid "How do I force a line break when line breaks are ignored in my manuscript?"
+msgstr ""
+"Comment forcer un saut de ligne lorsque les sauts de ligne sont ignorés dans "
+"mon manuscrit ?"
+
+#: ../../source/usage/howto.rst:65
+msgid ""
+"In the **Manuscript Build Settings** you can choose to ignore line breaks "
+"within paragraphs in your text. However, some times you still need those "
+"breaks. Like for instance on the cover page where you may need to add your name "
+"and address. In such cases, you can add ``[br]`` where you want line breaks. "
+"These breaks cannot be ignored by any settings and will always be respected."
+msgstr ""
+"Dans les **Paramètres de compilation du manuscrit**, vous pouvez choisir "
+"d'ignorer les sauts de ligne dans les paragraphes de votre texte. Cependant, "
+"ces sauts de ligne sont parfois nécessaires. Comme par exemple sur la page de "
+"couverture où vous pouvez avoir besoin d'ajouter votre nom et votre adresse. "
+"Dans ce cas, vous pouvez ajouter ``[br]`` à l'endroit où vous souhaitez des "
+"sauts de ligne. Ces sauts de ligne ne peuvent être ignorés par aucun paramètre "
+"et seront toujours respectés."
+
+#: ../../source/usage/howto.rst
+msgid "How do I turn off first line indent for a specific paragraph?"
+msgstr ""
+"Comment désactiver l'indentation de la première ligne pour un paragraphe "
+"spécifique ?"
+
+#: ../../source/usage/howto.rst:75
+msgid ""
+"If you have first line indent enabled, but have a specific paragraph that you "
+"don't want indented, you can disable the indentation by explicitly adding text "
+"alignment. For instance by adding ``<<`` to the end to left-align it. Aligned "
+"paragraphs are not indented."
+msgstr ""
+"Si l'indentation de la première ligne est activée, mais qu'un paragraphe "
+"spécifique ne doit pas être indenté, vous pouvez désactiver l'indentation en "
+"ajoutant explicitement l'alignement du texte. Par exemple, en ajoutant ``<<`` à "
+"la fin du paragraphe pour l'aligner à gauche. Les paragraphes alignés ne sont "
+"pas indentés."
+
+#: ../../source/usage/howto.rst:79
+msgid "See :ref:`docs_usage_align_indent` for more details."
+msgstr "Voir :ref:`docs_usage_align_indent` pour plus de détails."
+
+#: ../../source/usage/howto.rst:83
+msgid "Organising Your Text"
+msgstr "Organiser son texte"
+
+#: ../../source/usage/howto.rst
+msgid "How do I add introductory text to chapters?"
+msgstr "Comment ajouter un texte d'introduction aux chapitres ?"
+
+#: ../../source/usage/howto.rst:88
+msgid ""
+"Sometimes chapters have a short preface, like a brief piece of text or a quote "
+"to set the stage before the first scene begins."
+msgstr ""
+"Parfois, les chapitres sont précédés d'une courte préface, comme un court texte "
+"ou une citation pour planter le décor avant le début de la première scène."
+
+#: ../../source/usage/howto.rst:91
+msgid ""
+"If you add separate files for chapters and scenes, the chapter file is the "
+"perfect place to add such text. Separating chapter and scene files also allows "
+"you to make scene files child documents of the chapter."
+msgstr ""
+"Si vous ajoutez des fichiers distincts pour les chapitres et les scènes, le "
+"fichier de chapitre est l'endroit idéal pour ajouter ce type de texte. La "
+"séparation des fichiers de chapitres et de scènes vous permet également de "
+"faire des fichiers de scènes des documents enfants du chapitre."
+
+#: ../../source/usage/howto.rst
+msgid "How do I distinguishing between soft and hard scene breaks?"
+msgstr ""
+"Comment faire la distinction entre les ruptures de scènes douces et les "
+"ruptures de scènes dures ?"
+
+#: ../../source/usage/howto.rst:98
+msgid ""
+"Depending on your writing style, you may need to separate between soft and hard "
+"scene breaks within chapters. Like for instance if you switch point-of-view "
+"character often."
+msgstr ""
+"En fonction de votre style d'écriture, vous pouvez avoir besoin de faire une "
+"distinction entre les ruptures de scènes douces et les ruptures de scènes dures "
+"au sein des chapitres. Par exemple, si vous changez souvent de point de vue."
+
+#: ../../source/usage/howto.rst:101
+msgid ""
+"In such cases you may want to use different scene headings for hard and soft "
+"scene breaks. The **Build Manuscript** tool will let you define a different "
+"format for scenes using the ``###`` and ``###!`` heading codes when you "
+"generate your manuscript. You can for instance add the common \"``* * *``\" for "
+"hard breaks and select to hide soft scene breaks, which will just insert an "
+"empty paragraph in their place. See :ref:`docs_ui_manuscript_settings` for more "
+"details."
+msgstr ""
+"Dans ce cas, vous pouvez utiliser des titres de scène différents pour les "
+"coupures de scène dures et douces. L'outil **Compilation du manuscrit** vous "
+"permettra de définir un format différent pour les scènes en utilisant les codes "
+"d'en-tête ``###`` et ``###!`` lors de la génération de votre manuscrit. Vous "
+"pouvez par exemple ajouter l'habituel « ``* * *`` » pour les coupures dures et "
+"choisir de masquer les coupures douces, ce qui aura pour effet d'insérer un "
+"paragraphe vide à leur place. Voir :ref:`docs_ui_manuscript_settings` pour plus "
+"de détails."
+
+#: ../../source/usage/howto.rst:111
+msgid "Other Tools"
+msgstr "Autres outils"
+
+#: ../../source/usage/howto.rst
+msgid "How do I convert my project to/from the yWriter format?"
+msgstr "Comment convertir mon projet au format yWriter ?"
+
+#: ../../source/usage/howto.rst:116
+msgid ""
+"There is a tool available that lets you convert a `yWriter <http://spacejock."
+"com/yWriter7.html>`_ project to a novelWriter project, and vice versa."
+msgstr ""
+"Il existe un outil qui vous permet de convertir un projet `yWriter <http://"
+"spacejock.com/yWriter7.html>`_ en un projet novelWriter, et vice versa."
+
+#: ../../source/usage/howto.rst:119
+msgid ""
+"The tool is available at `peter88213.github.io/yw2nw <https://peter88213.github."
+"io/yw2nw/>`__"
+msgstr ""
+"L'outil est disponible à l'adresse `peter88213.github.io/yw2nw <https://"
+"peter88213.github.io/yw2nw/>`__"

docs/source/locales/fr/LC_MESSAGES/usage/introduction.po

@@ -0,0 +1,161 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-27 21:24+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/introduction.rst:5
+msgid "Introduction"
+msgstr "Introduction"
+
+#: ../../source/usage/introduction.rst:9
+msgid ""
+"In a nutshell, novelWriter is a plain text editor that lets you organise "
+"one or more novels and associated notes as many smaller documents. You "
+"can at any time generate standard document formats from these plain text "
+"documents. Whether it is an outline of your story, a draft, a complete "
+"manuscript, or even a collection of your character notes or other notes."
+msgstr ""
+"En bref, novelWriter est un éditeur de texte brut qui vous permet "
+"d'organiser un ou plusieurs romans et les notes associées sous la forme "
+"de plusieurs petits documents. Vous pouvez à tout moment générer des "
+"formats de documents standard à partir de ces documents en texte brut. "
+"Qu'il s'agisse d'une ébauche de votre histoire, d'un brouillon, d'un "
+"manuscrit complet ou même d'une collection de notes sur les personnages "
+"ou d'autres notes."
+
+#: ../../source/usage/introduction.rst:16
+msgid "Why Plain Text?"
+msgstr "Pourquoi du texte brut ?"
+
+#: ../../source/usage/introduction.rst:18
+msgid ""
+"The idea is to let you be creative without having to deal with "
+"formatting while you are writing, or be distracted by it."
+msgstr ""
+"L'idée est de vous permettre d'être créatif sans avoir à vous préoccuper "
+"de la mise en forme pendant que vous écrivez, ou sans être distrait par "
+"elle."
+
+#: ../../source/usage/introduction.rst:21
+msgid ""
+"Of course, you probably need *some* form of minimal formatting for your "
+"text. At the very least you need emphasis. Most people are familiar with "
+"adding emphasis using ``_underscores_`` and ``**asterisks**``. This "
+"formatting standard comes from Markdown_ and is supported by "
+"novelWriter. It also uses Markdown formatting for defining document "
+"headings, which is how you distinguish between chapters and scenes."
+msgstr ""
+"Bien entendu, vous avez probablement besoin d'une sorte de mise en forme "
+"minimale pour votre texte. Au minimum, vous avez besoin d'une mise en "
+"valeur. La plupart des gens sont familiers avec l'ajout d'emphase en "
+"utilisant ``_underscores_`` et ``**asterisks**``. Ce standard de "
+"formatage vient de Markdown_ et est supporté par novelWriter. Il utilise "
+"également le formatage Markdown pour définir les titres du document, ce "
+"qui permet de faire la distinction entre les chapitres et les scènes."
+
+#: ../../source/usage/introduction.rst:27
+msgid ""
+"For those special cases where you need more complex formatting, a set of "
+"shortcodes are available. To make these codes easier to use, a dropdown "
+"button bar is available in the editor panel with standard format "
+"buttons. So don't worry. You don't have to learn any of these codes."
+msgstr ""
+"Pour les cas particuliers où vous avez besoin d'un formatage plus "
+"complexe, un ensemble de shortcodes est disponible. Pour faciliter "
+"l'utilisation de ces codes, une barre de boutons déroulante est "
+"disponible dans le panneau de l'éditeur avec des boutons de formatage "
+"standard. Ne vous inquiétez donc pas. Vous n'avez pas besoin d'apprendre "
+"ces codes."
+
+#: ../../source/usage/introduction.rst:33
+msgid "Adding Meta Data"
+msgstr "Ajout de métadonnées"
+
+#: ../../source/usage/introduction.rst:35
+msgid ""
+"In addition to the body text of your story, novelWriter allows you to "
+"enter some additional meta data into your text documents to indicate "
+"things like which characters are present in a chapter or scene, whose "
+"point of view we're seeing, what location the events take place in, and "
+"so on."
+msgstr ""
+"Outre le corps du texte de votre histoire, novelWriter vous permet de "
+"saisir des métadonnées supplémentaires dans vos documents texte afin "
+"d'indiquer les personnages présents dans un chapitre ou une scène, le "
+"point de vue de chacun, le lieu où se déroulent les événements, etc."
+
+#: ../../source/usage/introduction.rst:39
+msgid ""
+"Since the editor is plain text, this is done on special lines of text "
+"starting with an ``@`` character. The editor will show an auto-complete "
+"menu to help you write these lines. We will talk more about this later."
+msgstr ""
+"Comme l'éditeur est en texte brut, cela se fait sur des lignes de texte "
+"spéciales commençant par le caractère ``@``. L'éditeur affichera un menu "
+"d'auto-complétion pour vous aider à écrire ces lignes. Nous en "
+"reparlerons plus tard."
+
+#: ../../source/usage/introduction.rst:43
+msgid ""
+"You can also add your own author's comments in your text, without these "
+"comments becoming a part of the story itself. A comment line starts with "
+"a ``%`` character. There are different types of comments, and an auto-"
+"complete menu can help you here too. More about this later as well."
+msgstr ""
+"Vous pouvez également ajouter vos propres commentaires d'auteur dans "
+"votre texte, sans que ces commentaires fassent partie de l'histoire elle-"
+"même. Une ligne de commentaire commence par le caractère ``%``. Il "
+"existe différents types de commentaires, et un menu d'auto-complétion "
+"peut vous aider ici aussi. Nous y reviendrons plus tard."
+
+#: ../../source/usage/introduction.rst:47
+msgid "Limitations"
+msgstr "Restrictions"
+
+#: ../../source/usage/introduction.rst:49
+msgid ""
+"Please keep in mind that novelWriter is designed for writing fiction, so "
+"the formatting features available are limited to those relevant for this "
+"purpose. It is *not* suitable for technical writing. It is also *not* a "
+"full-featured Markdown editor."
+msgstr ""
+"Gardez à l'esprit que novelWriter est conçu pour l'écriture de fictions, "
+"et que les fonctions de formatage disponibles sont donc limitées à "
+"celles qui sont pertinentes à cette fin. Il n'est *pas* adapté à la "
+"rédaction technique. Ce n'est pas non plus un éditeur Markdown complet."
+
+#: ../../source/usage/introduction.rst:53
+msgid ""
+"In addition, novelWriter is not intended as a tool for organising "
+"research for writing, and therefore lacks formatting features you may "
+"need for this purpose. The notes feature in is mainly intended for "
+"character profiles and plot outlines. It is recommended to use a proper "
+"note-taking tool for research. This is anyway more practical as you may "
+"use the same research for multiple projects."
+msgstr ""
+"En outre, novelWriter n'est pas conçu comme un outil d'organisation de "
+"la recherche en vue de l'écriture, et ne dispose donc pas des fonctions "
+"de formatage dont vous pourriez avoir besoin à cette fin. La fonction de "
+"notes est principalement destinée aux profils de personnages et aux "
+"grandes lignes de l'intrigue. Il est recommandé d'utiliser un outil de "
+"prise de notes approprié pour la recherche. C'est de toute façon plus "
+"pratique, car vous pouvez utiliser la même recherche pour plusieurs "
+"projets."

docs/source/locales/fr/LC_MESSAGES/usage/organising_project.po

@@ -0,0 +1,538 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 14:11+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/organising_project.rst:5
+msgid "Organising Your Project"
+msgstr "Organiser votre projet"
+
+#: ../../source/usage/organising_project.rst:7
+msgid ""
+"Your project is organised into a set of top level folders called \"Root "
+"Folders\", which each have specific meaning in the project. Your project "
+"documents and notes are stored under these root folders. All the content "
+"of your project is available in the **Project Content** panel on the "
+"left side of the main window."
+msgstr ""
+"Votre projet est organisé en un ensemble de dossiers de premier niveau "
+"appelés « dossiers racines », qui ont chacun une signification "
+"spécifique dans le projet. Les documents et les notes de votre projet "
+"sont stockés dans ces dossiers racines. Tout le contenu de votre projet "
+"est disponible dans le panneau **Contenu du projet** sur le côté gauche "
+"de la fenêtre principale."
+
+#: ../../source/usage/organising_project.rst:14
+msgid "The **Project Content** tree populated with example documents."
+msgstr ""
+"L'arborescence **Contenu du projet** avec des exemples de documents."
+
+#: ../../source/usage/organising_project.rst:16
+msgid ""
+"Each line in the project tree shows the name of each item, its word "
+"count (or alternatively character count), an icon for :ref:"
+"`docs_usage_project_active`, and a custom icon for :ref:"
+"`docs_usage_project_status` of each item. These latter two are covered "
+"alter in this section."
+msgstr ""
+"Chaque ligne de l'arborescence du projet montre le nom de chaque "
+"élément, son nombre de mots (ou de caractères), une icône pour :ref:"
+"`docs_usage_project_active`, et une icône personnalisée pour :ref:"
+"`docs_usage_project_status` de chaque élément. Ces deux derniers points "
+"sont abordés plus loin dans cette section."
+
+#: ../../source/usage/organising_project.rst:20
+msgid ""
+"You can add, view and edit documents in the project tree by right-"
+"clicking on them. Some features are also located in the buttons along "
+"the top, next to the **Project Content** label."
+msgstr ""
+"Vous pouvez ajouter, visualiser et modifier des documents dans "
+"l'arborescence du projet en cliquant dessus avec le bouton droit de la "
+"souris. Certaines fonctions se trouvent également dans les boutons "
+"situés en haut, à côté de l'étiquette **Contenu du projet**."
+
+#: ../../source/usage/organising_project.rst:27
+msgid "How Root Folders Work"
+msgstr "Fonctionnement des dossiers racines"
+
+#: ../../source/usage/organising_project.rst:29
+msgid ""
+"Projects are structured into a set of top level folders called \"Root "
+"Folders\". They are visible in the project tree at the left side of the "
+"main window. Each type of root folder has a distinct icon."
+msgstr ""
+"Les projets sont structurés en un ensemble de dossiers de premier niveau "
+"appelés « dossiers racines ». Ils sont visibles dans l'arborescence du "
+"projet, à gauche de la fenêtre principale. Chaque type de dossier racine "
+"possède une icône distincte."
+
+#: ../../source/usage/organising_project.rst:32
+msgid ""
+"The documents that make up your story go into a root folder of type "
+"**Novel**. Your notes go into the other root folders. These other root "
+"folder types are separated into types depending on what kind of notes go "
+"into them. This is not only for organisation. It also matters to how you "
+"can reference these notes later. We will come back to this in the :ref:"
+"`docs_usage_tags_refs` section."
+msgstr ""
+"Les documents qui constituent votre histoire sont placés dans un dossier "
+"racine de type **roman**. Vos notes sont placées dans les autres "
+"dossiers racines. Ces autres types de dossiers racines sont séparés en "
+"fonction du type de notes qu'ils contiennent. Il ne s'agit pas seulement "
+"d'une question d'organisation. Cela a également une incidence sur la "
+"manière dont vous pourrez faire référence à ces notes ultérieurement. "
+"Nous y reviendrons dans la section :ref:`docs_usage_tags_refs`."
+
+#: ../../source/usage/organising_project.rst:37
+msgid ""
+"A new project may not have all of the root folders present, but you can "
+"add the ones you want from the project tree tool bar."
+msgstr ""
+"Un nouveau projet peut ne pas contenir tous les dossiers racines, mais "
+"vous pouvez ajouter ceux que vous souhaitez à partir de la barre "
+"d'outils de l'arborescence du projet."
+
+#: ../../source/usage/organising_project.rst:40
+msgid ""
+"The intended usage of each type of root folder is listed below. However, "
+"aside from the **Novel** folder, no restrictions are applied by "
+"novelWriter on what you put in them. You can use them however you want."
+msgstr ""
+"L'utilisation prévue de chaque type de dossier racine est indiquée ci-"
+"dessous. Cependant, à part le dossier **Roman**, aucune restriction "
+"n'est appliquée par novelWriter sur ce que vous mettez dans ces "
+"dossiers. Vous pouvez les utiliser comme bon vous semble."
+
+#: ../../source/usage/organising_project.rst:46
+msgid "Root Folder Types"
+msgstr "Types de dossiers racines"
+
+#: ../../source/usage/organising_project.rst:48
+msgid "**Novel** (Story)"
+msgstr "**roman** (histoire)"
+
+#: ../../source/usage/organising_project.rst:49
+msgid ""
+"This is where you put the documents that are part of your story. You can "
+"create multiple Novel folders if you wish, but various parts of the "
+"application assumes each Novel folder belong to one novel."
+msgstr ""
+"C'est là que vous placez les documents qui font partie de votre "
+"histoire. Vous pouvez créer plusieurs dossiers Roman si vous le "
+"souhaitez, mais plusieurs parties de l'application supposent que chaque "
+"dossier Roman appartient à un seul roman."
+
+#: ../../source/usage/organising_project.rst:53
+msgid ""
+"The Novel folder is somewhat special in that it can contain documents "
+"for chapters, scenes and story partitions. How this is indicated is "
+"covered in the section :ref:`docs_usage_headings`."
+msgstr ""
+"Le dossier roman est un peu spécial en ce sens qu'il peut contenir des "
+"documents pour les chapitres, les scènes et les parties de l'histoire. "
+"La façon dont cela est indiqué est couverte dans la section :ref:"
+"`docs_usage_headings`."
+
+#: ../../source/usage/organising_project.rst:56
+msgid "**Plot** (Notes)"
+msgstr "**Intrigue** (Notes)"
+
+#: ../../source/usage/organising_project.rst:57
+msgid ""
+"This is where you can keep notes and outlines of your story plots. Such "
+"notes can be particularly useful if you have outlines for sub plot. You "
+"can make references to these subplots from the scene documents, which "
+"makes it easier to track story progress."
+msgstr ""
+"C'est là que vous pouvez conserver des notes et les grandes lignes des "
+"intrigues de votre histoire. Ces notes peuvent être particulièrement "
+"utiles si vous avez des plans de sous-intrigues. Vous pouvez faire "
+"référence à ces intrigues secondaires à partir des documents de scène, "
+"ce qui facilite le suivi de la progression de l'histoire."
+
+#: ../../source/usage/organising_project.rst:61
+msgid "**Characters** (Notes)"
+msgstr "**Personnages** (Notes)"
+
+#: ../../source/usage/organising_project.rst:62
+msgid ""
+"Character notes go in this root folder type. For your main characters, "
+"you may want to make one document for each character. For smaller "
+"characters you can put multiple into the same document. In your chapters "
+"and scenes you can reference these character notes as point-of-view or "
+"focus characters."
+msgstr ""
+"Les notes concernant les personnages sont placées dans ce type de "
+"dossier racine. Pour vos personnages principaux, vous pouvez créer un "
+"document pour chacun d'entre eux. Pour les personnages secondaires, vous "
+"pouvez en mettre plusieurs dans le même document. Dans vos chapitres et "
+"vos scènes, vous pouvez faire référence à ces notes de personnages en "
+"tant que points de vue ou personnages principaux."
+
+#: ../../source/usage/organising_project.rst:67
+msgid "**Locations** (Notes)"
+msgstr "**Lieux** (Notes)"
+
+#: ../../source/usage/organising_project.rst:68
+msgid ""
+"The locations where your story takes place can be documented here. This, "
+"together with Plot and Characters are the key story elements to track, "
+"and to reference from your chapter and scene documents."
+msgstr ""
+"Les lieux où se déroule votre histoire peuvent être documentés ici. Avec "
+"l'intrigue et les personnages, ce sont les éléments clés de l'histoire "
+"qu'il faut suivre et auxquels il faut faire référence dans les documents "
+"relatifs aux chapitres et aux scènes."
+
+#: ../../source/usage/organising_project.rst:72
+msgid "**Timeline** (Notes)"
+msgstr "**Ligne de temps** (Notes)"
+
+#: ../../source/usage/organising_project.rst:73
+msgid ""
+"If the story has multiple plot timelines or jumps in time within the "
+"same plot, this folder type can be used to track this."
+msgstr ""
+"Si l'histoire comporte plusieurs lignes temporelles ou des sauts dans le "
+"temps au sein d'une même intrigue, ce type de dossier peut être utilisé "
+"pour en assurer le suivi."
+
+#: ../../source/usage/organising_project.rst:76
+msgid "**Objects** (Notes)"
+msgstr "**Objets** (Notes)"
+
+#: ../../source/usage/organising_project.rst:77
+msgid ""
+"Important objects in the story, for instance physical objects that "
+"change hands often, can be tracked here."
+msgstr ""
+"Les objets importants de l'histoire, par exemple les objets physiques "
+"qui changent souvent de mains, peuvent être suivis ici."
+
+#: ../../source/usage/organising_project.rst:80
+msgid "**Entities** (Notes)"
+msgstr "**Entités** (Notes)"
+
+#: ../../source/usage/organising_project.rst:81
+msgid ""
+"Does your plot have many powerful organisations or companies? Or other "
+"entities that are part of the plot? They can be organised here."
+msgstr ""
+"Votre intrigue comporte-t-elle de nombreuses organisations ou "
+"entreprises puissantes ? Ou d'autres entités qui font partie de "
+"l'intrigue ? Vous pouvez les organiser ici."
+
+#: ../../source/usage/organising_project.rst:84
+msgid "**Custom** (Notes)"
+msgstr "**Personnalisé** (Notes)"
+
+#: ../../source/usage/organising_project.rst:85
+msgid ""
+"The custom root folder type can be used for tracking anything else not "
+"covered by the above options."
+msgstr ""
+"Le type de dossier racine personnalisé peut être utilisé pour suivre "
+"tout ce qui n'est pas couvert par les options ci-dessus."
+
+#: ../../source/usage/organising_project.rst:88
+msgid "**Templates**"
+msgstr "Modèles"
+
+#: ../../source/usage/organising_project.rst:89
+msgid ""
+"Any document added under this root folder will be made available as "
+"template options when creating new documents. See :ref:"
+"`docs_usage_project_documents_templates` for more details."
+msgstr ""
+"Tout document ajouté dans ce dossier racine sera disponible en tant "
+"qu'options de modèle lors de la création de nouveaux documents. Voir :"
+"ref:`docs_usage_project_documents_templates` pour plus de détails."
+
+#: ../../source/usage/organising_project.rst:92
+msgid "**Archive**"
+msgstr "**Archive**"
+
+#: ../../source/usage/organising_project.rst:93
+msgid ""
+"If you don't want to delete a document, or put it in the **Trash** "
+"folder where it may be deleted, but still want it out of your main "
+"project, you can put it in this folder. The contents of the document "
+"will be ignored by the scanner that looks for tags, and it will be "
+"ignored in any outline view and in your manuscript."
+msgstr ""
+"Si vous ne voulez pas supprimer un document ou le placer dans le dossier "
+"**Poubelle** où il peut être supprimé, mais que vous voulez quand même "
+"le retirer de votre projet principal, vous pouvez le placer dans ce "
+"dossier. Le contenu du document sera ignoré par le scanner qui recherche "
+"les balises, et il sera ignoré dans toute vue d'ensemble et dans votre "
+"manuscrit."
+
+#: ../../source/usage/organising_project.rst:98
+msgid "**Trash**"
+msgstr "**Poubelle**"
+
+#: ../../source/usage/organising_project.rst:99
+msgid ""
+"This folder behaves like you expect. Anything dropped in here can be "
+"deleted permanently from the project, and the content doesn't show up "
+"anywhere else in novelWriter."
+msgstr ""
+"Ce dossier se comporte comme vous vous y attendez. Tout ce qui y est "
+"déposé peut être supprimé définitivement du projet, et son contenu "
+"n'apparaît nulle part ailleurs dans novelWriter."
+
+#: ../../source/usage/organising_project.rst:102
+msgid ""
+"The root folder types are closely tied to the tags and reference system. "
+"Each folder type for novel and notes corresponds to one or more "
+"categories of tags that can be used to reference the content in them. "
+"See :ref:`docs_usage_tags_refs` for more details."
+msgstr ""
+"Les types de dossiers racine sont étroitement liés au système de balises "
+"et de références. Chaque type de dossier pour les romans et les notes "
+"correspond à une ou plusieurs catégories de balises qui peuvent être "
+"utilisées pour référencer le contenu qu'ils contiennent. Voir :ref:"
+"`docs_usage_tags_refs` pour plus de détails."
+
+#: ../../source/usage/organising_project.rst:108
+msgid ""
+"The root folders have standard names, but you can rename them to "
+"whatever you want."
+msgstr ""
+"Les dossiers racine ont des noms standard, mais vous pouvez les renommer "
+"comme vous le souhaitez."
+
+#: ../../source/usage/organising_project.rst:114
+msgid "Regular Folders"
+msgstr "Dossiers ordinaires"
+
+#: ../../source/usage/organising_project.rst:116
+msgid ""
+"You can add regular folders anywhere you want in the project. The "
+"folders are there purely as a way for you to organise the documents in "
+"meaningful sections and to be able to collapse and hide them in the "
+"project tree when you're not working on those documents."
+msgstr ""
+"Vous pouvez ajouter des dossiers ordinaires où vous le souhaitez dans le "
+"projet. Les dossiers sont là uniquement pour vous permettre d'organiser "
+"les documents en sections significatives et pour pouvoir les réduire et "
+"les cacher dans l'arborescence du projet lorsque vous ne travaillez pas "
+"sur ces documents."
+
+#: ../../source/usage/organising_project.rst:120
+msgid ""
+"When novelWriter is processing the documents in a project, like for "
+"instance when you create a manuscript from it, these folders are "
+"ignored. Only the order of the documents themselves matter."
+msgstr ""
+"Lorsque novelWriter traite les documents d'un projet, comme par exemple "
+"lorsque vous créez un manuscrit à partir de ce projet, ces dossiers sont "
+"ignorés. Seul l'ordre des documents eux-mêmes compte."
+
+#: ../../source/usage/organising_project.rst:127
+msgid "Documents"
+msgstr "Documents"
+
+#: ../../source/usage/organising_project.rst:129
+msgid ""
+"You can add documents anywhere you want in your project structure. You "
+"can even add documents as child items of other documents, just as if "
+"they were folders. This makes it easy to associate a set of scenes with "
+"their chapter. You can also do this in your notes, where you for "
+"instance may have a hierarchy of your locations."
+msgstr ""
+"Vous pouvez ajouter des documents où vous le souhaitez dans la structure "
+"de votre projet. Vous pouvez même ajouter des documents en tant "
+"qu'éléments enfants d'autres documents, comme s'il s'agissait de "
+"dossiers. Cela permet d'associer facilement un ensemble de scènes à leur "
+"chapitre. Vous pouvez également procéder de la même manière dans vos "
+"notes, où vous pouvez par exemple avoir une hiérarchie de vos lieux."
+
+#: ../../source/usage/organising_project.rst:134
+msgid ""
+"The name on a document in the project tree is not linked to any headings "
+"in the document text. Think of the document name as a file name. You can "
+"rename a document, or any other item in the project, at any time."
+msgstr ""
+"Le nom d'un document dans l'arborescence du projet n'est lié à aucun "
+"titre dans le texte du document. Considérez le nom du document comme un "
+"nom de fichier. Vous pouvez renommer un document, ou tout autre élément "
+"du projet, à tout moment."
+
+#: ../../source/usage/organising_project.rst:138
+msgid "Documents come in two types:"
+msgstr "Les documents sont de deux types :"
+
+#: ../../source/usage/organising_project.rst:140
+msgid "**Novel Documents**"
+msgstr "**Documents du roman**"
+
+#: ../../source/usage/organising_project.rst:141
+msgid ""
+"These are the documents that make up your story or novel. They can only "
+"be added under a root folder of type **Novel**. You can technically also "
+"add them under **Archive**. See :ref:`docs_usage_headings` for more "
+"details on how these documents are handled by novelWriter."
+msgstr ""
+"Ce sont les documents qui constituent votre histoire ou votre roman. Ils "
+"ne peuvent être ajoutés que dans un dossier racine de type **Roman**. "
+"Techniquement, vous pouvez aussi les ajouter dans **Archive**. Voir :ref:"
+"`docs_usage_headings` pour plus de détails sur la façon dont ces "
+"documents sont gérés par novelWriter."
+
+#: ../../source/usage/organising_project.rst:145
+msgid "**Project Notes**"
+msgstr "*Notes de projet**"
+
+#: ../../source/usage/organising_project.rst:146
+msgid ""
+"These are the documents where you keep your notes. You can add them "
+"anywhere in your project, including under **Novel** type folders. If you "
+"do add them there, they are not treated as a part of the story by "
+"default."
+msgstr ""
+"Il s'agit des documents dans lesquels vous conservez vos notes. Vous "
+"pouvez les ajouter n'importe où dans votre projet, y compris dans les "
+"dossiers de type **Roman**. Si vous les ajoutez à cet endroit, ils ne "
+"sont pas traités par défaut comme faisant partie de l'histoire."
+
+#: ../../source/usage/organising_project.rst:150
+msgid ""
+"You can convert between the two types of documents where both types are "
+"allowed. You can also convert folders into documents, which may "
+"sometimes be convenient too."
+msgstr ""
+"Vous pouvez convertir les deux types de documents lorsque les deux types "
+"sont autorisés. Vous pouvez également convertir des dossiers en "
+"documents, ce qui peut parfois s'avérer pratique."
+
+#: ../../source/usage/organising_project.rst:153
+msgid ""
+"Another convenient feature is that documents can be split into sub-"
+"documents by its headings, or multiple documents merged into one. This "
+"is particularly useful if you start out with larger structural "
+"documents, like one containing all chapters and scenes in an act, and "
+"then split those when you start writing. See :ref:`docs_ui_split_merge` "
+"for more details."
+msgstr ""
+"Une autre caractéristique pratique est que les documents peuvent être "
+"divisés en sous-documents par leurs titres, ou que plusieurs documents "
+"peuvent être fusionnés en un seul. Ceci est particulièrement utile si "
+"vous commencez avec des documents structurels plus importants, comme un "
+"document contenant tous les chapitres et scènes d'un acte, et que vous "
+"les divisez ensuite lorsque vous commencez à écrire. Voir :ref:"
+"`docs_ui_split_merge` pour plus de détails."
+
+#: ../../source/usage/organising_project.rst:162
+msgid "Document Templates"
+msgstr "Modèles de documents"
+
+#: ../../source/usage/organising_project.rst:164
+msgid ""
+"If you wish to create template documents to be used when creating new "
+"documents, like for instance a character note template, you can add a "
+"**Templates** root folder to your project. Any document added to this "
+"root folder will show up in the **Add Item** menu in the project tree "
+"toolbar. When selected, a new document is created with its content "
+"copied from the chosen template."
+msgstr ""
+"Si vous souhaitez créer des documents modèles à utiliser lors de la "
+"création de nouveaux documents, comme par exemple un modèle de note de "
+"personnage, vous pouvez ajouter un dossier racine **Modèles** à votre "
+"projet.Tout document ajouté à ce dossier racine apparaîtra dans le menu "
+"**Ajouter un élément** de la barre d'outils de l'arborescence du projet."
+"Lorsqu'il est sélectionné, un nouveau document est créé dont le contenu "
+"est copié à partir du modèle choisi."
+
+#: ../../source/usage/organising_project.rst:175
+msgid "Active and Inactive Documents"
+msgstr "Documents actifs et inactifs"
+
+#: ../../source/usage/organising_project.rst:177
+msgid ""
+"A document can be set as \"Active\" or \"Inactive\", which alters the "
+"icon in the third column of the project tree. These are mostly intended "
+"for your convenience as they will indicate whether the document is meant "
+"to be included in the manuscript or not. You can think of an inactive "
+"status as a whole-document out-take. It allows you to take it out "
+"without moving it to **Archive**."
+msgstr ""
+"Un document peut être défini comme « actif » ou « inactif », ce qui "
+"modifie l'icône dans la troisième colonne de l'arborescence du projet. "
+"Ces statuts sont principalement destinés à vous faciliter la tâche, car "
+"ils indiquent si le document est destiné à être inclus dans le manuscrit "
+"ou non. Vous pouvez considérer le statut inactif comme un retrait du "
+"document entier. Il vous permet de le retirer sans le déplacer vers "
+"**Archives**."
+
+#: ../../source/usage/organising_project.rst:182
+msgid ""
+"Inactive documents are by default excluded from your manuscript, but you "
+"can override this if you wish. See :ref:`docs_ui_manuscript_selection` "
+"for more details."
+msgstr ""
+"Les documents inactifs sont par défaut exclus de votre manuscrit, mais "
+"vous pouvez modifier cela si vous le souhaitez. Voir :ref:"
+"`docs_ui_manuscript_selection` pour plus de détails."
+
+#: ../../source/usage/organising_project.rst:189
+msgid "Importance and Status"
+msgstr "Importance et état"
+
+#: ../../source/usage/organising_project.rst:191
+msgid ""
+"Each document or folder in your project can have either a \"Status\" or "
+"\"Importance\" label set. These are labels and icons that you control "
+"and define yourself, and novelWriter doesn't use them for anything. You "
+"can modify these labels in **Project Settings**. See :ref:"
+"`docs_ui_projects_settings_status` for more details."
+msgstr ""
+"Chaque document ou dossier de votre projet peut avoir une étiquette « "
+"Statut » ou « Importance ». Ce sont des étiquettes et des icônes que "
+"vous contrôlez et définissez vous-même, et novelWriter ne les utilise "
+"pas pour quoi que ce soit. Vous pouvez modifier ces étiquettes dans "
+"**Paramètres du projet**. Voir :ref:`docs_ui_projects_settings_status` "
+"pour plus de détails."
+
+#: ../../source/usage/organising_project.rst:196
+msgid ""
+"The \"Status\" labels are intended to tag a novel document as for "
+"instance a draft or as completed, and the \"Importance\" labels are "
+"intended to tag character notes, or other project notes, as for instance "
+"a main, major, or minor character or story element."
+msgstr ""
+"Les étiquettes « Statut » sont destinées à étiqueter un document de "
+"roman comme étant par exemple un brouillon ou comme étant terminé, et "
+"les étiquettes « Importance » sont destinées à étiqueter les notes sur "
+"les personnages, ou d'autres notes sur le projet, comme par exemple un "
+"personnage principal, majeur ou mineur ou un élément de l'histoire."
+
+#: ../../source/usage/organising_project.rst:200
+msgid ""
+"Whether a document uses a \"Status\" or \"Importance\" label depends on "
+"which root folder it lives in. If it's in a **Novel** type folder, it "
+"uses the \"Status\" label, otherwise it uses an \"Importance\" label."
+msgstr ""
+"L'utilisation d'une étiquette « Statut » ou « Importance » pour un "
+"document dépend du dossier racine dans lequel il se trouve. S'il se "
+"trouve dans un dossier de type **Roman**, il utilise l'étiquette « "
+"Statut », sinon il utilise l'étiquette « Importance »."

docs/source/locales/fr/LC_MESSAGES/usage/tags_and_references.po

@@ -0,0 +1,548 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 14:07+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/usage/tags_and_references.rst:5
+msgid "Tags and References"
+msgstr "Étiquettes et références"
+
+#: ../../source/usage/tags_and_references.rst:7
+msgid ""
+"One of the core features of novelWriter is its **Tags and References** "
+"system. This is perhaps one of the features that makes novelWriter "
+"different from other similar applications. It is therefore not always "
+"obvious to new users how this is supposed to work."
+msgstr ""
+"L'une des principales caractéristiques de novelWriter est son système "
+"d'**Étiquettes et de Références**. C'est peut-être l'une des "
+"caractéristiques qui différencie novelWriter d'autres applications "
+"similaires. Il n'est donc pas toujours évident pour les nouveaux "
+"utilisateurs de comprendre comment cela est censé fonctionner."
+
+#: ../../source/usage/tags_and_references.rst:11
+msgid ""
+"In novelWriter there are no forms or tables to fill in to define "
+"characters, locations or other elements of your story. Instead, you "
+"create documents in one of the root folders for notes. Within these "
+"documents you can set **tags**, like for instance for your main "
+"character. If you then want to annotate a scene with this character as "
+"its point-of-view, you create a **reference** to the tag."
+msgstr ""
+"Dans novelWriter, il n'y a pas de formulaires ou de tableaux à remplir "
+"pour définir les personnages, les lieux ou d'autres éléments de votre "
+"histoire. Au lieu de cela, vous créez des documents dans l'un des "
+"dossiers racine pour les notes. Dans ces documents, vous pouvez définir "
+"des **étiquettes**, par exemple pour votre personnage principal. Si vous "
+"souhaitez ensuite annoter une scène avec ce personnage comme point de "
+"vue, vous créez une **référence** à l'étiquette."
+
+#: ../../source/usage/tags_and_references.rst:19
+msgid ""
+"If you find the Tags and Reference system difficult to follow just from "
+"reading this chapter, you can create a new project in the **Welcome** "
+"dialog's New Project form and select \"Create an example project\" from "
+"the \"Pre-fill project\" option. The example project contains several "
+"examples of tags and references."
+msgstr ""
+"Si le système d'étiquettes et de références vous semble difficile à "
+"suivre à la seule lecture de ce chapitre, vous pouvez créer un nouveau "
+"projet dans le formulaire Nouveau projet de la boîte de dialogue "
+"**Bienvenue** et sélectionner « Créer un projet d'exemple » dans l'option "
+"« Pré-remplir le projet ». Le projet d'exemple contient plusieurs "
+"exemples d'étiquettes et de références."
+
+#: ../../source/usage/tags_and_references.rst:28
+msgid "How to Use Tags"
+msgstr "Comment utiliser les étiquettes"
+
+#: ../../source/usage/tags_and_references.rst:30
+msgid ""
+"The structure of your novelWriter project is inferred from the headings "
+"within the documents, not the documents themselves. See :ref:"
+"`docs_usage_headings` for more details. Therefore, metadata is also "
+"associated with headings, and not the documents themselves."
+msgstr ""
+"La structure de votre projet novelWriter est déduite des titres des "
+"documents, et non des documents eux-mêmes. Voir :ref:"
+"`docs_usage_headings` pour plus de détails. Par conséquent, les "
+"métadonnées sont également associées aux titres, et non aux documents eux-"
+"mêmes."
+
+#: ../../source/usage/tags_and_references.rst:34
+msgid ""
+"A \"tag\" in novelWriter is a word or phrase that you define as belonging "
+"to a heading. Tags are set by using the ``@tag`` keyword."
+msgstr ""
+"Une « étiquette » dans novelWriter est un mot ou une phrase que vous "
+"définissez comme appartenant à une rubrique. Les étiquettes sont définies "
+"en utilisant le mot-clé ``@tag``."
+
+#: ../../source/usage/tags_and_references.rst:37
+msgid "The basic format of a tag is ``@tag: TagName``."
+msgstr "Le format de base d'un tag est ``@tag: NomÉtiquette``."
+
+#: ../../source/usage/tags_and_references.rst:39
+msgid "An alternative format of a tag is ``@tag: TagName | Display Name``."
+msgstr ""
+"Un autre format de balise est ``@tag : NomÉtiquette | Nom Affiché``."
+
+#: ../../source/usage/tags_and_references.rst:41
+msgid "``tagName`` (Required)"
+msgstr "``NomÉtiquette`` (Requis)"
+
+#: ../../source/usage/tags_and_references.rst:42
+msgid ""
+"This is a unique identifier of your choosing. It is the value you use "
+"later for making references back to the heading in the document. The tag "
+"must be unique."
+msgstr ""
+"Il s'agit d'un identifiant unique de votre choix. C'est la valeur que "
+"vous utiliserez plus tard pour faire référence à l'intitulé dans le "
+"document. L'étiquette doit être unique."
+
+#: ../../source/usage/tags_and_references.rst:45
+msgid "``Display Name`` (Optional)"
+msgstr "``Nom Affiché`` (Facultatif)"
+
+#: ../../source/usage/tags_and_references.rst:46
+msgid ""
+"This is an optional display name used for the tag. When you build your "
+"manuscript, you can for instance insert the point-of-view character name "
+"directly into chapter titles. By default, the ``tagName`` value is used "
+"in such headings, but if you use a shortened format internally in your "
+"project, you can use the display name to specify a more suitable format "
+"for your chapter title."
+msgstr ""
+"Il s'agit d'un nom d'affichage facultatif utilisé pour l'étiquette. "
+"Lorsque vous construisez votre manuscrit, vous pouvez par exemple insérer "
+"le nom du personnage du point de vue directement dans les titres des "
+"chapitres. Par défaut, la valeur ``NomÉtiquette`` est utilisée dans ces "
+"titres, mais si vous utilisez un format raccourci en interne dans votre "
+"projet, vous pouvez utiliser le nom d'affichage pour spécifier un format "
+"plus approprié pour votre titre de chapitre."
+
+#: ../../source/usage/tags_and_references.rst:53
+msgid ""
+"You can only set **one** tag per heading, and the tag has to be unique "
+"across **all** documents in the project."
+msgstr ""
+"Vous ne pouvez définir **qu'une seule** étiquette par en-tête, et "
+"l'étiquette doit être unique dans **tous** les documents du projet."
+
+#: ../../source/usage/tags_and_references.rst:56
+msgid ""
+"After a tag has been defined, it can be referenced in novel documents, or "
+"cross-referenced in other notes. Tags will also show up in the **Outline "
+"View** and in the **References** panel under the document viewer when a "
+"document is open in the viewer. See :ref:`docs_ui_main_outline` and :ref:"
+"`docs_ui_edit_view_view_references` for more details."
+msgstr ""
+"Une fois qu'une étiquette a été définie, elle peut être référencée dans "
+"de nouveaux documents ou faire l'objet de références croisées dans "
+"d'autres notes. Les étiquettes apparaîtront également dans la **Vue en "
+"plan** et dans le panneau **Références** sous l'afficheur de documents "
+"lorsqu'un document est ouvert dans l'afficheur. Voir :ref:"
+"`docs_ui_main_outline` et :ref:`docs_ui_edit_view_view_references` pour "
+"plus de détails."
+
+#: ../../source/usage/tags_and_references.rst:61
+msgid ""
+"The editor will indicate to you that the keyword is correctly used and "
+"that the tag is allowed, that is, the tag is unique, by adding a colour "
+"highlighting to it. An invalid tag should have a wiggly line under it, "
+"and will not receive the colour that valid tags do."
+msgstr ""
+"L'éditeur vous indiquera que le mot-clé est correctement utilisé et que "
+"l'étiquette est autorisée, c'est-à-dire qu'elle est unique, en la "
+"surlignant d'une couleur. Une étiquette non valide doit être soulignée "
+"par une ligne ondulée et ne reçoit pas la même couleur que les étiquettes "
+"valides."
+
+#: ../../source/usage/tags_and_references.rst:65
+msgid ""
+"The tag is the only part of notes that novelWriter uses. The rest of the "
+"document content is there for you to use in whatever way you wish."
+msgstr ""
+"L'étiquette est la seule partie des notes que novelWriter utilise. Le "
+"reste du contenu du document peut être utilisé comme bon vous semble."
+
+#: ../../source/usage/tags_and_references.rst:70
+msgid ""
+"Tags are no longer case sensitive. The tags are by default displayed with "
+"the capitalisation you use when defining the tag, but you don't have to "
+"use the same capitalisation when referencing it later."
+msgstr ""
+"Les étiquettes ne sont plus sensibles à la casse. Les étiquettes sont "
+"affichées par défaut avec la majuscule utilisée lors de la définition de "
+"l'étiquette, mais vous n'êtes pas obligé d'utiliser la même majuscule "
+"lorsque vous y faites référence ultérieurement."
+
+#: ../../source/usage/tags_and_references.rst:76
+msgid "Tags can have an optional display name for manuscript builds."
+msgstr ""
+"Les étiquettes peuvent avoir un nom d'affichage facultatif pour la "
+"compilation du manuscrit."
+
+#: ../../source/usage/tags_and_references.rst:80
+msgid ""
+"You can now add tags also to Novel Documents. These can be used for cross-"
+"referencing between chapters and scenes, and also from notes if desired."
+msgstr ""
+"Vous pouvez désormais ajouter des étiquettes aux documents du roman. "
+"Celles-ci peuvent être utilisées pour les références croisées entre les "
+"chapitres et les scènes, ainsi qu'à partir des notes si vous le souhaitez."
+
+#: ../../source/usage/tags_and_references.rst:83
+#: ../../source/usage/tags_and_references.rst:200
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/usage/tags_and_references.rst:85
+msgid "Example of a note document for a character with a tag set:"
+msgstr ""
+"Exemple de document de notes pour un personnage avec un jeu d'étiquettes :"
+
+#: ../../source/usage/tags_and_references.rst:95
+msgid ""
+"When this is done in a document in a root folder of type **Characters**, "
+"the tag is automatically treated as an available character in your "
+"project with the value \"Jane\". You will then be able to reference "
+"\"Jane\" in any of your other documents using the reference keywords for "
+"characters."
+msgstr ""
+"Lorsque cela est fait dans un document d'un dossier racine de type "
+"**Personnages**, l'étiquette est automatiquement traitée comme un "
+"personnage disponible dans votre projet avec la valeur « Jane ». Vous "
+"pourrez alors faire référence à « Jane » dans n'importe lequel de vos "
+"autres documents en utilisant les mots-clés de référence pour les "
+"personnages."
+
+#: ../../source/usage/tags_and_references.rst:99
+msgid ""
+"The character \"Jane\" will also show up in the **Character** tab in the "
+"**Reference** panel below the document viewer."
+msgstr ""
+"Le personnage « Jane » apparaîtra également dans l'onglet **Personnage** "
+"du panneau **Référence** situé sous l'afficheur de document."
+
+#: ../../source/usage/tags_and_references.rst:104
+msgid ""
+"It is the root folder type that defines what category of story elements "
+"the tag is indexed under. See :ref:`docs_usage_project_roots` for more "
+"details."
+msgstr ""
+"C'est le type de dossier racine qui définit la catégorie d'éléments de "
+"l'histoire sous laquelle l'étiquette est indexée. Voir :ref:"
+"`docs_usage_project_roots` pour plus de détails."
+
+#: ../../source/usage/tags_and_references.rst:111
+msgid "How to Use References"
+msgstr "Comment utiliser les références"
+
+#: ../../source/usage/tags_and_references.rst:113
+msgid ""
+"Each heading of any level in your project can contain references to tags "
+"set in your notes. The references are gathered by the project index and "
+"used to generate the **Outline View**, among other things."
+msgstr ""
+"Chaque titre de n'importe quel niveau de votre projet peut contenir des "
+"références à des étiquettes définies dans vos notes. Ces références sont "
+"rassemblées par l'index du projet et utilisées pour générer la **Vue "
+"d'ensemble**, entre autres choses."
+
+#: ../../source/usage/tags_and_references.rst:117
+msgid ""
+"References are set with a special keyword, with a list of corresponding "
+"tags. The valid keywords are listed below. The format of a reference line "
+"is ``@keyword: value1, [value2] ... [valueN]``. All reference keywords "
+"allow multiple values."
+msgstr ""
+"Les références sont définies à l'aide d'un mot-clé spécial, accompagné "
+"d'une liste d'étiquettes correspondantes. Les mots-clés valides sont "
+"listés ci-dessous. Le format d'une ligne de référence est ``@mot-clé : "
+"valeur1, [valeur2] ... [valeurN]``. Tous les mots-clés de référence "
+"autorisent des valeurs multiples."
+
+#: ../../source/usage/tags_and_references.rst:121
+msgid "``@pov``"
+msgstr "``@pov``"
+
+#: ../../source/usage/tags_and_references.rst:122
+msgid ""
+"The point-of-view character for the current section. The target must be a "
+"note tag in a **Character** type root folder."
+msgstr ""
+"Le personnage de point de vue pour la section en cours. La cible doit "
+"être une étiquette note dans un dossier racine de type **Personnages**."
+
+#: ../../source/usage/tags_and_references.rst:125
+msgid "``@focus``"
+msgstr "``@focus``"
+
+#: ../../source/usage/tags_and_references.rst:126
+msgid ""
+"The character that has the focus for the current section. This can be "
+"used in cases where the focus is not the point-of-view character. The "
+"target must be a note tag in a **Character** type root folder."
+msgstr ""
+"Le personnage qui est au centre de l'attention pour la section en cours. "
+"Ceci peut être utilisé dans les cas où le focus n'est pas un personnage "
+"de point de vue. La cible doit être une étiquette note dans un dossier "
+"racine de type **Personnages**."
+
+#: ../../source/usage/tags_and_references.rst:130
+msgid "``@char``"
+msgstr "``@char``"
+
+#: ../../source/usage/tags_and_references.rst:131
+msgid ""
+"For other characters in the current section. The target must be a note "
+"tag in a **Character** type root folder. This should not include the "
+"point-of-view or focus character if those references are used."
+msgstr ""
+"Autres personnages de la section courante. La cible doit être une "
+"étiquette de note dans un dossier racine de type **Personnages**. Cela ne "
+"doit pas inclure le point de vue ou le personnage principal si ces "
+"références sont utilisées."
+
+#: ../../source/usage/tags_and_references.rst:135
+msgid "``@plot``"
+msgstr "``@plot``"
+
+#: ../../source/usage/tags_and_references.rst:136
+msgid ""
+"The plot or subplot advanced in the current section. The target must be a "
+"note tag in a **Plot** type root folder."
+msgstr ""
+"L'intrigue ou la sous-intrigue développée dans la section en cours. La "
+"cible doit être une étiquette note dans un dossier racine de type "
+"**Intrigue**."
+
+#: ../../source/usage/tags_and_references.rst:139
+msgid "``@time``"
+msgstr "``@time``"
+
+#: ../../source/usage/tags_and_references.rst:140
+msgid ""
+"The timelines touched by the current section. The target must be a note "
+"tag in a **Timeline** type root folder."
+msgstr ""
+"Les lignes de temps concernées par la section en cours. La cible doit "
+"être une étiquette note dans un dossier racine de type **Chronologie**."
+
+#: ../../source/usage/tags_and_references.rst:143
+msgid "``@location``"
+msgstr "``@location``"
+
+#: ../../source/usage/tags_and_references.rst:144
+msgid ""
+"The location the current section takes place in. The target must be a "
+"note tag in a **Locations** type root folder."
+msgstr ""
+"L'endroit où se déroule la section en cours. La cible doit être une "
+"étiquette note dans un dossier racine de type **lieux**."
+
+#: ../../source/usage/tags_and_references.rst:147
+msgid "``@object``"
+msgstr "``@object``"
+
+#: ../../source/usage/tags_and_references.rst:148
+msgid ""
+"Objects present in the current section. The target must be a note tag in "
+"a **Object** type root folder."
+msgstr ""
+"Objets présents dans la section courante. La cible doit être une "
+"étiquette de note dans un dossier racine de type **Objets**."
+
+#: ../../source/usage/tags_and_references.rst:151
+msgid "``@entity``"
+msgstr "``@entity``"
+
+#: ../../source/usage/tags_and_references.rst:152
+msgid ""
+"Entities present in the current section. The target must be a note tag in "
+"an **Entities** type root folder."
+msgstr ""
+"Entités présentes dans la section courante. La cible doit être une "
+"étiquette note dans un dossier racine de type **Entités**."
+
+#: ../../source/usage/tags_and_references.rst:155
+msgid "``@custom``"
+msgstr "``@custom``"
+
+#: ../../source/usage/tags_and_references.rst:156
+msgid ""
+"Custom references in the current section. The target must be a note tag "
+"in a **Custom** type root folder. The custom folder are for any other "
+"category of notes you may want to use."
+msgstr ""
+"Références personnalisées dans la section en cours. La cible doit être "
+"une étiquette de note dans un dossier racine de type **personnalisé**. "
+"Les dossiers personnalisés sont destinés à toute autre catégorie de notes "
+"que vous souhaiteriez utiliser."
+
+#: ../../source/usage/tags_and_references.rst:159
+msgid "``@mention``"
+msgstr "``@mention``"
+
+#: ../../source/usage/tags_and_references.rst:160
+msgid ""
+"For anything, anyone or anyplace mentioned, but not present in the "
+"current section. It is intended for those cases where you reveal details "
+"about a character or place in a scene without otherwise being a part of "
+"it. This can be useful when checking for consistency later. Any tag in "
+"any root note folder can be listed under ``@mention``."
+msgstr ""
+"Pour toute chose, toute personne ou tout lieu mentionné, mais non présent "
+"dans la section en cours. Il est destiné aux cas où vous révélez des "
+"détails sur un personnage ou un lieu dans une scène sans en faire partie. "
+"Cela peut s'avérer utile pour vérifier la cohérence ultérieurement. "
+"N'importe quel étiquette dans n'importe quel dossier de notes racine peut "
+"être listé sous `@mention``."
+
+#: ../../source/usage/tags_and_references.rst:165
+msgid "``@story``"
+msgstr "``@story``"
+
+#: ../../source/usage/tags_and_references.rst:166
+msgid ""
+"This is used when referencing a Novel Document, like a scene or chapter, "
+"from somewhere else in your project. It is possible to also set tags in "
+"documents in a **Novel** type folder, and this is the keyword you use to "
+"reference those."
+msgstr ""
+"Ce mot-clé est utilisé pour référencer un document de roman, comme une "
+"scène ou un chapitre, à partir d'un autre endroit de votre projet. Il est "
+"également possible de définir des étiquettes dans les documents d'un "
+"dossier de type **Roman**, et c'est le mot-clé que vous utilisez pour "
+"référencer ces documents."
+
+#: ../../source/usage/tags_and_references.rst:170
+msgid ""
+"When tags and references are used correctly, it will be indicated by "
+"highlight colours in the editor."
+msgstr ""
+"Lorsque les étiquettes et les références sont utilisés correctement, cela "
+"est indiqué par des couleurs en surbrillance dans l'éditeur."
+
+#: ../../source/usage/tags_and_references.rst:175
+msgid ""
+"The highlighter may be mistaken if the index of defined tags is out of "
+"date. If so, press :kbd:`F9` to regenerate it, or select **Rebuild "
+"Index** from the **Tools** menu. In general, the index for a document is "
+"regenerated when it is saved, so this shouldn't normally be necessary."
+msgstr ""
+"Le surligneur peut se tromper si l'index des étiquettes définies n'est "
+"pas à jour. Si c'est le cas, appuyez sur :kbd:`F9` pour le régénérer, ou "
+"sélectionnez **Reconstruire l'index** dans le menu **Outils**. En "
+"général, l'index d'un document est régénéré lorsqu'il est sauvegardé, ce "
+"qui ne devrait pas être nécessaire."
+
+#: ../../source/usage/tags_and_references.rst:181
+msgid ""
+"If you add a reference in the editor to a tag that doesn't yet exist, you "
+"can right-click it and select **Create Note for Tag**. This will generate "
+"a new note automatically in the correct type of root folder, with the new "
+"tag defined."
+msgstr ""
+"Si vous ajoutez une référence dans l'éditeur à une étiquette qui n'existe "
+"pas encore, vous pouvez cliquer dessus avec le bouton droit de la souris "
+"et sélectionner **Créer une note pour l'étiquette**. Cela générera "
+"automatiquement une nouvelle note dans le bon type de dossier racine, "
+"avec la nouvelle étiquette définie."
+
+#: ../../source/usage/tags_and_references.rst:185
+msgid ""
+"One note can also reference another note in the same way novel documents "
+"do. When the note is opened in the document viewer, the references become "
+"clickable links, making it easier to follow connections in the plot. You "
+"can follow links in the document editor by clicking them with the mouse "
+"while holding down the :kbd:`Ctrl` key. Clicked links are always opened "
+"in the view panel."
+msgstr ""
+"Une note peut également faire référence à une autre note, de la même "
+"manière que les documents de romans. Lorsque la note est ouverte dans "
+"l'éditeur de documents, les références deviennent des liens cliquables, "
+"ce qui facilite le suivi des connexions dans l'intrigue. Vous pouvez "
+"suivre les liens dans l'éditeur de documents en les cliquant avec la "
+"souris tout en maintenant la touche :kbd:`Ctrl` enfoncée. Les liens "
+"cliqués sont toujours ouverts dans le panneau de visualisation."
+
+#: ../../source/usage/tags_and_references.rst:190
+msgid ""
+"Your notes don't show up in the **Outline View**, so referencing between "
+"notes is only meaningful if you want to be able to click-navigate between "
+"them, or of course if you just want to highlight that two notes are "
+"related."
+msgstr ""
+"Vos notes n'apparaissent pas dans la **Vue d'ensemble**, de sorte que les "
+"références entre les notes n'ont de sens que si vous souhaitez pouvoir "
+"naviguer d'une note à l'autre par un simple clic ou, bien sûr, si vous "
+"souhaitez simplement mettre en évidence que deux notes sont liées."
+
+#: ../../source/usage/tags_and_references.rst:196
+msgid ""
+"If you cross-reference between notes and export your project as an HTML "
+"document using the **Manuscript Build** tool, the cross-references become "
+"clickable links in the exported HTML document as well."
+msgstr ""
+"Si vous faites des références croisées entre les notes et que vous "
+"exportez votre projet en tant que document HTML à l'aide de l'outil "
+"**Compiler le manuscrit**, les références croisées deviennent également "
+"des liens cliquables dans le document HTML exporté."
+
+#: ../../source/usage/tags_and_references.rst:202
+msgid "Example of a novel document with references to characters and plots:"
+msgstr ""
+"Exemple de document de roman avec références aux personnages et aux "
+"intrigues :"
+
+#: ../../source/usage/tags_and_references.rst:221
+msgid "Auto-Completion in the Editor"
+msgstr "Autocomplétion dans l'éditeur"
+
+#: ../../source/usage/tags_and_references.rst:223
+msgid ""
+"An auto-completer context menu will show up automatically in the document "
+"editor when you type the character ``@`` on a new line. It will first "
+"suggest tag or reference keywords for you to add, and after the ``:`` has "
+"been added, suggest references from the list of tags you have already "
+"defined."
+msgstr ""
+"Un menu contextuel d'auto-complétion s'affiche automatiquement dans "
+"l'éditeur de document lorsque vous tapez le caractère ``@`` sur une "
+"nouvelle ligne. Il vous proposera d'abord des mots-clés d'étiquette ou de "
+"référence à ajouter, puis, après l'ajout de ``:``, des références à "
+"partir de la liste des étiquettes que vous avez déjà définies."
+
+#: ../../source/usage/tags_and_references.rst:227
+msgid ""
+"You can use the auto-completer to add multiple references with a ``,`` "
+"between them, and even type new ones. Notes for new references can be "
+"created by right-clicking on them and selecting **Create Note for Tag** "
+"from the menu."
+msgstr ""
+"Vous pouvez utiliser l'auto-complétion pour ajouter plusieurs références "
+"avec un ``,`` entre elles, et même en taper de nouvelles. Les notes pour "
+"les nouvelles références peuvent être créées en faisant un clic droit sur "
+"celles-ci et en sélectionnant **Créer une note pour l'étiquette** dans le "
+"menu."

docs/source/locales/fr/LC_MESSAGES/user_interface/editor_viewer.po

@@ -0,0 +1,440 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 17:39+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/user_interface/editor_viewer.rst:5
+msgid "The Editor and Viewer"
+msgstr "L'éditeur et l'afficheur"
+
+#: ../../source/user_interface/editor_viewer.rst:9
+msgid ""
+"This chapter covers in more detail how the document editor and viewer "
+"panels work."
+msgstr ""
+"Ce chapitre décrit plus en détail le fonctionnement de l'éditeur de "
+"documents et des panneaux de visualisation."
+
+#: ../../source/user_interface/editor_viewer.rst:15
+msgid "Editing a Document"
+msgstr "Édition d'un document"
+
+#: ../../source/user_interface/editor_viewer.rst:19
+msgid "A screenshot of the Document Editor panel."
+msgstr "Capture d'écran du panneau de l'éditeur de documents."
+
+#: ../../source/user_interface/editor_viewer.rst:21
+msgid ""
+"To edit a document, double-click it in the project tree, press the :kbd:"
+"`Return` key while having it selected, or drag and drop it onto the "
+"editor panel. This will open the document in the document editor."
+msgstr ""
+"Pour éditer un document, double-cliquez dessus dans l'arborescence du "
+"projet, appuyez sur la touche :kbd:`Return` lorsqu'il est sélectionné, "
+"ou faites-le glisser et déposez-le dans le panneau de l'éditeur. Le "
+"document s'ouvre alors dans l'éditeur de documents."
+
+#: ../../source/user_interface/editor_viewer.rst:25
+msgid ""
+"The editor has a maximise button, which toggles the **Focus Mode**, and "
+"a close button in the top--right corner. On the top--left side you will "
+"find a tools button that opens a toolbar with a few buttons for applying "
+"text formatting, a drop down menu for navigating between headings, and a "
+"search button to open the search dialog."
+msgstr ""
+"L'éditeur dispose d'un bouton d'agrandissement, qui permet de basculer "
+"en **Mode sans distraction**, et d'un bouton de fermeture dans le coin "
+"supérieur droit. En haut à gauche, vous trouverez un bouton « Outils » "
+"qui ouvre une barre d'outils avec quelques boutons pour appliquer le "
+"formatage du texte, un menu déroulant pour naviguer entre les rubriques, "
+"et un bouton « Recherche » pour ouvrir la boîte de dialogue de recherche."
+
+#: ../../source/user_interface/editor_viewer.rst:30
+msgid ""
+"Both the document editor and viewer will show the label of the currently "
+"open document in the header at the top of the edit or view panel. "
+"Optionally, the full project path to the document can be shown. This can "
+"be set in **Preferences**."
+msgstr ""
+"L'éditeur de documents et la visualisation affichent l'étiquette du "
+"document actuellement ouvert dans l'en-tête en haut du panneau d'édition "
+"ou de visualisation. En option, le chemin complet du projet vers le "
+"document peut être affiché. Cette option peut être définie dans les "
+"**Préférences**."
+
+#: ../../source/user_interface/editor_viewer.rst:36
+msgid ""
+"Clicking on the document title bar will select the document in the "
+"project tree and thus reveal its location there, making it easier to "
+"find in a large project."
+msgstr ""
+"En cliquant sur la barre de titre du document, vous sélectionnez le "
+"document dans l'arborescence du projet et révélez ainsi son emplacement, "
+"ce qui permet de le retrouver plus facilement dans un projet volumineux."
+
+#: ../../source/user_interface/editor_viewer.rst:39
+msgid ""
+"Any references in the editor can be opened in the viewer by moving the "
+"cursor to the label and pressing :kbd:`Ctrl+Return`. You can also "
+"control-click them with your mouse."
+msgstr ""
+"Toutes les références de l'éditeur peuvent être ouvertes dans "
+"l'afficheur en déplaçant le curseur sur l'étiquette et en appuyant sur :"
+"kbd:`Ctrl+Return`. Vous pouvez également faire un contrôle-clic avec "
+"votre souris."
+
+#: ../../source/user_interface/editor_viewer.rst:44
+msgid "Spell Checking"
+msgstr "Vérification de l'orthographe"
+
+#: ../../source/user_interface/editor_viewer.rst:46
+msgid ""
+"A third party library called Enchant is used for spell checking in the "
+"editor. The controls for spell checking are found in the **Tools** menu. "
+"You can also set spell checking language in **Project Settings**."
+msgstr ""
+"Une bibliothèque tierce appelée Enchant est utilisée pour la "
+"vérification orthographique dans l'éditeur. Les commandes de "
+"vérification orthographique se trouvent dans le menu **Outils**. Vous "
+"pouvez également définir la langue de la vérification orthographique "
+"dans **Paramètres du projet**."
+
+#: ../../source/user_interface/editor_viewer.rst:50
+msgid ""
+"This spell checking library comes with support for custom words that you "
+"can add by selecting \"Add Word to Dictionary\" from the context menu "
+"when a word is highlighted by the spell checker as misspelled. The "
+"custom words are managed on a per-project basis, and the list of words "
+"can be edited from the **Project Word List** tool available from the "
+"**Tools** menu."
+msgstr ""
+"Cette bibliothèque de vérification orthographique prend en charge les "
+"mots personnalisés que vous pouvez ajouter en sélectionnant « Ajouter un "
+"mot au dictionnaire » dans le menu contextuel lorsqu'un mot est mis en "
+"évidence par le vérificateur orthographique comme étant mal "
+"orthographié. Les mots personnalisés sont gérés par projet et la liste "
+"des mots peut être modifiée à partir de l'outil **Liste de mots du "
+"projet** disponible dans le menu **Outils**.\n"
+"\n"
+"Traduit avec DeepL.com (version gratuite)"
+
+#: ../../source/user_interface/editor_viewer.rst:57
+msgid ""
+"Generally, spell checking dictionaries are collected from your operating "
+"system, but on Windows they are not. See :ref:`docs_more_custom_dict` "
+"for how to add spell checking dictionaries on Windows."
+msgstr ""
+"En général, les dictionnaires de vérification orthographique sont "
+"recueillis par votre système d'exploitation, mais ce n'est pas le cas "
+"sous Windows. Voir :ref:`docs_more_custom_dict` pour savoir comment "
+"ajouter des dictionnaires de vérification orthographique sous Windows."
+
+#: ../../source/user_interface/editor_viewer.rst:63
+msgid "Word Counts"
+msgstr "Nombre de mots"
+
+#: ../../source/user_interface/editor_viewer.rst:65
+msgid ""
+"A character, word, and paragraph count is maintained for each document, "
+"as well as for each section of a document following a heading. The word "
+"count and change of words in the current session is displayed in the "
+"footer of any document open in the editor, and all stats are shown in "
+"the details panel below the project tree for any document selected in "
+"the project or novel trees."
+msgstr ""
+"Un décompte des caractères, des mots et des paragraphes est maintenu "
+"pour chaque document, ainsi que pour chaque section d'un document "
+"suivant un titre. Le nombre de mots et le changement de mots dans la "
+"session en cours sont affichés dans le pied de page de tout document "
+"ouvert dans l'éditeur, et toutes les statistiques sont affichées dans le "
+"panneau de détails situé sous l'arborescence du projet pour tout "
+"document sélectionné dans l'arborescence du projet ou des romans."
+
+#: ../../source/user_interface/editor_viewer.rst:70
+msgid ""
+"The word counts are not updated in real time, but run in the background "
+"every few seconds for as long as the document is being actively edited."
+msgstr ""
+"Le décompte des mots n'est pas mis à jour en temps réel, mais s'exécute "
+"en arrière-plan toutes les quelques secondes tant que le document est "
+"activement édité."
+
+#: ../../source/user_interface/editor_viewer.rst:73
+msgid ""
+"A total project word count is displayed in the status bar. The total "
+"count depends on the sum of the values in the project tree, which again "
+"depend on an up to date project index. If the counts seem wrong, a full "
+"project word recount can be initiated by rebuilding the project's index. "
+"Either from the **Tools** menu, or by pressing :kbd:`F9`."
+msgstr ""
+"Le nombre total de mots du projet est affiché dans la barre d'état. Le "
+"décompte total dépend de la somme des valeurs de l'arborescence du "
+"projet, qui dépendent à leur tour d'un index du projet à jour. Si le "
+"décompte semble erroné, un recomptage complet des mots du projet peut "
+"être lancé en reconstruisant l'index du projet. Soit à partir du menu "
+"**Outils**, soit en appuyant sur :kbd:`F9`."
+
+#: ../../source/user_interface/editor_viewer.rst:78
+msgid ""
+"The rules for how the counts are made is covered in more detail in :ref:"
+"`docs_more_counting`."
+msgstr ""
+"Les règles de comptage sont décrites plus en détail dans :ref:"
+"`docs_more_counting`."
+
+#: ../../source/user_interface/editor_viewer.rst:82
+msgid ""
+"For some languages, character count is the more interesting statistics. "
+"You can select to display character count instead of word count in the "
+"user interface in **Preferences**."
+msgstr ""
+"Pour certaines langues, le nombre de caractères est la statistique la "
+"plus intéressante. Vous pouvez choisir d'afficher le nombre de "
+"caractères plutôt que le nombre de mots dans l'interface utilisateur "
+"dans **Préférences**."
+
+#: ../../source/user_interface/editor_viewer.rst:91
+msgid "Search & Replace"
+msgstr "Rechercher & Remplacer"
+
+#: ../../source/user_interface/editor_viewer.rst:95
+msgid "A screenshot of the Document Editor search box."
+msgstr ""
+"Capture d'écran de la boîte de recherche de l'éditeur de documents."
+
+#: ../../source/user_interface/editor_viewer.rst:97
+msgid ""
+"The document editor has a search and replace tool that can be activated "
+"with :kbd:`Ctrl+F` for search mode or :kbd:`Ctrl+H` for search and "
+"replace mode."
+msgstr ""
+"L'éditeur de documents dispose d'un outil de recherche et de "
+"remplacement qui peut être activé avec :kbd:`Ctrl+F` pour le mode "
+"recherche ou :kbd:`Ctrl+H` pour le mode recherche et remplacement."
+
+#: ../../source/user_interface/editor_viewer.rst:100
+msgid ""
+"Pressing :kbd:`Return` while in the search box will search for the next "
+"occurrence of the word, and :kbd:`Shift+Return` for the previous. "
+"Pressing :kbd:`Return` in the replace box, will replace the highlighted "
+"text and move to the next result."
+msgstr ""
+"En appuyant sur :kbd:`Retour` dans le champ de recherche, on recherche "
+"l'occurrence suivante du mot, et :kbd:`Maj+Retour` l'occurrence "
+"précédente. En appuyant sur :kbd:`Retour` dans la zone de remplacement, "
+"vous remplacerez le texte surligné et passerez au résultat suivant."
+
+#: ../../source/user_interface/editor_viewer.rst:104
+msgid ""
+"There are a number of settings for the search tool available as toggle "
+"switches above the search box. They allow you to search for, in order: "
+"matched case only, whole word results only, search using regular "
+"expressions, loop search when reaching the end of the document, and move "
+"to the next document when reaching the end. There is also a switch that "
+"will try to match the case of the word when the replacement is made. "
+"That is, it will try to keep the word upper, lower, or capitalised to "
+"match the word being replaced."
+msgstr ""
+"Il existe un certain nombre de paramètres pour l'outil de recherche, "
+"disponibles sous forme de commutateurs au-dessus de la boîte de "
+"recherche. Ils vous permettent de rechercher, dans l'ordre : la "
+"correspondance entre les majuscules et les minuscules, le mot entier "
+"uniquement, les expressions régulières, la recherche en boucle lorsque "
+"vous atteignez la fin du document et le passage au document suivant "
+"lorsque vous atteignez la fin du document. Il existe également un "
+"commutateur qui tente de faire correspondre la casse du mot au moment du "
+"remplacement. En d'autres termes, il essaiera de conserver le mot en "
+"majuscules, en minuscules ou en capitales pour qu'il corresponde au mot "
+"remplacé."
+
+#: ../../source/user_interface/editor_viewer.rst:115
+msgid "Auto-Replace as You Type"
+msgstr "Remplacement automatique au fur et à mesure de la saisie"
+
+#: ../../source/user_interface/editor_viewer.rst:117
+msgid ""
+"A few auto-replace features are supported by the editor. You can control "
+"every aspect of the auto-replace feature from **Preferences**. You can "
+"also disable this feature entirely if you wish."
+msgstr ""
+"Quelques fonctions de remplacement automatique sont prises en charge par "
+"l'éditeur. Vous pouvez contrôler tous les aspects de la fonction de "
+"remplacement automatique dans les **Préférences**. Vous pouvez également "
+"désactiver entièrement cette fonction si vous le souhaitez."
+
+#: ../../source/user_interface/editor_viewer.rst:122
+msgid ""
+"If you don't like auto-replacement, all symbols inserted by this feature "
+"are also available in the :guilabel:`Insert` menu, and via :ref:"
+"`docs_features_shortcuts_insert`. You may also be using a `Compose Key`_ "
+"setup, which means you may not need the auto-replace feature at all."
+msgstr ""
+"Si vous n'aimez pas le remplacement automatique, tous les symboles "
+"insérés par cette fonctionnalité sont également disponibles dans le "
+"menu :guilabel:`Insert`, et via :ref:`docs_features_shortcuts_insert`. "
+"Vous pouvez également utiliser une configuration `Compose Key`_, ce qui "
+"signifie que vous n'avez pas du tout besoin de la fonctionnalité de "
+"remplacement automatique."
+
+#: ../../source/user_interface/editor_viewer.rst:126
+msgid ""
+"The editor is able to replace two and three hyphens with short and long "
+"dashes, four dashes with a horizontal bar, three dots with ellipsis, and "
+"replace straight single and double quotes with user-defined quote "
+"symbols. It will also try to determine whether to use the opening or "
+"closing symbol, although this feature isn't always accurate. Especially "
+"distinguishing between closing single quote and apostrophe can be tricky "
+"for languages that use the same symbol for these, like English does."
+msgstr ""
+"L'éditeur est capable de remplacer deux et trois traits d'union par des "
+"tirets courts et longs, quatre tirets par une barre horizontale, trois "
+"points par une ellipse, et de remplacer les guillemets simples et "
+"doubles par des symboles de guillemets définis par l'utilisateur. Il "
+"tente également de déterminer s'il convient d'utiliser le symbole "
+"d'ouverture ou de fermeture, bien que cette fonction ne soit pas "
+"toujours exacte. En particulier, la distinction entre le guillemet "
+"simple fermant et l'apostrophe peut s'avérer délicate dans les langues "
+"qui utilisent le même symbole pour ces deux types de guillemets, comme "
+"c'est le cas en anglais."
+
+#: ../../source/user_interface/editor_viewer.rst:135
+msgid ""
+"If the auto-replace feature changes a symbol when you did not want it to "
+"change, pressing :kbd:`Ctrl+Z` once after the auto-replacement will undo "
+"it without undoing the character you typed."
+msgstr ""
+"Si la fonction de remplacement automatique modifie un symbole alors que "
+"vous ne le souhaitiez pas, appuyez sur :kbd:`Ctrl+Z` une fois après le "
+"remplacement automatique pour l'annuler sans annuler le caractère que "
+"vous avez tapé."
+
+#: ../../source/user_interface/editor_viewer.rst:143
+msgid "Viewing a Document"
+msgstr "Visualisation d'un document"
+
+#: ../../source/user_interface/editor_viewer.rst:147
+msgid "A screenshot of the Document Viewer panel."
+msgstr "Capture d'écran de la visualisation de documents."
+
+#: ../../source/user_interface/editor_viewer.rst:149
+msgid ""
+"Any document in the project tree can also be viewed in parallel in a "
+"right hand side document viewer. To view a document, press :kbd:"
+"`Ctrl+R`, select **View Document** in the menu or context menu, or drag "
+"and drop the document onto the viewer panel. If you have a middle mouse "
+"button, middle-clicking on the document will also open it in the viewer."
+msgstr ""
+"Tout document de l'arborescence du projet peut également être visualisé "
+"en parallèle dans une visionneuse de documents sur le côté droit. Pour "
+"visualiser un document, appuyez sur :kbd:`Ctrl+R`, sélectionnez "
+"**Afficher ce document** dans le menu ou le menu contextuel, ou glissez-"
+"déposez le document sur le panneau de visualisation. Si vous disposez "
+"d'un bouton du milieu de la souris, un clic du milieu sur le document "
+"l'ouvrira également dans l'afficheur."
+
+#: ../../source/user_interface/editor_viewer.rst:154
+msgid ""
+"The document viewed does not have to be the same document as the one "
+"currently being edited. However, If you *are* viewing the same document, "
+"pressing :kbd:`Ctrl+R` from the editor will update the document with "
+"your latest changes. You can also press the reload button in the top--"
+"right corner of the viewer panel, next to the close button, to achieve "
+"the same thing."
+msgstr ""
+"Le document visualisé ne doit pas nécessairement être le même que celui "
+"qui est en cours d'édition. Cependant, si vous *voyez* le même document, "
+"presser :kbd:`Ctrl+R` depuis l'éditeur mettra à jour le document avec "
+"vos dernières modifications. Vous pouvez également appuyer sur le bouton "
+"de rechargement dans le coin supérieur droit du panneau de "
+"visualisation, à côté du bouton de fermeture, pour obtenir la même chose."
+
+#: ../../source/user_interface/editor_viewer.rst:159
+msgid ""
+"In the viewer, references become clickable links. Clicking them will "
+"replace the content of the viewer with the content of the document the "
+"reference points to."
+msgstr ""
+"Dans l'afficheur, les références deviennent des liens cliquables. En "
+"cliquant sur ces liens, le contenu de l'afficheur est remplacé par le "
+"contenu du document auquel la référence renvoie."
+
+#: ../../source/user_interface/editor_viewer.rst:162
+msgid ""
+"The document viewer keeps a history of viewed documents, which you can "
+"navigate with the arrow buttons in the top--left corner of the viewer. "
+"If your mouse has backward and forward navigation buttons, these can be "
+"used as well. They work just like the backward and forward features in a "
+"browser. The left-most button is a dropdown menu for quickly navigation "
+"between headings in the document. The edit button on the right will open "
+"the viewed document in the editor."
+msgstr ""
+"L'afficheur de documents conserve un historique des documents consultés, "
+"que vous pouvez parcourir à l'aide des boutons fléchés situés dans le "
+"coin supérieur gauche du visualiseur. Si votre souris possède des "
+"boutons de navigation vers l'avant et vers l'arrière, vous pouvez "
+"également les utiliser. Ils fonctionnent de la même manière que les "
+"fonctions de navigation vers l'avant et vers l'arrière d'un navigateur. "
+"Le bouton le plus à gauche est un menu déroulant qui permet de naviguer "
+"rapidement entre les rubriques du document. Le bouton d'édition situé à "
+"droite permet d'ouvrir le document visualisé dans l'éditeur."
+
+#: ../../source/user_interface/editor_viewer.rst:172
+msgid "Document References"
+msgstr "Références des documents"
+
+#: ../../source/user_interface/editor_viewer.rst:174
+msgid ""
+"At the bottom of the viewer panel you will find a **References** panel. "
+"(If it is hidden, click the button on the left side of the footer area "
+"to reveal it.) This panel contains a References tab with links to all "
+"documents referring back to the one you're currently viewing, if any has "
+"been defined. If you have created root folders and tags for various "
+"story elements like characters and plot points, these will appear as "
+"additional tabs in this panel."
+msgstr ""
+"En bas du panneau de visualisation, vous trouverez un panneau "
+"**Références**. (S'il est caché, cliquez sur le bouton situé à gauche du "
+"pied de page pour le faire apparaître). Ce panneau contient un onglet "
+"Références avec des liens vers tous les documents qui renvoient à celui "
+"que vous êtes en train de visualiser, si un tel document a été défini. "
+"Si vous avez créé des dossiers racines et des étiquettes pour divers "
+"éléments de l'histoire, tels que les personnages et les points de "
+"l'intrigue, ceux-ci apparaîtront sous forme d'onglets supplémentaires "
+"dans ce panneau."
+
+#: ../../source/user_interface/editor_viewer.rst:182
+msgid ""
+"The **References** panel relies on an up-to-date project index. The "
+"index is maintained automatically. However, if anything is missing, or "
+"seems wrong, the index can always be rebuilt by selecting **Rebuild "
+"Index** from the **Tools** menu, or by pressing :kbd:`F9`."
+msgstr ""
+"Le panneau **Références** s'appuie sur un index des projets mis à jour. "
+"L'index est maintenu automatiquement. Cependant, si quelque chose manque "
+"ou semble erroné, l'index peut toujours être reconstruit en "
+"sélectionnant **Rebuild Index** dans le menu **Tools**, ou en pressant :"
+"kbd:`F9`."
+
+#: ../../source/user_interface/editor_viewer.rst:188
+msgid "The reference panel was redesigned and the additional tabs added."
+msgstr ""
+"Le panneau de référence a été redessiné et des onglets supplémentaires "
+"ont été ajoutés."

docs/source/locales/fr/LC_MESSAGES/user_interface/main_window.po

@@ -0,0 +1,500 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 16:42+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/user_interface/main_window.rst:5
+msgid "The Main Window"
+msgstr "La fenêtre principale"
+
+#: ../../source/user_interface/main_window.rst:7
+msgid ""
+"The user interface of novelWriter is intended to be as minimalistic as "
+"practically possible, while at the same time provide useful features "
+"needed for writing a novel."
+msgstr ""
+"L'interface utilisateur de novelWriter se veut aussi minimaliste que "
+"possible, tout en offrant les fonctionnalités utiles à l'écriture d'un "
+"roman."
+
+#: ../../source/user_interface/main_window.rst:10
+msgid ""
+"The main window does not by default have an editor toolbar like many "
+"other applications do. This reduces clutter, and since the documents are "
+"formatted with style tags, it is not needed most of the time. Still, a "
+"small formatting toolbar can be popped out by clicking the left-most "
+"button in the header of the document editor. It gives quick access to "
+"standard formatting codes."
+msgstr ""
+"La fenêtre principale ne comporte pas, par défaut, de barre d'outils "
+"d'édition, comme c'est le cas dans de nombreuses autres applications. "
+"Cela réduit l'encombrement et, comme les documents sont formatés avec "
+"des balises de style, la barre d'outils n'est pas nécessaire la plupart "
+"du temps. Néanmoins, une petite barre d'outils de formatage peut être "
+"affichée en cliquant sur le bouton le plus à gauche dans l'en-tête de "
+"l'éditeur de documents. Elle permet d'accéder rapidement aux codes de "
+"formatage standard."
+
+#: ../../source/user_interface/main_window.rst:15
+msgid ""
+"Most formatting features supported are also available through keyboard "
+"shortcuts, as well as available in the main menu under **Format**, so "
+"you don't have to look up formatting codes every time you need them. For "
+"reference, a list of all shortcuts can be found in the :ref:"
+"`docs_features_shortcuts` section."
+msgstr ""
+"La plupart des fonctions de formatage supportées sont également "
+"disponibles par des raccourcis clavier, ainsi que dans le menu principal "
+"sous **Format**, de sorte que vous n'avez pas à chercher les codes de "
+"formatage à chaque fois que vous en avez besoin. Pour référence, une "
+"liste de tous les raccourcis peut être trouvée dans la section :ref:"
+"`docs_features_shortcuts`."
+
+#: ../../source/user_interface/main_window.rst:20
+msgid ""
+"On the left side of the main window you will find a sidebar. This bar "
+"has buttons for the standard views you can switch between, a quick link "
+"to the **Build Manuscript** tool, and a set of project-related tools and "
+"quick access to settings at the bottom."
+msgstr ""
+"Sur le côté gauche de la fenêtre principale, vous trouverez une barre "
+"latérale. Cette barre comporte des boutons pour les vues standard entre "
+"lesquelles vous pouvez basculer, un lien rapide vers l'outil **Compiler "
+"le manuscrit**, ainsi qu'un ensemble d'outils liés au projet et un accès "
+"rapide aux paramètres dans la partie inférieure."
+
+#: ../../source/user_interface/main_window.rst:26
+msgid "Project Tree and Editor View"
+msgstr "Arborescence du projet et vue de l'éditeur"
+
+#: ../../source/user_interface/main_window.rst:30
+msgid "A screenshot of the Project Tree and Editor View."
+msgstr ""
+"Capture d'écran de l'arborescence du projet et de la vue de l'éditeur."
+
+#: ../../source/user_interface/main_window.rst:32
+msgid ""
+"When **Project Tree View** in the sidebar is selected, the work area is "
+"split in two, or optionally three, panels. The left-most panel contains "
+"the project tree and all the documents in your project. The second panel "
+"is the document editor."
+msgstr ""
+"Lorsque l'option **Arborescence du projet** de la barre latérale est "
+"sélectionnée, l'espace de travail est divisé en deux, ou éventuellement "
+"trois, panneaux. Le panneau le plus à gauche contient l'arborescence du "
+"projet et tous les documents de votre projet. Le deuxième panneau est "
+"l'éditeur de documents."
+
+#: ../../source/user_interface/main_window.rst:36
+msgid ""
+"An optional third panel on the right side contains a document viewer "
+"which can view any document in your project independently of what is "
+"open in the document editor. This panel is not intended as a preview "
+"window, although you can use it for this purpose if you wish. For "
+"instance if you need to check that the formatting tags behave as you "
+"expect. However, the main purpose of the viewer is for viewing your "
+"notes next to your editor while you're writing."
+msgstr ""
+"Un troisième panneau facultatif sur le côté droit contient une "
+"visionneuse de documents qui peut afficher n'importe quel document de "
+"votre projet indépendamment de ce qui est ouvert dans l'éditeur de "
+"documents. Ce panneau n'est pas conçu comme une fenêtre de "
+"prévisualisation, bien que vous puissiez l'utiliser à cette fin si vous "
+"le souhaitez. Par exemple, si vous avez besoin de vérifier que les "
+"balises de formatage se comportent comme vous le souhaitez. Cependant, "
+"l'objectif principal de la visionneuse est de visualiser vos notes à "
+"côté de votre éditeur pendant que vous écrivez."
+
+#: ../../source/user_interface/main_window.rst:42
+msgid ""
+"The editor also has a **Focus Mode** you can toggle either from the "
+"menu, from the icon in the editor's header, or by pressing :kbd:`F8`. "
+"When **Focus Mode** is enabled, all the user interface elements other "
+"than the document editor itself are hidden away."
+msgstr ""
+"L'éditeur dispose également d'un **Mode sans distraction** que vous "
+"pouvez activer soit à partir du menu, soit à partir de l'icône dans l'en-"
+"tête de l'éditeur, soit en appuyant sur :kbd:`F8`. Lorsque le **Mode "
+"sans distraction** est activé, tous les éléments de l'interface "
+"utilisateur autres que l'éditeur de document lui-même sont cachés."
+
+#: ../../source/user_interface/main_window.rst:46
+msgid ""
+"The project tree will highlight with a different background colour the "
+"document that is currently open in the editor."
+msgstr ""
+"L'arborescence du projet met en évidence, avec une couleur d'arrière-"
+"plan différente, le document actuellement ouvert dans l'éditeur."
+
+#: ../../source/user_interface/main_window.rst:51
+msgid "Drag & Drop"
+msgstr "Glisser-déposer"
+
+#: ../../source/user_interface/main_window.rst:53
+msgid ""
+"The project tree allows drag & drop so you to reorder your documents and "
+"folders. Moving a document in the project tree will affect the text's "
+"position when you assemble your manuscript in the **Manuscript Build** "
+"tool."
+msgstr ""
+"L'arborescence du projet permet d'effectuer un glisser-déposer pour "
+"réorganiser les documents et les dossiers. Le déplacement d'un document "
+"dans l'arborescence du projet affectera la position du texte lorsque "
+"vous assemblerez votre manuscrit dans l'outil **Compilation du "
+"manuscrit**."
+
+#: ../../source/user_interface/main_window.rst:57
+msgid ""
+"Documents and their folders can be rearranged freely within their root "
+"folders. If you move a **Novel Document** out of a **Novel** folder, it "
+"will be converted to a **Project Note**. Notes can be moved freely "
+"between all root folders, but keep in mind that if you move a note into "
+"a **Novel** type root folder, its \"Importance\" setting will be "
+"replaced by a \"Status\" setting. See :ref:`docs_usage_project_status` "
+"for more details. The old value will not be overwritten though, and "
+"should be restored if you move it back at some point."
+msgstr ""
+"Les documents et leurs dossiers peuvent être réorganisés librement à "
+"l'intérieur de leur dossier racine. Si vous déplacez un **Document "
+"roman** hors d'un dossier **Roman**, il sera converti en **Note de "
+"projet**. Les notes peuvent être déplacées librement entre tous les "
+"dossiers racine, mais gardez à l'esprit que si vous déplacez une note "
+"dans un dossier racine de type **Roman**, son paramètre « Importance » "
+"sera remplacé par un paramètre « Statut ». Voir :ref:"
+"`docs_usage_project_status` pour plus de détails. L'ancienne valeur ne "
+"sera pas écrasée, et devrait être restaurée si vous la déplacez à "
+"nouveau à un moment donné."
+
+#: ../../source/user_interface/main_window.rst:64
+msgid ""
+"Root folders in the project tree cannot be dragged and dropped at all. "
+"If you want to reorder them, you can move them up or down with respect "
+"to each other using the arrow buttons at the top of the project tree, or "
+"by pressing :kbd:`Ctrl+Up` or :kbd:`Ctrl+Down` when they are selected."
+msgstr ""
+"Les dossiers racines de l'arborescence du projet ne peuvent pas être "
+"déplacés. Si vous souhaitez les réorganiser, vous pouvez les déplacer "
+"vers le haut ou vers le bas en utilisant les boutons fléchés en haut de "
+"l'arborescence du projet, ou en appuyant sur :kbd:`Ctrl+Haut` ou :kbd:"
+"`Ctrl+Bas` lorsqu'ils sont sélectionnés."
+
+#: ../../source/user_interface/main_window.rst:70
+msgid ""
+"You can drag and drop documents onto the editor or viewer panel to open "
+"them."
+msgstr ""
+"Vous pouvez faire glisser et déposer des documents sur le panneau de "
+"l'éditeur ou de la visionneuse pour les ouvrir."
+
+#: ../../source/user_interface/main_window.rst:76
+msgid ""
+"You can now select multiple items in the project tree by holding down "
+"the :kbd:`Ctrl` or :kbd:`Shift` key while selecting items."
+msgstr ""
+"Vous pouvez maintenant sélectionner plusieurs éléments dans "
+"l'arborescence du projet en maintenant la touche :kbd:`Ctrl` ou :kbd:"
+"`Maj` enfoncée pendant la sélection des éléments."
+
+#: ../../source/user_interface/main_window.rst:85
+msgid "Novel View and Editor View"
+msgstr "Vue du roman et vue de l'éditeur"
+
+#: ../../source/user_interface/main_window.rst:89
+msgid "A screenshot of the Novel Tree and Editor View."
+msgstr ""
+"Capture d'écran de l'arborescence des romans et de la vue de l'éditeur."
+
+#: ../../source/user_interface/main_window.rst:91
+msgid ""
+"When **Novel Tree View** in the sidebar is selected, the project tree is "
+"replaced by an overview of your novel structure for a specific **Novel** "
+"type root folder. Instead of showing individual documents, the tree now "
+"shows all headings of your text. This includes multiple headings within "
+"the same document."
+msgstr ""
+"Lorsque l'option **Arborescence du roman** de la barre latérale est "
+"sélectionnée, l'arborescence du projet est remplacée par une vue "
+"d'ensemble de la structure de votre roman pour un dossier racine "
+"spécifique de type **Roman**. Au lieu d'afficher des documents "
+"individuels, l'arborescence montre maintenant tous les titres de votre "
+"texte. Cela inclut les titres multiples au sein d'un même document."
+
+#: ../../source/user_interface/main_window.rst:96
+msgid ""
+"Each heading is indented according to the heading level, not its parent/"
+"child relationship to other elements of your project. You can open and "
+"edit your novel documents from this view as well. All headings contained "
+"in the currently open document should be highlighted in the view to "
+"indicate which ones belong together in the same document."
+msgstr ""
+"Chaque titre est indenté en fonction du niveau du titre, et non de sa "
+"relation parent/enfant avec d'autres éléments de votre projet. Vous "
+"pouvez également ouvrir et modifier vos nouveaux documents à partir de "
+"cette vue. Toutes les rubriques contenues dans le document actuellement "
+"ouvert doivent être mises en évidence dans la vue pour indiquer celles "
+"qui appartiennent au même document."
+
+#: ../../source/user_interface/main_window.rst:101
+msgid ""
+"If you have multiple **Novel** type root folders, the header of the "
+"novel view becomes a dropdown box. You can then switch between them by "
+"clicking the :guilabel:`Outline of ...` text. You can also click the "
+"novel icon button next to it."
+msgstr ""
+"Si vous avez plusieurs dossiers racine de type **Nouveau**, l'en-tête de "
+"la vue roman devient une liste déroulante. Vous pouvez alors passer de "
+"l'un à l'autre en cliquant sur le texte :guilabel:`Plan de ...`. Vous "
+"pouvez également cliquer sur le bouton de l'icône du roman situé à côté."
+
+#: ../../source/user_interface/main_window.rst:105
+msgid ""
+"Generally, the novel view should update when you make changes to the "
+"novel structure, including edits of the current document in the editor. "
+"The information is only updated when the automatic save of the document "
+"is triggered, or you manually press :kbd:`Ctrl+S` to save changes. (You "
+"can adjust the auto-save interval in **Preferences**.) You can also "
+"regenerate the whole novel view by pressing the refresh button in the "
+"novel view header."
+msgstr ""
+"En général, la vue du roman doit être mise à jour lorsque vous apportez "
+"des modifications à la structure du roman, y compris les modifications "
+"du document courant dans l'éditeur. Les informations ne sont mises à "
+"jour que lorsque la sauvegarde automatique du document est déclenchée, "
+"ou lorsque vous appuyez manuellement sur :kbd:`Ctrl+S` pour sauvegarder "
+"les modifications (vous pouvez ajuster l'intervalle de sauvegarde "
+"automatique dans **Préférences**). Vous pouvez également régénérer la "
+"vue du roman en entier en appuyant sur le bouton d'actualisation dans "
+"l'en-tête de la vue du roman."
+
+#: ../../source/user_interface/main_window.rst:111
+msgid ""
+"It is possible to show an optional third column in the novel view. The "
+"settings are available from the menu button in the toolbar."
+msgstr ""
+"Il est possible d'afficher une troisième colonne facultative dans la vue "
+"nouvelle. Les paramètres sont disponibles à partir du bouton de menu "
+"dans la barre d'outils."
+
+#: ../../source/user_interface/main_window.rst:114
+msgid ""
+"If you click the triangular icon to the right of each item, a tooltip "
+"will pop out showing all the meta data collected for that heading."
+msgstr ""
+"Si vous cliquez sur l'icône triangulaire à droite de chaque élément, une "
+"infobulle s'affichera, indiquant toutes les métadonnées collectées pour "
+"cette rubrique."
+
+#: ../../source/user_interface/main_window.rst:119
+msgid ""
+"You cannot reorganise the entries in the novel view, or add any new "
+"documents, as that would imply restructuring the content of the "
+"documents themselves. Any such editing must be done in the project tree. "
+"However, you can add new headings to existing documents, or change "
+"references, which will be updated in this view when the document is "
+"saved."
+msgstr ""
+"Il n'est pas possible de réorganiser les entrées dans la vue roman, ni "
+"d'ajouter de nouveaux documents, car cela impliquerait de restructurer "
+"le contenu des documents eux-mêmes. Toute modification de ce type doit "
+"être effectuée dans l'arborescence du projet. Cependant, vous pouvez "
+"ajouter de nouveaux titres aux documents existants ou modifier les "
+"références, qui seront mises à jour dans cette vue lors de "
+"l'enregistrement du document."
+
+#: ../../source/user_interface/main_window.rst:128
+msgid "Novel Outline View"
+msgstr "Vue d'ensemble du roman"
+
+#: ../../source/user_interface/main_window.rst:132
+msgid "A screenshot of the Novel Outline View."
+msgstr "Capture d'écran de l'affichage du plan du roman."
+
+#: ../../source/user_interface/main_window.rst:134
+msgid ""
+"When **Novel Outline View** in the sidebar is selected, the tree, editor "
+"and viewer are replaced by a table that shows the entire novel structure "
+"with all the tags and references listed. You can select which novel "
+"folder to display from the dropdown menu. You can optionally choose to "
+"show a combination of all novel folders."
+msgstr ""
+"Lorsque vous sélectionnez **Vue du plan du roman** dans la barre "
+"latérale, l'arborescense, l'éditeur et la visionneuse sont remplacés par "
+"un tableau qui affiche la structure complète du roman avec toutes les "
+"étiquettes et références répertoriées. Vous pouvez sélectionner le "
+"dossier du roman à afficher dans le menu déroulant. Vous pouvez "
+"également choisir d'afficher une combinaison de tous les dossiers de "
+"romans."
+
+#: ../../source/user_interface/main_window.rst:139
+msgid ""
+"Pretty much all collected meta data is available in this view. You can "
+"select which columns to display from the menu button. This includes "
+"various meta data and information extracted from your :ref:"
+"`docs_usage_tags_refs`. The order of the columns can also be changed by "
+"dragging them to a different position. You column settings are saved "
+"between sessions on a per-project basis."
+msgstr ""
+"Pratiquement toutes les métadonnées collectées sont disponibles dans "
+"cette vue. Vous pouvez sélectionner les colonnes à afficher à partir du "
+"bouton de menu. Cela inclut diverses métadonnées et informations "
+"extraites de vos :ref:`docs_usage_tags_refs`. L'ordre des colonnes peut "
+"également être modifié en les faisant glisser vers une position "
+"différente. Les paramètres de vos colonnes sont sauvegardés entre les "
+"sessions sur une base par projet."
+
+#: ../../source/user_interface/main_window.rst:146
+msgid "The **Title** column cannot be disabled or moved."
+msgstr "La colonne **Titre** ne peut pas être désactivée ou déplacée."
+
+#: ../../source/user_interface/main_window.rst:148
+msgid ""
+"The information viewed in the outline is based on the project index. "
+"While novelWriter does its best to keep the index up to date when "
+"contents change, you can always rebuild it manually by pressing :kbd:"
+"`F9` if something isn't right."
+msgstr ""
+"Les informations affichées dans le plan sont basées sur l'index du "
+"projet. Bien que novelWriter fasse de son mieux pour maintenir l'index à "
+"jour lorsque le contenu change, vous pouvez toujours le reconstruire "
+"manuellement en appuyant sur :kbd:`F9` si quelque chose ne va pas."
+
+#: ../../source/user_interface/main_window.rst:152
+msgid ""
+"The outline view itself can be regenerated by pressing the refresh "
+"button. By default, the content is refreshed each time you switch to "
+"this view."
+msgstr ""
+"La vue d'ensemble elle-même peut être régénérée en appuyant sur le "
+"bouton d'actualisation. Par défaut, le contenu est actualisé chaque fois "
+"que vous basculez dans cette vue."
+
+#: ../../source/user_interface/main_window.rst:155
+msgid ""
+"The **Synopsis** column of the outline view takes its information from a "
+"specially formatted comment. See :ref:`docs_usage_comments_synopsis`."
+msgstr ""
+"La colonne **Synopsis** de la vue d'ensemble tire ses informations d'un "
+"commentaire spécialement formaté. Voir :ref:"
+"`docs_usage_comments_synopsis`."
+
+#: ../../source/user_interface/main_window.rst:160
+msgid "Project Search"
+msgstr "Recherche dans un projet"
+
+#: ../../source/user_interface/main_window.rst:162
+msgid ""
+"A global search tool is available from the side bar. It allows you to "
+"search through your entire project. The tool does not provide a replace "
+"feature. There is a search and replace tool available in the document "
+"editor that acts on the open document. See :ref:"
+"`docs_ui_edit_view_search` for more details."
+msgstr ""
+"Un outil de recherche global est disponible dans la barre latérale. Il "
+"vous permet d'effectuer une recherche dans l'ensemble de votre projet. "
+"Cet outil n'offre pas de fonction de remplacement. Il existe un outil de "
+"recherche et de remplacement disponible dans l'éditeur de document qui "
+"agit sur le document ouvert. Voir :ref:`docs_ui_edit_view_search` pour "
+"plus de détails."
+
+#: ../../source/user_interface/main_window.rst:171
+msgid "Switching Focus"
+msgstr "Changer de focus"
+
+#: ../../source/user_interface/main_window.rst:173
+msgid ""
+"If the project or novel view does not have focus, pressing :kbd:`Ctrl+T` "
+"switches focus to whichever of the two is visible. If one of them "
+"already has focus, the key press will switch between them instead."
+msgstr ""
+"Si la vue du projet ou du roman n'a pas le focus, presser :kbd:`Ctrl+T` "
+"fait basculer le focus sur celle des deux qui est visible. Si l'une "
+"d'entre elles a déjà le focus, la pression sur la touche permet de "
+"passer de l'une à l'autre."
+
+#: ../../source/user_interface/main_window.rst:177
+msgid ""
+"Likewise, pressing :kbd:`Ctrl+E` will switch focus to the document "
+"editor or viewer, or if any of them already have focus, it will switch "
+"focus between them."
+msgstr ""
+"De même, en appuyant sur :kbd:`Ctrl+E`, le focus passe à l'éditeur ou à "
+"l'afficheur du document, ou si l'un d'entre eux est déjà au focus, il "
+"passe de l'un à l'autre."
+
+#: ../../source/user_interface/main_window.rst:180
+msgid ""
+"These two shortcuts make it possible to jump between all these GUI "
+"elements without having to reach for the mouse or touchpad."
+msgstr ""
+"Ces deux raccourcis permettent de passer d'un élément de l'interface "
+"graphique à l'autre sans avoir à saisir la souris ou le pavé tactile."
+
+#: ../../source/user_interface/main_window.rst:183
+msgid "See :ref:`docs_features_shortcuts` for more details."
+msgstr "Voir :ref:`docs_features_shortcuts` pour plus de détails."
+
+#: ../../source/user_interface/main_window.rst:187
+msgid "Colour Themes"
+msgstr "Thèmes"
+
+#: ../../source/user_interface/main_window.rst:189
+msgid ""
+"By default, novelWriter uses a light colour theme. You can also choose "
+"between a standard dark theme that have neutral colours, or a series of "
+"other included themes, from **Preferences**."
+msgstr ""
+"Par défaut, novelWriter utilise un thème de couleur claire. Vous pouvez "
+"également choisir un thème sombre standard avec des couleurs neutres, ou "
+"une série d'autres thèmes inclus, dans les **Préférences**."
+
+#: ../../source/user_interface/main_window.rst:192
+msgid ""
+"If you wish, you *can* create your own colour themes, and even have them "
+"added to the application. See :ref:`docs_more_custom_theme` for more "
+"details."
+msgstr ""
+"Si vous le souhaitez, vous pouvez créer vos propres thèmes de couleurs, "
+"et même les ajouter à l'application. Voir :ref:`docs_more_custom_theme` "
+"pour plus de détails."
+
+#: ../../source/user_interface/main_window.rst:195
+msgid ""
+"Switching the GUI colour theme does not affect the colours of the editor "
+"and viewer. They have separate themes selectable from the \"Document "
+"colour theme\" setting in **Preferences**. They are separated because "
+"there are a lot more options to choose from for the editor and viewer."
+msgstr ""
+"Le changement de thème de couleur de l'interface graphique n'affecte pas "
+"les couleurs de l'éditeur et de l'afficheur. Ils ont des thèmes séparés "
+"qui peuvent être sélectionnés à partir du paramètre « Thème de couleur "
+"du document » dans les **Préférences**. Ils sont séparés parce qu'il y a "
+"beaucoup plus d'options à choisir pour l'éditeur et l'aff."
+
+#: ../../source/user_interface/main_window.rst:201
+msgid ""
+"If you switch between light and dark mode on the GUI, you should also "
+"switch editor theme to match, otherwise icons may be hard to see in the "
+"editor and viewer."
+msgstr ""
+"Si vous passez du mode clair au mode foncé dans l'interface graphique, "
+"vous devez également changer le thème de l'éditeur pour qu'il "
+"corresponde, sinon les icônes risquent d'être difficiles à voir dans "
+"l'éditeur et l'afficheur."

docs/source/locales/fr/LC_MESSAGES/user_interface/manuscript.po

@@ -0,0 +1,687 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 21:08+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/user_interface/manuscript.rst:5
+msgid "Building the Manuscript"
+msgstr "Compiler le manuscrit"
+
+#: ../../source/user_interface/manuscript.rst:9
+msgid ""
+"You can at any time build a manuscript, an outline of your notes, or any other "
+"type of document from the text in your project. All of this is handled by the "
+"**Manuscript Build** tool. You can activate it from the sidebar, the **Tools** "
+"menu, or by pressing :kbd:`F5`."
+msgstr ""
+"Vous pouvez à tout moment compiler un manuscrit, une ébauche de vos notes ou "
+"tout autre type de document à partir du texte de votre projet. Tout cela est "
+"géré par l'outil **Compiler le manuscrit**. Vous pouvez l'activer à partir de "
+"la barre latérale, du menu **Outils**, ou en appuyant sur :kbd:`F5`."
+
+#: ../../source/user_interface/manuscript.rst:15
+msgid ""
+"The term \"Build\" in this context means to assemble or generate a single "
+"document from a selection of your project documents. You can select between "
+"multiple standard document formats."
+msgstr ""
+"Dans ce contexte, le terme « Construire » signifie assembler ou générer un "
+"document unique à partir d'une sélection de documents de votre projet. Vous "
+"pouvez choisir entre plusieurs formats de documents standard."
+
+#: ../../source/user_interface/manuscript.rst:20
+msgid ""
+"This tool is new for version 2.1. A simpler tool was used for earlier versions."
+msgstr ""
+"Cet outil est nouveau pour la version 2.1. Un outil plus simple était utilisé "
+"pour les versions précédentes."
+
+#: ../../source/user_interface/manuscript.rst:26
+msgid "The Manuscript Build Tool"
+msgstr "L'outil de compilation de manuscrit"
+
+#: ../../source/user_interface/manuscript.rst:31
+msgid "The **Manuscript Build** tool main window."
+msgstr "La fenêtre principale de l'outil **Compiler le manuscrit**."
+
+#: ../../source/user_interface/manuscript.rst:33
+msgid ""
+"The main window of the **Manuscript Build** tool contains a list of all the "
+"builds you have defined, a selection of settings, and a few buttons to "
+"generate preview, open the print dialog, or run the build to create a "
+"manuscript document."
+msgstr ""
+"La fenêtre principale de l'outil **Compiler le manuscrit** contient une liste "
+"de toutes les structures que vous avez définies, une sélection de paramètres "
+"et quelques boutons permettant de générer un aperçu, d'ouvrir la boîte de "
+"dialogue d'impression ou d'exécuter la compilation pour créer un document "
+"manuscrit."
+
+#: ../../source/user_interface/manuscript.rst:39
+msgid "Outline and Word Counts"
+msgstr "Plan et nombre de mots"
+
+#: ../../source/user_interface/manuscript.rst:44
+msgid "The **Manuscript Build** tool main window with the **Outline** visible."
+msgstr ""
+"La fenêtre principale de l'outil **Compiler le manuscrit** avec le **Plan** "
+"visible."
+
+#: ../../source/user_interface/manuscript.rst:46
+msgid ""
+"The **Outline** tab on the left lets you navigate the headings in the preview "
+"document. It will show up to scene level headings for novel documents, and "
+"level 2 headings for notes."
+msgstr ""
+"L'onglet **Plan** sur la gauche vous permet de naviguer dans les rubriques du "
+"document de prévisualisation. Il affiche les titres de niveau scène pour les "
+"documents de roman, et les titres de niveau 2 pour les notes."
+
+#: ../../source/user_interface/manuscript.rst:49
+msgid ""
+"A collapsible panel of word and character counts is also available below the "
+"preview pane. These are calculated from the text you have included in the "
+"document, and are more accurate counts than what's available in the project "
+"tree since they are counted *after formatting*."
+msgstr ""
+"Un panneau rétractable indiquant le nombre de mots et de caractères est "
+"également disponible sous le volet de prévisualisation. Ces chiffres sont "
+"calculés à partir du texte que vous avez inclus dans le document et sont plus "
+"précis que ceux disponibles dans l'arborescence du projet puisqu'ils sont "
+"comptés *après le formatage*."
+
+#: ../../source/user_interface/manuscript.rst:53
+msgid ""
+"For a detailed description on how they are counted, see :ref:"
+"`docs_more_counting`."
+msgstr ""
+"Pour une description détaillée de la façon dont ils sont comptés, voir :ref:"
+"`docs_more_counting`."
+
+#: ../../source/user_interface/manuscript.rst:59
+msgid "Build Settings"
+msgstr "Paramètres de compilation"
+
+#: ../../source/user_interface/manuscript.rst:61
+msgid ""
+"You can edit a build definition by opening it in the **Manuscript Build "
+"Settings** dialog, either by double-clicking or by selecting it and pressing "
+"the edit button in the toolbar."
+msgstr ""
+"Vous pouvez éditer une définition de compilation en l'ouvrant dans la boîte de "
+"dialogue **Paramètres de compilation du manuscrit**, soit en double-cliquant, "
+"soit en la sélectionnant et en appuyant sur le bouton d'édition dans la barre "
+"d'outils."
+
+#: ../../source/user_interface/manuscript.rst:66
+msgid ""
+"You can keep the **Manuscript Build Settings** dialog open while testing the "
+"different options, and just hit the :guilabel:`Apply` button. You can test the "
+"result of your settings change by pressing the :guilabel:`Preview` button in "
+"the main **Manuscript Build** window. When you're happy with the result, you "
+"can close the settings."
+msgstr ""
+"Vous pouvez garder la boîte de dialogue **Paramètres de compilation du "
+"manuscrit** ouverte pendant que vous testez les différentes options, et "
+"simplement cliquer sur le bouton :guilabel:`appliquer`. Vous pouvez tester le "
+"résultat de votre changement de paramètres en appuyant sur le bouton :guilabel:"
+"`Aperçu` dans la fenêtre principale **Compilation du manuscrit**. Lorsque vous "
+"êtes satisfait du résultat, vous pouvez fermer les paramètres."
+
+#: ../../source/user_interface/manuscript.rst:75
+msgid "Document Selection"
+msgstr "Sélection des documents"
+
+#: ../../source/user_interface/manuscript.rst:80
+msgid "The **Selections** page of the **Manuscript Build Settings** dialog."
+msgstr ""
+"La page **Sélection** de la boîte de dialogue **Paramètres de construction du "
+"manuscrit**."
+
+#: ../../source/user_interface/manuscript.rst:82
+msgid ""
+"The **Selections** page of the **Manuscript Build Settings** dialog allows you "
+"to fine tune which documents are included in the build. The included documents "
+"are indicated by an icon in the last column. On the right you have some filter "
+"options for selecting content of a specific type, and a set of switches for "
+"which root folders to include."
+msgstr ""
+"La page **Sélections** de la boîte de dialogue **Paramètres de compilation du "
+"manuscrit** vous permet d'affiner les documents inclus dans la compilation. "
+"Les documents inclus sont indiqués par une icône dans la dernière colonne. Sur "
+"la droite, vous disposez d'options de filtrage pour sélectionner le contenu "
+"d'un type spécifique, et d'un ensemble de commutateurs pour les dossiers "
+"racines à inclure."
+
+#: ../../source/user_interface/manuscript.rst:87
+msgid ""
+"You can override the result of these filters by marking one or more documents "
+"and selecting to explicitly include or exclude them by using the buttons below "
+"the tree view. The last button can be used to reset the override and return "
+"control to the filter settings."
+msgstr ""
+"Vous pouvez remplacer le résultat de ces filtres en marquant un ou plusieurs "
+"documents et en choisissant de les inclure ou de les exclure explicitement à "
+"l'aide des boutons situés sous l'arborescence. Le dernier bouton peut être "
+"utilisé pour réinitialiser l'annulation et redonner le contrôle aux paramètres "
+"du filtre."
+
+#: ../../source/user_interface/manuscript.rst:91
+msgid ""
+"In the figure, the orange icon and the blue icon indicates which documents are "
+"included, and the red icon indicates that a document is explicitly excluded."
+msgstr ""
+"Dans la figure, l'icône orange et l'icône bleue indiquent les documents "
+"inclus, et l'icône rouge indique qu'un document est explicitement exclu."
+
+#: ../../source/user_interface/manuscript.rst:94
+msgid ""
+"By default, inactive documents are excluded, but you can override this in the "
+"filter settings. See :ref:`docs_usage_project_active` for more details."
+msgstr ""
+"Par défaut, les documents inactifs sont exclus, mais vous pouvez modifier cela "
+"dans les paramètres du filtre. Voir :ref:`docs_usage_project_active` pour plus "
+"de détails."
+
+#: ../../source/user_interface/manuscript.rst:101
+msgid "Formatting Headings"
+msgstr "Mise en forme des en-têtes"
+
+#: ../../source/user_interface/manuscript.rst:106
+msgid "The **Headings** page of the **Manuscript Build Settings** dialog."
+msgstr ""
+"La page **En-têtes** de la boîte de dialogue **Paramètres de construction du "
+"manuscrit**."
+
+#: ../../source/user_interface/manuscript.rst:108
+msgid ""
+"The **Headings** page of the **Manuscript Build Settings** dialog allows you "
+"to set how the headings in your Novel Documents are formatted. By default, the "
+"title is just copied as-is, indicated by the ``{Title}`` format. You can "
+"change this to for instance add chapter numbers and scene numbers, or insert "
+"character names, like shown in the figure above."
+msgstr ""
+"La page **En-têtes** de la boîte de dialogue **Paramètres de compilation du "
+"manuscrit** vous permet de définir la façon dont les titres de vos documents "
+"du roman sont formatés. Par défaut, le titre est simplement copié tel quel, "
+"indiqué par le format ``{Title}``  Vous pouvez modifier ce format pour, par "
+"exemple, ajouter des numéros de chapitre et de scène, ou insérer des noms de "
+"personnages, comme indiqué dans la figure ci-dessus."
+
+#: ../../source/user_interface/manuscript.rst:113
+msgid ""
+"Clicking the edit button next to a format will copy the formatting string into "
+"the edit box where it can be modified, and where a syntax highlighter will "
+"help indicate which parts are automatically generated by the build tool. The :"
+"guilabel:`Insert` button is a dropdown list of these formats, and selecting "
+"one will insert it at the position of the cursor."
+msgstr ""
+"Cliquer sur le bouton d'édition à côté d'un format copiera la chaîne de "
+"formatage dans la boîte d'édition où elle peut être modifiée, et où un "
+"surligneur de syntaxe aidera à indiquer quelles parties sont automatiquement "
+"générées par l'outil de construction. Le bouton :guilabel:`Insérer` est une "
+"liste déroulante de ces formats, et en sélectionner un l'insérera à la "
+"position du curseur."
+
+#: ../../source/user_interface/manuscript.rst:118
+msgid ""
+"Any text you add that isn't highlighted in colours will remain in your "
+"formatted titles. ``{Title}`` will always be replaced by the text in the "
+"heading from your documents."
+msgstr ""
+"Tout texte que vous ajoutez et qui n'est pas surligné en couleur restera dans "
+"vos titres formatés. ``{Title}`` sera toujours remplacé par le texte de l'en-"
+"tête de vos documents."
+
+#: ../../source/user_interface/manuscript.rst:121
+msgid "Heading Formats"
+msgstr "Formats d'en-tête"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Code"
+msgstr "Code"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Description"
+msgstr "Description"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{BR}``"
+msgstr "``{BR}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a line break."
+msgstr "Insérer un saut de ligne."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Title}``"
+msgstr "``{Title}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert the original title text."
+msgstr "Insérer le texte du titre original."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Chapter}``"
+msgstr "``{Chapter}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a chapter number."
+msgstr "Insérer un numéro de chapitre."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Chapter:Word}``"
+msgstr "``{Chapter:Word}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a chapter number as a word."
+msgstr "Insérer un numéro de chapitre sous forme de mot."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Chapter:URoman}``"
+msgstr "``{Chapter:URoman}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a chapter number as an upper case Roman numeral."
+msgstr ""
+"Insérer un numéro de chapitre sous la forme d'un chiffre romain majuscule."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Chapter:LRoman}``"
+msgstr "``{Chapter:LRoman}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a chapter number as an lower case Roman numeral."
+msgstr ""
+"Insérer un numéro de chapitre sous la forme d'un chiffre romain minuscule."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Scene}``"
+msgstr "``{Scene}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a scene number within the current chapter."
+msgstr "Insérer un numéro de scène dans le chapitre en cours."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Scene:Abs}``"
+msgstr "``{Scene:Abs}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "Insert a scene number unique to the whole manuscript."
+msgstr "Insérer un numéro de scène unique pour l'ensemble du manuscrit."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Char:POV}``"
+msgstr "``{Char:POV}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid ""
+"Insert the point-of-view character's :ref:`display name "
+"<docs_usage_tags_refs_tags>`."
+msgstr ""
+"Insérer le :ref:`nom affiché <docs_usage_tags_refs_tags>` du personnage de "
+"point de vue."
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid "``{Char:Focus}``"
+msgstr "``{Char:Focus}``"
+
+#: ../../source/user_interface/manuscript.rst:1
+msgid ""
+"Insert the focus character's :ref:`display name <docs_usage_tags_refs_tags>`."
+msgstr ""
+"Insérer le :ref:`nom affiché<docs_usage_tags_refs_tags>` du personnage cible."
+
+#: ../../source/user_interface/manuscript.rst:136
+msgid ""
+"You can preview the result of these format strings by clicking :guilabel:"
+"`Apply`, and then clicking :guilabel:`Preview` in the **Manuscript Build** "
+"tool main window."
+msgstr ""
+"Vous pouvez prévisualiser le résultat de ces chaînes de formatage en cliquant "
+"sur :guilabel:`appliquer`, puis en cliquant sur :guilabel:`aperçu` dans la "
+"fenêtre principale de l'outil **Compiler le manuscrit**."
+
+#: ../../source/user_interface/manuscript.rst:143
+msgid "Automatic Numbering"
+msgstr "Numérotation automatique"
+
+#: ../../source/user_interface/manuscript.rst:145
+msgid ""
+"The headings formatter allows you to automatically insert chapter and scene "
+"numbers into your headings. The automatic chapter number counter will skip all "
+"chapter headings marked as unnumbered using the heading format described in :"
+"ref:`docs_usage_headings_levels`."
+msgstr ""
+"Le formateur de titres vous permet d'insérer automatiquement des numéros de "
+"chapitre et de scène dans vos titres. Le compteur automatique de numéros de "
+"chapitre sautera tous les titres de chapitre marqués comme non numérotés en "
+"utilisant le format de titre décrit dans :ref:`docs_usage_headings_levels`."
+
+#: ../../source/user_interface/manuscript.rst:149
+msgid ""
+"Scene numbers are mostly intended for use in a draft manuscript. You can "
+"either insert absolute scene numbers that counts every scene in the novel, or "
+"you can insert per-chapter scene numbers that reset to 1 for each new chapter."
+msgstr ""
+"Les numéros de scène sont principalement destinés à être utilisés dans un "
+"brouillon de manuscrit. Vous pouvez soit insérer des numéros de scène absolus "
+"qui comptent toutes les scènes du roman, soit des numéros de scène par "
+"chapitre qui se remettent à 1 pour chaque nouveau chapitre."
+
+#: ../../source/user_interface/manuscript.rst:153
+msgid ":bdg-info:`Example`"
+msgstr ":bdg-info:`Exemple`"
+
+#: ../../source/user_interface/manuscript.rst:155
+msgid "This will create a chapter title on the format \"Chapter 1: Title Text\":"
+msgstr ""
+"Cela créera un titre de chapitre au format « Chapitre 1 : Texte du titre » :"
+
+#: ../../source/user_interface/manuscript.rst:161
+msgid "This will create a scene title on the format \"Scene 1.1: Title Text\":"
+msgstr "Cela créera un titre de scène au format « Scene 1.1 : Texte du titre » :"
+
+#: ../../source/user_interface/manuscript.rst:169
+msgid "Scene Separators"
+msgstr "Séparateurs de scènes"
+
+#: ../../source/user_interface/manuscript.rst:171
+msgid ""
+"If you don't want any titles for your scenes (or for your sections if you have "
+"them), you can leave the formatting boxes empty. If so, an empty paragraph "
+"will be inserted between the scenes or sections instead, resulting in a gap in "
+"the text. You can also enable the :guilabel:`Hide` setting, which will ignore "
+"them completely. That is, there won't even be an extra gap inserted."
+msgstr ""
+"Si vous ne voulez pas de titres pour vos scènes (ou pour vos sections si vous "
+"en avez), vous pouvez laisser les cases de mise en forme vides. Dans ce cas, "
+"un paragraphe vide sera inséré entre les scènes ou les sections, ce qui créera "
+"un vide dans le texte. Vous pouvez également activer le paramètre :guilabel:"
+"`Caché`, qui les ignorera complètement. En d'autres termes, il n'y aura même "
+"pas d'espace supplémentaire inséré."
+
+#: ../../source/user_interface/manuscript.rst:176
+msgid ""
+"Alternatively, if you want a separator text between them, like the common ``* "
+"* *``, you can enter the desired separator text as the format. If the format "
+"is any piece of static text, it will always be treated as a separator. A "
+"static separator is only inserted between scenes, as opposed to a formatted "
+"heading which is also inserted before the first scene of a chapter."
+msgstr ""
+"Alternativement, si vous voulez un texte séparateur entre eux, comme le commun "
+"``* * *``, vous pouvez entrer le texte séparateur désiré comme format. Si le "
+"format est un morceau de texte statique, il sera toujours traité comme un "
+"séparateur. Un séparateur statique n'est inséré qu'entre les scènes, "
+"contrairement à un titre formaté qui est également inséré avant la première "
+"scène d'un chapitre."
+
+#: ../../source/user_interface/manuscript.rst:185
+msgid "Hard and Soft Scenes"
+msgstr "Scènes dures et douces"
+
+#: ../../source/user_interface/manuscript.rst:187
+msgid ""
+"If you wish to distinguish between so-called soft and hard scene breaks, you "
+"can use the alternative scene heading format in your text. You can then give "
+"these headings a different formatting in the **Headings** settings."
+msgstr ""
+"Si vous souhaitez faire la distinction entre les ruptures de scène douces et "
+"dures, vous pouvez utiliser le format alternatif de l'en-tête de scène dans "
+"votre texte. Vous pouvez ensuite donner à ces titres un format différent dans "
+"les paramètres **En-têtes**."
+
+#: ../../source/user_interface/manuscript.rst:191
+msgid ""
+"See :ref:`docs_usage_headings_levels` for more info on how to format "
+"alternative scene headings in your text."
+msgstr ""
+"Voir :ref:`docs_usage_headings_levels` pour plus d'informations sur la façon "
+"de formater des titres de scène alternatifs dans votre texte."
+
+#: ../../source/user_interface/manuscript.rst:196
+msgid "Output Settings"
+msgstr "Paramètres de sortie"
+
+#: ../../source/user_interface/manuscript.rst:198
+msgid ""
+"The **Formatting** sections of the **Manuscript Build Settings** dialog "
+"control a number of other settings for the output. This includes formatting, "
+"but also what content is included. You can for instance select to include "
+"comments, synopsis. tags and reference, and even exclude the body text itself."
+msgstr ""
+"Les sections **Formatage** de la boîte de dialogue **Paramètres de compilation "
+"du manuscrit** contrôlent un certain nombre d'autres paramètres pour la "
+"sortie. Il s'agit notamment du formatage, mais aussi du contenu inclus. Vous "
+"pouvez par exemple choisir d'inclure les commentaires, le synopsis, les "
+"étiquettes et les références, et même d'exclure le corps du texte lui-même."
+
+#: ../../source/user_interface/manuscript.rst:207
+msgid "Building Manuscript Documents"
+msgstr "Création des manuscrits"
+
+#: ../../source/user_interface/manuscript.rst:212
+msgid ""
+"The **Manuscript Build** dialog used for writing the actual manuscript "
+"documents."
+msgstr ""
+"Le dialogue **compiler le manuscrit** est utilisé pour créer les manuscrits "
+"proprement dits."
+
+#: ../../source/user_interface/manuscript.rst:214
+msgid ""
+"When you press the :guilabel:`Build` button on the **Build Manuscript** tool "
+"main window, a special file dialog opens up. This is where you pick your "
+"desired output format and where to write the file."
+msgstr ""
+"Lorsque vous appuyez sur le bouton :guilabel:`Construire` dans la fenêtre "
+"principale de l'outil **Compiler le manuscrit**, une boîte de dialogue "
+"spéciale s'ouvre. C'est là que vous choisissez le format de sortie désiré et "
+"l'endroit où écrire le fichier."
+
+#: ../../source/user_interface/manuscript.rst:218
+msgid ""
+"On the left side of the dialog is a list of all the available file formats, "
+"and on the right, a list of the documents which are included based on the "
+"build definition you selected. You can choose an output path, and set a base "
+"file name as well. The file extension will be added automatically."
+msgstr ""
+"La partie gauche de la boîte de dialogue contient une liste de tous les "
+"formats de fichiers disponibles, et la partie droite, une liste des documents "
+"qui sont inclus en fonction de la définition de la construction que vous avez "
+"sélectionnée. Vous pouvez choisir un chemin de sortie et définir un nom de "
+"fichier de base. L'extension du fichier sera ajoutée automatiquement."
+
+#: ../../source/user_interface/manuscript.rst:222
+msgid ""
+"To generate the manuscript document, press the :guilabel:`Build` button. A "
+"small progress bar will show the build progress, but for small projects it may "
+"pass very fast."
+msgstr ""
+"Pour générer le document manuscrit, appuyez sur le bouton :guilabel:"
+"`Construire`. Une petite barre de progression indique l'avancement de la "
+"construction, mais pour les petits projets, elle peut passer très vite."
+
+#: ../../source/user_interface/manuscript.rst:227
+msgid "File Formats"
+msgstr "Formats de fichiers"
+
+#: ../../source/user_interface/manuscript.rst:229
+msgid "The following document formats are supported:"
+msgstr "Les formats de documents suivants sont pris en charge :"
+
+#: ../../source/user_interface/manuscript.rst:231
+msgid "Open Document"
+msgstr "Open Document"
+
+#: ../../source/user_interface/manuscript.rst:232
+msgid ""
+"The Build tool can produce either an ``.odt`` file, or an ``.fodt`` file. The "
+"latter is just a flat version of the document format as a single XML file. "
+"Most rich text editors support the former, and only a few the latter."
+msgstr ""
+"L'outil de construction peut produire soit un fichier ``.odt``, soit un "
+"fichier ``.fodt``. Ce dernier n'est qu'une version plate du format du document "
+"sous la forme d'un fichier XML unique. La plupart des éditeurs de texte riche "
+"supportent le premier, et seulement quelques uns le second."
+
+#: ../../source/user_interface/manuscript.rst:236
+msgid "Microsoft Word Document"
+msgstr "Document Microsoft Word"
+
+#: ../../source/user_interface/manuscript.rst:237
+msgid ""
+"The Microsoft Word Document format writes a single ``.docx`` file. It uses a "
+"fairly basic format that should be compatible with most rich text editors."
+msgstr ""
+"Le format Microsoft Word Document permet d'écrire un seul fichier ``.docx``. "
+"Il utilise un format assez basique qui devrait être compatible avec la plupart "
+"des éditeurs de texte riche."
+
+#: ../../source/user_interface/manuscript.rst:240
+msgid "Portable Document Format (PDF)"
+msgstr "Format de document portable (PDF)"
+
+#: ../../source/user_interface/manuscript.rst:241
+msgid ""
+"The PDF is generated from a copy of the preview document, and should have the "
+"same formatting capabilities as the preview. It's identical to what is "
+"produced if you select the print option and print to PDF."
+msgstr ""
+"Le PDF est généré à partir d'une copie du document de prévisualisation et "
+"devrait avoir les mêmes capacités de formatage que la prévisualisation. Il est "
+"identique à celui qui est produit lorsque vous sélectionnez l'option "
+"d'impression et que vous imprimez au format PDF."
+
+#: ../../source/user_interface/manuscript.rst:245
+msgid "novelWriter HTML"
+msgstr "novelWriter HTML"
+
+#: ../../source/user_interface/manuscript.rst:246
+msgid ""
+"The HTML format writes a single ``.htm`` file with minimal style formatting. "
+"The HTML document is suitable for further processing by document conversion "
+"tools like Pandoc_, for importing in word processors, or for printing from "
+"browser."
+msgstr ""
+"Le format HTML écrit un seul fichier ``.htm`` avec un formatage de style "
+"minimal. Le document HTML peut être traité par des outils de conversion de "
+"documents tels que Pandoc_, importé dans un traitement de texte ou imprimé à "
+"partir d'un navigateur."
+
+#: ../../source/user_interface/manuscript.rst:250
+msgid "Standard/Extended Markdown"
+msgstr "Markdown standard/étendu"
+
+#: ../../source/user_interface/manuscript.rst:251
+msgid ""
+"The Markdown format comes in both Standard and Extended flavour. The *only* "
+"difference in terms of novelWriter functionality is the support for strike "
+"through text, which is not supported by the Standard flavour."
+msgstr ""
+"Le format Markdown existe en version standard et en version étendue. La "
+"*seule* différence en termes de fonctionnalité de novelWriter est la prise en "
+"charge du texte barré, qui n'est pas prise en charge par la version standard."
+
+#: ../../source/user_interface/manuscript.rst:255
+msgid "novelWriter Markup"
+msgstr "novelWriter Markup"
+
+#: ../../source/user_interface/manuscript.rst:256
+msgid ""
+"This is simply a concatenation of the project documents selected by the "
+"filters into a ``.txt`` file. The documents are stacked together in the order "
+"they appear in the project tree, with comments, tags, etc. included if they "
+"are selected. This is a useful format for exporting the project for later "
+"import back into novelWriter."
+msgstr ""
+"Il s'agit simplement d'une concaténation des documents du projet sélectionnés "
+"par les filtres dans un fichier ``.txt``. Les documents sont empilés dans "
+"l'ordre où ils apparaissent dans l'arborescence du projet, avec les "
+"commentaires, les balises, etc. inclus s'ils sont sélectionnés. C'est un "
+"format utile pour exporter le projet et le réimporter plus tard dans "
+"novelWriter."
+
+#: ../../source/user_interface/manuscript.rst:263
+msgid "Microsoft Word and PDF output options were added."
+msgstr "Les options de sortie Microsoft Word et PDF ont été ajoutées."
+
+#: ../../source/user_interface/manuscript.rst:267
+msgid "Additional Formats"
+msgstr "Formats supplémentaires"
+
+#: ../../source/user_interface/manuscript.rst:269
+msgid ""
+"In addition to the above document formats, the novelWriter HTML and Markup "
+"formats can also be wrapped in a JSON file. These files will have a meta data "
+"entry and a body entry."
+msgstr ""
+"En plus des formats de document ci-dessus, les formats HTML et Markup de "
+"novelWriter peuvent également être enveloppés dans un fichier JSON. Ces "
+"fichiers auront une entrée pour les métadonnées et une entrée pour le corps du "
+"texte."
+
+#: ../../source/user_interface/manuscript.rst:272
+msgid ""
+"The text body is saved in a two-level list. The outer list contains one entry "
+"per document, in the order they appear in the project tree. Each document is "
+"then split up into a list as well, with one entry per paragraph it contains."
+msgstr ""
+"Le corps du texte est enregistré dans une liste à deux niveaux. La liste "
+"extérieure contient une entrée par document, dans l'ordre où ils apparaissent "
+"dans l'arborescence du projet. Chaque document est ensuite divisé en une "
+"liste, avec une entrée par paragraphe qu'il contient."
+
+#: ../../source/user_interface/manuscript.rst:276
+msgid ""
+"These files are mainly intended for scripted post-processing for those who "
+"want that option. A JSON file can be imported directly into a Python dict "
+"object or a PHP array, to mentions a few options."
+msgstr ""
+"Ces fichiers sont principalement destinés au post-traitement par script pour "
+"ceux qui souhaitent cette option. Un fichier JSON peut être importé "
+"directement dans un objet dict de Python ou dans un tableau de PHP, pour ne "
+"citer que quelques options."
+
+#: ../../source/user_interface/manuscript.rst:283
+msgid "Printing"
+msgstr "Impression"
+
+#: ../../source/user_interface/manuscript.rst:285
+msgid ""
+"The :guilabel:`Print` button allows you to print the content in the preview "
+"window. You can either print to one of your system's printers, or select PDF "
+"as your output format from the printer icon on the print dialog."
+msgstr ""
+"Le bouton :guilabel:`Imprimer` vous permet d'imprimer le contenu de la fenêtre "
+"de prévisualisation. Vous pouvez soit imprimer sur l'une des imprimantes de "
+"votre système, soit sélectionner le format PDF à partir de l'icône de "
+"l'imprimante dans la boîte de dialogue d'impression."
+
+#: ../../source/user_interface/manuscript.rst:291
+msgid ""
+"The paper format should default to whatever your system default is. If you "
+"want to change it, you have to select it from the **Print Preview** dialog."
+msgstr ""
+"Le format de papier doit être défini par défaut, quel que soit le format par "
+"défaut de votre système. Si vous souhaitez le modifier, vous devez le "
+"sélectionner dans la boîte de dialogue **Aperçu avant impression**."

docs/source/locales/fr/LC_MESSAGES/user_interface/projects.po

@@ -0,0 +1,367 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 17:22+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/user_interface/projects.rst:5
+msgid "Managing Projects"
+msgstr "Gestion des projets"
+
+#: ../../source/user_interface/projects.rst:7
+msgid ""
+"Your text in novelWriter is organised into projects. Each project is "
+"meant to contain one novel and associated notes. If you have multiple "
+"novels in a series, with the same characters and shared notes, it is "
+"also possible to keep all of them in the same project by creating "
+"multiple **Novel** root folders. See :ref:`docs_usage_project_roots` for "
+"more details."
+msgstr ""
+"Votre texte dans novelWriter est organisé en projets. Chaque projet est "
+"censé contenir un roman et les notes associées. Si vous avez plusieurs "
+"romans dans une série, avec les mêmes personnages et des notes "
+"partagées, il est également possible de les garder tous dans le même "
+"projet en créant plusieurs dossiers racine **Roman**. Voir :ref:"
+"`docs_usage_project_roots` pour plus de détails."
+
+#: ../../source/user_interface/projects.rst:16
+msgid "Creating A New Project"
+msgstr "Créer un nouveau projet"
+
+#: ../../source/user_interface/projects.rst:18
+msgid ""
+"You can create a new project from the **Project** menu by selecting "
+"**Create or Open Project**. This will open the **Welcome** dialog, where "
+"you can select the :guilabel:`New` button that will assist you in "
+"creating a project. This dialog is also displayed when you start "
+"novelWriter."
+msgstr ""
+"Vous pouvez créer un nouveau projet à partir du menu **Projet** en "
+"sélectionnant **Créer ou ouvrir un projet**. Cela ouvrira la boîte de "
+"dialogue **Accueil**, où vous pourrez sélectionner le bouton :guilabel:"
+"`Nouveau` qui vous aidera à créer un projet. Cette boîte de dialogue "
+"s'affiche également lorsque vous démarrez novelWriter."
+
+#: ../../source/user_interface/projects.rst:22
+msgid ""
+"A novelWriter project requires a dedicated folder for storing its files "
+"on the local file system. If you're interested in the details of how "
+"projects are stored, you can have a look at the section :ref:"
+"`docs_technical_storage`."
+msgstr ""
+"Un projet novelWriter nécessite un dossier dédié pour stocker ses "
+"fichiers sur le système de fichiers local. Si vous êtes intéressé par "
+"les détails de la façon dont les projets sont stockés, vous pouvez "
+"consulter la section :ref:`docs_technical_storage`."
+
+#: ../../source/user_interface/projects.rst:26
+msgid ""
+"A list of recently opened projects is maintained, and displayed in the "
+"**Welcome** dialog. A project can be removed from this list by selecting "
+"it and pressing the :kbd:`Del` key or by right-clicking it and selecting "
+"the **Remove Project** option."
+msgstr ""
+"Une liste des projets récemment ouverts est maintenue et affichée dans "
+"la boîte de dialogue **Bienvenue**. Un projet peut être supprimé de "
+"cette liste en le sélectionnant et en appuyant sur la touche :kbd:"
+"`Suppr` ou en faisant un clic droit sur le projet et en sélectionnant "
+"l'option **Supprimer le projet**."
+
+#: ../../source/user_interface/projects.rst:32
+msgid ""
+"The project list (left) and new project form (right) of the **Welcome** "
+"dialog."
+msgstr ""
+"La liste des projets (à gauche) et le formulaire de nouveau projet (à "
+"droite) de la boîte de dialogue **Bienvenue**."
+
+#: ../../source/user_interface/projects.rst:34
+msgid ""
+"Project-specific settings are available in **Project Settings** in the "
+"**Project** menu. See further details below in the :ref:"
+"`docs_ui_projects_settings` section."
+msgstr ""
+"Les paramètres spécifiques au projet sont disponibles dans **Paramètres "
+"du projet** dans le menu **Projet**. Voir plus de détails ci-dessous "
+"dans la section :ref:`docs_ui_projects_settings`."
+
+#: ../../source/user_interface/projects.rst:37
+msgid ""
+"Details about the project's novel text, including word counts, and a "
+"table of contents with word and page counts, is available through the "
+"**Novel Details** dialog. Statistics about the project is also available "
+"in the **Manuscript Build** tool."
+msgstr ""
+"Les détails du texte du roman du projet, y compris le nombre de mots et "
+"une table des matières avec le nombre de mots et de pages, sont "
+"disponibles dans la boîte de dialogue **Détails du roman**. Des "
+"statistiques sur le projet sont également disponibles dans l'outil "
+"**Compiler le manuscrit**."
+
+#: ../../source/user_interface/projects.rst:43
+msgid "Template Projects"
+msgstr "Modèles de projets"
+
+#: ../../source/user_interface/projects.rst:45
+msgid ""
+"From the Welcome dialog you can also create a new from another existing "
+"project. If you have a specific structure you want to use for all your "
+"new projects, you can create a dedicated project to be used as a "
+"template, and select to copy an existing project from the \"Prefill "
+"Project\" option from the **New Project** form."
+msgstr ""
+"Dans la boîte de dialogue de bienvenue, vous pouvez également créer un "
+"nouveau projet à partir d'un autre projet existant. Si vous souhaitez "
+"utiliser une structure spécifique pour tous vos nouveaux projets, vous "
+"pouvez créer un projet dédié qui servira de modèle et choisir de copier "
+"un projet existant à partir de l'option « Pré-remplir le projet » du "
+"formulaire **Nouveau projet**."
+
+#: ../../source/user_interface/projects.rst:54
+msgid "Project Settings"
+msgstr "Paramètres du projet"
+
+#: ../../source/user_interface/projects.rst:56
+msgid ""
+"The **Project Settings** can be accessed from the **Project** menu, or "
+"by pressing :kbd:`Ctrl+Shift+,`. This will open a dialog box, with a set "
+"of tabs."
+msgstr ""
+"Les **Paramètres du projet** sont accessibles depuis le menu **Projet**, "
+"ou en appuyant sur :kbd:`Ctrl+Maj+,`. Cela ouvrira une boîte de "
+"dialogue, avec une série d'onglets."
+
+#: ../../source/user_interface/projects.rst:61
+msgid "General Settings"
+msgstr "Paramètres généraux"
+
+#: ../../source/user_interface/projects.rst:63
+msgid ""
+"The **Settings** tab holds the project name, author, and language "
+"settings."
+msgstr ""
+"L'onglet **Paramètres** contient les paramètres relatifs au nom du "
+"projet, à l'auteur et à la langue."
+
+#: ../../source/user_interface/projects.rst:65
+msgid ""
+"The **Project Name** can be edited here. It is used for the main window "
+"title and for generating backup files. So keep in mind that if you do "
+"change this setting, the backup file names will change too."
+msgstr ""
+"Le **Nom du projet** peut être modifié ici. Il est utilisé pour le titre "
+"de la fenêtre principale et pour la génération des fichiers de "
+"sauvegarde. Gardez donc à l'esprit que si vous modifiez ce paramètre, "
+"les noms des fichiers de sauvegarde changeront également."
+
+#: ../../source/user_interface/projects.rst:69
+msgid ""
+"You can also change the **Author** and **Project Language** setting. "
+"These are only used when building the manuscript, for some formats. The "
+"language setting is also used when inserting text into documents in the "
+"viewer, like for instance labels for keywords and special comments."
+msgstr ""
+"Vous pouvez également modifier les paramètres **Auteur** et **Langue du "
+"projet**. Ces paramètres ne sont utilisés que lors de la compilation du "
+"manuscrit, pour certains formats. Le paramètre de langue est également "
+"utilisé lors de l'insertion de texte dans les documents dans "
+"l'afficheur, comme par exemple les étiquettes pour les mots-clés et les "
+"commentaires spéciaux."
+
+#: ../../source/user_interface/projects.rst:73
+msgid ""
+"If your project is in a different language than your main spell checking "
+"language is set to, you can override the default setting here. The "
+"project language can also be changed from the **Tools** menu."
+msgstr ""
+"Si votre projet est rédigé dans une langue différente de la langue de "
+"vérification orthographique principale, vous pouvez remplacer le "
+"paramètre par défaut ici. La langue du projet peut également être "
+"modifiée à partir du menu **Outils**."
+
+#: ../../source/user_interface/projects.rst:77
+msgid ""
+"You can also override the automatic backup setting for the project if "
+"you wish."
+msgstr ""
+"Vous pouvez également remplacer le paramètre de sauvegarde automatique "
+"du projet si vous le souhaitez."
+
+#: ../../source/user_interface/projects.rst:83
+msgid "Status and Importance"
+msgstr "Statut et Importance"
+
+#: ../../source/user_interface/projects.rst:85
+msgid ""
+"Each document or folder of type **Novel** can be given a \"Status\" "
+"label accompanied by a coloured icon with an optional shape selected "
+"from a list of pre-defined shapes. Each document or folder of the "
+"remaining types can be given an \"Importance\" label with the same "
+"customisation options."
+msgstr ""
+"Chaque document ou dossier de type **Roman** peut recevoir une étiquette "
+"« Statut » accompagnée d'une icône colorée avec une forme optionnelle "
+"sélectionnée dans une liste de formes prédéfinies. Chaque document ou "
+"dossier des autres types peut recevoir une étiquette « Importance » avec "
+"les mêmes options de personnalisation."
+
+#: ../../source/user_interface/projects.rst:89
+msgid ""
+"These labels are there purely for your convenience, and you are not "
+"required to use them for any other features to work. No other part of "
+"novelWriter accesses this information. The intention is to use these to "
+"indicate at what stage of completion each novel document is, or how "
+"important the content of a note is to the story. You don't have to use "
+"them this way, that's just what they were intended for, but you can make "
+"them whatever you want."
+msgstr ""
+"Ces étiquettes sont là uniquement pour votre commodité, et vous n'êtes "
+"pas obligé de les utiliser pour que d'autres fonctionnalités "
+"fonctionnent. Aucune autre partie de novelWriter n'accède à ces "
+"informations. L'intention est de les utiliser pour indiquer à quel stade "
+"d'achèvement se trouve chaque document de roman, ou à quel point le "
+"contenu d'une note est important pour l'histoire. Vous n'êtes pas obligé "
+"de les utiliser de cette manière, c'est juste ce pour quoi elles ont été "
+"conçues, mais vous pouvez en faire ce que vous voulez."
+
+#: ../../source/user_interface/projects.rst:95
+msgid ""
+"Both status and importance labels can be exported and imported so you "
+"can share them between projects, or define a standard set for all your "
+"writing projects. When you import labels to a project, they are always "
+"added as *new* labels."
+msgstr ""
+"Les étiquettes de statut et d'importance peuvent être exportées et "
+"importées afin que vous puissiez les partager entre les projets ou "
+"définir un ensemble standard pour tous vos projets d'écriture. Lorsque "
+"vous importez des étiquettes dans un projet, elles sont toujours "
+"ajoutées en tant que *nouvelles* étiquettes."
+
+#: ../../source/user_interface/projects.rst:99
+msgid "See also :ref:`docs_usage_project_status`."
+msgstr "Voir aussi :ref:`docs_usage_project_status`."
+
+#: ../../source/user_interface/projects.rst:103
+msgid ""
+"Status or importance level currently in use cannot be deleted, but they "
+"can be edited."
+msgstr ""
+"Le statut ou le niveau d'importance en cours d'utilisation ne peut pas "
+"être supprimé, mais il peut être modifié."
+
+#: ../../source/user_interface/projects.rst:107
+msgid "Text Auto-Replace"
+msgstr "Remplacement automatique du texte"
+
+#: ../../source/user_interface/projects.rst:109
+msgid ""
+"A set of automatically replaced keywords can be added in this tab. The "
+"keywords in the left column will be replaced by the text in the right "
+"column when documents are opened in the viewer. They will also be "
+"applied to manuscript builds."
+msgstr ""
+"Un ensemble de mots-clés de remplacement automatiquement peut être "
+"ajouté dans cet onglet. Les mots-clés de la colonne de gauche seront "
+"remplacés par le texte de la colonne de droite lorsque les documents "
+"seront ouverts dans l'afficheur. Ils seront également appliqués aux "
+"constructions de manuscrits."
+
+#: ../../source/user_interface/projects.rst:113
+msgid ""
+"The auto-replace feature will replace text in angle brackets that is in "
+"this list. The syntax highlighter will add an alternate colour to text "
+"matching the syntax, but it doesn't check if the text is in this list."
+msgstr ""
+"La fonction de remplacement automatique remplace le texte entre crochets "
+"qui se trouve dans cette liste. Le surligneur syntaxique ajoutera une "
+"couleur alternative au texte correspondant à la syntaxe, mais il ne "
+"vérifie pas si le texte se trouve dans cette liste."
+
+#: ../../source/user_interface/projects.rst:119
+msgid ""
+"A keyword cannot contain spaces. The angle brackets are added by "
+"default, and when used in the text are a part of the keyword to be "
+"replaced. This is to ensure that parts of the text aren't "
+"unintentionally replaced by the content of the list."
+msgstr ""
+"Un mot-clé ne peut pas contenir d'espaces. Les crochets sont ajoutés par "
+"défaut et, lorsqu'ils sont utilisés dans le texte, ils font partie du "
+"mot-clé à remplacer. Cela permet de s'assurer que certaines parties du "
+"texte ne sont pas remplacées involontairement par le contenu de la liste."
+
+#: ../../source/user_interface/projects.rst:127
+msgid "Backup"
+msgstr "Sauvegarde"
+
+#: ../../source/user_interface/projects.rst:129
+msgid ""
+"An automatic backup system is built into novelWriter. In order to use "
+"it, a backup path to where the backup files are to be stored must be "
+"provided in **Preferences**. The path defaults to a folder named "
+"\"Backups\" in your home directory."
+msgstr ""
+"Un système de sauvegarde automatique est intégré à novelWriter. Pour "
+"l'utiliser, un chemin d'accès à l'endroit où les fichiers de sauvegarde "
+"doivent être stockés doit être indiqué dans les **Préférences**. Le "
+"chemin d'accès est par défaut un dossier nommé « Backups » dans votre "
+"répertoire personnel."
+
+#: ../../source/user_interface/projects.rst:133
+msgid ""
+"Backups can run automatically when a project is closed, which also "
+"implies it is run when the application itself is closed. Backups are "
+"date stamped zip files of the project files in the project folder (files "
+"not strictly a part of the project are ignored). The zip archives are "
+"stored in a subfolder of the backup path. The subfolder will have the "
+"same name as the **Project Name** defined in :ref:"
+"`docs_ui_projects_settings`."
+msgstr ""
+"Les sauvegardes peuvent être exécutées automatiquement lorsqu'un projet "
+"est fermé, ce qui implique également qu'elles sont exécutées lorsque "
+"l'application elle-même est fermée. Les sauvegardes sont des fichiers "
+"zip ayant la même date que les  fichiers du projet dans le dossier du "
+"projet (les fichiers qui ne font pas strictement partie du projet sont "
+"ignorés). Les archives zip sont stockées dans un sous-dossier du chemin "
+"de sauvegarde. Le sous-dossier aura le même nom que le **Nom du projet** "
+"défini dans :ref:`docs_ui_projects_settings`."
+
+#: ../../source/user_interface/projects.rst:139
+msgid ""
+"The backup feature, when configured, can also be run manually from the "
+"**Tools** menu. It is also possible to disable automated backups for a "
+"given project in **Project Settings**."
+msgstr ""
+"La fonction de sauvegarde, lorsqu'elle est configurée, peut également "
+"être exécutée manuellement à partir du menu **Outils**. Il est également "
+"possible de désactiver les sauvegardes automatiques pour un projet donné "
+"dans **Paramètres du projet**."
+
+#: ../../source/user_interface/projects.rst:144
+msgid ""
+"For the backup to be able to run, the **Project Name** must be set in "
+"**Project Settings**. This value is used to generate the name and path "
+"of the backups. Without it, the backup will not run at all, but it will "
+"produce a warning message."
+msgstr ""
+"Pour que la sauvegarde puisse être exécutée, le **Nom du projet** doit "
+"être défini dans **Paramètres du projet**. Cette valeur est utilisée "
+"pour générer le nom et le chemin des sauvegardes. Sans cette valeur, la "
+"sauvegarde ne s'exécutera pas du tout, mais elle produira un message "
+"d'avertissement."

docs/source/locales/fr/LC_MESSAGES/user_interface/split_and_merge.po

@@ -0,0 +1,124 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 17:44+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/user_interface/split_and_merge.rst:5
+msgid "Split and Merge Documents"
+msgstr "Fractionner et fusionner des documents"
+
+#: ../../source/user_interface/split_and_merge.rst:7
+msgid ""
+"Under the **Transform** submenu in the context menu of an item in the "
+"project tree, you will find several options on how to change a document "
+"or folder. This includes changing between document and note, but also "
+"splitting them into multiple documents, or merging child items into a "
+"single document."
+msgstr ""
+"Dans le sous-menu **Transformation** du menu contextuel d'un élément de "
+"l'arborescence du projet, vous trouverez plusieurs options permettant de "
+"modifier un document ou un dossier. Il s'agit notamment de passer d'un "
+"document à une note, mais aussi de les diviser en plusieurs documents ou "
+"de fusionner des éléments enfants en un seul document."
+
+#: ../../source/user_interface/split_and_merge.rst:14
+msgid "Splitting Documents"
+msgstr "Découper des documents"
+
+#: ../../source/user_interface/split_and_merge.rst:18
+msgid "The **Split Document** dialog."
+msgstr "La boîte de dialogue **découper un document**."
+
+#: ../../source/user_interface/split_and_merge.rst:20
+msgid ""
+"The **Split Document by Headings** option will open a dialog that allows "
+"you to split the selected document into multiple new documents based on "
+"the headings it contains. You can select at which heading level the "
+"split is to be performed from the dropdown box. The list box will "
+"preview which headings will be split into new documents."
+msgstr ""
+"L'option **découper le document selon les titres** ouvre une boîte de "
+"dialogue qui vous permet de découper le document sélectionné en "
+"plusieurs nouveaux documents sur la base des en-têtes qu'il contient. "
+"Vous pouvez sélectionner le niveau de rubrique auquel le fractionnement "
+"doit être effectué dans la liste déroulante. La liste déroulante affiche "
+"un aperçu des rubriques qui seront scindées en nouveaux documents."
+
+#: ../../source/user_interface/split_and_merge.rst:25
+msgid ""
+"You are given the option to create a folder for these new documents, and "
+"whether or not to create a hierarchy of documents. That is, put sections "
+"under scenes, and scenes under chapters."
+msgstr ""
+"Vous avez la possibilité de créer un dossier pour ces nouveaux documents "
+"et de créer ou non une hiérarchie entre les documents. C'est-à-dire de "
+"placer les sections sous les scènes, et les scènes sous les chapitres."
+
+#: ../../source/user_interface/split_and_merge.rst:28
+msgid ""
+"The source document *is not* deleted in the process, but you have the "
+"option to let the tool move the source document to the **Trash** folder."
+msgstr ""
+"Le document source n'est pas supprimé au cours du processus, mais vous "
+"avez la possibilité de laisser l'outil déplacer le document source dans "
+"le dossier **Poubelle**."
+
+#: ../../source/user_interface/split_and_merge.rst:33
+msgid "Merging Documents"
+msgstr "Fusionner des documents"
+
+#: ../../source/user_interface/split_and_merge.rst:37
+msgid "The **Merge Documents** dialog."
+msgstr "La boîte de dialogue **Fusionner des documents**."
+
+#: ../../source/user_interface/split_and_merge.rst:39
+msgid ""
+"You have two options for merging documents that are child elements of "
+"another document. You can either **Merge Child Items into Self** and "
+"**Merge Child Items into New**. The first option will pull all content "
+"of child items and merge them into the parent document, while the second "
+"option will create a new document in the process."
+msgstr ""
+"Vous disposez de deux options pour fusionner des documents qui sont des "
+"éléments enfants d'un autre document. Vous pouvez soit **Intégrer les "
+"éléments enfants**, soit **Créer une fusion des éléments enfants**. La "
+"première option permet d'extraire tout le contenu des éléments enfants "
+"et de les fusionner dans le document parent, tandis que la seconde "
+"option crée un nouveau document au cours du processus."
+
+#: ../../source/user_interface/split_and_merge.rst:44
+msgid ""
+"When merging documents in a folder, only the latter option is possible, "
+"so only the choice **Merge Documents in Folder** is available."
+msgstr ""
+"Lors de la fusion de documents dans un dossier, seule cette dernière "
+"option est possible, de sorte que seul le choix **Fusionner les "
+"documents dans un dossier** est disponible."
+
+#: ../../source/user_interface/split_and_merge.rst:47
+msgid ""
+"In either case, the **Merge Documents** dialog will let you exclude "
+"documents you don't want to include, and it also lets you reorder them "
+"if you wish."
+msgstr ""
+"Dans les deux cas, la boîte de dialogue **Fusionner des documents** vous "
+"permet d'exclure les documents que vous ne souhaitez pas inclure et de "
+"les réorganiser si vous le souhaitez."

docs/source/locales/fr/LC_MESSAGES/user_interface/statistics.po

@@ -0,0 +1,114 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2025
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2025.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.7rc1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-05-27 19:59+0200\n"
+"PO-Revision-Date: 2025-05-28 21:12+0200\n"
+"Last-Translator: \n"
+"Language-Team: fr <LL@li.org>\n"
+"Language: fr\n"
+"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"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/user_interface/statistics.rst:5
+msgid "Writing Statistics"
+msgstr "Statistiques d'écriture"
+
+#: ../../source/user_interface/statistics.rst:7
+msgid ""
+"When you work on a project, a log file records when you opened it, when "
+"you closed it, and the total word counts of your novel documents and "
+"notes at the end of the session, provided that the session lasted either "
+"more than 5 minutes, or that the total word count changed. For more "
+"details about the log file itself, see :ref:`docs_technical_storage`."
+msgstr ""
+"Lorsque vous travaillez sur un projet, un fichier journal enregistre le "
+"moment où vous l'avez ouvert, le moment où vous l'avez fermé, et le "
+"nombre total de mots de vos nouveaux documents et notes à la fin de la "
+"session, à condition que la session ait duré plus de 5 minutes, ou que "
+"le nombre total de mots ait changé. Pour plus de détails sur le fichier "
+"journal lui-même, voir :ref:`docs_technical_storage`."
+
+#: ../../source/user_interface/statistics.rst:12
+msgid ""
+"A tool to view the content of the log file is available in the **Tools** "
+"menu under **Writing Statistics**. You can also launch it by pressing :"
+"kbd:`F6`, or find it on the sidebar."
+msgstr ""
+"Un outil permettant de visualiser le contenu du fichier journal est "
+"disponible dans le menu **Outils** sous **Statistiques d'écriture**. "
+"Vous pouvez également le lancer en appuyant sur :kbd:`F6`, ou le trouver "
+"dans la barre latérale."
+
+#: ../../source/user_interface/statistics.rst:15
+msgid ""
+"The tool will show a list of all your sessions, and a set of filters to "
+"apply to the data. You can also export the filtered data to a JSON file "
+"or to a CSV file that can be opened by a spreadsheet application like "
+"for instance Libre Office Calc or Excel."
+msgstr ""
+"L'outil affichera une liste de toutes vos sessions, ainsi qu'un ensemble "
+"de filtres à appliquer aux données. Vous pouvez également exporter les "
+"données filtrées vers un fichier JSON ou vers un fichier CSV qui peut "
+"être ouvert par un tableur comme par exemple Libre Office Calc ou Excel."
+
+#: ../../source/user_interface/statistics.rst:21
+msgid "Idle Time"
+msgstr "Temps d'inactivité"
+
+#: ../../source/user_interface/statistics.rst:23
+msgid ""
+"The log file stores how much of the session time was spent idle. The "
+"definition of idle here is that the novelWriter main window loses focus, "
+"or the user hasn't made any changes to the currently open document in "
+"five minutes. You can change the number of minutes in **Preferences**."
+msgstr ""
+"Le fichier journal enregistre la durée de la session passée en mode "
+"inactif. La définition de l'inactivité ici est que la fenêtre principale "
+"de novelWriter perd le focus, ou que l'utilisateur n'a pas fait de "
+"changements dans le document ouvert depuis cinq minutes. Vous pouvez "
+"modifier le nombre de minutes dans les **Préférences**."
+
+#: ../../source/user_interface/statistics.rst:29
+msgid "Session Timer"
+msgstr "Chronomètre de session"
+
+#: ../../source/user_interface/statistics.rst:31
+msgid ""
+"A session timer is by default visible in the status bar. The icon will "
+"show you a clock icon when you are active, and a pause icon when you are "
+"considered \"idle\" per the criteria mentioned above."
+msgstr ""
+"Un chronomètre de session est visible par défaut dans la barre d'état. "
+"L'icône affiche une horloge lorsque vous êtes actif et une icône de "
+"pause lorsque vous êtes considéré comme « inactif » selon les critères "
+"mentionnés ci-dessus."
+
+#: ../../source/user_interface/statistics.rst:34
+msgid ""
+"If you do not wish to see the timer, you can click on it once to hide "
+"it. The icon will still be visible. Click the icon once more to display "
+"the timer again."
+msgstr ""
+"Si vous ne souhaitez pas voir le chronomètre, vous pouvez cliquer une "
+"fois dessus pour le masquer. L'icône restera visible. Cliquez à nouveau "
+"sur l'icône pour afficher à nouveau le chronomètre."
+
+#: ../../source/user_interface/statistics.rst:39
+msgid ""
+"As of version 2.6, clicking the timer text or icon in the status bar "
+"will toggle its visibility."
+msgstr ""
+"Depuis la version 2.6, un clic sur le texte ou l'icône du minuteur dans "
+"la barre d'état permet de basculer sa visibilité."

docs/source/more/counting.rst

@@ -1,13 +1,13 @@
-.. _a_counting:
+.. _docs_more_counting:
 
 ********************
 Word and Text Counts
 ********************
 
 This is an overview of how words and other counts of your text are performed. The counting rules
-should be relatively standard, and are compared to Libre Office Writer rules.
+should be relatively standard, and are comparable to Libre Office Writer rules.
 
-The counts provided in the app on the raw text is meant to be approximate. For more accurate
+The counts provided in the app on the raw text are meant to be approximate. For more accurate
 counts, you need to build your manuscript in the **Manuscript Tool** and check the counts on the
 generated preview.
 

docs/source/more/customise.rst

@@ -1,4 +1,4 @@
-.. _a_custom:
+.. _docs_more_custom:
 
 **************
 Customisations
@@ -11,7 +11,7 @@ There are a few ways you can customise novelWriter yourself. Currently, you can
 your own syntax themes, and install additional dictionaries.
 
 
-.. _a_custom_dict:
+.. _docs_more_custom_dict:
 
 Spell Check Dictionaries
 ========================
@@ -19,6 +19,7 @@ Spell Check Dictionaries
 novelWriter uses Enchant_ as the spell checking tool. Depending on your operating system, it may or
 may not load all installed spell check dictionaries automatically.
 
+
 Linux and MacOS
 ---------------
 
@@ -26,6 +27,7 @@ On Linux and MacOS, you generally only have to install hunspell, aspell or myspe
 your system like you do for other applications. See your distro or OS documentation for how to do
 this. These dictionaries should show up as available spell check languages in novelWriter.
 
+
 Windows
 -------
 
@@ -61,7 +63,7 @@ You can find the various dictionaries on the `Free Desktop`_ website.
    each line and download that.
 
 
-.. _a_custom_theme:
+.. _docs_more_custom_theme:
 
 Syntax and GUI Themes
 =====================
@@ -84,17 +86,17 @@ Remember to also change the name of your theme by modifying the ``name`` setting
 file, otherwise you may not be able to distinguish them in **Preferences**.
 
 For novelWriter to be able to locate the custom theme files, you must copy them to the
-:ref:`a_locations_data` location in your home or user area. There should be a folder there named
+:ref:`docs_technical_locations_data` location in your home or user area. There should be a folder there named
 ``syntax`` for syntax themes, just ``themes`` for GUI themes, and ``icons`` for icon themes. These
 folders are created the first time you start novelWriter.
 
 Once the files are copied there, they should show up in **Preferences** with the label you
 set as ``name`` inside the file.
 
-.. versionadded:: 2.0
-   The ``icontheme`` value was added to GUI themes. Make sure you set this value in existing custom
-   themes. Otherwise, novelWriter will try to guess your icon theme, and may not pick the most
-   suitable one.
+.. note::
+
+   The theme file formats change regularly in new releases. It is up to you to keep custom theme
+   files up to date.
 
 
 Custom GUI and Icons Theme
@@ -112,7 +114,26 @@ A GUI theme ``.conf`` file consists of the following settings:
    url         = https://example.com
    license     = CC BY-SA 4.0
    licenseurl  = https://creativecommons.org/licenses/by-sa/4.0/
-   icontheme   = typicons_light
+
+   [Icons]
+   default         = 100, 100, 100
+   faded           = 100, 100, 100
+   red             = 255,   0,   0
+   orange          = 255, 128,   0
+   yellow          = 255, 255,   0
+   green           =   0, 255,   0
+   aqua            =   0, 255, 255
+   blue            =   0,   0, 255
+   purple          = 255,   0, 255
+
+   [Project]
+   root            =   0, 255, 255
+   folder          = 255, 255,   0
+   file            = 100, 100, 100
+   title           =   0, 255,   0
+   chapter         = 255,   0,   0
+   scene           =   0,   0, 255
+   note            = 255, 255,   0
 
    [Palette]
    window          = 100, 100, 100
@@ -134,24 +155,23 @@ A GUI theme ``.conf`` file consists of the following settings:
    helptext        =   0,   0,   0
    fadedtext       = 128, 128, 128
    errortext       = 255,   0,   0
-   statusnone      = 120, 120, 120
-   statussaved     =   2, 133,  37
-   statusunsaved   = 200,  15,  39
 
-In the Main section you must at least define the ``name`` and ``icontheme`` settings. The
-``icontheme`` settings should correspond to one of the internal icon themes, either
-``typicons_light`` or ``typicons_dark``, or to an icon theme in your custom icons directory. The
-setting must match the icon theme's folder name.
+In the Main section you must at least define the ``name`` settings.
 
 The Palette values correspond to the Qt enum values for ``QPalette::ColorRole``, see the
-`Qt documentation <https://doc.qt.io/qt-5.15/qpalette.html#ColorRole-enum>`_ for more details. The
+`Qt documentation <https://doc.qt.io/qt-6/qpalette.html#ColorRole-enum>`_ for more details. The
 colour values are RGB numbers on the format ``r, g, b`` where each is an integer from ``0`` to
 ``255``. Omitted values are not loaded and will use default values. If the ``helptext`` colour is
 not defined, it is computed as a colour between the ``window`` and ``windowtext`` colour.
+Additional shades of some of the colours are also computed. These are mainly used for 3D effects.
 
 .. versionadded:: 2.5
    The ``fadedtext`` and ``errortext`` theme colour entries were added.
 
+.. versionadded:: 2.7
+   The ``icontheme`` setting was dropped as the icon theme is now its own setting.
+   The ``[Icons]`` and ``[Project]`` sections were added, and the ``status*`` settings removed.
+
 
 Custom Syntax Theme
 -------------------

docs/source/more/handling_errors.rst

@@ -0,0 +1,62 @@
+.. _docs_more_errors:
+
+***************
+Handling Errors
+***************
+
+In case something goes wrong, novelWriter has a few built-in features to reduce the chance your
+work is lost. In case of a crash, it will also try to save whatever changes you have made before
+exiting, if this is at all possible.
+
+The storage solution is designed to save each text document independently, so only the document
+you're working on is actually at a risk of losing data in the event of a crash.
+
+
+.. _docs_more_errors_orphaned:
+
+Recovered Documents
+===================
+
+If novelWriter crashes or otherwise exits without saving the project state, or if you're using a
+file synchronisation tool that runs out of sync, there may be files in the project storage folder
+that aren't tracked in the core project file. These files, when discovered, are recovered and added
+back into the project when a project is opened.
+
+The discovered files are scanned for metadata that give clues as to where the document may
+previously have been located in the project. The project loading routine will try to put them back
+as close as possible to this location, if it still exists. Generally, it will be appended to the
+end of the folder where it previously was located. If that folder doesn't exist, it will try to add
+it to the correct root folder type. If it cannot figure out which root folder is correct, the
+document will be added to the **Novel** root folder. Finally, if a **Novel** does not exist, one
+will be created.
+
+If the title of the document can be recovered, the word "Recovered:" will be added as a prefix to
+indicate that it may need further attention. If the title cannot be determined, the document will
+be named after its internal key, which is a string of characters and numbers.
+
+
+.. _docs_more_errors_lock:
+
+Project Lockfile
+================
+
+To prevent data loss caused by file conflicts when novelWriter projects are synchronised via file
+synchronisation tools, a project lockfile is written to the project storage folder when a project
+is open. If you try to open a project that already has such a file present, you will be presented
+with a warning, and some information about where else novelWriter thinks the project is also open.
+You will be given the option to ignore this warning, and continue opening the project at your own
+risk.
+
+.. note::
+
+   If, for some reason, novelWriter or your computer crashes, the lock file may remain even if
+   there are no other instances keeping the project open. In such a case it is safe to ignore the
+   lock file warning when re-opening the project.
+
+.. warning::
+
+   If you choose to ignore the warning and continue opening the project, and multiple instances of
+   the project are in fact open, you are likely to cause inconsistencies and create diverging
+   project files, potentially resulting in loss of data and orphaned files. You are not likely to
+   lose any actual text unless both instances have the same document open in the editor, and
+   novelWriter will try to resolve project inconsistencies the next time you open the project.

docs/source/more/project_format.rst

@@ -1,12 +1,9 @@
-.. _a_prjfmt:
+.. _docs_more_project_formats:
 
 **********************
 Project Format Changes
 **********************
 
-.. _File Format Spec 1.5: _static/fileformatspec15.pdf
-.. _documentation: https://docs.novelwriter.io/
-
 Most of the changes to the file formats over the history of novelWriter have no impact on the
 user side of things. The project files are generally updated automatically. However, some of the
 changes require minor actions from the user.
@@ -14,28 +11,17 @@ changes require minor actions from the user.
 The key changes in the formats are listed in this chapter, as well as the user actions required,
 where applicable.
 
-.. only:: not html
-
-   A full project file format specification is available in the online documentation_.
+A full project file format specification is available under "More Documents".
 
 .. caution::
+
    When you update a project from one format version to the next, the project can no longer be
    opened by a version of novelWriter prior to the version where the new file format was
    introduced. You will get a notification about any updates to your project file format and will
    have the option to decline the upgrade.
 
-.. only:: html
 
-   **For Developers**
-
-   A full description of the current file format is available in the
-   :download:`File Format Spec 1.5 <fileformatspec15.pdf>`
-   document, available as a PDF. This document is intended for contributors to novelWriter, those
-   building project conversion tools, either to or from tne novelWriter format, and for those who
-   wish to make their own templating system.
-
-
-.. _a_prjfmt_1_5:
+.. _docs_more_project_formats_1_5:
 
 Format 1.5 Changes
 ==================
@@ -49,7 +35,7 @@ heading of the document is now saved to the item rather than in the index. The c
 automatically the first time a project is loaded. No user action is required.
 
 
-.. _a_prjfmt_1_4:
+.. _docs_more_project_formats_1_4:
 
 Format 1.4 Changes
 ==================
@@ -63,7 +49,7 @@ compact format that is simpler and faster to parse, and easier to extend. The co
 automatically the first time a project is loaded. No user action is required.
 
 
-.. _a_prjfmt_1_3:
+.. _docs_more_project_formats_1_3:
 
 Format 1.3 Changes
 ==================
@@ -83,25 +69,26 @@ should be used only a few places in any given project. These are as follows:
 **Title Pages**
 
 * The formatting of the level one title on the title page must be changed from ``# Title Text`` to
-  ``#! Title Text`` in order to retain the previous functionality. See :ref:`a_fmt_head`.
+  ``#! Title Text`` in order to retain the previous functionality.
+  See :ref:`docs_usage_headings_levels`.
 * Any text that was previously centred on the page must be manually centred using the text
-  alignment feature. See :ref:`a_fmt_align`.
+  alignment feature. See :ref:`docs_usage_align_indent`.
 
 **Unnumbered Chapters**
 
 * Since the specific layout for unnumbered chapters has been dropped, such chapters must all use
   the ``##! Chapter Name`` formatting code instead of ``## Chapter Name``. This also includes
   chapters marked by an asterisk: ``## *Chapter Name``, as this feature has also been dropped.
-  See :ref:`a_fmt_head`.
+  See :ref:`docs_usage_headings_levels`.
 
 **Plain Pages**
 
 * The layout named "Plain Page" has also been removed. The only feature of this layout was that it
   ensured that the content always started on a fresh page. In the new format, fresh pages can be
-  set anywhere in the text with the ``[NEW PAGE]`` code. See :ref:`a_fmt_break`.
+  set anywhere in the text with the ``[new page]`` code. See :ref:`docs_usage_formatting_breaks`.
 
 
-.. _a_prjfmt_1_2:
+.. _docs_more_project_formats_1_2:
 
 Format 1.2 Changes
 ==================
@@ -109,9 +96,10 @@ Format 1.2 Changes
 This project format was introduced in novelWriter version 0.10.
 
 With this format, the way auto-replace entries were stored in the main project XML file changed.
+Conversion from this format is done automatically.
 
 
-.. _a_prjfmt_1_1:
+.. _docs_more_project_formats_1_1:
 
 Format 1.1 Changes
 ==================
@@ -122,10 +110,11 @@ With this format, the ``content`` folder was introduced in the project storage.
 novelWriter documents were saved in a series of folders numbered from ``data_0`` to ``data_f``.
 
 It also reduces the number of meta data and cache files. These files are automatically deleted if
-an old project is opened. This was also when the Table of Contents file was introduced.
+an old project is opened. This was also when the Table of Contents file was introduced. Conversion
+from this format is done automatically.
 
 
-.. _a_prjfmt_1_0:
+.. _docs_more_project_formats_1_0:
 
 Format 1.0 Changes
 ==================

docs/source/more/typography.rst

@@ -1,4 +1,4 @@
-.. _a_typ:
+.. _docs_more_typographical:
 
 *******************
 Typographical Notes
@@ -12,26 +12,22 @@ Typographical Notes
 novelWriter has some support for typographical symbols that are not usually easily available in
 many text editors. This includes for instance the proper unicode quotation marks, dashes, ellipsis,
 thin spaces, etc. All these symbols are available from the **Insert** menu, and via
-keyboard shortcuts. See :ref:`a_kb_ins`.
+keyboard shortcuts. See :ref:`docs_features_shortcuts_insert`.
 
 This chapter provides some additional information on how novelWriter handles these symbols.
 
 
-.. _a_typ_notes:
-
-Special Notes on Symbols
-========================
-
-This section contains additional notes on the available special symbols.
-
-
 Dashes and Ellipsis
--------------------
+===================
 
-With the auto-replace feature enabled (see :ref:`a_ui_edit_auto`), multiple hyphens are converted
-automatically to short and long dashes, and three dots to ellipsis. The last auto-replace can
-always be reverted with the undo command :kbd:`Ctrl+Z`, reverting the text to what you typed before
-the automatic replacement occurred.
+With the auto-replace feature enabled (see :ref:`docs_ui_edit_view_auto`), two and three hyphens
+are converted automatically to short and long dashes, four hyphens to a horizontal bar, and three
+dots to ellipsis.
+
+.. tip::
+
+   The last auto-replace can always be reverted with the undo command :kbd:`Ctrl+Z`, reverting the
+   text to what you typed before the automatic replacement occurred.
 
 In addition, "Figure Dash" is available. The Figure Dash is a dash that has the same width as the
 numbers of the same font, for most fonts. It helps to align numbers nicely in columns when you need
@@ -39,24 +35,22 @@ to use a dash in them.
 
 
 Single and Double Quotes
-------------------------
+========================
 
 All the different quotation marks listed on the `Quotation Mark`_ Wikipedia page are available, and
 can be selected as auto-replaced symbols for straight single and double quote key strokes. The
 settings can be found in **Preferences**.
 
-Ordinarily, text wrapped in quotes are highlighted by the editor. This is meant as a convenience
-for highlighting dialogue between characters. This feature can be disabled in
-**Preferences** if this feature isn't wanted.
+If your text contains straight single and double quotes, there are two convenience functions in the
+**Format** menu that can be used to re-format a selected section of text with the correct quote
+symbols.
 
-The editor distinguishes between text wrapped in regular straight double quotes and the
-user-selected double quote symbols. This is to help the writer recognise which parts of the text
-are not using the chosen quote symbols. Two convenience functions in the **Format** menu
-can be used to re-format a selected section of text with the correct quote symbols.
+You can enable dialogue recognition and colour highlighting for novel documents.
+See :ref:`docs_features_dialogue` for more details.
 
 
 Single and Double Prime
-------------------------
+=======================
 
 Both single and double prime symbols are available in the **Insert** menu. These symbols
 are the correct symbols to use for unit symbols for feet, inches, minutes, and seconds. The usage
@@ -66,8 +60,10 @@ codes. Using these correctly will also prevent the auto-replace and dialogue hig
 misunderstanding their meaning in the text.
 
 
+.. _docs_more_typographical_symbols_apostrophe:
+
 Modifier Letter Apostrophe
---------------------------
+==========================
 
 The auto-replace feature will consider any right-facing single straight quote as a quote symbol,
 even if it is intended as an apostrophe. This also includes the syntax highlighter, which may
@@ -79,13 +75,15 @@ right single quotation marks, depending on the font. There is a Wikipedia articl
 `Modifier letter apostrophe`_ with more details.
 
 .. note::
+
    On export with the **Build Manuscript** tool, these apostrophes will be replaced
    automatically with the corresponding right hand single quote symbol as is generally recommended.
-   Therefore it doesn't really matter if you only use them to correct syntax highlighting.
+   Therefore it doesn't really matter if you only use them to correct syntax highlighting in some
+   places, and not others.
 
 
-Special Space Symbols
----------------------
+White Space Symbols
+===================
 
 A few variations of the regular space character is supported. The correct typographical way to
 separate a number from its unit is with a `thin space`_. It is usually 2/3 the width of a regular
@@ -97,5 +95,11 @@ A regular space can also be made into a non-breaking space if needed.
 All non-breaking spaces are highlighted with a differently coloured background to make it easier to
 spot them in the text. The colour will depend on the selected colour theme.
 
-The thin and non-breaking spaces are converted to their corresponding HTML codes on export to HTML
-format.
+You can insert these spaces in your text using the following keyboard combinations:
+
+* A non-breaking space can be inserted with :kbd:`Ctrl+K`, :kbd:`Space`.
+* Thin spaces are also supported, and can be inserted with :kbd:`Ctrl+K`, :kbd:`Shift+Space`.
+* Non-breaking thin space can be inserted with :kbd:`Ctrl+K`, :kbd:`Ctrl+Space`.
+
+These are all insert features, and the **Insert** menu has more. The keyboard shortcuts for them
+are also listed in :ref:`docs_features_shortcuts`.

docs/source/project_overview.rst

@@ -1,390 +0,0 @@
-.. _a_proj:
-
-*****************
-Managing Projects
-*****************
-
-Your text in novelWriter is organised into projects. Each project is meant to contain one novel
-and associated notes. If you have multiple novels in a series, with the same characters and shared
-notes, it is also possible to keep all of them in the same project.
-
-.. _a_proj_new:
-
-Creating Project
-================
-
-New projects can be created from the **Project** menu by selecting **Create or Open Project**. This
-will open the **Welcome** dialog, where you can select the :guilabel:`New` button that will assist
-you in creating a new project. This dialog is also displayed when you start novelWriter.
-
-A novelWriter project requires a dedicated folder for storing its files on the local file system.
-If you're interested in the details, you can have a look at the chapter :ref:`a_storage`.
-
-A list of recently opened projects is maintained, and displayed in the **Welcome** dialog. A
-project can be removed from this list by selecting it and pressing the :kbd:`Del` key or by
-right-clicking it and selecting the **Remove Project** option.
-
-.. figure:: images/fig_welcome.jpg
-
-   The project list (left) and new project form (right) of the :guilabel:`Welcome` dialog.
-
-Project-specific settings are available in **Project Settings** in the **Project** menu. See
-further details below in the :ref:`a_proj_settings` section.
-
-Details about the project's novel text, including word counts, and a table of contents with word
-and page counts, is available through the **Novel Details** dialog. Statistics about the project
-is also available in the **Manuscript Build** tool.
-
-
-Template Projects
------------------
-
-From the Welcome dialog you can also create a new from another existing project. If you have a
-specific structure you want to use for all your new projects, you can create a dedicated project to
-be used as a template, and select to copy an existing project from the :guilabel:"Prefill Project"
-option from the **New Project** form.
-
-
-.. _a_proj_roots:
-
-Project Structure
-=================
-
-Projects are structured into a set of top level folders called "Root Folders". They are visible in
-the project tree at the left side of the main window.
-
-The :term:`novel documents` go into a root folder of type **Novel**. :term:`Project notes` go into
-the other root folders. These other root folder types are intended for your notes on the various
-elements of your story. Using them is of course entirely optional.
-
-A new project may not have all of the root folders present, but you can add the ones you want from
-the project tree tool bar.
-
-Each root folder has one or more :term:`reference` :term:`keyword` associated with it that is used
-to reference them from other documents and notes. The intended usage of each type of root folder is
-listed below. However, aside from the **Novel** folder, no restrictions are applied by the
-application on what you put in them. You can use them however you want.
-
-The root folder system is closely connected to how the Tags and References system works. For more
-details, see the :ref:`a_references` chapter.
-
-
-Root Folder Types
------------------
-
-**Novel**
-   This is the root folder type for text that goes into the final novel or novels. This class of
-   documents have other rules and features than the project notes. See :ref:`a_struct` for more
-   details.
-
-**Plot**
-   This is the root folder type where main plots can be outlined. It is optional, but adding at
-   least brief notes can be useful in order to tag plot elements for the **Outline View**. Tags in
-   this folder can be references using the ``@plot`` keyword.
-
-**Characters**
-   Character notes go in this root folder type. These are especially important if you want to use
-   the **Outline View** to see which character appears where, which part of the story is told from
-   a specific character's point-of-view, or focusing on a particular character's storyline.
-
-   The character names can also be inserted into for instance chapter titles when you create your
-   manuscript. Tags in this type of folder can be referenced using the ``@pov`` keyword for
-   point-of-view characters, ``@focus`` for a focus character, or the ``@char`` keyword for any
-   other character present.
-
-**Locations**
-   The locations folder type is for various scene locations that you want to track. Tags in this
-   folder can be references using the ``@location`` keyword.
-
-**Timeline**
-   If the story has multiple plot timelines or jumps in time within the same plot, this folder type
-   can be used to track this. Tags in this type of folder can be references using the ``@time``
-   keyword.
-
-**Objects**
-   Important objects in the story, for instance physical objects that change hands often, can be
-   tracked here. Tags in this type of folder can be references using the ``@object`` keyword.
-
-**Entities**
-   Does your plot have many powerful organisations or companies? Or other entities that are part of
-   the plot? They can be organised here. Tags in this type of folder can be references using the
-   ``@entity`` keyword.
-
-**Custom**
-   The custom root folder type can be used for tracking anything else not covered by the above
-   options. Tags in this folder type can be references using the ``@custom`` keyword.
-
-The root folders are closely tied to the tags and reference system. Each folder type corresponds to
-the categories of tags that can be used to reference them. For more information about the tags
-listed, see :ref:`a_references_references`.
-
-There is also a ``@mention`` keyword that can be used to reference any tag.
-See :ref:`a_references_references` for more details.
-
-.. note::
-   You can rename root folders to whatever you want. However, this doesn't change the reference
-   keyword or what they do.
-
-.. versionadded:: 2.0
-   As of version 2.0, you can make multiple root folders of each kind to split up your project.
-
-
-.. _a_proj_roots_del:
-
-Deleted Documents
------------------
-
-Deleted documents are moved into a special **Trash** root folder. Documents in the trash folder can
-then be deleted permanently, either individually, or by emptying the trash from the menu. Documents
-in the trash folder are removed from the :term:`project index` and cannot be referenced.
-
-A document or a folder can be moved to trash from the **Project** menu, or by pressing
-:kbd:`Ctrl+Shift+Del`. Root folders can only be removed when they are empty.
-
-
-.. _a_proj_roots_out:
-
-Archived Documents
-------------------
-
-If you don't want to delete a document, or put it in the **Trash** folder where it may be deleted
-accidentally, but still want it out of your main project tree, you can create an **Archive** root
-folder instead and move it there. It has the same effect as moving it to **Trash**, but it is safe
-from deletion.
-
-You can drag any document to this folder and preserve its settings. The document will always be
-excluded from the **Build Manuscript** tool. It is also removed from the :term:`project index`, so
-the tags and references defined in it will not show up anywhere else.
-
-
-.. _a_proj_roots_dirs:
-
-Using Folders in the Project Tree
----------------------------------
-
-Regular folders, those that are not root folders, have no structural significance to the project.
-When novelWriter is processing the documents in a project, like for instance when you create a
-manuscript from it, these folders are ignored. Only the order of the documents themselves matter.
-
-The folders are there purely as a way for you to organise the documents in meaningful sections and
-to be able to collapse and hide them in the project tree when you're not working on those
-documents.
-
-.. versionadded:: 2.0
-   As of version 2.0 it is possible to add child documents to other documents. This is particularly
-   useful when you create chapters and scenes. If you add separate scene documents, you should also
-   add separate chapter documents, even if they only contain a chapter heading. You can then add
-   scene documents as child items to the chapters.
-
-
-.. _a_proj_roots_orphaned:
-
-Recovered Documents
--------------------
-
-If novelWriter crashes or otherwise exits without saving the project state, or if you're using a
-file synchronisation tool that runs out of sync, there may be files in the project storage folder
-that aren't tracked in the core project file. These files, when discovered, are recovered and added
-back into the project.
-
-The discovered files are scanned for metadata that give clues as to where the document may
-previously have been located in the project. The project loading routine will try to put them back
-as close as possible to this location, if it still exists. Generally, it will be appended to the
-end of the folder where it previously was located. If that folder doesn't exist, it will try to add
-it to the correct root folder type. If it cannot figure out which root folder is correct, the
-document will be added to the **Novel** root folder. Finally, if a **Novel** does not exist, one
-will be created.
-
-If the title of the document can be recovered, the word "Recovered:" will be added as a prefix to
-indicate that it may need further attention. If the title cannot be determined, the document will
-be named after its internal key, which is a string of characters and numbers.
-
-
-.. _a_proj_roots_lock:
-
-Project Lockfile
-----------------
-
-To prevent lost documents caused by file conflicts when novelWriter projects are synchronised via
-file synchronisation tools, a project lockfile is written to the project storage folder when a
-project is open. If you try to open a project which already has such a file present, you will be
-presented with a warning, and some information about where else novelWriter thinks the project is
-also open. You will be given the option to ignore this warning, and continue opening the project at
-your own risk.
-
-.. note::
-   If, for some reason, novelWriter or your computer crashes, the lock file may remain even if
-   there are no other instances keeping the project open. In such a case it is safe to ignore the
-   lock file warning when re-opening the project.
-
-.. warning::
-   If you choose to ignore the warning and continue opening the project, and multiple instances of
-   the project are in fact open, you are likely to cause inconsistencies and create diverging
-   project files, potentially resulting in loss of data and orphaned files. You are not likely to
-   lose any actual text unless both instances have the same document open in the editor, and
-   novelWriter will try to resolve project inconsistencies the next time you open the project.
-
-
-.. _a_proj_files:
-
-Project Documents
-=================
-
-New documents can be created from the toolbar in the project tree, or by pressing :kbd:`Ctrl+N`.
-This will open the create new item menu and let you choose between a number of pre-defined
-documents and folders. You will be prompted for a label for the new item.
-
-You can always rename an item by selecting **Rename Item** from the **Project** menu, or by
-pressing :kbd:`F2` when a document or folder is selected.
-
-Other settings for project documents and folders are available from the context menu that you can
-activate by right-clicking on an it in the tree. The **Transform** submenu includes options for
-converting, splitting, or merging documents. See :ref:`a_ui_tree_split_merge` for more details on
-the latter two.
-
-
-Document Templates
-------------------
-
-If you wish to create template documents to be used when creating new project documents, like for
-instance a character note template, you can add a **Templates** root folder to your project. Any
-document added to this root folder will show up in the **Add Item** menu in the project tree
-toolbar. When selected, a new document is created with its content copied from the chosen template.
-
-.. versionadded:: 2.3
-
-
-.. _a_proj_files_counts:
-
-Word Counts
------------
-
-A character, word and paragraph count is maintained for each document, as well as for each section
-of a document following a :term:`heading<headings>`. The word count and change of words in the
-current session is displayed in the footer of any document open in the editor, and all stats are
-shown in the details panel below the project tree for any document selected in the project or novel
-trees.
-
-The word counts are not updated in real time, but run in the background every few seconds for as
-long as the document is being actively edited.
-
-A total project word count is displayed in the status bar. The total count depends on the sum of
-the values in the project tree, which again depend on an up to date :term:`project index`. If the
-counts seem wrong, a full project word recount can be initiated by rebuilding the project's index.
-Either from the **Tools** menu, or by pressing :kbd:`F9`.
-
-The rules for how the counts are made is covered in more detail in :ref:`a_counting`.
-
-
-.. _a_proj_settings:
-
-Project Settings
-================
-
-The **Project Settings** can be accessed from the **Project** menu, or by pressing
-:kbd:`Ctrl+Shift+,`. This will open a dialog box, with a set of tabs.
-
-
-Settings Tab
-------------
-
-The **Settings** tab holds the project name, author, and language settings.
-
-The **Project Name** can be edited here. It is used for the main window title and for generating
-backup files. So keep in mind that if you do change this setting, the backup file names will change
-too.
-
-You can also change the **Authors** and **Project Language** setting. These are only used when
-building the manuscript, for some formats. The language setting is also used when inserting text
-into documents in the viewer, like for instance labels for keywords and special comments.
-
-If your project is in a different language than your main spell checking language is set to, you
-can override the default setting here. The project language can also be changed from the **Tools**
-menu.
-
-You can also override the automatic backup setting for the project if you wish.
-
-
-Status and Importance Tabs
---------------------------
-
-Each document or folder of type **Novel** can be given a "Status" label accompanied by a coloured
-icon with an optional shape selected from a list of pre-defined shapes. Each document or folder of
-the remaining types can be given an "Importance" label with the same customisation options.
-
-These labels are there purely for your convenience, and you are not required to use them for any
-other features to work. No other part of novelWriter accesses this information. The intention is to
-use these to indicate at what stage of completion each novel document is, or how important the
-content of a note is to the story. You don't have to use them this way, that's just what they were
-intended for, but you can make them whatever you want.
-
-See also :ref:`a_ui_tree_status`.
-
-.. note::
-   The status or importance level currently in use by one or more documents cannot be deleted, but
-   they can be edited.
-
-
-Auto-Replace Tab
-----------------
-
-A set of automatically replaced keywords can be added in this tab. The keywords in the left column
-will be replaced by the text in the right column when documents are opened in the viewer. They will
-also be applied to manuscript builds.
-
-The auto-replace feature will replace text in angle brackets that is in this list. The syntax
-highlighter will add an alternate colour to text matching the syntax, but it doesn't check if the
-text is in this list.
-
-.. note::
-   A keyword cannot contain spaces. The angle brackets are added by default, and when used in the
-   text are a part of the keyword to be replaced. This is to ensure that parts of the text aren't
-   unintentionally replaced by the content of the list.
-
-
-.. _a_proj_backup:
-
-Backup
-======
-
-An automatic backup system is built into novelWriter. In order to use it, a backup path to where
-the backup files are to be stored must be provided in **Preferences**. The path defaults to a
-folder named "Backups" in your home directory.
-
-Backups can be run automatically when a project is closed, which also implies it is run when the
-application itself is closed. Backups are date stamped zip files of the project files in the
-project folder (files not strictly a part of the project are ignored). The zip archives are stored
-in a subfolder of the backup path. The subfolder will have the same name as the **Project Name** as
-defined in :ref:`a_proj_settings`.
-
-The backup feature, when configured, can also be run manually from the **Tools** menu. It is also
-possible to disable automated backups for a given project in **Project Settings**.
-
-.. note::
-   For the backup to be able to run, the **Project Name** must be set in **Project Settings**. This
-   value is used to generate the name and path of the backups. Without it, the backup will not run
-   at all, but it will produce a warning message.
-
-
-.. _a_proj_stats:
-
-Writing Statistics
-==================
-
-When you work on a project, a log file records when you opened it, when you closed it, and the
-total word counts of your novel documents and notes at the end of the session, provided that the
-session lasted either more than 5 minutes, or that the total word count changed. For more details
-about the log file, see :ref:`a_storage`.
-
-A tool to view the content of the log file is available in the **Tools** menu under **Writing
-Statistics**. You can also launch it by pressing :kbd:`F6`, or find it on the sidebar.
-
-The tool will show a list of all your sessions, and a set of filters to apply to the data. You can
-also export the filtered data to a JSON file or to a CSV file that can be opened by a spreadsheet
-application like for instance Libre Office Calc or Excel.
-
-.. versionadded:: 1.2
-   As of version 1.2, the log file also stores how much of the session time was spent idle. The
-   definition of idle here is that the novelWriter main window loses focus, or the user hasn't made
-   any changes to the currently open document in five minutes. The number of minutes can be altered
-   in **Preferences**.

docs/source/project_references.rst

@@ -1,228 +0,0 @@
-.. _a_references:
-
-*******************
-Tags and References
-*******************
-
-In novelWriter there are no forms or tables to fill in to define characters, locations or other
-elements of your story. Instead, you create :term:`project notes` which you can mark as
-representing these story elements by creating a :term:`tag`. Whenever you want to link a piece of
-your story to a note defining a story element, like a character, you create a :term:`reference`
-back to that tag. You can also cross-link your project notes in the same way.
-
-This is perhaps one of the features that makes novelWriter different from other, similar
-applications. It is therefore not always obvious to new users how this is supposed to work, so
-this chapter hopes to explain in more detail how to use this tags and references system.
-
-.. tip::
-   If you find the Tags and Reference system difficult to follow just from reading this chapter,
-   you can create a new project in the **Welcome** dialog's New project form and select  "Create an
-   example project" from the "Pre-fill project" option. The example project contains several
-   examples of tags and references.
-
-
-.. _a_references_metadata:
-
-Metadata in novelWriter
-=======================
-
-The structure of your novelWriter project is inferred from the :term:`headings` within the
-documents, not the documents themselves. See :ref:`a_struct_heads` for more details. Therefore,
-metadata is also associated with headings, and not the documents directly.
-
-If you split your project into separate documents for each scene, this distinction may not matter.
-However, there are several benefits to using documents at a larger structural scale when first
-starting your project. For instance, it may make more sense to define all your scenes, and even
-chapters, in a single document at first, or perhaps a document per act. You can later split these
-documents up using the document split feature. See :ref:`a_ui_tree_split_merge` for more details.
-
-You can do the same with your notes. You can treat each heading as an independent element of your
-notes that can be referenced somewhere else. That way you can collect all your minor or background
-characters in a single note file, and still be able to reference them individually by separating
-them with headings and assigning each a tag.
-
-
-.. _a_references_tags:
-
-How to Use Tags
-===============
-
-A "tag" in novelWriter is a word or phrase that you define as belonging to a heading. Tags are set
-by using the ``@tag`` :term:`keyword`.
-
-The basic format of a tag is ``@tag: tagName``.
-
-An alternative format of a tag is ``@tag: tagName | displayName``.
-
-``tagName`` (Required)
-   This is a unique identifier of your choosing. It is the value you use later for making
-   references back to this document, or section of the document.
-
-``displayName`` (Optional)
-   This is an optional display name used for the tag. When you build your manuscript, you can for
-   instance insert the point of view character name directly into chapter headings. By default, the
-   ``tagName`` value is used in such headings, but if you use a shortened format internally in your
-   project, you can use this to specify a more suitable format for your manuscript headings.
-
-You can only set **one** tag per heading, and the tag has to be unique across **all** documents in
-the project.
-
-After a tag has been defined, it can be referenced in novel documents, or cross-referenced in other
-notes. Tags will also show up in the **Outline View** and in the references panel under the
-document viewer when a document is open in the viewer.
-
-The syntax highlighter will indicate to you that the keyword is correctly used and that the tag is
-allowed, that is, the tag is unique. Duplicate tags should be detected as long as the index is up
-to date. An invalid tag should have a green wiggly line under it, and will not receive the colour
-that valid tags do.
-
-The tag is the only part of these notes that novelWriter uses. The rest of the document content is
-there for you to use in whatever way you wish. Of course, the content of the documents can be added
-to the manuscript, or an outline document. If you want to compile a single document of all your
-notes, you can do this from the **Manuscript Build** tool.
-
-.. versionadded:: 2.2
-   Tags are no longer case sensitive. The tags are by default displayed with the capitalisation you
-   use when defining the tag, but you don't have to use the same capitalisation when referencing
-   it later.
-
-.. versionadded:: 2.3
-   Tags can have an optional display name for manuscript builds.
-
-Example of a heading with a tag for a character of the story:
-
-.. code-block:: md
-
-   # Character: Jane Doe
-
-   @tag: Jane | Jane Doe
-
-   Some information about the character Jane Doe.
-
-When this is done in a document in a :term:`Root Folder` of type "Characters", the tag is
-automatically treated as an available character in your project with the value "Jane", and you will
-be able to reference it in any of your other documents using the reference keywords for characters.
-It will also show up in the Character tab in the Reference panel below the document viewer, and in
-the reference auto-completer menu in the editor when you fill in references. See :ref:`a_ui_view`
-and :ref:`a_references_completer`.
-
-It is the root folder type that defines what category of story elements the tag is indexed under.
-See the :ref:`a_proj_roots` section for an overview of available root folder types. They are also
-covered in the next section.
-
-
-.. _a_references_references:
-
-How to Use References
-=====================
-
-Each heading of any level in your project can contain references to tags set in project notes. The
-references are gathered by the indexer and used to generate the **Outline View**, among other
-things.
-
-References are set as a :term:`keyword` and a list of corresponding tags. The valid keywords are
-listed below. The format of a reference line is ``@keyword: value1, [value2] ... [valueN]``. All
-reference keywords allow multiple values.
-
-``@pov``
-   The point-of-view character for the current section. The target must be a note tag in a
-   **Character** type root folder.
-
-``@focus``
-   The character that has the focus for the current section. This can be used in cases where the
-   focus is not a point-of-view character. The target must be a note tag in a **Character** type
-   root folder.
-
-``@char``
-   Other characters in the current section. The target must be a note tag in a **Character** type
-   root folder. This should not include the point-of-view or focus character if those references
-   are used.
-
-``@plot``
-   The plot or subplot advanced in the current section. The target must be a note tag in a **Plot**
-   type root folder.
-
-``@time``
-   The timelines touched by the current section. The target must be a note tag in a **Timeline**
-   type root folder.
-
-``@location``
-   The location the current section takes place in. The target must be a note tag in a
-   **Locations** type root folder.
-
-``@object``
-   Objects present in the current section. The target must be a note tag in a **Object** type root
-   folder.
-
-``@entity``
-   Entities present in the current section. The target must be a note tag in an **Entities** type
-   root folder.
-
-``@custom``
-   Custom references in the current section. The target must be a note tag in a **Custom** type
-   root folder. The custom folder are for any other category of notes you may want to use.
-
-``@mention``
-   Anything mentioned, but not present in the current section. It is intended for those cases where
-   you reveal details about a character or place in a scene without it being otherwise a part of
-   it. This can be useful when checking for consistency later. Any tag in any root note folder can
-   be listed under mentions.
-
-The syntax highlighter will alert the user that the tags and references are used correctly, and
-that the tags referenced exist.
-
-.. note::
-   The highlighter may be mistaken if the index of defined tags is out of date. If so, press
-   :kbd:`F9` to regenerate it, or select **Rebuild Index** from the **Tools** menu. In general, the
-   index for a document is regenerated when it is saved, so this shouldn't normally be necessary.
-
-.. tip::
-   If you add a reference in the editor to a tag that doesn't yet exist, you can right-click it and
-   select **Create Note for Tag**. This will generate a new project note automatically with the new
-   tag defined. In order for this to be possible, a root folder for that category of references
-   must already exist.
-
-One note can also reference another note in the same way novel documents do. When the note is
-opened in the document viewer, the references become clickable links, making it easier to follow
-connections in the plot. You can follow links in the document editor by clicking them with the
-mouse while holding down the :kbd:`Ctrl` key. Clicked links are always opened in the view panel.
-
-Project notes don't show up in the **Outline View**, so referencing between notes is only
-meaningful if you want to be able to click-navigate between them, or of course if you just want to
-highlight that two notes are related.
-
-.. tip::
-   If you cross-reference between notes and export your project as an HTML document using the
-   **Manuscript Build** tool, the cross-references become clickable links in the exported HTML
-   document as well.
-
-Example of a novel document with references to characters and plots:
-
-.. code-block:: md
-
-   ## Chapter 1
-
-   @pov: Jane
-
-   ### Scene 1
-
-   @char: John, Sam
-   @plot: Main
-
-   Once upon a time ...
-
-
-.. _a_references_completer:
-
-The References Auto-Completer
------------------------------
-
-An auto-completer context menu will show up automatically in the document editor when you type the
-character ``@`` on a new line. It will first suggest tag or reference keywords for you to add, and
-after the ``:`` has been added, suggest references from the list of tags you have already defined.
-
-You can use the auto-completer to add multiple references with a ``,`` between them, and even type
-new ones. New references can be created by right-clicking on them and selecting **Create Note for
-Tag** from the menu.
-
-.. versionadded:: 2.2

docs/source/project_structure.rst

@@ -1,140 +0,0 @@
-.. _a_struct:
-
-***************
-Novel Structure
-***************
-
-This chapter covers the structure of a novel project.
-
-There are two different types of documents in a project, **Novel Documents** and **Project Notes**.
-Active novel documents can only live in a **Novel** type root folder. You can also move them to
-**Archive** and **Trash** of course, where they become inactive.
-
-The project tree can distinguish between the different heading levels of the novel documents using
-coloured icons, and optionally add emphasis on the label, set in **Preferences** for easier
-identification.
-
-
-.. _a_struct_heads:
-
-Importance of Headings
-======================
-
-Subfolders under root folders have no impact on the structure of the novel itself. The structure is
-instead dictated by the heading level of the headings within the documents.
-
-Four levels of headings are supported, signified by the number of hashes (``#``) preceding the
-title. See also the :ref:`a_fmt` section for more details about the markup syntax.
-
-.. note::
-   The heading levels are not only important when generating the manuscript, they are also used by
-   the indexer when building the outline tree in the **Outline View** as well as in the **Novel
-   Tree**. Each heading also starts a new region where new Tags and References can be defined. See
-   :ref:`a_references` for more details.
-
-The syntax for the four basic heading types, and the three special types, is listed in section
-:ref:`a_fmt_head`. The meaning of the four levels for the structure of your novel is as follows:
-
-**Heading Level 1: Partition**
-   This heading level signifies that the text refers to a top level heading. This is useful when
-   you want to split the manuscript up into books, parts, or acts. These headings are not required.
-   The novel title itself should use the special heading level ``#!`` covered in :ref:`a_fmt_head`.
-
-**Heading Level 2: Chapter**
-   This heading level signifies a chapter. Each time you want to start a new chapter, you must add
-   such a heading. If you choose to split your manuscript up into one document per scene, you need
-   a single chapter document with just the heading. You can of course also add a synopsis and
-   reference keywords to the chapter document. If you want to open the chapter with a quote or
-   other introductory text that isn't part of a scene, this is also where you'd put that text.
-
-**Heading Level 3: Scene**
-   This heading level signifies a scene. You must provide a title text, but the title text can be
-   replaced with a scene separator or just skipped entirely when you build your manuscript. If you
-   need to distinguish between hard and soft scene breaks, there is an alternative format for
-   scenes you can use for this distinction. The formatting is covered in :ref:`a_fmt_head`. See
-   also :ref:`a_struct_heads_scenes`.
-
-**Heading Level 4: Section**
-   This heading level can be used to split up a scene, usually called a "section" in the
-   documentation and the user interface. These can be useful if you want to change references
-   mid-scene, like if you change the point-of-view character. You are free to use sections as you
-   wish, and you can filter them out of the final manuscript.
-
-Page breaks can be automatically added before partition, chapter and scene headings from the
-**Manuscript Build** tool when you build your project to a format that supports page breaks. If you
-want page breaks in other places, you have to specify them manually. See :ref:`a_fmt_break`.
-
-.. tip::
-   There are multiple options of how to process novel headings when building the manuscript. For
-   instance, chapter numbers can be applied automatically, and so can scene numbers if you want
-   them in a draft manuscript. You can also insert point-of-view character names in chapter titles.
-   See the :ref:`a_manuscript` page for more details.
-
-
-.. _a_struct_heads_title:
-
-Novel Title and Front Matter
-----------------------------
-
-It is recommended that you add a document at the very top of each **Novel** root folder with the
-novel title as the first line. You should modify the level 1 heading format code with an ``!`` in
-order to render it as a document title that is excluded from any automatic Table of Content in a
-manuscript build document, like so:
-
-.. code-block:: md
-
-   #! My Novel
-
-   >> _by Jane Doe_ <<
-
-The title is by default centred on the page. You can add more text to the page as you wish, like
-for instance the author's name and details.
-
-If you want an additional page of text after the title page, starting on a fresh page, you can add
-``[new page]`` on a line by itself, and continue the text after it. This will insert a page break
-before the text. See also :ref:`a_fmt_break`.
-
-
-.. _a_struct_heads_unnum:
-
-Unnumbered Chapter Headings
----------------------------
-
-If you use the automatic numbering feature for your chapters, but you want to keep some special
-chapters separate from this, you can add an ``!`` to the level 2 heading formatting code to tell
-the build tool to skip these chapters when adding numbers.
-
-.. code-block:: md
-
-   ##! Unnumbered Chapter Title
-
-   Chapter Text
-
-There is a separate formatting feature for such chapter titles in the **Manuscript Build** tool as
-well. See the :ref:`a_manuscript` page for more details. When building a document of a format that
-supports page breaks, also unnumbered chapters can have a page break added just like for normal
-chapters.
-
-
-.. _a_struct_heads_scenes:
-
-Hard and Soft Scene Breaks
---------------------------
-
-If you need two different ways to style scenes in your manuscript, like if you want to insert
-different scene separators for soft and hard scene breaks, there is an alternative scene format
-available for scene headings with a ``!`` added to the formatting code.
-
-.. code-block:: md
-
-   ### Soft Scene Transition
-
-   A soft scene break.
-
-   ###! Hard Scene Transition
-
-   A hard scene break.
-
-There is a separate formatting feature for these titles in the **Manuscript Build** tool.
-
-.. versionadded:: 2.4

docs/source/technical/locations.rst

@@ -1,16 +1,16 @@
-.. _a_locations:
+.. _docs_technical_locations:
 
 **************
 File Locations
 **************
 
-.. _QStandardPaths: https://doc.qt.io/qt-5/qstandardpaths.html
+.. _QStandardPaths: https://doc.qt.io/qt-6/qstandardpaths.html
 
 novelWriter will create a few files on your system outside of the application folder itself. These
 file locations are described in this chapter.
 
 
-.. _a_locations_conf:
+.. _docs_technical_locations_conf:
 
 Configuration
 =============
@@ -33,7 +33,7 @@ user's username on Windows.
    different way, these locations may also be different.
 
 
-.. _a_locations_data:
+.. _docs_technical_locations_data:
 
 Application Data
 ================
@@ -62,4 +62,4 @@ The Application Data location also holds several folders:
 
 ``icons``, ``syntax`` and ``themes``
    These folders are empty by default, but this is where the user can store custom theme files.
-   See :ref:`a_custom` for more details.
+   See :ref:`docs_more_custom` for more details.

docs/source/technical/source.rst

@@ -1,4 +1,4 @@
-.. _a_source:
+.. _docs_technical_source:
 
 *******************
 Running from Source
@@ -12,6 +12,7 @@ This chapter describes various ways of running novelWriter directly from the sou
 to build the various components like the translation files and documentation.
 
 .. note::
+
    The text below assumes the command ``python`` corresponds to a Python 3 executable. Python 2 is
    now deprecated, but on many systems the command ``python3`` may be needed instead. Likewise,
    ``pip`` may need to be replaced with ``pip3``.
@@ -22,10 +23,10 @@ by running:
 
 .. code-block:: bash
 
-   python pkgutils.py help
+   python pkgutils.py --help
 
 
-.. _a_source_depend:
+.. _docs_technical_source_depend:
 
 Dependencies
 ============
@@ -36,12 +37,11 @@ Everything else is handled with standard Python libraries.
 
 The following Python packages are needed to run all features of novelWriter:
 
-* ``PyQt5`` – needed for connecting with the Qt5 libraries.
+* ``PyQt6`` – needed for connecting with the Qt6 libraries.
 * ``PyEnchant`` – needed for spell checking (optional).
 
-PyQt/Qt must be at least 5.15.0. If you want spell checking, you must install the ``PyEnchant``
-package. The spell check library must be at least 3.0 to work with Windows. On Linux, 2.0 also
-works fine.
+If you want spell checking, you must install the ``PyEnchant`` package. The spell check library
+must be at least 3.0 to work with Windows. On Linux, 2.0 also works fine.
 
 If you install from PyPi, these dependencies should be installed automatically. If you install from
 source, dependencies can still be installed from PyPi with:
@@ -51,13 +51,14 @@ source, dependencies can still be installed from PyPi with:
    pip install -r requirements.txt
 
 .. note::
+
    On Linux distros, the Qt library is usually split up into multiple packages. In some cases,
    secondary dependencies may not be installed automatically. For novelWriter, the library files
    for rendering the SVG icons may be left out and needs to be installed manually. This is the
    case on for instance Arch Linux.
 
 
-.. _a_source_install:
+.. _docs_technical_source_install:
 
 Build and Install from Source
 =============================
@@ -90,7 +91,7 @@ different:
    pip install --user dist/novelWriter-2.0.7-py3-none-any.whl
 
 
-.. _a_source_i18n:
+.. _docs_technical_source_i18n:
 
 Building the Translation Files
 ==============================
@@ -110,12 +111,13 @@ This requires that the Qt Linguist tool is installed on your system. On Ubuntu a
 needed package is called ``qttools5-dev-tools``.
 
 .. note::
+
    If you want to improve novelWriter with translation files for another language, or update an
    existing translation, instructions for how to contribute can be found in the ``README.md`` file
    in the ``i18n`` folder of the source code.
 
 
-.. _a_source_sample:
+.. _docs_technical_source_sample:
 
 Building the Example Project
 ============================
@@ -129,7 +131,7 @@ running:
    python pkgutils.py sample
 
 
-.. _a_source_docs:
+.. _docs_technical_source_docs:
 
 Building the Documentation
 ==========================
@@ -139,7 +141,7 @@ packages from PyPi:
 
 .. code-block:: bash
 
-   pip install -r docs/source/requirements.txt
+   pip install -r docs/requirements.txt
 
 The documentation can then be built from the root folder in the source code by running:
 
@@ -154,8 +156,9 @@ You can also build a PDF manual from the documentation using the ``pkgutils.py``
 
 .. code-block:: bash
 
-   python pkgutils.py manual
+   python pkgutils.py docs-pdf en
 
-This will build the documentation as a PDF using LaTeX. The file will then be copied into the
-assets folder and made available in the **Help** menu in novelWriter. The Sphinx build system has a
-few extra dependencies when building the PDF. Please check the `Sphinx Docs`_ for more details.
+This will build the English documentation as a PDF using LaTeX. The file will then be copied into
+the assets folder and made available in the **Help** menu in novelWriter. Replace ``en`` with
+``all`` to build for all languages. The Sphinx build system has a few extra dependencies when
+building the PDF. Please check the `Sphinx Docs`_ for more details.

docs/source/technical/storage.rst

@@ -1,14 +1,54 @@
-.. _a_storage:
+.. _docs_technical_storage:
 
 ******************
 How Data is Stored
 ******************
 
-.. _documentation: https://docs.novelwriter.io/
+.. _version control: https://en.wikipedia.org/wiki/Version_control
 
 This chapter contains details of how novelWriter stores and handles the project data.
 
 
+Overview
+========
+
+The files of a novelWriter project are stored in a dedicated project folder. The project structure
+is kept in a file at the root of this folder called ``nwProject.nwx``. All the document files and
+associated meta data are stored in other folders below the project folder.
+
+This way of storing data was chosen for several reasons.
+
+Firstly, all the text you add to your project is saved directly to your project folder in separate
+files. Only the project structure and the text you are currently editing is stored in memory at any
+given time, which means there is a smaller risk of losing data if the application or your computer
+crashes.
+
+Secondly, having multiple small files means it is very easy to synchronise them between computers
+with standard file synchronisation tools.
+
+Thirdly, if you use `version control`_ software to track the changes to your project, the file
+formats used for the files are well suited. All the JSON documents have line breaks and indents as
+well, which makes it easier to track them with version control software.
+
+.. note::
+
+   Since novelWriter has to keep track of a bunch of files and folders when a project is open, it
+   may not run well on some virtual file systems. A file or folder must be accessible with exactly
+   the path it was saved or created with. An example where this is not the case is the way Google
+   Drive is mapped on Linux Gnome desktops using gvfs/gio.
+
+.. caution::
+
+   You should not add additional files to the project folder yourself. Nor should you, as a rule,
+   manually edit files within it. If you really must manually edit the text files, e.g. with some
+   automated task you want to perform, you need to rebuild the Project Index when you open
+   the project again.
+
+   Editing text files in the ``content`` folder is less risky as these are just plain text. Editing
+   the main project XML file, however, may make the project file unreadable and you may crash
+   novelWriter and lose project structure information and project settings.
+
+
 Project Structure
 =================
 
@@ -36,14 +76,7 @@ The project XML file is indent-formatted, and is suitable for diff tools and ver
 most of the file will stay static, although a timestamp is set in the meta section on line 2, and
 various meta data entries incremented, on each save.
 
-.. only:: not html
-
-   A full project file format specification is available in the online documentation_.
-
-.. only:: html
-
-   A full description of the current file format is available in the
-   :download:`File Format Spec 1.5 <fileformatspec15.pdf>` document, available as a PDF.
+A full project file format specification is available under "More Documents".
 
 
 Project Documents

docs/source/technical/tests.rst

@@ -1,4 +1,4 @@
-.. _a_pytest:
+.. _docs_technical_pytest:
 
 *************
 Running Tests

docs/source/usage/advanced_formatting.rst

@@ -0,0 +1,149 @@
+.. _docs_usage_formatting:
+
+*******************
+Advanced Formatting
+*******************
+
+Standard Markdown formatting is somewhat limited, so novelWriter has some additional formatting
+codes for special use cases. These codes are all based on brackets, and some allow an additional
+value to be set after a colon.
+
+This section covers all these formatting codes.
+
+
+.. _docs_usage_formatting_shortcodes:
+
+Formatting with Shortcodes
+==========================
+
+For basic formatting, like emphasis, you should use the standard Markdown style formatting tags
+descried in :ref:`docs_usage_basics_emphasis` whenever possible.
+
+For additional formatting options, you can use shortcodes. Shortcodes is a form of in-line codes
+that wrap the section of text to be formatted. Shortcodes can be nested to apply multiple formats
+to the same piece of text.
+
+These shortcodes are intended for special formatting cases, or more complex cases that cannot be
+solved with simple Markdown-like formatting codes. Available shortcodes are listed below.
+
+.. csv-table:: Shortcodes Formats
+   :header: "Syntax", "Description"
+   :widths: 40, 60
+   :class: "tight-table"
+
+   "``[b]text[/b]``",     "Text is displayed as bold text."
+   "``[i]text[/i]``",     "Text is displayed as italicised text."
+   "``[s]text[/s]``",     "Text is displayed as strike through text."
+   "``[u]text[/u]``",     "Text is displayed as underlined text."
+   "``[m]text[/m]``",     "Text is displayed as highlighted text."
+   "``[sup]text[/sup]``", "Text is displayed as superscript text."
+   "``[sub]text[/sub]``", "Text is displayed as subscript text."
+   "``[footnote:key]``",  "A reference to a :ref:`footnote comment <docs_usage_comments_footnotes>`."
+
+Unlike Markdown style codes, these can be used anywhere within a paragraph. Even in the middle of a
+word if you need to. You can also freely combine them to form more complex formatting.
+
+The shortcodes are available from the **Format** menu and in the editor toolbar, which can be
+activated by clicking the left-most icon button in the editor header.
+
+.. note::
+
+   Shortcodes are not processed until you generate a preview or generate a manuscript document. So
+   there is no highlighting of the text between the formatting markers. There is also no check that
+   your markers make sense. You must ensure that you have both the opening and closing formatting
+   markers where you want them.
+
+.. versionadded:: 2.2
+
+
+.. _docs_usage_formatting_breaks:
+
+Vertical Space and Page Breaks
+==============================
+
+You can apply page breaks to partition, chapter and scene headings for novel documents from the
+**Manuscript Build** tool. If you need to add a page break or additional vertical spacing in other
+places, there are special codes available for this purpose.
+
+Adding more than one line break between paragraphs will **not** increase the space between those
+paragraphs when generating a manuscript document. To add additional space between paragraphs, add
+the text ``[vspace]`` on a line of its own, and the **Manuscript Build** tool will insert a blank
+paragraph in its place.
+
+If you need multiple blank paragraphs just add a colon and a number to the above code. For
+instance, writing ``[vspace:3]`` will insert three blank paragraphs.
+
+If you need to add a page break somewhere, put the text ``[new page]`` on a line by itself before
+the text you wish to start on a new page.
+
+.. note::
+
+   The page break code is applied to the text that follows it. It adds a "page break before" mark
+   to the text when exporting to HTML or Open Document. This means that a ``[new page]`` code which
+   has no text following it will not result in a page break.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   This is a text paragraph.
+
+   [vspace:2]
+
+   This is another text paragraph, but there will be two empty paragraphs
+   between them.
+
+   [new page]
+
+   This text will start on a new page if the build format supports pages.
+
+
+.. _docs_usage_formatting_counts:
+
+Inserting Word Counts in the Text
+=================================
+
+The cover page of a manuscript normally has the word count stated on it. Any statistics value
+collected by novelWriter can be inserted into any document using a special shortcode. You can
+insert the code for any of the available statistics values from the **Insert** menu under
+**Word/Character Count**.
+
+The value inserted is the actual count for your entire manuscript, so it is not populated until you
+run the **Manuscript Build** tool. Until then they will show up as "0" in the viewer panel.
+
+The available codes are:
+
+.. csv-table:: Stats Shortcodes
+   :header: "Code", "Description"
+   :class: "tight-table"
+
+   "``[field:allChars]``",       "Characters"
+   "``[field:textChars]``",      "Characters in Text"
+   "``[field:titleChars]``",     "Characters in Headings"
+   "``[field:paragraphCount]``", "Paragraphs"
+   "``[field:titleCount]``",     "Headings"
+   "``[field:allWordChars]``",   "Characters, No Spaces"
+   "``[field:textWordChars]``",  "Characters in Text, No Spaces"
+   "``[field:titleWordChars]``", "Characters in Headings, No Spaces"
+   "``[field:allWords]``",       "Words"
+   "``[field:textWords]``",      "Words in Text"
+   "``[field:titleWords]``",     "Words in Headings"
+
+:bdg-info:`Example`
+
+This is an example cover page. A similar page is automatically generated when you create a new
+project.
+
+.. code-block:: md
+
+   Jane Smith[br]
+   42 Main Street[br]
+   1234 Capital City <<
+
+   [vspace:5]
+
+   #! Example
+
+   >> **By Jane Smith** <<
+
+   >> Word Count: [field:textWords] <<

docs/source/usage/alignment_and_indent.rst

@@ -0,0 +1,78 @@
+.. _docs_usage_align_indent:
+
+*************************
+Alignment and Indentation
+*************************
+
+The Markdown standard doesn't have commands for aligning text, so novelWriter adds its own syntax
+for this. It also has syntax for indentation, which is similar to Markdown block quotes.
+
+
+Paragraph Alignment and Indentation
+===================================
+
+All documents have the text by default aligned to the left or justified, depending on your setting
+in **Preferences**.
+
+You can override the default text alignment on individual paragraphs by specifying alignment tags.
+These tags are double angle brackets. Either ``>>`` or ``<<``. You put them either before or after
+the paragraph, and they will "push" the text towards the edge the brackets point towards. This
+should be fairly intuitive.
+
+Indentation uses a similar syntax. But here you use a single ``>`` or ``<`` to "push" the text away
+from the edge.
+
+:bdg-info:`Example`
+
+.. csv-table:: Text Alignment and Indentation
+   :header: "Syntax", "Description"
+   :widths: 40, 60
+   :class: "tight-table"
+
+   "``>> Right aligned text``",        "The text paragraph is right-aligned."
+   "``Left aligned text <<``",         "The text paragraph is left-aligned."
+   "``>> Centred text <<``",           "The text paragraph is centred."
+   "``> Left indented text``",         "The text has an increased left margin."
+   "``Right indented text <``",        "The text has an increased right margin."
+   "``> Left/right indented text <``", "The text has both margins increased."
+
+.. note::
+
+   The text editor will not show the alignment and indentation live. But the viewer will show them
+   when you open the document there. It will of course also be reflected in the document generated
+   from the **Manuscript Build** tool as long as the format supports paragraph alignment.
+
+
+Alignment with Line Breaks
+==========================
+
+If you have line breaks in the paragraph, the markers for all the lines are combined and used for
+the entire paragraph. For the following text, all lines will be centred:
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   >> I am the very model of a modern Major-General
+   I've information vegetable, animal, and mineral
+   I know the kings of England, and I quote the fights historical
+   From Marathon to Waterloo, in order categorical <<
+
+
+Alignment with First Line Indent
+================================
+
+If you have first line indent enabled in your manuscript build settings, you probably want to
+disable it for text in verses. Adding any alignment tags will cause the first line indent to be
+switched off for that paragraph.
+
+:bdg-info:`Example`
+
+The following text will always be aligned against the left margin:
+
+.. code-block:: md
+
+   I am the very model of a modern Major-General <<
+   I've information vegetable, animal, and mineral
+   I know the kings of England, and I quote the fights historical
+   From Marathon to Waterloo, in order categorical

docs/source/usage/basic_formatting.rst

@@ -0,0 +1,95 @@
+.. _docs_usage_basics:
+
+****************
+Basic Formatting
+****************
+
+.. _Markdown: https://en.wikipedia.org/wiki/Markdown
+
+The basic text formatting syntax of novelWriter is based on Markdown_. It is only a subset of the
+Markdown syntax though. Lists, images, and links are not supported.
+
+That said, URLs in the text should automatically be highlighted and become clickable. However, only
+URLs starting with "http" or "https" are recognised. In the editor, you must hold down the
+:kbd:`Ctrl` key when clicking a URL to follow it.
+
+
+.. _docs_usage_basics_paragraphs:
+
+Text Paragraphs
+===============
+
+A text paragraph is indicated by a blank line. That is, you need two line breaks to separate two
+fragments of text into two paragraphs. Single line breaks are treated as line breaks within a
+paragraph.
+
+It is important that you actually follow this rule. You should not, for instance, mimic indented
+paragraphs manually in the editor. This, and a lot of other formatting options that can be
+applied to text paragraphs in the :ref:`Manuscript Tool <docs_ui_manuscript>` depend on paragraphs
+being separated by blank lines.
+
+:bdg-success:`Correct`
+
+.. code-block:: md
+
+   ### Scene
+
+   This is a text paragraph.
+
+   This is another text paragraph.
+
+:bdg-danger:`Incorrect`
+
+.. code-block:: md
+
+   ### Scene
+
+   This is a text paragraph.
+       This is meant to be another text paragraph.
+
+If you do as shown in the "Incorrect" example, novelWriter will understand this as a single
+paragraph with two lines.
+
+
+.. _docs_usage_basics_emphasis:
+
+Text Emphasis with Markdown
+===========================
+
+A minimal set of Markdown text emphasis styles are supported for text paragraphs.
+
+``_text_``
+   The text is rendered as emphasised text (italicised).
+
+``**text**``
+   The text is rendered as strongly emphasised text (bold).
+
+``~~text~~``
+   Strike through text.
+
+In Markdown guides it is often recommended to differentiate between strong emphasis and emphasis
+by using ``**`` for strong and ``_`` for emphasis, although Markdown generally also supports ``__``
+for strong and ``*`` for emphasis. However, since the differentiation makes the highlighting and
+conversion significantly simpler and faster, in novelWriter this is a rule, not just a
+recommendation.
+
+In addition, the following rules apply:
+
+1. The emphasis and strike through formatting tags do not allow spaces between the words and the
+   tag itself. That is, ``**text**`` is valid, ``**text **`` is not.
+2. More generally, the delimiters must be on the outer edge of words. That is, ``some **text in
+   bold** here`` is valid, ``some** text in bold** here`` is not.
+3. If using both ``**`` and ``_`` to wrap the same text, the underscore must be the **inner**
+   wrapper. This is due to the underscore also being a valid word character, so if they are on the
+   outside, they violate rule 2.
+4. Text emphasis does not span past line breaks. If you need to add emphasis to multiple lines or
+   paragraphs, you must apply it to each of them in turn.
+5. Text emphasis can only be used in comments and paragraphs. Headings and meta data tags don't
+   allow for formatting, and any formatting markup will be displayed as-is.
+
+.. tip::
+
+   novelWriter supports standard escape syntax for the emphasis markup characters in case the
+   editor misunderstands your intended usage of them. That is, ``\*``, ``\_`` and ``\~`` will
+   generate a plain ``*``, ``_`` and ``~``, respectively, without interpreting them as part of the
+   markup.

docs/source/usage/chapters_and_scenes.rst

@@ -0,0 +1,96 @@
+.. _docs_usage_headings:
+
+*******************
+Chapters and Scenes
+*******************
+
+.. _Markdown: https://en.wikipedia.org/wiki/Markdown
+
+Since novelWriter uses a plain text format, the structure of your novel must follow a certain set
+of simple rules. For documents in a **Novel** type root folder, it is the heading that determines
+if the document is a chapter or a scene.
+
+The formatting of headings is based on Markdown_. A heading is indicated by a line starting with
+one or more ``#`` characters. It accepts up to four of these. You can use multiple headings in the
+same document, but it is the first heading that determines which icon and information is displayed
+in the project tree.
+
+.. note::
+
+   You can use the same heading levels for your notes in the other root folders, but they aren't
+   treated as chapters or scenes, so there you are free to use them as you want.
+
+
+.. _docs_usage_headings_levels:
+
+Heading Levels
+==============
+
+.. figure:: images/fig_heading_levels.png
+
+   An illustration of how heading levels correspond to the novel structure.
+
+Four levels of headings are understood for novel documents. You can pick and choose from these as
+you want, but if your story has chapters, you should use these headings to indicate them. If you
+also add scene headings, you have better control of how your scene separators are formatted in your
+manuscript. The chapter and scenes headings are also displayed in the
+:ref:`Novel View <docs_ui_main_novel>` and :ref:`Outline View <docs_ui_main_outline>`.
+
+``# Title Text``
+   This is a heading level one. This heading indicates the start of a new partition. Partitions are
+   for when you want to split your story into "Part 1", "Part 2", etc. You can also choose to use
+   them for splitting the text up into acts, and then hide these headings in your manuscript so
+   that they are not included in the output.
+
+``## Chapter Title``
+   This is a heading level two. This heading indicates the start of a new chapter. Chapter numbers
+   can be inserted automatically when building the manuscript, so you don't have to do this in the
+   title. See :ref:`docs_ui_manuscript_head_numbers` for more details.
+
+``### Scene Title``
+   This is a heading level three. This heading indicates the start of a new scene. Scene numbers or
+   scene separators can be inserted automatically when building the manuscript, so you can use the
+   title field as a working title for your scenes if you wish, but you must provide a minimal
+   title.
+
+``#### Section Title``
+   This is a heading level four. This heading indicates the start of a new section. Section titles
+   can be replaced by separators or ignored completely when building the manuscript. The meaning of
+   a section is really whatever you want it to be. You can use it to split your scenes up into
+   chunks, or into separate documents.
+
+For headings level one through three, adding a ``!`` modifies the meaning of the heading. The
+alternative meaning of the heading is only relevant when you generate your manuscript, but you may
+want to keep the use cases in mind while writing.
+
+``#! Title Text``
+   This tells the **Manuscript Build** tool that the level one heading is intended to be used for
+   the novel or notes folder's main title, like for instance the novel title on the cover page.
+   When building the manuscript, this will use a different styling of the title, which you can
+   modify independently from how partition titles are styled.
+   See :ref:`docs_usage_front_back_matter_title` for more details.
+
+``##! Chapter Title``
+   This tells the **Manuscript Build** tool to not assign a chapter number to this chapter title if
+   automatic chapter numbers are enabled. Such titles are useful for prologues and epilogues for
+   instance. See :ref:`docs_usage_front_back_matter_unnumbered` for more details.
+
+``###! Scene Title``
+   This is an alternative scene heading that can be formatted differently in the **Manuscript
+   Build** tool. It is intended for separating "soft" and "hard" scene breaks. Aside from this, it
+   behaves identically to a regular scene heading. See :ref:`docs_ui_manuscript_head_hard_soft`
+   for more details.
+
+The formatting of these headings can be customised quite extensively in the
+:ref:`Manuscript Tool <docs_ui_manuscript>`, which is covered in a separate part of the
+documentation.
+
+.. note::
+
+   The space after the ``#`` or ``!`` character is mandatory. The editor will change colour and
+   font size when the heading is correctly formatted.
+
+Page breaks can be automatically added before titles, partition, chapter and scene headings from
+the **Manuscript Build** tool when you build your project to a format that supports page breaks.
+If you want page breaks in other places, you have to specify them manually.
+See :ref:`docs_usage_formatting_breaks` for more details.

docs/source/usage/comments.rst

@@ -0,0 +1,164 @@
+.. _docs_usage_comments:
+
+******************
+Comments and Notes
+******************
+
+You can add comments to your text that are not a part of the story. Regular comments are intended
+for you to add notes to yourself inside the text, which may be useful when you revise your drafts.
+However, there are several types of comments you can use.
+
+This section covers the basic comment types. There are a couple of advanced features that use
+comment syntax too, but they are covered later.
+
+
+.. _docs_usage_comments_plain:
+
+Plain Comments
+==============
+
+A plain comment is a line or paragraph that starts with the character ``%`` as its first character.
+You can put them wherever you like in your documents, and you can choose to include or exclude them
+from your manuscript.
+
+For the most part, novelWriter completely ignores these comments. They are not included in your
+word or character counts either, and are only displayed in the document viewer panel if you enable
+them.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ### Scene
+
+   A regular text paragraph in the scene.
+
+   % A comment you've added for your own notes.
+
+   Another regular text paragraph in the scene.
+
+
+.. _docs_usage_comments_synopsis:
+
+Synopsis or Description Comments
+================================
+
+A special kind of comments are **Synopsis** and **Short Description** comments. They are different
+from plain comments in that they can be displayed alongside other information about a scene or a
+character or other story element described in a note. As with plain comments, they can be included
+in your manuscript, but they are formatted differently than plain comments.
+
+.. note::
+
+   A summary or description comment can be used once, and only once, for each heading as they are
+   considered a description of the content of the text under that heading. If you add two such
+   comments under the same heading, the last one will be used.
+
+
+Synopsis
+--------
+
+A **Synopsis** comment is intended for adding a summary of your chapters and scenes.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ### Scene
+
+   %Synopsis: A summary of the content of the scene.
+
+   The actual scene text.
+
+
+Short Description
+-----------------
+
+A **Short Description** comment behaves exactly the same as a synopsis comment, but is intended as
+a description of a story element, like a character.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   # Characters
+
+   ## Darth Vader
+
+   %Short: A Sith Lord that used to be a Jedi.
+
+   Your text about the character.
+
+   ## Luke Skywalker
+
+   %Short: A Jedi. The son of Darth Vader.
+
+   Your text about the character.
+
+.. note::
+
+   The ``%Synopsis:`` and ``%Short:`` comment prefixes are interchangeable, but when you include
+   them in the manuscript, they are labelled based on the prefix, so the latter may make more sense
+   for a Character note than the former.
+
+
+.. _docs_usage_comments_footnotes:
+
+Footnote Comments
+=================
+
+Footnotes are added with a shortcode, paired with a matching comment for the actual footnote text.
+The matching is done with a key that links the two. If you insert a footnote from the **Insert**
+menu, a unique key is generated for you. Shortcodes in general are covered in more detail in
+:ref:`docs_usage_formatting_shortcodes`.
+
+The insert footnote feature will add the footnote shortcode marker at the position of your cursor
+in the editor panel, and create the associated footnote comment right after the paragraph. It will
+then move the cursor there so you can immediately start typing the footnote text.
+
+The footnote comment can be anywhere in the document, so if you wish to move them to, say, the
+bottom of the text, you are free to do so.
+
+Footnote keys are only required to be unique within a document, so if you copy, move or merge text,
+you must make sure the keys are not duplicated. If you use the automatically generated keys from
+the **Insert** menu, they are unique among all indexed documents. They are not guaranteed to be
+unique against footnotes in the **Archive** or **Trash** folder though, but the chance of
+accidentally generating the same key twice in a project is relatively small.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ### Scene
+
+   This is a text paragraph with a footnote[footnote:fn1] in the middle.
+
+   %Footnote.fn1: This is the text of the footnote.
+
+.. versionadded:: 2.5
+
+
+.. _docs_usage_comments_ignored:
+
+Ignored Text
+============
+
+If you want to completely ignore some of the text in your documents, but are not ready to delete
+it, you can add ``%~`` before the text paragraph or line. This will cause novelWriter to skip the
+text entirely when generating previews or building manuscripts.
+
+This is a better way of removing text than converting them to regular comments, as you may want to
+include regular comments in your previews or draft manuscript.
+
+You can toggle the ignored text feature on and off for a paragraph by pressing :kbd:`Ctrl+Shift+D`
+on your keyboard with your cursor somewhere in the paragraph.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ### Scene
+
+   %~ This text is ignored.
+
+   This text is a regular paragraph.

docs/source/usage/front_back_matter.rst

@@ -0,0 +1,79 @@
+.. _docs_usage_front_back_matter:
+
+*********************
+Front and Back Matter
+*********************
+
+Front and back matter documents are documents that go before and after your main story text. They
+can include pages like your cover page, content tables, prologues, epilogues, etc. These special
+pages and sections are supported to some extent by novelWriter.
+
+
+.. _docs_usage_front_back_matter_title:
+
+The Title Page
+==============
+
+It is recommended that you add a document at the very top of each **Novel** root folder with the
+novel title in it. You should modify the level 1 heading format code with an ``!`` in order to
+render it as a document title that is excluded from any automatic Table of Content in a manuscript
+build document.
+
+You can also add the author name and address above this if this is required by the manuscript
+format you use, and additional space added before the title.
+
+:bdg-info:`Example`
+
+This is the title page novelWriter generates automatically for a new project as of version 2.6:
+
+.. code-block:: md
+
+   Jane Doe[br]
+   Address Line 1[br]
+   Address Line 2 <<
+
+   [vspace:5]
+
+   #! My Novel
+
+   >> **By Jane Doe** <<
+
+   >> Word Count: [field:textWords] <<
+
+The title is by default centred on the page. You can add more text to the page as you wish, like
+for instance the author's name and details.
+
+The default title page inserts the word count for text only, but you can add other counts too.
+See :ref:`docs_usage_formatting_counts` for more details.
+
+
+.. _docs_usage_front_back_matter_pages:
+
+Additional Pages
+================
+
+If you want an additional page of text after the title page, starting on a fresh page, you can add
+``[new page]`` on a line by itself, and continue the text after it. This will insert a page break
+before the text. See :ref:`docs_usage_formatting_breaks` for more details.
+
+
+.. _docs_usage_front_back_matter_unnumbered:
+
+Unnumbered Chapters
+===================
+
+If you use the automatic numbering feature for your chapters, but you want to keep some special
+chapters separate from this, you can add an ``!`` to the level 2 heading formatting code to tell
+the build tool to skip these chapters when adding numbers.
+
+Unnumbered chapters are useful for prologue and epilogue chapters, and also for interlude chapters
+if you use those in your text. There is a separate formatting feature for such chapter titles in
+the **Manuscript Build** tool. See the :ref:`docs_ui_manuscript` page for more details.
+
+:bdg-info:`Example`
+
+.. code-block:: md
+
+   ##! Unnumbered Chapter Title
+
+   Chapter Text

docs/source/usage/howto.rst

@@ -1,4 +1,4 @@
-.. _a_howto:
+.. _docs_usage_howto:
 
 *************
 Tips & Tricks
@@ -16,7 +16,7 @@ This is a list of hopefully helpful little tips on how to get the most out of no
 Managing the Project
 ====================
 
-.. dropdown:: Create a Project from a Template
+.. dropdown:: How do I create a project from a template?
    :animate: fade-in-slide-down
 
    On the Welcome dialog's **Create New Project** form, you can select to "Prefill Project" from
@@ -24,7 +24,7 @@ Managing the Project
    dedicated to be a template project. If you have a structure and settings you want to use for
    every new project, this is the best solution.
 
-.. dropdown:: Merge Multiple Documents Into One
+.. dropdown:: How do I merge multiple documents into one?
    :animate: fade-in-slide-down
 
    If you need to merge a selection of documents in your project into a single document, you can
@@ -33,30 +33,20 @@ Managing the Project
    and :guilabel:`Merge Documents in Folder`.
 
    In the dialog that pops up, the documents will be in the same order as in the folder, but you
-   can rearrange them here of you wish. See :ref:`a_ui_tree_split_merge` for more details.
+   can rearrange them here of you wish. See :ref:`docs_ui_split_merge` for more details.
+
+.. dropdown:: How do I share status or importance labels between projects?
+   :animate: fade-in-slide-down
+
+   The status or importance labels you have defined in a project can be exported from **Project
+   Settings** from the respective configuration tabs. You can then import these labels in another
+   project.
 
 
 Layout Tricks
 =============
 
-.. dropdown:: Align Paragraphs with Line Breaks
-   :animate: fade-in-slide-down
-
-   If you have line breaks in you paragraphs, and also want to apply additional text alignment or
-   indentation, you must apply the alignment tags to the first line.
-
-   For example, this will centre the two lines.
-
-   .. code-block:: md
-
-      >> Line one is centred. <<
-      Line two is also centred.
-
-      This text is not centred, because it is a new paragraph.
-
-   See :ref:`a_fmt_align` for more details.
-
-.. dropdown:: Create a Simple Table
+.. dropdown:: How do I create a table?
    :animate: fade-in-slide-down
 
    The formatting tools available in novelWriter don't allow for complex structures like tables.
@@ -69,20 +59,30 @@ Layout Tricks
    This is most suitable for your notes, as the result in exported documents cannot be guaranteed
    to match. Especially if you don't use the same font in your manuscript as in the editor.
 
-.. dropdown:: Turn Off First Line Indent for a Paragraph
+.. dropdown:: How do I force a line break when line breaks are ignored in my manuscript?
+   :animate: fade-in-slide-down
+
+   In the **Manuscript Build Settings** you can choose to ignore line breaks within paragraphs in
+   your text. However, some times you still need those breaks. Like for instance on the cover page
+   where you may need to add your name and address. In such cases, you can add ``[br]`` where you
+   want line breaks. These breaks cannot be ignored by any settings and will always be respected.
+
+   .. versionadded:: 2.6
+
+.. dropdown:: How do I turn off first line indent for a specific paragraph?
    :animate: fade-in-slide-down
 
    If you have first line indent enabled, but have a specific paragraph that you don't want
-   indented, you can disable the indentation by explicitly add text alignment. Aligned paragraphs
-   are not indented. For instance by adding ``<<`` to the end to left-align it,
+   indented, you can disable the indentation by explicitly adding text alignment. For instance by
+   adding ``<<`` to the end to left-align it. Aligned paragraphs are not indented.
 
-   See :ref:`a_fmt_align` for more details.
+   See :ref:`docs_usage_align_indent` for more details.
 
 
 Organising Your Text
 ====================
 
-.. dropdown:: Add Introductory Text to Chapters
+.. dropdown:: How do I add introductory text to chapters?
    :animate: fade-in-slide-down
 
    Sometimes chapters have a short preface, like a brief piece of text or a quote to set the stage
@@ -92,7 +92,7 @@ Organising Your Text
    such text. Separating chapter and scene files also allows you to make scene files child
    documents of the chapter.
 
-.. dropdown:: Distinguishing Soft and Hard Scene Breaks
+.. dropdown:: How do I distinguishing between soft and hard scene breaks?
    :animate: fade-in-slide-down
 
    Depending on your writing style, you may need to separate between soft and hard scene breaks
@@ -101,8 +101,8 @@ Organising Your Text
    In such cases you may want to use different scene headings for hard and soft scene breaks. The
    **Build Manuscript** tool will let you define a different format for scenes using the ``###``
    and ``###!`` heading codes when you generate your manuscript. You can for instance add the
-   common "``* * *``" for hard breaks and select to soft scene breaks, which will just insert an
-   empty paragraph in their place. See :ref:`a_manuscript_settings` for more details.
+   common "``* * *``" for hard breaks and select to hide soft scene breaks, which will just insert
+   an empty paragraph in their place. See :ref:`docs_ui_manuscript_settings` for more details.
 
    .. versionadded:: 2.4
 
@@ -110,7 +110,7 @@ Organising Your Text
 Other Tools
 ===========
 
-.. dropdown:: Convert Project to/from yWriter Format
+.. dropdown:: How do I convert my project to/from the yWriter format?
    :animate: fade-in-slide-down
 
    There is a tool available that lets you convert a `yWriter <http://spacejock.com/yWriter7.html>`_

docs/source/usage/introduction.rst

@@ -0,0 +1,57 @@
+.. _docs_usage:
+
+************
+Introduction
+************
+
+.. _Markdown: https://en.wikipedia.org/wiki/Markdown
+
+In a nutshell, novelWriter is a plain text editor that lets you organise one or more novels and
+associated notes as many smaller documents. You can at any time generate standard document formats
+from these plain text documents. Whether it is an outline of your story, a draft, a complete
+manuscript, or even a collection of your character notes or other notes.
+
+
+Why Plain Text?
+===============
+
+The idea is to let you be creative without having to deal with formatting while you are writing, or
+be distracted by it.
+
+Of course, you probably need *some* form of minimal formatting for your text. At the very least you
+need emphasis. Most people are familiar with adding emphasis using ``_underscores_`` and
+``**asterisks**``. This formatting standard comes from Markdown_ and is supported by novelWriter.
+It also uses Markdown formatting for defining document headings, which is how you distinguish
+between chapters and scenes.
+
+For those special cases where you need more complex formatting, a set of shortcodes are available.
+To make these codes easier to use, a dropdown button bar is available in the editor panel with
+standard format buttons. So don't worry. You don't have to learn any of these codes.
+
+
+Adding Meta Data
+================
+
+In addition to the body text of your story, novelWriter allows you to enter some additional meta
+data into your text documents to indicate things like which characters are present in a chapter or
+scene, whose point of view we're seeing, what location the events take place in, and so on.
+
+Since the editor is plain text, this is done on special lines of text starting with an ``@``
+character. The editor will show an auto-complete menu to help you write these lines. We will talk
+more about this later.
+
+You can also add your own author's comments in your text, without these comments becoming a part of
+the story itself. A comment line starts with a ``%`` character. There are different types of
+comments, and an auto-complete menu can help you here too. More about this later as well.
+
+.. admonition:: Limitations
+
+   Please keep in mind that novelWriter is designed for writing fiction, so the formatting features
+   available are limited to those relevant for this purpose. It is *not* suitable for technical
+   writing. It is also *not* a full-featured Markdown editor.
+
+   In addition, novelWriter is not intended as a tool for organising research for writing, and
+   therefore lacks formatting features you may need for this purpose. The notes feature in is
+   mainly intended for character profiles and plot outlines. It is recommended to use a proper
+   note-taking tool for research. This is anyway more practical as you may use the same research
+   for multiple projects.

docs/source/usage/organising_project.rst

@@ -0,0 +1,202 @@
+.. _docs_usage_project:
+
+***********************
+Organising Your Project
+***********************
+
+Your project is organised into a set of top level folders called "Root Folders", which each have
+specific meaning in the project. Your project documents and notes are stored under these root
+folders. All the content of your project is available in the **Project Content** panel on the left
+side of the main window.
+
+.. figure:: images/fig_project_tree.png
+
+   The **Project Content** tree populated with example documents.
+
+Each line in the project tree shows the name of each item, its word count (or alternatively
+character count), an icon for :ref:`docs_usage_project_active`, and a custom icon for
+:ref:`docs_usage_project_status` of each item. These latter two are covered alter in this section.
+
+You can add, view and edit documents in the project tree by right-clicking on them. Some features
+are also located in the buttons along the top, next to the **Project Content** label.
+
+
+.. _docs_usage_project_roots:
+
+How Root Folders Work
+=====================
+
+Projects are structured into a set of top level folders called "Root Folders". They are visible in
+the project tree at the left side of the main window. Each type of root folder has a distinct icon.
+
+The documents that make up your story go into a root folder of type **Novel**. Your notes go into
+the other root folders. These other root folder types are separated into types depending on what
+kind of notes go into them. This is not only for organisation. It also matters to how you can
+reference these notes later. We will come back to this in the :ref:`docs_usage_tags_refs` section.
+
+A new project may not have all of the root folders present, but you can add the ones you want from
+the project tree tool bar.
+
+The intended usage of each type of root folder is listed below. However, aside from the **Novel**
+folder, no restrictions are applied by novelWriter on what you put in them. You can use them
+however you want.
+
+
+Root Folder Types
+-----------------
+
+**Novel** (Story)
+   This is where you put the documents that are part of your story. You can create multiple Novel
+   folders if you wish, but various parts of the application assumes each Novel folder belong to
+   one novel.
+
+   The Novel folder is somewhat special in that it can contain documents for chapters, scenes and
+   story partitions. How this is indicated is covered in the section :ref:`docs_usage_headings`.
+
+**Plot** (Notes)
+   This is where you can keep notes and outlines of your story plots. Such notes can be
+   particularly useful if you have outlines for sub plot. You can make references to these subplots
+   from the scene documents, which makes it easier to track story progress.
+
+**Characters** (Notes)
+   Character notes go in this root folder type. For your main characters, you may want to make one
+   document for each character. For smaller characters you can put multiple into the same document.
+   In your chapters and scenes you can reference these character notes as point-of-view or focus
+   characters.
+
+**Locations** (Notes)
+   The locations where your story takes place can be documented here. This, together with Plot and
+   Characters are the key story elements to track, and to reference from your chapter and scene
+   documents.
+
+**Timeline** (Notes)
+   If the story has multiple plot timelines or jumps in time within the same plot, this folder type
+   can be used to track this.
+
+**Objects** (Notes)
+   Important objects in the story, for instance physical objects that change hands often, can be
+   tracked here.
+
+**Entities** (Notes)
+   Does your plot have many powerful organisations or companies? Or other entities that are part of
+   the plot? They can be organised here.
+
+**Custom** (Notes)
+   The custom root folder type can be used for tracking anything else not covered by the above
+   options.
+
+**Templates**
+   Any document added under this root folder will be made available as template options when
+   creating new documents. See :ref:`docs_usage_project_documents_templates` for more details.
+
+**Archive**
+   If you don't want to delete a document, or put it in the **Trash** folder where it may be
+   deleted, but still want it out of your main project, you can put it in this folder. The contents
+   of the document will be ignored by the scanner that looks for tags, and it will be ignored in
+   any outline view and in your manuscript.
+
+**Trash**
+   This folder behaves like you expect. Anything dropped in here can be deleted permanently from
+   the project, and the content doesn't show up anywhere else in novelWriter.
+
+The root folder types are closely tied to the tags and reference system. Each folder type for novel
+and notes corresponds to one or more categories of tags that can be used to reference the content
+in them. See :ref:`docs_usage_tags_refs` for more details.
+
+.. tip::
+
+   The root folders have standard names, but you can rename them to whatever you want.
+
+
+.. _docs_usage_project_folders:
+
+Regular Folders
+===============
+
+You can add regular folders anywhere you want in the project. The folders are there purely as a way
+for you to organise the documents in meaningful sections and to be able to collapse and hide them
+in the project tree when you're not working on those documents.
+
+When novelWriter is processing the documents in a project, like for instance when you create a
+manuscript from it, these folders are ignored. Only the order of the documents themselves matter.
+
+
+.. _docs_usage_project_documents:
+
+Documents
+=========
+
+You can add documents anywhere you want in your project structure. You can even add documents as
+child items of other documents, just as if they were folders. This makes it easy to associate a set
+of scenes with their chapter. You can also do this in your notes, where you for instance may have a
+hierarchy of your locations.
+
+The name on a document in the project tree is not linked to any headings in the document text.
+Think of the document name as a file name. You can rename a document, or any other item in the
+project, at any time.
+
+Documents come in two types:
+
+**Novel Documents**
+   These are the documents that make up your story or novel. They can only be added under a root
+   folder of type **Novel**. You can technically also add them under **Archive**. See
+   :ref:`docs_usage_headings` for more details on how these documents are handled by novelWriter.
+
+**Project Notes**
+   These are the documents where you keep your notes. You can add them anywhere in your project,
+   including under **Novel** type folders. If you do add them there, they are not treated as a part
+   of the story by default.
+
+You can convert between the two types of documents where both types are allowed. You can also
+convert folders into documents, which may sometimes be convenient too.
+
+Another convenient feature is that documents can be split into sub-documents by its headings, or
+multiple documents merged into one. This is particularly useful if you start out with larger
+structural documents, like one containing all chapters and scenes in an act, and then split those
+when you start writing. See :ref:`docs_ui_split_merge` for more details.
+
+
+.. _docs_usage_project_documents_templates:
+
+Document Templates
+------------------
+
+If you wish to create template documents to be used when creating new documents, like for instance
+a character note template, you can add a **Templates** root folder to your project. Any document
+added to this root folder will show up in the **Add Item** menu in the project tree toolbar. When
+selected, a new document is created with its content copied from the chosen template.
+
+.. versionadded:: 2.3
+
+
+.. _docs_usage_project_active:
+
+Active and Inactive Documents
+=============================
+
+A document can be set as "Active" or "Inactive", which alters the icon in the third column of the
+project tree. These are mostly intended for your convenience as they will indicate whether the
+document is meant to be included in the manuscript or not. You can think of an inactive status as a
+whole-document out-take. It allows you to take it out without moving it to **Archive**.
+
+Inactive documents are by default excluded from your manuscript, but you can override this if you
+wish. See :ref:`docs_ui_manuscript_selection` for more details.
+
+
+.. _docs_usage_project_status:
+
+Importance and Status
+=====================
+
+Each document or folder in your project can have either a "Status" or "Importance" label set. These
+are labels and icons that you control and define yourself, and novelWriter doesn't use them for
+anything. You can modify these labels in **Project Settings**.
+See :ref:`docs_ui_projects_settings_status` for more details.
+
+The "Status" labels are intended to tag a novel document as for instance a draft or as completed,
+and the "Importance" labels are intended to tag character notes, or other project notes, as for
+instance a main, major, or minor character or story element.
+
+Whether a document uses a "Status" or "Importance" label depends on which root folder it lives in.
+If it's in a **Novel** type folder, it uses the "Status" label, otherwise it uses an "Importance"
+label.

docs/source/usage/tags_and_references.rst

@@ -0,0 +1,231 @@
+.. _docs_usage_tags_refs:
+
+*******************
+Tags and References
+*******************
+
+One of the core features of novelWriter is its **Tags and References** system. This is perhaps one
+of the features that makes novelWriter different from other similar applications. It is therefore
+not always obvious to new users how this is supposed to work.
+
+In novelWriter there are no forms or tables to fill in to define characters, locations or other
+elements of your story. Instead, you create documents in one of the root folders for notes. Within
+these documents you can set **tags**, like for instance for your main character. If you then want
+to annotate a scene with this character as its point-of-view, you create a **reference** to the
+tag.
+
+.. tip::
+
+   If you find the Tags and Reference system difficult to follow just from reading this chapter,
+   you can create a new project in the **Welcome** dialog's New Project form and select "Create an
+   example project" from the "Pre-fill project" option. The example project contains several
+   examples of tags and references.
+
+
+.. _docs_usage_tags_refs_tags:
+
+How to Use Tags
+===============
+
+The structure of your novelWriter project is inferred from the headings within the documents, not
+the documents themselves. See :ref:`docs_usage_headings` for more details. Therefore, metadata is
+also associated with headings, and not the documents themselves.
+
+A "tag" in novelWriter is a word or phrase that you define as belonging to a heading. Tags are set
+by using the ``@tag`` keyword.
+
+The basic format of a tag is ``@tag: TagName``.
+
+An alternative format of a tag is ``@tag: TagName | Display Name``.
+
+``tagName`` (Required)
+   This is a unique identifier of your choosing. It is the value you use later for making
+   references back to the heading in the document. The tag must be unique.
+
+``Display Name`` (Optional)
+   This is an optional display name used for the tag. When you build your manuscript, you can for
+   instance insert the point-of-view character name directly into chapter titles. By default, the
+   ``tagName`` value is used in such headings, but if you use a shortened format internally in your
+   project, you can use the display name to specify a more suitable format for your chapter title.
+
+.. note::
+
+   You can only set **one** tag per heading, and the tag has to be unique across **all** documents
+   in the project.
+
+After a tag has been defined, it can be referenced in novel documents, or cross-referenced in other
+notes. Tags will also show up in the **Outline View** and in the **References** panel under the
+document viewer when a document is open in the viewer. See :ref:`docs_ui_main_outline` and
+:ref:`docs_ui_edit_view_view_references` for more details.
+
+The editor will indicate to you that the keyword is correctly used and that the tag is allowed,
+that is, the tag is unique, by adding a colour highlighting to it. An invalid tag should have a
+wiggly line under it, and will not receive the colour that valid tags do.
+
+The tag is the only part of notes that novelWriter uses. The rest of the document content is there
+for you to use in whatever way you wish.
+
+.. versionadded:: 2.2
+
+   Tags are no longer case sensitive. The tags are by default displayed with the capitalisation you
+   use when defining the tag, but you don't have to use the same capitalisation when referencing
+   it later.
+
+.. versionadded:: 2.3
+
+   Tags can have an optional display name for manuscript builds.
+
+.. versionadded:: 2.6
+
+   You can now add tags also to Novel Documents. These can be used for cross-referencing between
+   chapters and scenes, and also from notes if desired.
+
+:bdg-info:`Example`
+
+Example of a note document for a character with a tag set:
+
+.. code-block:: md
+
+   # Character: Jane Doe
+
+   @tag: Jane | Jane Doe
+
+   Some information about the character Jane Doe.
+
+When this is done in a document in a root folder of type **Characters**, the tag is automatically
+treated as an available character in your project with the value "Jane". You will then be able to
+reference "Jane" in any of your other documents using the reference keywords for characters.
+
+The character "Jane" will also show up in the **Character** tab in the **Reference** panel below
+the document viewer.
+
+.. note::
+
+   It is the root folder type that defines what category of story elements the tag is indexed
+   under. See :ref:`docs_usage_project_roots` for more details.
+
+
+.. _docs_usage_tags_refs_refs:
+
+How to Use References
+=====================
+
+Each heading of any level in your project can contain references to tags set in your notes. The
+references are gathered by the project index and used to generate the **Outline View**, among other
+things.
+
+References are set with a special keyword, with a list of corresponding tags. The valid keywords
+are listed below. The format of a reference line is ``@keyword: value1, [value2] ... [valueN]``.
+All reference keywords allow multiple values.
+
+``@pov``
+   The point-of-view character for the current section. The target must be a note tag in a
+   **Character** type root folder.
+
+``@focus``
+   The character that has the focus for the current section. This can be used in cases where the
+   focus is not the point-of-view character. The target must be a note tag in a **Character** type
+   root folder.
+
+``@char``
+   For other characters in the current section. The target must be a note tag in a **Character**
+   type root folder. This should not include the point-of-view or focus character if those
+   references are used.
+
+``@plot``
+   The plot or subplot advanced in the current section. The target must be a note tag in a **Plot**
+   type root folder.
+
+``@time``
+   The timelines touched by the current section. The target must be a note tag in a **Timeline**
+   type root folder.
+
+``@location``
+   The location the current section takes place in. The target must be a note tag in a
+   **Locations** type root folder.
+
+``@object``
+   Objects present in the current section. The target must be a note tag in a **Object** type root
+   folder.
+
+``@entity``
+   Entities present in the current section. The target must be a note tag in an **Entities** type
+   root folder.
+
+``@custom``
+   Custom references in the current section. The target must be a note tag in a **Custom** type
+   root folder. The custom folder are for any other category of notes you may want to use.
+
+``@mention``
+   For anything, anyone or anyplace mentioned, but not present in the current section. It is
+   intended for those cases where you reveal details about a character or place in a scene without
+   otherwise being a part of it. This can be useful when checking for consistency later. Any tag in
+   any root note folder can be listed under ``@mention``.
+
+``@story``
+   This is used when referencing a Novel Document, like a scene or chapter, from somewhere else in
+   your project. It is possible to also set tags in documents in a **Novel** type folder, and this
+   is the keyword you use to reference those.
+
+When tags and references are used correctly, it will be indicated by highlight colours in the
+editor.
+
+.. note::
+
+   The highlighter may be mistaken if the index of defined tags is out of date. If so, press
+   :kbd:`F9` to regenerate it, or select **Rebuild Index** from the **Tools** menu. In general, the
+   index for a document is regenerated when it is saved, so this shouldn't normally be necessary.
+
+.. tip::
+
+   If you add a reference in the editor to a tag that doesn't yet exist, you can right-click it and
+   select **Create Note for Tag**. This will generate a new note automatically in the correct type
+   of root folder, with the new tag defined.
+
+One note can also reference another note in the same way novel documents do. When the note is
+opened in the document viewer, the references become clickable links, making it easier to follow
+connections in the plot. You can follow links in the document editor by clicking them with the
+mouse while holding down the :kbd:`Ctrl` key. Clicked links are always opened in the view panel.
+
+Your notes don't show up in the **Outline View**, so referencing between notes is only meaningful
+if you want to be able to click-navigate between them, or of course if you just want to highlight
+that two notes are related.
+
+.. tip::
+
+   If you cross-reference between notes and export your project as an HTML document using the
+   **Manuscript Build** tool, the cross-references become clickable links in the exported HTML
+   document as well.
+
+:bdg-info:`Example`
+
+Example of a novel document with references to characters and plots:
+
+.. code-block:: md
+
+   ## Chapter 1
+
+   @pov: Jane
+
+   ### Scene 1
+
+   @char: John, Sam
+   @plot: Main
+
+   Once upon a time ...
+
+
+.. _docs_usage_tags_refs_completer:
+
+Auto-Completion in the Editor
+-----------------------------
+
+An auto-completer context menu will show up automatically in the document editor when you type the
+character ``@`` on a new line. It will first suggest tag or reference keywords for you to add, and
+after the ``:`` has been added, suggest references from the list of tags you have already defined.
+
+You can use the auto-completer to add multiple references with a ``,`` between them, and even type
+new ones. Notes for new references can be created by right-clicking on them and selecting **Create
+Note for Tag** from the menu.
+
+.. versionadded:: 2.2