Release 2.7 Beta 1 (#2308)

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

@@ -1,103 +0,0 @@
-name: Build
-
-on: workflow_dispatch
-
-jobs:
-  buildAssets:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Python Setup
-        uses: actions/setup-python@v4
-        with:
-          python-version: "3.11"
-          architecture: x64
-
-      - name: Install Packages (apt)
-        run: |
-          sudo apt update
-          sudo apt install qttools5-dev-tools latexmk texlive texlive-latex-extra
-
-      - name: Checkout Source
-        uses: actions/checkout@v3
-
-      - name: Install Packages (pip)
-        run: pip install -r docs/source/requirements.txt
-
-      - name: Build Assets
-        run: python pkgutils.py qtlrelease sample manual
-
-      - name: Upload Artifacts
-        uses: actions/upload-artifact@v3
-        with:
-          name: nw-assets
-          path: |
-            novelwriter/assets/sample.zip
-            novelwriter/assets/manual.pdf
-            novelwriter/assets/i18n/*.qm
-          if-no-files-found: error
-          retention-days: 1
-
-  buildLinux:
-    needs: buildAssets
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        python-version: ["3.11"]
-        linux-tag: ["manylinux_2_24_x86_64", "manylinux_2_28_x86_64"]
-    steps:
-      - name: Python Setup
-        uses: actions/setup-python@v4
-        with:
-          python-version: "3.11"
-          architecture: x64
-
-      - name: Install Packages (pip)
-        run: pip install python-appimage
-
-      - name: Checkout Source
-        uses: actions/checkout@v3
-
-      - name: Download Artifacts
-        uses: actions/download-artifact@v3
-        with:
-          name: nw-assets
-          path: novelwriter/assets
-
-      - name: Build AppImage
-        run: python pkgutils.py build-appimage --linux-tag ${{ matrix.linux-tag }} --python-version ${{ matrix.python-version }}
-
-      - name: Upload Artifacts
-        uses: actions/upload-artifact@v3
-        with:
-          name: novelWriter-Packages
-          path: |
-            dist_appimage/novelWriter*.AppImage
-            dist_appimage/novelWriter*.AppImage.sha256
-          if-no-files-found: error
-          retention-days: 1
-
-  buildMac:
-    needs: buildAssets
-    runs-on: macos-12
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Download Artifacts
-        uses: actions/download-artifact@v3
-        with:
-          name: nw-assets
-          path: novelwriter/assets
-
-      - name: Build App Bundle
-        run: ./setup/macos/build.sh
-
-      - name: Upload DMG
-        uses: actions/upload-artifact@v3
-        with:
-          name: novelWriter-Packages
-          path: |
-            dist_macos/novelWriter*.dmg
-            dist_macos/novelWriter*.dmg.sha256
-          if-no-files-found: error
-          retention-days: 1

.github/workflows/build_assets.yml

@@ -0,0 +1,39 @@
+name: BuildAssets
+
+on: workflow_call
+
+jobs:
+  buildAssets:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Python Setup
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+          architecture: x64
+
+      - name: Install Packages (apt)
+        run: |
+          sudo apt update
+          sudo apt install qttools5-dev-tools latexmk texlive texlive-latex-extra
+
+      - name: Checkout Source
+        uses: actions/checkout@v4
+
+      - name: Install Packages (pip)
+        run: pip install -U -r requirements.txt -r docs/requirements.txt
+
+      - name: Build Assets
+        run: |
+          python pkgutils.py build-assets
+
+      - name: Upload Artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: nw-assets
+          path: |
+            novelwriter/assets/manual*.pdf
+            novelwriter/assets/sample.zip
+            novelwriter/assets/i18n/*.qm
+          if-no-files-found: error
+          retention-days: 14

.github/workflows/build_linux.yml

@@ -0,0 +1,46 @@
+name: BuildLinux
+
+on: workflow_dispatch
+
+jobs:
+  buildAssets:
+    uses: ./.github/workflows/build_assets.yml
+
+  buildLinux-AppImage:
+    needs: buildAssets
+    runs-on: ubuntu-latest
+    env:
+      PYTHON_VERSION: "3.13"
+      LINUX_TAG: "manylinux_2_28_x86_64"
+    steps:
+      - name: Python Setup
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+          architecture: x64
+
+      - name: Install Packages (pip)
+        run: pip install python-appimage
+
+      - name: Checkout Source
+        uses: actions/checkout@v4
+
+      - name: Download Artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: nw-assets
+          path: novelwriter/assets
+
+      - name: Build AppImage
+        id: build
+        run: |
+          echo "BUILD_VERSION=$(python pkgutils.py version)" >> $GITHUB_OUTPUT
+          python pkgutils.py build-appimage --linux-tag $LINUX_TAG --python-version $PYTHON_VERSION
+
+      - name: Upload Artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: novelWriter-${{ steps.build.outputs.BUILD_VERSION }}-Linux-AppImage
+          path: dist_appimage/*.AppImage*
+          if-no-files-found: error
+          retention-days: 14

.github/workflows/build_mac.yml

@@ -0,0 +1,69 @@
+name: BuildMacOS
+
+on: workflow_dispatch
+
+jobs:
+  buildAssets:
+    uses: ./.github/workflows/build_assets.yml
+
+  buildMac-AMD64:
+    needs: buildAssets
+    runs-on: macos-latest
+    env:
+      PYTHON_VERSION: "3.13"
+      PACKAGE_ARCH: x86_64
+      MINICONDA_ARCH: x86_64
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Download Artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: nw-assets
+          path: novelwriter/assets
+
+      - name: Build App Bundle
+        id: build
+        run: |
+          echo "BUILD_VERSION=$(python pkgutils.py version)" >> $GITHUB_OUTPUT
+          ./setup/macos/build.sh $PYTHON_VERSION $PACKAGE_ARCH $MINICONDA_ARCH
+
+      - name: Upload DMG
+        uses: actions/upload-artifact@v4
+        with:
+          name: novelWriter-${{ steps.build.outputs.BUILD_VERSION }}-MacOS-AMD64-DMG
+          path: dist_macos/*.dmg*
+          if-no-files-found: error
+          retention-days: 14
+
+  buildMac-M1:
+    needs: buildAssets
+    runs-on: macos-latest
+    env:
+      PYTHON_VERSION: "3.13"
+      PACKAGE_ARCH: aarch64
+      MINICONDA_ARCH: arm64
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Download Artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: nw-assets
+          path: novelwriter/assets
+
+      - name: Build App Bundle
+        id: build
+        run: |
+          echo "BUILD_VERSION=$(python pkgutils.py version)" >> $GITHUB_OUTPUT
+          ./setup/macos/build.sh $PYTHON_VERSION $PACKAGE_ARCH $MINICONDA_ARCH
+
+      - name: Upload DMG
+        uses: actions/upload-artifact@v4
+        with:
+          name: novelWriter-${{ steps.build.outputs.BUILD_VERSION }}-MacOS-M1-DMG
+          path: dist_macos/*.dmg*
+          if-no-files-found: error
+          retention-days: 14

.github/workflows/build_win.yml

@@ -0,0 +1,62 @@
+name: BuildWindows
+
+on: workflow_dispatch
+
+jobs:
+  buildAssets:
+    uses: ./.github/workflows/build_assets.yml
+
+  buildWin64:
+    needs: buildAssets
+    runs-on: windows-latest
+    steps:
+      - name: Python Setup
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+          architecture: x64
+
+      - name: Checkout Source
+        uses: actions/checkout@v4
+
+      - name: Download Assets
+        uses: actions/download-artifact@v4
+        with:
+          name: nw-assets
+          path: novelwriter/assets
+
+      - name: Build Setup Installer
+        id: build
+        run: |
+          echo "BUILD_VERSION=$(python pkgutils.py version)" >> $Env:GITHUB_OUTPUT
+          python pkgutils.py build-win-exe
+
+      - name: Upload Unsigned Artifacts
+        id: upload-unsigned-artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: novelWriter-${{ steps.build.outputs.BUILD_VERSION }}-Win-Setup
+          path: dist/*.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 "
+          github-artifact-id: "${{ steps.upload-unsigned-artifact.outputs.artifact-id }}"
+          wait-for-completion: true
+          output-artifact-directory: "dist/"
+          parameters: |
+            version: "${{ steps.build.outputs.BUILD_VERSION }}"
+
+      - name: Upload Signed Artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: novelWriter-${{ steps.build.outputs.BUILD_VERSION }}-Win-Setup-Signed
+          path: dist/*.exe
+          if-no-files-found: error
+          retention-days: 14

.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

@@ -0,0 +1,32 @@
+name: i18n
+
+on:
+  push:
+    branches:
+      - i18n/*
+
+jobs:
+  buildI18n:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Python Setup
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+          architecture: x64
+      - name: Install Packages (apt)
+        run: |
+          sudo apt update
+          sudo apt install qttools5-dev-tools
+      - name: Checkout Source
+        uses: actions/checkout@v4
+      - name: Build Assets
+        run: python pkgutils.py qtlrelease
+      - name: Upload Artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: nw-i18n
+          path: |
+            novelwriter/assets/i18n/*.qm
+          if-no-files-found: error
+          retention-days: 7

.github/workflows/syntax.yml

@@ -1,30 +1,37 @@
-name: Flake8
+name: Linting
 
 on:
   push:
     branches:
       - main
-      - dev
+      - release
   pull_request:
     branches:
       - main
-      - dev
+      - release
 
 jobs:
   checkSyntax:
     runs-on: ubuntu-latest
     steps:
       - name: Python Setup
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: 3
           architecture: x64
       - name: Checkout Source
-        uses: actions/checkout@v3
-      - name: Install flake8
-        run: pip install flake8
-      - name: Syntax Check
+        uses: actions/checkout@v4
+      - 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
+          ruff --version
+          ruff check
+      - name: Pyright Check
+        run: |
+          pyright --version
+          pyright
+      - name: Isort Check
+        run: |
+          isort --version
+          isort --check .

.github/workflows/test_linux.yml

@@ -4,38 +4,43 @@ on:
   push:
     branches:
       - main
-      - dev
+      - release
   pull_request:
     branches:
       - main
-      - dev
+      - release
 
 jobs:
   testLinux:
     strategy:
       matrix:
-        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+      fail-fast: false
     runs-on: ubuntu-latest
     steps:
       - name: Python Setup
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
           architecture: x64
       - 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@v3
+        uses: actions/checkout@v4
       - name: Install Dependencies (pip)
         run: |
           pip install -U -r requirements.txt -r tests/requirements.txt
       - name: Run Build Commands
-        run: python pkgutils.py qtlrelease sample
+        run: |
+          python pkgutils.py qtlrelease
+          python pkgutils.py sample
       - name: Run Tests
         run: |
           export QT_QPA_PLATFORM=offscreen
-          pytest -v --cov=novelwriter --timeout=60
+          python -m pytest -v --cov=novelwriter --timeout=60
       - name: Upload to Codecov
-        uses: codecov/codecov-action@v3
+        uses: codecov/codecov-action@v5
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/test_mac.yml

@@ -4,32 +4,34 @@ on:
   push:
     branches:
       - main
-      - dev
+      - release
   pull_request:
     branches:
       - main
-      - dev
+      - release
 
 jobs:
   testMac:
-    runs-on: macos-latest
+    runs-on: macos-13
     steps:
       - name: Python Setup
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
           architecture: x64
       - name: Install Packages (brew)
         run: |
           brew install enchant
       - name: Checkout Source
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Install Dependencies (pip)
         run: |
           pip install -U pyobjc -r requirements.txt -r tests/requirements.txt
       - name: Run Tests
         run: |
           export QT_QPA_PLATFORM=offscreen
-          pytest -v --cov=novelwriter --timeout=60
+          python -m pytest -v --cov=novelwriter --timeout=60
       - name: Upload to Codecov
-        uses: codecov/codecov-action@v3
+        uses: codecov/codecov-action@v5
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/test_win.yml

@@ -4,28 +4,30 @@ on:
   push:
     branches:
       - main
-      - dev
+      - release
   pull_request:
     branches:
       - main
-      - dev
+      - release
 
 jobs:
   testWin:
     runs-on: windows-latest
     steps:
       - name: Python Setup
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
           architecture: x64
       - name: Checkout Source
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Install Dependencies (pip)
         run: |
           pip install -U -r requirements.txt -r tests/requirements.txt
       - name: Run Tests
         run: |
-          pytest -v --cov=novelwriter --timeout=60
+          python -m pytest -v --cov=novelwriter --timeout=60
       - name: Upload to Codecov
-        uses: codecov/codecov-action@v3
+        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.*
@@ -50,3 +53,9 @@ ToC.txt
 # Coverage
 /.coverage
 /coverage.*
+
+# Other
+/test.py
+.config
+.local
+*.patch

CONTRIBUTING.md

@@ -1,45 +1,44 @@
 # Contributing Guide
 
-When contributing to this repository, please first discuss the change you wish to make via the
-issue tracker or the discussions page with the owner of this repository. 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 just make a pull request directly.
+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
+just make a pull request directly.
 
-The following contributions are welcome:
+**The following contributions are welcome:**
 
 * Bugfixes for new or existing bugs. Please also report new bugs in the issue tracker even if you
   also provide a fix. It makes it easier to keep track of what has been fixed and when.
-* Translations via the [crowdin project page](https://crowdin.com/project/novelwriter).
+* 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:
+**Please do not:**
 
-* Make a pull request that restructures or reformats existing code. If you think some parts of the
+* Make a pull request that restructures or reformats existing code. If you think some part of the
   code could be improved, please make an issue thread or start a discussion. The same applies to
   any text document in the repository.
 
-## Pull Requests
+## Picking the Correct Branch for a Pull Request
 
-This project follows the [OneFlow](https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow)
-model. 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 own `main`
-branch.
+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.
 
-**Note:** If your contribution is a bugfix for a specific version, please make a bugfix branch from
-the tag you want the fix to be applied to, not directly from the `main` branch. This is important.
+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.
 
-Also check the following:
+**Also check the following:**
 
 * 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 by the
-  maintainer.
+  folder, although it doesn't check everything. The same check is also run on pull requests.
 * 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.
-* Do not submit files that were not actively changed but have otherwise been modifed. This is
+* Do not submit files that were not actively changed but have otherwise been modified. This is
   mostly an issue with translation files. The language tool may update all files in the `i18n`
   folder.
 
@@ -68,14 +67,14 @@ style guide, but with a few exceptions. Some key points are listed below.
   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
   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 preferrable.
+  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.
 
 **Variable and Function Names**
 
 * PEP8 allows for camelCase for consistency with existing code. The Qt library uses camelCase, so
-  the Python source code does too.
+  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.
 
@@ -83,19 +82,29 @@ style guide, but with a few exceptions. Some key points are listed below.
 
 * Only indentation by multiples of 4 spaces is allowed.
 * No trailing spaces should occur on any line in the source code, including empty lines.
-* Ideally, a function should end on the same indention level as it started. Exceptions are allowed
-  if it makes the code easier to follow.
+* All common line wrapping methods are allowed in the code, 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**
+
+* 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 `setup.cfg` file in the root of this project has the following settings for `flake8` that
-matches the above code style:
+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
@@ -115,7 +124,7 @@ command will give you a detailed description of the code lines that do not confo
 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 becuse it doesn't actually follow the
+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 `-`.

CREDITS.md

@@ -2,63 +2,76 @@
 
 ## Main Developer
 
-* Veronica Berglyd Olsen (@vkbo)
+* Veronica Berglyd Olsen
 
 ## Contributors
 
-* Concept: Marian Lückhof (@Number042)
-* Internationalisation: Bruno Meneguello (@bkmeneguello)
-* Setup and Packaging: Rachel Powers (@Ryex)
+* Early Concept: Marian Lückhof
+* Internationalisation: Bruno Meneguello
+* Setup and Packaging: Rachel Powers
 
 For other contributions, see the project's [Contributors](https://github.com/vkbo/novelWriter/graphs/contributors) page.
 
+## Artwork
+
+The artwork on the Welcome dialog was created by Louis Durrant.
+
 ## Translations
 
 The default language is English (UK) with English (US) as an option. These are the original
 translators for the languages currently available:
 
-* Dutch: Martijn van der Kleijn (@mvdkleijn)
-* French: Jan Lüdke (@jyhelle)
-* German: Myian (@heymyian)
-* Italian: Riccardo Mangili
-* Japanese: hebekeg (@hebekeg)
-* Latin American Spanish: Tommy Marplatt (@tmarplatt)
-* Norwegian: Veronica Berglyd Olsen (@vkbo)
-* Portuguese: Bruno Meneguello (@bkmeneguello)
-* Simplified Chinese: Qianzhi Long (@longqzh)
+* **Czech:** Tomáš Zmek (perteus)
+* **Dutch:** Martijn van der Kleijn (mvdkleijn)
+* **French:** Jan Lüdke (jyhelle)
+* **German:** Myian (HeyMyian)
+* **Italian:** Riccardo Mangili
+* **Japanese:** hebekeg
+* **Latin American Spanish:** Tommy Marplatt (tmarplatt)
+* **Norwegian:** Veronica Berglyd Olsen (vkbo)
+* **Polish:** Anna Maria Polak (Nauthiz)
+* **Portuguese:** Bruno Meneguello (bkmeneguello)
+* **Russian:** Konstantin Tan (k1kimosha)
+* **Simplified Chinese:** Qianzhi Long (longqzh)
 
 Additional larger translation contributions:
 
-* French: Albert Aribaud (@aaribaud)
+* **French:** Albert Aribaud (aaribaud)
+* **Portuguese:** Oli Maia (olimaia)
 
 Translations are managed on [Crowdin](https://crowdin.com/project/novelwriter), and more
-contributions are listed on the project's [Members](https://crowdin.com/project/novelwriter/members) page.
+contributions are listed on the project's Members page.
 
 ## Libraries
 
 The following libraries are dependencies of novelWriter:
 
-* [Qt5](https://www.qt.io) by Qt Company
-* [PyQt5](https://www.riverbankcomputing.com/software/pyqt) by Riverbank Computing
-* [Enchant](https://abiword.github.io/enchant) by Dom Lachowicz
-* [PyEnchant](https://pyenchant.github.io/pyenchant) by Dimitri Merejkowsky
+* **Qt6** by Qt Company
+* **PyQt6** by Riverbank Computing
+* **Enchant** by Dom Lachowicz
+* **PyEnchant** by Dimitri Merejkowsky
 
 ## Assets
 
 Some of the assets bundled with novelWriter were adapted from the following sources:
 
-* [Typicons](https://github.com/stephenhutchings/typicons.font) icons by Stephen Hutchings (CC BY-SA 4.0)
-* [Tomorrow](https://github.com/chriskempson/base16) syntax themes by Chris Kempson (MIT License)
-* [Owl](https://github.com/sdras/night-owl-vscode-theme) syntax themes by Sarah Drasner (MIT License)
-* [Solarized](https://github.com/altercation/solarized) themes by Ethan Schoonover (MIT License)
+* **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)
+* **Cyberpunk Night** theme by Anders Lemvigh (CC BY-SA 4.0)
+* **Dracula** theme by Zeno Rocha (MIT License)
+* **Snazzy Light** theme by Florian Reuschel (MIT License)
 
 ## Fonts
 
-The font used for the main novelWriter logo, mimetype and text banners is:
+The font used for the main novelWriter logo, mimetype and text banners is Pridi.
 
-* Pridi by Cadson Demak (Open Font License, Version 1.1)
+* **Pridi** by Cadson Demak (Open Font License, Version 1.1)
 
 ## Special Mentions
 
-Additional thanks to @johnblommers who was an early user and who has provided a lot of very useful
+Additional thanks to John Blommers who was an early user and who has provided a lot of very useful
 feedback over the years.

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">
@@ -29,18 +29,31 @@ documentation.
 * PyPi Project: [pypi.org/project/novelWriter](https://pypi.org/project/novelWriter)
 * Social Media: [fosstodon.org/@novelwriter](https://fosstodon.org/@novelwriter)
 
+## Sponsors
+
+<table style="border: none;">
+<tr>
+  <td><img align="left" style="height: 25px;" src="https://raw.githubusercontent.com/vkbo/novelWriter/main/setup/signpath_logo.png"></td>
+  <td>Free code signing on Windows provided by <a href="https://about.signpath.io/">SignPath.io</a>, certificate by <a href="https://signpath.org/">SignPath Foundation</a>.</td>
+</tr>
+</table>
+
 ## Implementation
 
-novelWriter is written with Python 3 (3.8+) using Qt5 and PyQt5 (5.10+), and is released on Linux,
-Windows and macOS. It can in principle run on any Operating System that also supports Qt, PyQt and
+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
@@ -49,6 +62,10 @@ code, please also read the full
 
 Project credits are available in [CREDITS.md](https://github.com/vkbo/novelWriter/blob/main/CREDITS.md).
 
+**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
 
 New translations are always welcome. This project uses Crowdin to maintain translations, and you
@@ -56,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,7 @@
-sphinx-book-theme
-sphinx>=5.0
-sphinx-favicon
-sphinx-design
-pygments>=2.7
 docutils>=0.17.1
+pygments>=2.7
+sphinx-book-theme
+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()
@@ -41,6 +46,8 @@ 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/index.rst

@@ -1,13 +1,13 @@
-######################
-novelWriter User Guide
-######################
+##########
+User Guide
+##########
 
 | **Release Version:** |release|
 | **Updated:** |today|
 
-novelWriter is an open source plain text editor designed for writing novels assembled from many
-smaller 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
+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.
 
@@ -17,19 +17,18 @@ storage for robustness.
    :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 with a meta data header. The core
-project structure is stored in a single project XML file. Other meta data is saved as JSON files.
-See the :ref:`a_breakdown_storage` section for more details.
+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 can run Python 3 and has 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. novelWriter can also be run directly from the Python source, or installed from packages or
-with pip. See :ref:`a_started` for more details.
+Any operating system that has Python 3 and the Qt 6 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
 * Documentation: https://docs.novelwriter.io
+* Public Releases: https://releases.novelwriter.io
 * Internationalisation: https://crowdin.com/project/novelwriter
 * Source Code: https://github.com/vkbo/novelWriter
 * Source Releases: https://github.com/vkbo/novelWriter/releases
@@ -42,6 +41,7 @@ with pip. See :ref:`a_started` for more details.
    :hidden:
 
    Main Page <self>
+   More Documents <https://novelwriter.io/more/>
 
 .. toctree::
    :maxdepth: 1
@@ -52,7 +52,6 @@ with pip. See :ref:`a_started` for more details.
    int_overview
    int_started
    int_howto
-   int_customise
    int_glossary
 
 .. toctree::
@@ -66,7 +65,6 @@ with pip. See :ref:`a_started` for more details.
    usage_format
    usage_shortcuts
    usage_typography
-   usage_projectformat
 
 .. toctree::
    :maxdepth: 1
@@ -80,7 +78,23 @@ with pip. See :ref:`a_started` for more details.
 
 .. toctree::
    :maxdepth: 1
-   :caption: Additional Topics
+   :caption: Writing Aids
+   :hidden:
+
+   writing_story
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Additional Details
+   :hidden:
+
+   more_customise
+   more_projectformat
+   more_counting
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Technical Topics
    :hidden:
 
    tech_locations

docs/source/int_glossary.rst

@@ -13,7 +13,7 @@ Glossary
       see :ref:`a_proj_roots`.
 
    Novel Documents
-      These are documents that are created under a "Novel" :term:`root folder`. They behave
+      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.
@@ -50,7 +50,7 @@ Glossary
    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 header levels don't
+      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

docs/source/int_howto.rst

@@ -16,39 +16,73 @@ This is a list of hopefully helpful little tips on how to get the most out of no
 Managing the Project
 ====================
 
-.. dropdown:: Merge Multiple Documents Into One
+.. dropdown:: How do I create a project from a template?
    :animate: fade-in-slide-down
 
-   If you need to merge a set 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 files you want merged
-   into this folder. Then you can right click the folder, select :guilabel:`Transform` and
-   :guilabel:`Merge Documents in Folder`.
+   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.
+
+.. 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
+   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`.
 
    In the dialog that pops up, the documents will be in the same order as in the folder, but you
-   can also 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:`a_ui_tree_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:: 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.
    However, the editor does render tabs in a similar way that regular word processors do. You can
-   set the width of a tab in :guilabel:`Preferences`.
+   set the width of a tab in **Preferences**.
 
    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.
 
    This is most suitable for your notes, as the result in exported documents cannot be guaranteed
-   to match.
+   to match. Especially if you don't use the same font in your manuscript as in the editor.
+
+.. 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 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.
 
 
 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
@@ -56,25 +90,27 @@ Organising Your Text
 
    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 (added in novelWriter 2.0).
+   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
    within chapters. Like for instance if you switch point-of-view character often.
 
-   In such cases you may want to use the scene heading for hard scene breaks and section headings
-   for soft scene breaks. the :guilabel:`Build Manuscript` tool will let you add separate
-   formatting for the two when you generate your manuscript. You can for instance add the common
-   "``* * *``" for hard breaks and select to hide section breaks, which will just insert an empty
-   paragraph in their place. See :ref:`a_manuscript_settings` for more details.
+   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:`a_manuscript_settings` for more details.
+
+   .. versionadded:: 2.4
 
 
 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/int_introduction.rst

@@ -1,42 +1,68 @@
 .. _a_intro:
 
-************
-Key Features
-************
+********
+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. It uses a markup syntax inspired by
-Markdown_ to apply simple formatting to the text. It 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.
+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.
 
-Your novel project 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.
+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`. These are intended for
+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 headers up into multiple documents, or
-merge multiple documents into single documents. This makes it easier to use variations of the
+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
-one per act for instance, and later effortlessly split these up into scenes by their headers.
+for instance one document per act, and later effortlessly split these up into individual chapter or
+scene documents.
+
+
+.. _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. When you really want to focus on just writing, you can
-   switch the editor into :guilabel:`Focus Mode` where only the text editor panel itself is
-   visible, and the project structure view is hidden away.
+   text emphasis and paragraph alignment. Additional shortcodes are available for special
+   formatting cases when you need them.
+
+   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. This view
-   panel is intended for displaying another scene document, your character notes, plot notes, or any
+   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.
 
@@ -45,40 +71,46 @@ Below are some key features of novelWriter.
    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 a few documents and then
-   later split them into multiple documents based on their headers.
+   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**
-   As of novelWriter 2.0, you can have multiple Novel type root folders in a project. 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.
+   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 separately.
 
-**Keep track of your plot elements**
-   All notes in your project can be assigned a :term:`tag` that you can :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.
+**Keep track of your story elements**
+   All documents 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 or
+   scenes in the same document.
 
 **Get an overview of your story**
-   In the :guilabel:`Outline View` on the main window you can see an outline of all the chapters,
-   scenes, and sections of your project. If they have any references in them, 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 :guilabel:`Novel View` as an
-   alternative view to the project tree.
+   It is not the documents themselves that define the chapters and scenes of your story, but the
+   headings within 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 shows 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 when you don't need it
-   to free up space.
+   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.
 
-**Building your manuscript**
+**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, you can use the :guilabel:`Build Manuscript` tool to
+   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, a PDF, or to 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.
+   and how it is formatted. You can send the result to a printer, or generate an Open Document or
+   Word 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:
@@ -86,7 +118,7 @@ Below are some key features of novelWriter.
 Screenshots
 ===========
 
-.. figure:: images/screenshot_default.png
+.. figure:: images/screenshot_light.png
    :class: dark-light
 
    novelWriter with light colour theme

docs/source/int_overview.rst

@@ -1,69 +1,57 @@
-.. _a_overview:
+.. _a_reading:
 
-********
-Overview
-********
+******************
+What to Read First
+******************
 
-.. only:: html
+The documentation of novelWriter is quite extensive. There are a lot of features to get used to,
+but you don't need to know all of them to get started.
 
-   .. image:: images/python_powered.png
-      :align: right
-      :width: 220
+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.
 
-novelWriter is built as a cross-platform application using `Python 3 <https://www.python.org/>`_ as
-the programming language, and `Qt 5 <https://www.qt.io/>`_ for the user interface.
+The chapters labelled "Recommended Reading" includes additional information on how the different
+parts if the application work and what the features do. 
 
-novelWriter is built for Linux first, and this is where it works best. However, it also runs fine
-on Windows and MacOS due to the cross-platform framework it's built on. The author of the
-application doesn't own a Mac, so on-going Mac support is dependent on user feedback and user
-contributions.
-
-Spell checking in novelWriter is provided by a third party library called
-`Enchant <https://abiword.github.io/enchant/>`_. Please see the section on :ref:`a_custom_dict` for
-how to install spell checking languages.
-
-For install instructions, see :ref:`a_started`.
+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
+chapters will explain the main principles. They start with the basics, and get more detailed as you
 read on.
 
-:ref:`a_breakdown` – Essential Information
+: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
+: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
+: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
+: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
+: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
+: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.
 
-:ref:`a_prjfmt` – Optional
-   This chapter is more technical and has an overview of changes made to the way your project data
-   is stored. The format has changed a bit from time to time, and sometimes the changes require
-   that you make small modifications to your project. Everything you need to know is listed in this
-   chapter.
-
 
 Organising Your Projects
 ========================
@@ -73,20 +61,40 @@ structure of your novel and show you additional information about its flow and c
 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
+: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
+: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
+: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 :guilabel:`Manuscript Build` tool works, how you can control the
-   way chapter titles are formatted, and how scene and section breaks are handled.
+: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.
+
+
+Writing Aids
+============
+
+We are in the process of adding tools to novelWriter that can be used to track more information
+about your project to assist in your writing. These tools are entirely optional and will not be in
+your way if you choose to not use them.
+
+:ref:`a_story_structure` -- Writing Tools
+   Story structure comments are a way to add meta data that can be used to analyse the structure of
+   your writing. These comments can be exported to spreadsheets for analysis.
+
+
+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,12 +1,12 @@
 .. _a_started:
 
-***************
-Getting Started
-***************
+**********************
+Setup and Installation
+**********************
 
-.. _Enchant: https://abiword.github.io/enchant/
+.. _Enchant: http://rrthomas.github.io/enchant/
 .. _GitHub: https://github.com/vkbo/novelWriter
-.. _main website: https://novelwriter.io
+.. _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/
@@ -15,9 +15,10 @@ Getting Started
 .. _AppImage: https://appimage.org/
 
 Ready-made packages and installers for novelWriter are available for all major platforms, including
-Linux, Windows and MacOS. See below for install instructions for each platform.
+Linux, Windows and MacOS, from the `Downloads page`_. See below for additional install instructions
+for each platform.
 
-You can also install novelWriter from the Python Package Index (PyPi). See :ref:`a_started_pip`.
+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.
 
@@ -32,29 +33,24 @@ Installing on Windows
 =====================
 
 You can install novelWriter with both Python and library dependencies embedded using the Windows
-Installer (setup.exe) file from the `main website`_, or from the Releases_ page on GitHub_.
+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 the installer.
-
 
 .. _a_started_linux:
 
 Installing on Linux
 ===================
 
-A Debian package can be downloaded from the `main website`_, or from the Releases_ page on GitHub_.
-This package should work on both Debian, Ubuntu and Linux Mint, at least.
+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
@@ -82,7 +78,7 @@ 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 jammy main" | sudo tee /etc/apt/sources.list.d/novelwriter.list
+   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:
 
@@ -91,10 +87,6 @@ Then run the update and install commands as for Ubuntu:
    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:
@@ -112,8 +104,8 @@ completely standalone images for the app that include the necessary environment
 They can of course be run on any Linux distro, if you prefer this to native packages.
 
 .. note::
-   novelWriter generally don'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
+   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.
 
 
@@ -123,14 +115,14 @@ Installing on MacOS
 ===================
 
 You can install novelWriter with both its Python and library dependencies embedded using the DMG
-application image file from the `main website`_, or from the Releases_ page on GitHub_. Installing
-it should be straightforward.
+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
+* 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.
 
@@ -140,7 +132,7 @@ done by holding down the option key on your keyboard and clicking on the applica
 .. 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.
+   funding to pay for a commercial software signing certificate.
 
 
 .. _a_started_pip:
@@ -149,7 +141,7 @@ Installing from PyPi
 ====================
 
 novelWriter is also available on the Python Package Index, or PyPi_. This install method works on
-all supported operating systems.
+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

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/index.po

@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-02-03 16:59+0100\n"
+"PO-Revision-Date: 2025-02-03 17:00+0100\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:40
+msgid "Main Page"
+msgstr "Page d'accueil"
+
+#: ../../source/index.rst:45
+msgid "Introduction"
+msgstr "Introduction"
+
+#: ../../source/index.rst:56
+msgid "Using novelWriter"
+msgstr "Utiliser novelWriter"
+
+#: ../../source/index.rst:68
+msgid "Organising Your Project"
+msgstr "Organiser votre projet"
+
+#: ../../source/index.rst:78
+msgid "Additional Details"
+msgstr "Détails additionnels"
+
+#: ../../source/index.rst:87
+msgid "Technical Topics"
+msgstr "Sujets techniques"
+
+#: ../../source/index.rst:3
+msgid "User Guide"
+msgstr "Guide de l'utilisateur"
+
+#: ../../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 ""
+"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."
+msgstr ""
+"Le stockage du projet est adapté aux logiciels de contrôle de version, "
+"ainsi qu'aux outils de synchronisation de fichiers.Tout le texte est "
+"sauvegardé sous forme de fichiers de texte brut, et les données de votre "
+"projet sous les formats de données standard XML et JSON.Voir :ref:"
+"`a_storage` pour plus de détails."
+
+#: ../../source/index.rst:23
+msgid ""
+"Any operating system that has Python 3 and the Qt 6 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."
+msgstr ""
+"Tout système d'exploitation disposant de Python 3 et des bibliothèques Qt "
+"6 devrait pouvoir faire fonctionner novelWriter. Il fonctionne "
+"correctement sous Linux, Windows et MacOS, et des utilisateurs l'ont "
+"également testé sur d'autres plateformes. Voir :ref:`a_started` pour plus "
+"de détails."
+
+#: ../../source/index.rst:27
+msgid "**Useful Links**"
+msgstr "**Liens utiles**"
+
+#: ../../source/index.rst:29
+msgid "Website: https://novelwriter.io"
+msgstr "Site web : https://novelwriter.io"
+
+#: ../../source/index.rst:30
+msgid "Documentation: https://docs.novelwriter.io"
+msgstr "Documentation: https://docs.novelwriter.io"
+
+#: ../../source/index.rst:31
+msgid "Public Releases: https://releases.novelwriter.io"
+msgstr "Public Releases: https://releases.novelwriter.io"
+
+#: ../../source/index.rst:32
+msgid "Internationalisation: https://crowdin.com/project/novelwriter"
+msgstr "Internationalisation: https://crowdin.com/project/novelwriter"
+
+#: ../../source/index.rst:33
+msgid "Source Code: https://github.com/vkbo/novelWriter"
+msgstr "Code source : https://github.com/vkbo/novelWriter"
+
+#: ../../source/index.rst:34
+msgid "Source Releases: https://github.com/vkbo/novelWriter/releases"
+msgstr "Source Releases: https://github.com/vkbo/novelWriter/releases"
+
+#: ../../source/index.rst:35
+msgid "Issue Tracker: https://github.com/vkbo/novelWriter/issues"
+msgstr "Issue Tracker: https://github.com/vkbo/novelWriter/issues"
+
+#: ../../source/index.rst:36
+msgid "Feature Discussions: https://github.com/vkbo/novelWriter/discussions"
+msgstr "Feature Discussions: https://github.com/vkbo/novelWriter/discussions"
+
+#: ../../source/index.rst:37
+msgid "PyPi Project: https://pypi.org/project/novelWriter"
+msgstr "PyPi Project: https://pypi.org/project/novelWriter"
+
+#: ../../source/index.rst:38
+msgid "Social Media: https://fosstodon.org/@novelwriter"
+msgstr "Social Media: https://fosstodon.org/@novelwriter"

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

@@ -0,0 +1,201 @@
+# French translations for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 10:29+0100\n"
+"Last-Translator: \n"
+"Language-Team: \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/int_glossary.rst:5
+msgid "Glossary"
+msgstr "Glossaire"
+
+#: ../../source/int_glossary.rst:44
+msgid "Context Menu"
+msgstr "Menu contextuel"
+
+#: ../../source/int_glossary.rst:46
+msgid ""
+"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+.`."
+msgstr ""
+"Un menu contextuel est un menu qui apparaît lorsque vous faites un clic "
+"droit sur quelque chose dans l'interface utilisateur. Dans novelWriter, "
+"vous pouvez également ouvrir un menu contextuel en appuyant sur le "
+"raccourci clavier :kbd:`Ctrl+.`."
+
+#: ../../source/int_glossary.rst:49
+msgid "Headings"
+msgstr "En-têtes"
+
+#: ../../source/int_glossary.rst:51
+msgid ""
+"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`."
+msgstr ""
+"Chaque niveau d'en-têtes dans :term:`Documents du roman` a une "
+"signification spécifique en termes de structure de l'histoire. En "
+"d'autres termes, ils déterminent ce que novelWriter considère comme une "
+"partition, un chapitre, une scène ou une section de texte. Pour :term:"
+"`Notes de projet`, les niveaux d'en-tête n'ont pas d'importance. Pour "
+"plus de détails sur les en-têtes dans les documents de roman, voir :ref:"
+"`a_struct_heads`."
+
+#: ../../source/int_glossary.rst:55
+msgid "Keyword"
+msgstr "Mot-clé"
+
+#: ../../source/int_glossary.rst:57
+msgid ""
+"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>`."
+msgstr ""
+"Un mot-clé dans novelWriter est une commande spéciale que vous placez "
+"dans le texte de vos documents. Il ne s'agit pas de Markdown standard, "
+"mais ils sont utilisés dans novelWriter pour ajouter des informations "
+"qui sont interprétées par l'application. Par exemple, les mots-clés sont "
+"utilisés pour :term:`tags<tag>` et :term:`références<reference>`."
+
+#: ../../source/int_glossary.rst:62
+msgid ""
+"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."
+msgstr ""
+"Les mots-clés doivent toujours être sur leur propre ligne, et le premier "
+"caractère de la ligne doit toujours être le caractère ``@``. Le mot-clé "
+"doit également toujours être suivi du caractère ``:``, et les valeurs "
+"transmises à la commande sont ajoutées à la suite, séparées par des "
+"virgules."
+
+#: ../../source/int_glossary.rst:14
+msgid "Novel Documents"
+msgstr "Documents du roman"
+
+#: ../../source/int_glossary.rst:16
+msgid ""
+"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."
+msgstr ""
+"Il s'agit de documents créés sous un :term:`dossier racine` « Roman ». "
+"Ils se comportent différemment des :term:`Notes de projet`, et ont plus "
+"de restrictions. Par exemple, ils ne peuvent pas exister dans des "
+"dossiers destinés uniquement aux notes de projet. Voir le chapitre :ref:"
+"`a_struct` pour plus de détails."
+
+#: ../../source/int_glossary.rst:38
+msgid "Project Index"
+msgstr "Index du projet"
+
+#: ../../source/int_glossary.rst:40
+msgid ""
+"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`."
+msgstr ""
+"L'index du projet est un enregistrement de toutes les en-têtes d'un "
+"projet, avec toutes leurs métadonnées comme les commentaires de "
+"synopsis, les :term:`tags<tag>` et les :term:`références<reference>`. "
+"L'index du projet est mis à jour automatiquement, mais il peut aussi "
+"être régénéré manuellement à partir du menu :guilabel:`Outils` ou en "
+"appuyant sur :kbd:`F9`."
+
+#: ../../source/int_glossary.rst:20
+msgid "Project Notes"
+msgstr "Notes de projet"
+
+#: ../../source/int_glossary.rst:22
+msgid ""
+"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."
+msgstr ""
+"Les notes de projet sont des documents libres qui peuvent être placés "
+"n'importe où dans votre projet. Vous ne devez pas utiliser ces documents "
+"pour les éléments de l'histoire, mais uniquement pour les notes. Les "
+"notes de projet sont les fichiers sources utilisés par le système de "
+"balises et de références. Voir le chapitre :ref:`a_references` pour plus "
+"de détails sur leur utilisation."
+
+#: ../../source/int_glossary.rst:33
+msgid "Reference"
+msgstr "Référence"
+
+#: ../../source/int_glossary.rst:35
+msgid ""
+"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."
+msgstr ""
+"Une référence fait partie d'un ensemble de :term:`mots-clés<keyword>` "
+"qui peuvent être utilisés pour établir un lien avec un :term:`tag` dans "
+"un autre document. Les mots-clés de référence sont spécifiques aux "
+"différents types de :term:`dossier racine`. Une présentation complète "
+"est disponible dans le chapitre :ref:`a_references`."
+
+#: ../../source/int_glossary.rst:9
+msgid "Root Folder"
+msgstr "Dossier racine"
+
+#: ../../source/int_glossary.rst:11
+msgid ""
+"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`."
+msgstr ""
+"Un « dossier racine » est un dossier de premier niveau de l'arborescence "
+"du projet dans novelWriter. Chaque type de dossier racine possède une "
+"icône spécifique pour l'identifier. Pour une vue d'ensemble des types de "
+"dossiers racines disponibles, voir :ref:`a_proj_roots`."
+
+#: ../../source/int_glossary.rst:26
+msgid "Tag"
+msgstr "Tag"
+
+#: ../../source/int_glossary.rst:28
+msgid ""
+"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."
+msgstr ""
+"Un tag est une valeur définie par l'utilisateur et attribuée comme tag à "
+"une section de votre :term:`Notes de projet`. Elle est facultative et ne "
+"peut être définie qu'une seule fois par rubrique. Elle est définie en "
+"utilisant la syntaxe :term:`mot-clé` `@tag : valeur``, où `valeur`` est "
+"la partie définie par l'utilisateur. Chaque balise peut être référencée "
+"dans un autre fichier en utilisant l'un des mots-clés :term:`référence`. "
+"Voir le chapitre :ref:`a_references` pour plus de détails."

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

@@ -0,0 +1,299 @@
+# French translations for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 10:43+0100\n"
+"Last-Translator: \n"
+"Language-Team: \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/int_howto.rst:5
+msgid "Tips & Tricks"
+msgstr "Trucs et astuces"
+
+#: ../../source/int_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/int_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/int_howto.rst:17
+msgid "Managing the Project"
+msgstr "Gestion du projet"
+
+#: ../../source/int_howto.rst
+msgid "How do I create a project from a template?"
+msgstr "Comment créer un projet à partir d'un modèle ?"
+
+#: ../../source/int_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/int_howto.rst
+msgid "How do I merge multiple documents into one?"
+msgstr "Comment fusionner plusieurs documents en un seul ?"
+
+#: ../../source/int_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/int_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:"
+"`a_ui_tree_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:`a_ui_tree_split_merge` pour plus de détails."
+
+#: ../../source/int_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/int_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/int_howto.rst:47
+msgid "Layout Tricks"
+msgstr "Astuces de mise en page"
+
+#: ../../source/int_howto.rst
+msgid "How do I create a table?"
+msgstr "Comment créer un tableau ?"
+
+#: ../../source/int_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/int_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 le "
+"visualiseur, 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/int_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/int_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/int_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 construction 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/int_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/int_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/int_howto.rst:79
+msgid "See :ref:`a_fmt_align` for more details."
+msgstr "Voir :ref:`a_fmt_align` pour plus de détails."
+
+#: ../../source/int_howto.rst:83
+msgid "Organising Your Text"
+msgstr "Organiser son texte"
+
+#: ../../source/int_howto.rst
+msgid "How do I add introductory text to chapters?"
+msgstr "Comment ajouter un texte d'introduction aux chapitres ?"
+
+#: ../../source/int_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/int_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/int_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/int_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/int_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:`a_manuscript_settings` for more "
+"details."
+msgstr ""
+"Dans ce cas, vous pouvez utiliser des en-têtes de scène différents pour les "
+"coupures de scène dures et douces. L'outil **Compiler le 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 "
+"sélectionner des coupures de scènes douces, qui inséreront simplement un "
+"paragraphe vide à leur place. Voir :ref:`a_manuscript_settings` pour plus de "
+"détails."
+
+#: ../../source/int_howto.rst:111
+msgid "Other Tools"
+msgstr "Autres outils"
+
+#: ../../source/int_howto.rst
+msgid "How do I convert my project to/from the yWriter format?"
+msgstr "Comment convertir mon projet au format yWriter ?"
+
+#: ../../source/int_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/int_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/>`__"
+
+#~ msgid "Align Paragraphs with Line Breaks"
+#~ msgstr "Aligner les paragraphes avec des sauts de ligne"
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si vous avez des sauts de ligne dans vos paragraphes et que vous souhaitez "
+#~ "également appliquer un alignement ou une indentation du texte, vous devez "
+#~ "appliquer les balises d'alignement à la première ligne."
+
+#~ msgid "For example, this will centre the two lines."
+#~ msgstr "Par exemple, ceci centrera les deux lignes."

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

@@ -0,0 +1,349 @@
+# French translations for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-31 21:29+0100\n"
+"Last-Translator: \n"
+"Language-Team: \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/int_introduction.rst:5
+msgid "Overview"
+msgstr "Présentation générale"
+
+#: ../../source/int_introduction.rst:10
+msgid ""
+"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."
+msgstr ""
+"A la base, novelWriter est un éditeur de texte brut multi-documents. "
+"L'idée est de vous permettre d'éditer votre texte sans avoir à vous "
+"préoccuper de la mise en forme jusqu'à ce que vous génériez un projet de "
+"document ou un manuscrit. Au lieu de cela, vous pouvez vous concentrer "
+"sur l'écriture dès le début."
+
+#: ../../source/int_introduction.rst:14
+msgid ""
+"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."
+msgstr ""
+"Bien sûr, vous avez probablement besoin d'une certaine mise en forme "
+"pour votre texte. Au minimum, vous avez besoin d'accentuation. 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. Si vous avez "
+"besoin d'un formatage plus spécialisé, des options de formatage "
+"supplémentaires sont disponibles en utilisant un format shortcode. Voir :"
+"ref:`a_fmt_shortcodes` pour plus de détails."
+
+#: ../../source/int_introduction.rst:21
+msgid "Limitations"
+msgstr "Restrictions"
+
+#: ../../source/int_introduction.rst:23
+msgid ""
+"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."
+msgstr ""
+"novelWriter est conçu pour l'écriture de fictions, et les fonctions de "
+"formatage disponibles sont donc limitées à celles qui sont pertinentes "
+"pour cet usage. Il n'est *pas* adapté à la rédaction technique et n'est "
+"*pas* un éditeur Markdown complet."
+
+#: ../../source/int_introduction.rst:27
+msgid ""
+"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."
+msgstr ""
+"Il n'est pas non plus 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 de novelWriter est principalement destinée aux profils de "
+"personnages et aux ébauches d'intrigues."
+
+#: ../../source/int_introduction.rst:31
+msgid ""
+"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."
+msgstr ""
+"Votre projet de roman dans novelWriter est organisé comme une collection "
+"de documents de texte brut séparés au lieu d'un seul grand document. "
+"L'idée est de faciliter la réorganisation de la structure de votre "
+"projet sans avoir à couper et coller du texte entre les chapitres et les "
+"scènes."
+
+#: ../../source/int_introduction.rst:35
+msgid ""
+"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."
+msgstr ""
+"Il y a deux types de documents dans votre projet : :term:`Documents du "
+"roman` sont des documents qui font partie de votre histoire. L'autre "
+"type de documents est :term:`Notes de projet`, qui sont destinés à vos "
+"notes sur vos personnages, votre construction du monde, et ainsi de "
+"suite."
+
+#: ../../source/int_introduction.rst:39
+msgid ""
+"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 individual chapter or scene documents."
+msgstr ""
+"Vous pouvez à tout moment diviser les documents individuels par leurs "
+"titres en plusieurs documents ou fusionner plusieurs documents en un "
+"seul. Il est ainsi plus facile d'utiliser des variantes de la méthode "
+"Snowflake_ pour l'écriture. Vous pouvez commencer par rédiger des "
+"documents plus importants axés sur la structure, comme par exemple un "
+"document par acte, et les diviser ensuite sans effort en documents "
+"individuels de chapitres ou de scènes."
+
+#: ../../source/int_introduction.rst:49
+msgid "Key Features"
+msgstr "Fonctionnalités principales"
+
+#: ../../source/int_introduction.rst:51
+msgid "Below are some key features of novelWriter."
+msgstr "Voici quelques caractéristiques clés de novelWriter."
+
+#: ../../source/int_introduction.rst:53
+msgid "**Focus on writing**"
+msgstr "**Focus sur l'écriture**"
+
+#: ../../source/int_introduction.rst:54
+msgid ""
+"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 need them."
+msgstr ""
+"L'objectif de l'interface utilisateur est de vous permettre de vous "
+"concentrer sur l'écriture plutôt que de passer du temps à formater le "
+"texte. Le formatage est donc limité à un petit ensemble de balises de "
+"formatage pour des choses simples comme l'emphase du texte et "
+"l'alignement des paragraphes. Des shortcodes supplémentaires sont "
+"disponibles pour des cas de formatage particuliers lorsque vous en avez "
+"besoin."
+
+#: ../../source/int_introduction.rst:59
+msgid ""
+"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."
+msgstr ""
+"Lorsque vous souhaitez vraiment vous concentrer sur l'écriture, vous "
+"pouvez basculer l'éditeur en **Mode sans distraction**, où seul le "
+"panneau de l'éditeur de texte est visible, et la vue de la structure du "
+"projet est cachée."
+
+#: ../../source/int_introduction.rst:63
+msgid "**Keep an eye on your notes**"
+msgstr "**Gardez un œil sur vos notes**"
+
+#: ../../source/int_introduction.rst:64
+msgid ""
+"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."
+msgstr ""
+"La fenêtre principale peut éventuellement afficher une visionneuse de "
+"documents à droite de l'éditeur. La visionneuse est destinée à afficher "
+"un autre document de scène, vos notes de personnage, vos notes "
+"d'intrigue ou tout autre document auquel vous pourriez avoir besoin de "
+"vous référer lors de l'écriture. Il ne s'agit pas d'un panneau de "
+"prévisualisation du document que vous êtes en train d'éditer, mais si "
+"vous le souhaitez, vous pouvez également l'utiliser à cette fin."
+
+#: ../../source/int_introduction.rst:69
+msgid "**Organise your documents how you like**"
+msgstr "**Organisez vos documents à votre guise**"
+
+#: ../../source/int_introduction.rst:70
+msgid ""
+"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."
+msgstr ""
+"Vous pouvez diviser votre projet de roman en autant de documents "
+"individuels que vous le souhaitez. Lorsque vous transformez le projet en "
+"manuscrit, tous les documents sont collés ensemble dans l'ordre où ils "
+"apparaissent dans l'arborescence du projet. Vous pouvez utiliser aussi "
+"peu de documents texte que vous le souhaitez, mais en divisant le projet "
+"en chapitres et en scènes, vous pouvez facilement les réorganiser à "
+"l'aide de la fonction « glisser-déposer » de l'arborescence du projet. "
+"Vous pouvez également commencer avec moins de documents, puis les "
+"diviser en plusieurs documents en fonction des titres des chapitres et "
+"des scènes."
+
+#: ../../source/int_introduction.rst:77
+msgid "**Multi-novel project support**"
+msgstr "**Support de projets de plusieurs romans**"
+
+#: ../../source/int_introduction.rst:78
+msgid ""
+"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 separately."
+msgstr ""
+"Les principales parties de votre projet sont réparties dans des dossiers "
+"spéciaux de premier niveau appelés dossiers « racine ». Le texte "
+"principal de votre histoire se trouve dans le dossier racine « Roman ». "
+"Vous pouvez avoir plusieurs dossiers de ce type dans un projet et les "
+"renommer comme vous le souhaitez. Cela vous permet de conserver une "
+"série de romans individuels avec les mêmes personnages et la même "
+"construction du monde dans le même projet, et de créer des manuscrits "
+"pour chacun d'entre eux."
+
+#: ../../source/int_introduction.rst:84
+msgid "**Keep track of your story elements**"
+msgstr "**Tracez les éléments de votre histoire**"
+
+#: ../../source/int_introduction.rst:85
+msgid ""
+"All documents 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 or "
+"scenes in the same document."
+msgstr ""
+"Toutes les notes de votre projet peuvent se voir attribuer un :term:"
+"`tag` que vous pouvez ensuite :term:`référencer<reference>` à partir de "
+"n'importe quel autre document ou note. En fait, vous pouvez ajouter une "
+"nouvelle balise sous chaque titre d'une note si vous avez besoin de "
+"pouvoir référencer des sections spécifiques de celle-ci, ou si vous "
+"voulez conserver plusieurs sujets dans la même note."
+
+#: ../../source/int_introduction.rst:90
+msgid "**Get an overview of your story**"
+msgstr "**Obtenez une vue d'ensemble de votre histoire**"
+
+#: ../../source/int_introduction.rst:91
+msgid ""
+"It is not the documents themselves that define the chapters and scenes "
+"of your story, but the headings within 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."
+msgstr ""
+"Ce ne sont pas les documents eux-mêmes qui définissent les chapitres et "
+"les scènes de votre histoire, mais les titres qu'ils contiennent. Dans "
+"la **Vue d'ensemble** de la fenêtre principale, vous pouvez voir un "
+"aperçu de tous les titres de chapitres et de scènes de chaque dossier "
+"racine de roman de votre projet. S'ils contiennent des références, par "
+"exemple quel personnage se trouve dans quel chapitre et quelle scène, "
+"celles-ci sont répertoriées dans des colonnes supplémentaires."
+
+#: ../../source/int_introduction.rst:97
+msgid ""
+"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."
+msgstr ""
+"Vous pouvez également ajouter un synopsis à chaque chapitre ou scène, "
+"qui peut également être listé ici. Vous avez la possibilité d'ajouter ou "
+"de supprimer des colonnes d'informations dans ce plan. Un sous-ensemble "
+"des informations du plan est également disponible dans la **Vue roman** "
+"comme vue alternative à l'arborescence du projet."
+
+#: ../../source/int_introduction.rst:101
+msgid "**Get an overview of your story elements**"
+msgstr "**Obtenez une vue d'ensemble des éléments de votre histoire**"
+
+#: ../../source/int_introduction.rst:102
+msgid ""
+"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."
+msgstr ""
+"Sous le panneau de visualisation du document, vous trouverez une série "
+"d'onglets qui montrent les différents éléments de l'histoire pour "
+"lesquels vous avez créé des étiquettes. Les onglets sont classés en "
+"**Personnages**, **Intrigues**, etc., en fonction des catégories que "
+"vous utilisez dans votre histoire. Ce panneau peut être caché pour "
+"libérer de l'espace lorsque vous n'en avez pas besoin."
+
+#: ../../source/int_introduction.rst:107
+msgid "**Assembling your manuscript**"
+msgstr "**Assembler votre manuscrit**"
+
+#: ../../source/int_introduction.rst:108
+msgid ""
+"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 generate an Open Document or Word 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."
+msgstr ""
+"Que vous souhaitiez assembler un manuscrit, exporter toutes vos notes ou "
+"générer un plan de vos chapitres et scènes avec un synopsis, vous pouvez "
+"utiliser l'outil **Compiler le manuscrit** pour le faire. Cet outil vous "
+"permet de sélectionner les informations que vous souhaitez inclure dans "
+"le document généré, ainsi que son formatage. Vous pouvez envoyer le "
+"résultat à une imprimante ou générer un fichier Open Document ou Word "
+"Document qui peut être ouvert par la plupart des traitements de texte de "
+"type bureautique. Vous pouvez également générer le résultat sous forme "
+"de HTML ou de Markdown, tous deux adaptés à une conversion ultérieure "
+"dans d'autres formats."
+
+#: ../../source/int_introduction.rst:119
+msgid "Screenshots"
+msgstr "Captures d'écran"
+
+#: ../../source/int_introduction.rst:124
+msgid "novelWriter with light colour theme"
+msgstr "novelWriter avec un thème de couleur claire"
+
+#: ../../source/int_introduction.rst:129
+msgid "novelWriter with dark colour theme"
+msgstr "novelWriter avec un thème de couleur sombre"

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

@@ -0,0 +1,265 @@
+# French translations for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 10:33+0100\n"
+"Last-Translator: \n"
+"Language-Team: \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/int_overview.rst:5
+msgid "What to Read First"
+msgstr "Premières lectures"
+
+#: ../../source/int_overview.rst:7
+msgid ""
+"The documentation of novelWriter is quite extensive. There are a lot of "
+"features to get used to, but you don't need to know all of them to get "
+"started."
+msgstr ""
+"La documentation de novelWriter est assez complète. Il y a beaucoup de "
+"fonctionnalités auxquelles il faut s'habituer, mais vous n'avez pas "
+"besoin de toutes pour commencer."
+
+#: ../../source/int_overview.rst:10
+msgid ""
+"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."
+msgstr ""
+"Les chapitres ci-dessous intitulés « Informations essentielles » sont "
+"ceux que vous devez connaître pour utiliser correctement l'application. "
+"Par « correctement », on entend : de manière à ce que novelWriter "
+"comprenne la structure de base de votre texte. Il collecte de nombreuses "
+"informations à partir de votre texte et les utilise pour afficher la "
+"structure de celui-ci de différentes manières afin de vous aider à "
+"obtenir une vue d'ensemble de votre écriture."
+
+#: ../../source/int_overview.rst:15
+msgid ""
+"The chapters labelled \"Recommended Reading\" includes additional "
+"information on how the different parts if the application work and what "
+"the features do."
+msgstr ""
+"Les chapitres intitulés « Lectures recommandées » contiennent des "
+"informations supplémentaires sur le fonctionnement des différentes "
+"parties de l'application et sur les fonctionnalités."
+
+#: ../../source/int_overview.rst:18
+msgid ""
+"The \"Optional\" and \"Lookup\" chapters contain additional information "
+"or lookup tables that are not essential for using the application."
+msgstr ""
+"Les chapitres « Optionnel “ et ” Consulter » contiennent des "
+"informations supplémentaires ou des tables de consultation qui ne sont "
+"pas indispensables à l'utilisation de l'application."
+
+#: ../../source/int_overview.rst:23
+msgid "Using novelWriter"
+msgstr "Utiliser novelWriter"
+
+#: ../../source/int_overview.rst:25
+msgid ""
+"In order to use novelWriter effectively, you need to know the basics of "
+"how it works. The following chapters will explain the main principles. "
+"They start with the basics, and get more detailed as you read on."
+msgstr ""
+"Afin d'utiliser novelWriter de manière efficace, vous devez connaître "
+"les bases de son fonctionnement. Les chapitres suivants expliquent les "
+"grands principes. Ils commencent par les bases et deviennent de plus en "
+"plus détaillés au fur et à mesure de la lecture."
+
+#: ../../source/int_overview.rst:29
+msgid ":ref:`a_breakdown` – Essential Information"
+msgstr ":ref:`a_breakdown` - Informations essentielles"
+
+#: ../../source/int_overview.rst:30
+msgid ""
+"This chapter explains the basics of how the application works and what "
+"it can and cannot do."
+msgstr ""
+"Ce chapitre explique les bases du fonctionnement de l'application et ce "
+"qu'elle peut et ne peut pas faire."
+
+#: ../../source/int_overview.rst:32
+msgid ":ref:`a_ui_project` – Recommended Reading"
+msgstr ":ref:`a_ui_project` - Lecture recommandée"
+
+#: ../../source/int_overview.rst:33
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre explique plus en détail comment vous pouvez utiliser les "
+"composants de l'interface utilisateur pour organiser et visualiser votre "
+"travail de projet."
+
+#: ../../source/int_overview.rst:36
+msgid ":ref:`a_ui_writing` – Recommended Reading"
+msgstr ":ref:`a_ui_writing` - Lecture recommandée"
+
+#: ../../source/int_overview.rst:37
+msgid ""
+"This chapter will give you a more detailed explanation of how the text "
+"editor and viewer work."
+msgstr ""
+"Ce chapitre explique plus en détail le fonctionnement de l'éditeur de "
+"texte et de l'affichage."
+
+#: ../../source/int_overview.rst:39
+msgid ":ref:`a_fmt` – Essential Information"
+msgstr ":ref:`a_fmt` - Informations essentielles"
+
+#: ../../source/int_overview.rst:40
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre traite de la mise en forme du texte. L'éditeur étant du "
+"texte brut, la mise en forme du texte nécessite un balisage de base. La "
+"structure de votre roman est également déduite de la manière dont vous "
+"utilisez les titres. Les balises et les références sont mises en œuvre "
+"par des mots-clés spéciaux."
+
+#: ../../source/int_overview.rst:44
+msgid ":ref:`a_kb` – Optional / Lookup"
+msgstr ":ref:`a_kb` - Optionnel / Consulter"
+
+#: ../../source/int_overview.rst:45
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre énumère tous les raccourcis clavier de novelWriter et leur "
+"fonction. La plupart des raccourcis sont également listés à côté de "
+"leurs entrées de menu dans l'application, ou dans les info-bulles. Ce "
+"chapitre est principalement destiné à servir de référence."
+
+#: ../../source/int_overview.rst:49
+msgid ":ref:`a_typ` – Optional"
+msgstr ":ref:`a_typ` - Optionnel"
+
+#: ../../source/int_overview.rst:50
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre vous donne un aperçu des symboles typographiques spéciaux "
+"disponibles dans novelWriter. La fonction de remplacement automatique "
+"peut gérer l'insertion des symboles de guillemets standard de votre "
+"langue, ainsi que d'autres caractères spéciaux. Si vous utilisez "
+"d'autres symboles, leur utilisation est expliquée ici."
+
+#: ../../source/int_overview.rst:57
+msgid "Organising Your Projects"
+msgstr "Organiser vos projets"
+
+#: ../../source/int_overview.rst:59
+msgid ""
+"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."
+msgstr ""
+"En plus de gérer une collection de fichiers de texte brut, novelWriter "
+"peut interpréter et cartographier la structure de votre roman et vous "
+"fournir des informations supplémentaires sur son déroulement et son "
+"contenu. Pour bénéficier de ces fonctionnalités, vous devez structurer "
+"votre texte d'une manière spécifique et ajouter des métadonnées à "
+"extraire."
+
+#: ../../source/int_overview.rst:64
+msgid ":ref:`a_proj` – Essential Information"
+msgstr ":ref:`a_proj` - Informations essentielles"
+
+#: ../../source/int_overview.rst:65
+msgid ""
+"This chapter explains how you organise the content of your project, and "
+"how to set up automated backups of your work."
+msgstr ""
+"Ce chapitre explique comment organiser le contenu de votre projet et "
+"comment mettre en place des sauvegardes automatiques de votre travail."
+
+#: ../../source/int_overview.rst:68
+msgid ":ref:`a_struct` – Essential Information"
+msgstr ":ref:`a_struct` - Informations essentielles"
+
+#: ../../source/int_overview.rst:69
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre traite de la manière dont la structure de votre roman est "
+"encodée dans les documents textuels. Il explique comment les différents "
+"niveaux d'en-têtes sont utilisés, ainsi que certains formats spéciaux "
+"pour différents types d'en-têtes."
+
+#: ../../source/int_overview.rst:73
+msgid ":ref:`a_references` - Recommended Reading"
+msgstr ":ref:`a_references` - Lecture recommandée"
+
+#: ../../source/int_overview.rst:74
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre explique comment organiser vos notes et comment fonctionne "
+"le système de balises et de références. Ce système vous permet d'établir "
+"des liens entre les documents de votre projet et d'afficher ces "
+"références dans l'interface de l'application."
+
+#: ../../source/int_overview.rst:78
+msgid ":ref:`a_manuscript` - Recommended Reading"
+msgstr ":ref:`a_manuscript` - Lecture recommandée"
+
+#: ../../source/int_overview.rst:79
+msgid ""
+"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."
+msgstr ""
+"Ce chapitre explique le fonctionnement de l'outil **Manuscript Build**, "
+"la manière dont vous pouvez contrôler le formatage des titres de "
+"chapitre et la gestion des sauts de scène et de section."
+
+#: ../../source/int_overview.rst:84
+msgid "Additional Details & Technical Topics"
+msgstr "Détails supplémentaires et sujets techniques"
+
+#: ../../source/int_overview.rst:86
+msgid ""
+"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."
+msgstr ""
+"Les sections Détails supplémentaires et Sujets techniques contiennent "
+"des informations plus approfondies sur le fonctionnement des différents "
+"éléments de novelWriter. Ces informations ne sont pas essentielles pour "
+"commencer à utiliser novelWriter."

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

@@ -0,0 +1,340 @@
+# French translations for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 10:32+0100\n"
+"Last-Translator: \n"
+"Language-Team: \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/int_started.rst:5
+msgid "Setup and Installation"
+msgstr "Configuration et installation"
+
+#: ../../source/int_started.rst:17
+msgid ""
+"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 additional install instructions for each platform."
+msgstr ""
+"Des paquets prêts à l'emploi et des installateurs pour novelWriter sont "
+"disponibles pour toutes les plateformes principales, y compris Linux, Windows "
+"et MacOS, à partir de la page `Downloads`_. Voir ci-dessous les instructions "
+"d'installation supplémentaires pour chaque plateforme."
+
+#: ../../source/int_started.rst:21
+msgid ""
+"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."
+msgstr ""
+"Vous pouvez également installer novelWriter à partir de l'index des paquets "
+"Python (PyPi_). Voir :ref:`a_started_pip`. L'installation à partir de PyPi ne "
+"met pas en place de lanceurs d'icônes, vous devrez donc soit le faire vous-"
+"même, soit lancer novelWriter à partir de la ligne de commande."
+
+#: ../../source/int_started.rst:25
+msgid ""
+"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."
+msgstr ""
+"La vérification orthographique dans novelWriter est assurée par une "
+"bibliothèque tierce appelée Enchant_. En général, elle devrait extraire "
+"automatiquement les dictionnaires de votre système d'exploitation. Cependant, "
+"sous Windows, ils doivent être installés manuellement. Voir :ref:"
+"`a_custom_dict` pour plus de détails."
+
+#: ../../source/int_started.rst:33
+msgid "Installing on Windows"
+msgstr "Installation sous Windows"
+
+#: ../../source/int_started.rst:35
+msgid ""
+"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."
+msgstr ""
+"Vous pouvez installer novelWriter avec les dépendances Python et les "
+"bibliothèques intégrées en utilisant le fichier Windows Installer (setup.exe) "
+"depuis la page `Downloads`_, ou depuis la page Releases_ sur GitHub_. "
+"L'installation devrait être simple."
+
+#: ../../source/int_started.rst:39
+msgid ""
+"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."
+msgstr ""
+"Si vous rencontrez des problèmes, essayez de désinstaller la version "
+"précédente et de procéder à une nouvelle installation. Si vous avez déjà "
+"installé une version par une autre méthode, désinstallez-la d'abord, car les "
+"installations multiples sont connues pour causer des problèmes."
+
+#: ../../source/int_started.rst:47
+msgid "Installing on Linux"
+msgstr "Installation sous Linux"
+
+#: ../../source/int_started.rst:49
+msgid ""
+"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."
+msgstr ""
+"Un paquet Debian peut être téléchargé depuis la page `Downloads`_, ou depuis "
+"la page Releases_ sur GitHub_. Ce paquet devrait fonctionner sur Debian, "
+"Ubuntu et Linux Mint, au moins."
+
+#: ../../source/int_started.rst:52
+msgid ""
+"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>`__."
+msgstr ""
+"Si vous préférez, vous pouvez également ajouter le dépôt novelWriter sur "
+"Launchpad à votre gestionnaire de paquets. Les paquets Launchpad `sont signés "
+"par l'auteur <https://launchpad.net/~vkbo>`__."
+
+#: ../../source/int_started.rst:57
+msgid "Ubuntu"
+msgstr "Ubuntu"
+
+#: ../../source/int_started.rst:59
+msgid ""
+"You can add the Ubuntu PPA_ and install novelWriter with the following "
+"commands."
+msgstr ""
+"Vous pouvez ajouter le PPA_ Ubuntu et installer novelWriter avec les "
+"commandes suivantes."
+
+#: ../../source/int_started.rst:67
+msgid ""
+"If you want the `Pre-Release PPA`_ instead, add the ``ppa:vkbo/novelwriter-"
+"pre`` repository."
+msgstr ""
+"Si vous voulez le PPA `Pre-Release`_ à la place, ajoutez le dépôt ``ppa:vkbo/"
+"novelwriter-pre``."
+
+#: ../../source/int_started.rst:71
+msgid "Debian and Mint"
+msgstr "Debian et Mint"
+
+#: ../../source/int_started.rst:73
+msgid ""
+"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."
+msgstr ""
+"Comme il s'agit d'un paquetage purement Python, le PPA Launchpad peut en "
+"principe être utilisé sur Debian ou Mint. Cependant, la commande ci-dessus "
+"n'ajoutera pas la clé de signature, car elle est spécifique à Ubuntu."
+
+#: ../../source/int_started.rst:76
+msgid "Instead, run the following commands to add the repository and key:"
+msgstr ""
+"Au lieu de cela, exécutez les commandes suivantes pour ajouter le dépôt et la "
+"clé :"
+
+#: ../../source/int_started.rst:83
+msgid "Then run the update and install commands as for Ubuntu:"
+msgstr ""
+"Exécutez ensuite les commandes de mise à jour et d'installation comme pour "
+"Ubuntu :"
+
+#: ../../source/int_started.rst:91
+msgid ""
+"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:"
+msgstr ""
+"Si vous obtenez un message d'erreur du type ``gpg : failed to create "
+"temporary file`` lors de l'importation de la clé depuis le serveur de clés "
+"Ubuntu, essayez de créer le dossier sur lequel l'erreur s'est produite, et "
+"importez à nouveau la clé :"
+
+#: ../../source/int_started.rst:100
+msgid "AppImage Releases"
+msgstr "AppImage"
+
+#: ../../source/int_started.rst:102
+msgid ""
+"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."
+msgstr ""
+"Pour les distros Linux autres que celles mentionnées ci-dessus, l'option "
+"principale est AppImage_. Il s'agit d'images complètement autonomes pour "
+"l'application qui incluent l'environnement nécessaire pour faire fonctionner "
+"novelWriter. Elles peuvent bien sûr être exécutées sur n'importe quelle "
+"distribution Linux, si vous préférez cela aux paquets natifs."
+
+#: ../../source/int_started.rst:107
+msgid ""
+"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."
+msgstr ""
+"novelWriter ne supporte généralement pas les versions de Python qui ont "
+"atteint leur fin de vie. Si votre distro Linux utilise encore d'anciennes "
+"versions de Python et que novelWriter ne fonctionne pas, vous pouvez essayer "
+"l'AppImage à la place."
+
+#: ../../source/int_started.rst:115
+msgid "Installing on MacOS"
+msgstr "Installation sur MacOS"
+
+#: ../../source/int_started.rst:117
+msgid ""
+"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."
+msgstr ""
+"Vous pouvez installer novelWriter avec ses dépendances Python et "
+"bibliothèques intégrées en utilisant le fichier image de l'application DMG "
+"depuis la page `Downloads`_, ou depuis la page Releases_ sur GitHub_. "
+"L'installation devrait être simple."
+
+#: ../../source/int_started.rst:121
+msgid ""
+"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`."
+msgstr ""
+"Téléchargez le fichier DMG et ouvrez-le. Faites ensuite glisser l'icône "
+"novelWriter dans le dossier :guilabel:`Applications` sur la droite. Cela "
+"l'installera dans votre :guilabel:`Applications`."
+
+#: ../../source/int_started.rst:123
+msgid ""
+"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."
+msgstr ""
+"La première fois que vous essayez de le lancer, il vous dira que le bundle ne "
+"peut pas être vérifié, appuyez simplement sur le bouton :guilabel:`Open` pour "
+"ajouter une exception."
+
+#: ../../source/int_started.rst:125
+msgid ""
+"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."
+msgstr ""
+"Si aucun bouton :guilabel:`Open` n'apparaît dans la boîte de dialogue, "
+"relancez l'application en faisant un clic droit sur l'application dans le "
+"Finder et en sélectionnant :guilabel:`Open` dans le menu contextuel."
+
+#: ../../source/int_started.rst:129
+msgid ""
+"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."
+msgstr ""
+"Vous pouvez également accéder au menu contextuel par un clic d'option si vous "
+"disposez d'une souris à un bouton. Pour ce faire, maintenez la touche option "
+"de votre clavier enfoncée et cliquez sur l'application dans le Finder."
+
+#: ../../source/int_started.rst:133
+msgid ""
+"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 a commercial "
+"software signing certificate."
+msgstr ""
+"Le DMG de novelWriter n'est pas signé parce qu'Apple ne fournit actuellement "
+"aucun moyen aux projets open source à but non lucratif de signer correctement "
+"leurs programmes d'installation. Le projet novelWriter n'a pas les moyens de "
+"payer des certificats de signature de logiciels commerciaux."
+
+#: ../../source/int_started.rst:141
+msgid "Installing from PyPi"
+msgstr "Installation à partir de PyPi"
+
+#: ../../source/int_started.rst:143
+msgid ""
+"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."
+msgstr ""
+"novelWriter est également disponible sur le Python Package Index, ou PyPi_. "
+"Cette méthode d'installation fonctionne sur tous les systèmes d'exploitation "
+"compatibles avec un environnement Python approprié."
+
+#: ../../source/int_started.rst:146
+msgid ""
+"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."
+msgstr ""
+"Pour installer à partir de PyPi, vous devez d'abord avoir les commandes "
+"``python`` et ``pip`` disponibles sur votre système. Vous pouvez télécharger "
+"Python depuis `python.org`_. Il est recommandé d'installer la dernière "
+"version. Si vous êtes sous Windows, assurez-vous également de sélectionner "
+"l'option « Add Python to PATH » pendant l'installation."
+
+#: ../../source/int_started.rst:151
+msgid "To install novelWriter from PyPi, use the following command:"
+msgstr "Pour installer novelWriter depuis PyPi, utilisez la commande suivante :"
+
+#: ../../source/int_started.rst:157
+msgid "To upgrade an existing installation, use:"
+msgstr "Pour mettre à jour une installation existante, utilisez :"
+
+#: ../../source/int_started.rst:163
+msgid ""
+"When installing via pip, novelWriter can be launched from command line with:"
+msgstr ""
+"Lors de l'installation via pip, novelWriter peut être lancé depuis la ligne "
+"de commande avec :"
+
+#: ../../source/int_started.rst:169
+msgid ""
+"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."
+msgstr ""
+"Assurez-vous que l'emplacement d'installation de pip est dans votre variable "
+"PATH. Ce n'est pas toujours le cas par défaut, et vous pouvez alors obtenir "
+"une erreur « Not Found » lorsque vous exécutez la commande ``novelwriter``."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Le programme d'installation de novelWriter n'est pas signé parce que "
+#~ "Microsoft ne fournit pas actuellement un moyen pour les projets open "
+#~ "source à but non lucratif de signer correctement leurs programmes "
+#~ "d'installation. Le projet novelWriter n'a pas les moyens de payer des "
+#~ "certificats de signature de logiciels commerciaux. Vous verrez donc un "
+#~ "avertissement supplémentaire à ce sujet lorsque vous téléchargerez et "
+#~ "exécuterez le programme d'installation."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Il se peut que vous deviez utiliser les paquets Ubuntu 20.04 (focal) pour "
+#~ "Debian 11 ou antérieures. Les paquets Ubuntu plus récents utilisent un "
+#~ "algorithme de compression différent qui peut ne pas être pris en charge."

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

@@ -0,0 +1,319 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2025-01-26 16:54+0100\n"
+"Last-Translator: \n"
+"Language-Team: \n"
+"Language: fr\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\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 compared to Libre "
+"Office Writer rules."
+msgstr ""
+"Il s'agit d'une vue d'ensemble de la manière dont les mots et autres décomptes "
+"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 is 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 "
+"**Outil 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 courts (-) et longs (—) 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 en-têtes 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'en-tê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 en-tê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 en-tê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 en-tê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,350 @@
+# French translations for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2025-01-28 21:52+0100\n"
+"PO-Revision-Date: 2025-01-28 21:59+0100\n"
+"Last-Translator: \n"
+"Language-Team: \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:23
+msgid "Linux and MacOS"
+msgstr "Linux et MacOS"
+
+#: ../../source/more_customise.rst:25
+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:30
+msgid "Windows"
+msgstr "Windows"
+
+#: ../../source/more_customise.rst:32
+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:35
+msgid "**Install Tool**"
+msgstr "**Outil d'installation**"
+
+#: ../../source/more_customise.rst:37
+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:42
+msgid "**Manual Install**"
+msgstr "**Installation manuelle**"
+
+#: ../../source/more_customise.rst:44
+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:48
+msgid "``C:\\Users\\<USER>\\AppData\\Local\\enchant\\hunspell``"
+msgstr "``C:\\Users\\<USER>\\AppData\\Local\\enchant\\hunspell``"
+
+#: ../../source/more_customise.rst:50
+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:53
+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:56
+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:60
+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:67
+msgid "Syntax and GUI Themes"
+msgstr "Syntaxe et thèmes de l'interface graphique"
+
+#: ../../source/more_customise.rst:69
+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:73
+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:76
+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:78
+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:80
+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:83
+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:86
+msgid ""
+"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 ``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:`a_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 "
+"d'interface graphique, et ``icons`` pour les thèmes d'icônes. Ces dossiers "
+"sont créés la première fois que vous démarrez novelWriter."
+
+#: ../../source/more_customise.rst:91
+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:94
+msgid ""
+"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."
+msgstr ""
+"La valeur ``icontheme`` a été ajoutée aux thèmes GUI. Assurez-vous de "
+"définir cette valeur dans les thèmes personnalisés existants. Sinon, "
+"novelWriter essaiera de deviner votre thème d'icônes, et ne choisira peut-"
+"être pas le plus approprié."
+
+#: ../../source/more_customise.rst:101
+msgid "Custom GUI and Icons Theme"
+msgstr "Thème d'interface graphique et d'icônes personnalisé"
+
+#: ../../source/more_customise.rst:103
+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:141
+msgid ""
+"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."
+msgstr ""
+"Dans la section Main, vous devez au moins définir les paramètres ``name`` "
+"et ``icontheme``. Le paramètre ``icontheme`` doit correspondre à l'un des "
+"thèmes d'icônes internes, soit ``typicons_light`` ou ``typicons_dark``, "
+"soit à un thème d'icônes dans votre répertoire d'icônes personnalisé. Le "
+"paramètre doit correspondre au nom du dossier du thème d'icônes."
+
+#: ../../source/more_customise.rst:146
+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."
+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``."
+
+#: ../../source/more_customise.rst:152
+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:157
+msgid "Custom Syntax Theme"
+msgstr "Syntaxe des thèmes personnalisés"
+
+#: ../../source/more_customise.rst:159
+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:193
+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:197
+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:200
+msgid "The ``shortcode`` syntax colour entry was added."
+msgstr "Le paramètre de couleur ``shortcode`` a été ajouté."
+
+#: ../../source/more_customise.rst:203
+msgid "The ``optional`` syntax colour entry was added."
+msgstr "Le paramètre de couleur ``optional`` a été ajouté."
+
+#: ../../source/more_customise.rst:206
+msgid "The ``texthighlight`` syntax colour entry was added."
+msgstr "Le paramètre de couleur ``texthighlight`` a été ajouté."
+
+#: ../../source/more_customise.rst:209
+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_projectformat.po

@@ -0,0 +1,309 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2024-12-23 17:49+0100\n"
+"Last-Translator: \n"
+"Language-Team: \n"
+"Language: fr\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../source/more_projectformat.rst:5
+msgid "Project Format Changes"
+msgstr "Modifications du format des projet"
+
+#: ../../source/more_projectformat.rst:10
+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_projectformat.rst:14
+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_projectformat.rst:19
+msgid ""
+"A full project file format specification is available in the online "
+"documentation_."
+msgstr ""
+"Une spécification complète du format de fichier du projet est disponible "
+"dans la documentation en ligne_."
+
+#: ../../source/more_projectformat.rst:22
+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_projectformat.rst:29
+msgid "**For Developers**"
+msgstr "**Pour les développeurs**"
+
+#: ../../source/more_projectformat.rst:31
+msgid ""
+"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."
+msgstr ""
+"Une description complète du format de fichier actuel est disponible dans "
+"le document :download:`File Format Spec 1.5 <fileformatspec15.pdf>`, "
+"disponible au format PDF. Ce document est destiné aux contributeurs de "
+"novelWriter, à ceux qui construisent des outils de conversion de "
+"projets, soit vers, soit à partir du format novelWriter, et à ceux qui "
+"souhaitent créer leur propre système de gabarit."
+
+#: ../../source/more_projectformat.rst:41
+msgid "Format 1.5 Changes"
+msgstr "Format 1.5 Modifications"
+
+#: ../../source/more_projectformat.rst:43
+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_projectformat.rst:45
+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_projectformat.rst:55
+msgid "Format 1.4 Changes"
+msgstr "Format 1.4 Modifications"
+
+#: ../../source/more_projectformat.rst:57
+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_projectformat.rst:61
+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_projectformat.rst:69
+msgid "Format 1.3 Changes"
+msgstr "Format 1.3 Modifications"
+
+#: ../../source/more_projectformat.rst:71
+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_projectformat.rst:73
+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_projectformat.rst:76
+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_projectformat.rst:80
+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_projectformat.rst:83
+msgid "**Title Pages**"
+msgstr "**Pages de titres**"
+
+#: ../../source/more_projectformat.rst:85
+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:`a_fmt_head`."
+msgstr ""
+"Le formatage du titre de niveau 1 sur la page de titre doit être modifié "
+"de ``# Texte du titre`` à ``# ! Texte du titre`` afin de conserver la "
+"fonctionnalité précédente. Voir :ref:`a_fmt_head`."
+
+#: ../../source/more_projectformat.rst:87
+msgid ""
+"Any text that was previously centred on the page must be manually "
+"centred using the text alignment feature. See :ref:`a_fmt_align`."
+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:"
+"`a_fmt_align`."
+
+#: ../../source/more_projectformat.rst:90
+msgid "**Unnumbered Chapters**"
+msgstr "**Chapitres non numérotés**"
+
+#: ../../source/more_projectformat.rst:92
+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:`a_fmt_head`."
+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 de chapitre`` au lieu de `## Nom de 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:`a_fmt_head`."
+
+#: ../../source/more_projectformat.rst:97
+msgid "**Plain Pages**"
+msgstr "**Pages vierges**"
+
+#: ../../source/more_projectformat.rst:99
+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:`a_fmt_break`."
+msgstr ""
+"La mise en page appelée « Page vierge » 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 pages fraîches peuvent être placées n'importe où "
+"dans le texte avec le code ``[NEW PAGE]``. Voir :ref:`a_fmt_break`."
+
+#: ../../source/more_projectformat.rst:107
+msgid "Format 1.2 Changes"
+msgstr "Format 1.2 Modifications"
+
+#: ../../source/more_projectformat.rst:109
+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_projectformat.rst:111
+msgid ""
+"With this format, the way auto-replace entries were stored in the main "
+"project XML file changed."
+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é."
+
+#: ../../source/more_projectformat.rst:117
+msgid "Format 1.1 Changes"
+msgstr "Format 1.1 Modifications"
+
+#: ../../source/more_projectformat.rst:119
+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_projectformat.rst:121
+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_projectformat.rst:124
+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."
+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."
+
+#: ../../source/more_projectformat.rst:131
+msgid "Format 1.0 Changes"
+msgstr "Format 1.0 Modifications"
+
+#: ../../source/more_projectformat.rst:133
+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/project_manuscript.po

@@ -0,0 +1,531 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 11:05+0100\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/project_manuscript.rst:5
+msgid "Building the Manuscript"
+msgstr "Compiler le manuscrit"
+
+#: ../../source/project_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/project_manuscript.rst:15
+msgid ""
+"This tool is new for version 2.1. A simpler tool was used for earlier versions. "
+"The simpler tool only allows you to define a single set of options for the "
+"build, but otherwise had much the same functionality."
+msgstr ""
+"Cet outil est nouveau pour la version 2.1. Un outil plus simple était utilisé "
+"pour les versions précédentes. Cet outil plus simple ne vous permettait de "
+"définir qu'un seul ensemble d'options pour la compilation, mais il offrait à "
+"peu près les mêmes fonctionnalités."
+
+#: ../../source/project_manuscript.rst:23
+msgid "The Manuscript Build Tool"
+msgstr "L'outil de compilation de manuscrit"
+
+#: ../../source/project_manuscript.rst:28
+msgid "The **Manuscript Build** tool main window."
+msgstr "La fenêtre principale de l'outil **Compiler le manuscrit**."
+
+#: ../../source/project_manuscript.rst:30
+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/project_manuscript.rst:36
+msgid "Outline and Word Counts"
+msgstr "Plan et nombre de mots"
+
+#: ../../source/project_manuscript.rst:41
+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/project_manuscript.rst:43
+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/project_manuscript.rst:46
+msgid ""
+"A collapsible panel of word and character counts are also available below the "
+"preview document. 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 escamotable indiquant le nombre de mots et de caractères est "
+"également disponible sous le document 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/project_manuscript.rst:50
+msgid "For a detailed description on how they are counted, see :ref:`a_counting`."
+msgstr ""
+"Pour une description détaillée de la façon dont ils sont comptés, voir :ref:"
+"`a_counting`."
+
+#: ../../source/project_manuscript.rst:56
+msgid "Build Settings"
+msgstr "Paramètres de compilation"
+
+#: ../../source/project_manuscript.rst:58
+msgid ""
+"Each build definition can be edited 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 ""
+"Chaque définition de construction peut être éditée en l'ouvrant dans la boîte "
+"de dialogue **Paramètres de construction 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/project_manuscript.rst:63
+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 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 construction 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 vos réglages en appuyant sur le bouton :guilabel:`Aperçu` dans la "
+"fenêtre principale **Compiler le manuscrit**. Lorsque vous êtes satisfait du "
+"résultat, vous pouvez fermer les paramètres."
+
+#: ../../source/project_manuscript.rst:70
+msgid "Document Selection"
+msgstr "Sélection des documents"
+
+#: ../../source/project_manuscript.rst:75
+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/project_manuscript.rst:77
+msgid ""
+"The **Selections** page of the **Manuscript Build Settings** dialog allows you "
+"to fine tune which documents are included in the build. They are indicated by a "
+"green arrow 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élection** de la boîte de dialogue **Paramètres de construction du "
+"manuscrit** vous permet d'affiner les documents inclus dans la construction. "
+"Ils sont indiqués par une icône de flèche verte 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 racine "
+"à inclure."
+
+#: ../../source/project_manuscript.rst:82
+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/project_manuscript.rst:86
+msgid ""
+"In the figure, the green arrow icon and the blue pin icon indicates which "
+"documents are included, and the red forbidden icon indicates that a document is "
+"explicitly excluded."
+msgstr ""
+"Dans la figure, l'icône de la flèche verte et l'icône de l'épingle bleue "
+"indiquent les documents inclus, et l'icône de l'interdiction rouge indique "
+"qu'un document est explicitement exclu."
+
+#: ../../source/project_manuscript.rst:93
+msgid "Formatting Headings"
+msgstr "Mise en forme des en-têtes"
+
+#: ../../source/project_manuscript.rst:98
+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/project_manuscript.rst:100
+msgid ""
+"The **Headings** page of the **Manuscript Build Settings** dialog allows you to "
+"set how the headings in your :term:`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 construction du "
+"manuscrit** vous permet de définir le format des titres de vos :term:`Documents "
+"du roman`. Par défaut, le titre est simplement copié tel quel, comme l'indique "
+"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/project_manuscript.rst:105
+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/project_manuscript.rst:110
+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. ``{Titre}`` sera toujours remplacé par le texte de l'en-"
+"tête de vos documents."
+
+#: ../../source/project_manuscript.rst:113
+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/project_manuscript.rst:118
+msgid "Scene Separators"
+msgstr "Séparateurs de scènes"
+
+#: ../../source/project_manuscript.rst:120
+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 switch on 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:"
+"`Cacher`, qui les ignorera complètement. En d'autres termes, il n'y aura même "
+"pas d'espace supplémentaire inséré."
+
+#: ../../source/project_manuscript.rst:125
+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."
+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."
+
+#: ../../source/project_manuscript.rst:133
+msgid "Hard and Soft Scenes"
+msgstr "Scènes dures et douces"
+
+#: ../../source/project_manuscript.rst:135
+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/project_manuscript.rst:139
+msgid ""
+"See :ref:`a_fmt_head` for more info on how to format headings in your text."
+msgstr ""
+"Voir :ref:`a_fmt_head` pour plus d'informations sur la façon de formater les "
+"titres dans votre texte."
+
+#: ../../source/project_manuscript.rst:143
+msgid "Output Settings"
+msgstr "Paramètres de sortie"
+
+#: ../../source/project_manuscript.rst:145
+msgid ""
+"The **Content**, **Format** and **Output** pages of the **Manuscript Build "
+"Settings** dialog control a number of other settings for the output. Some of "
+"these only apply to specific output formats, which is indicated by the section "
+"headings on the settings pages."
+msgstr ""
+"Les pages **Contenu**, **Format** et **Sortie** de la boîte de dialogue "
+"**Paramètres de construction du manuscrit** contrôlent un certain nombre "
+"d'autres paramètres pour la sortie. Certains d'entre eux ne s'appliquent qu'à "
+"des formats de sortie spécifiques, ce qui est indiqué par les titres de section "
+"sur les pages de paramètres."
+
+#: ../../source/project_manuscript.rst:153
+msgid "Building Manuscript Documents"
+msgstr "Création des manuscrits"
+
+#: ../../source/project_manuscript.rst:158
+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/project_manuscript.rst:160
+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/project_manuscript.rst:164
+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/project_manuscript.rst:168
+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/project_manuscript.rst:173
+msgid "File Formats"
+msgstr "Formats de fichiers"
+
+#: ../../source/project_manuscript.rst:175
+msgid "Currently, four document formats are supported."
+msgstr "Actuellement, quatre formats de documents sont pris en charge."
+
+#: ../../source/project_manuscript.rst:177
+msgid "Open Document Format"
+msgstr "Open Document Format"
+
+#: ../../source/project_manuscript.rst:178
+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/project_manuscript.rst:182
+msgid "Microsoft Word Document Format"
+msgstr "Format de document Microsoft Word"
+
+#: ../../source/project_manuscript.rst:183
+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/project_manuscript.rst:186
+msgid "Portable Document Format (PDF)"
+msgstr "Format de document portable (PDF)"
+
+#: ../../source/project_manuscript.rst:187
+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/project_manuscript.rst:191
+msgid "novelWriter HTML"
+msgstr "novelWriter HTML"
+
+#: ../../source/project_manuscript.rst:192
+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/project_manuscript.rst:196
+msgid "Standard/Extended Markdown"
+msgstr "Markdown standard/étendu"
+
+#: ../../source/project_manuscript.rst:197
+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/project_manuscript.rst:201
+msgid "novelWriter Markup"
+msgstr "novelWriter Markup"
+
+#: ../../source/project_manuscript.rst:202
+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/project_manuscript.rst:209
+msgid "Microsoft Word and PDF output options were added."
+msgstr "Les options de sortie Microsoft Word et PDF ont été ajoutées."
+
+#: ../../source/project_manuscript.rst:213
+msgid "Additional Formats"
+msgstr "Formats supplémentaires"
+
+#: ../../source/project_manuscript.rst:215
+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. For HTML, also the accompanying CSS styles used by the "
+"preview are included."
+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. Pour le HTML, les styles CSS utilisés par la prévisualisation sont "
+"également inclus."
+
+#: ../../source/project_manuscript.rst:219
+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/project_manuscript.rst:223
+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/project_manuscript.rst:230
+msgid "Printing"
+msgstr "Impression"
+
+#: ../../source/project_manuscript.rst:232
+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/project_manuscript.rst:238
+msgid ""
+"The paper format should in all cases default to whatever your system default "
+"is. If you want to change it, you have to select it from the **Print Preview** "
+"dialog."
+msgstr ""
+"Dans tous les cas, 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**."
+
+#~ msgid "Print and PDF"
+#~ msgstr "Imprimer et PDF"

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

@@ -0,0 +1,588 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 11:14+0100\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/project_references.rst:5
+msgid "Tags and References"
+msgstr "Tags et références"
+
+#: ../../source/project_references.rst:7
+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 :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."
+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 :term:`notes de projet` que "
+"vous pouvez marquer comme représentant ces éléments de l'histoire en "
+"créant un :term:`tag`. Lorsque vous souhaitez lier un élément de votre "
+"histoire à une note définissant un élément de l'histoire, comme un "
+"personnage, vous créez un :term:`référence` qui renvoie à cette "
+"étiquette. Vous pouvez également créer des liens croisés entre les notes "
+"de votre projet de la même manière."
+
+#: ../../source/project_references.rst:13
+msgid ""
+"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."
+msgstr ""
+"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, c'est pourquoi ce chapitre vise à expliquer plus en détail "
+"comment utiliser ce système de balises et de références."
+
+#: ../../source/project_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 de balises 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 de balises "
+"et de références."
+
+#: ../../source/project_references.rst:28
+msgid "Metadata in novelWriter"
+msgstr "Métadonnées dans novelWriter"
+
+#: ../../source/project_references.rst:30
+msgid ""
+"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."
+msgstr ""
+"La structure de votre projet novelWriter est déduite des :term:`en-têtes` "
+"des documents, et non des documents eux-mêmes. Voir :ref:`a_struct_heads` "
+"pour plus de détails. Par conséquent, les métadonnées sont également "
+"associées aux en-têtes, et non aux documents directement."
+
+#: ../../source/project_references.rst:34
+msgid ""
+"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."
+msgstr ""
+"Si vous divisez votre projet en documents distincts pour chaque scène, "
+"cette distinction peut ne pas avoir d'importance. Cependant, "
+"l'utilisation de documents à une échelle structurelle plus large présente "
+"plusieurs avantages lorsque vous démarrez votre projet. Par exemple, il "
+"peut être plus judicieux de définir toutes les scènes, et même les "
+"chapitres, dans un seul document au départ, ou peut-être un document par "
+"acte. Vous pouvez par la suite diviser ces documents en utilisant la "
+"fonction de division de document. Voir :ref:`a_ui_tree_split_merge` pour "
+"plus de détails."
+
+#: ../../source/project_references.rst:40
+msgid ""
+"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. Or, you can lay "
+"out your plot in a single document and have a tag for each plot stage "
+"under separate headings."
+msgstr ""
+"Vous pouvez faire de même avec vos notes. Vous pouvez traiter chaque en-"
+"tête comme un élément indépendant de vos notes qui peut être référencé "
+"ailleurs. Ainsi, vous pouvez rassembler tous vos personnages mineurs ou "
+"de second plan dans un seul fichier de notes, tout en étant en mesure de "
+"les référencer individuellement en les séparant par des en-têtes et en "
+"leur attribuant à chacun une balise. Vous pouvez également présenter "
+"votre intrigue dans un seul document et attribuer une balise à chaque "
+"étape de l'intrigue dans des rubriques distinctes."
+
+#: ../../source/project_references.rst:50
+msgid "How to Use Tags"
+msgstr "Comment utiliser les tags"
+
+#: ../../source/project_references.rst:52
+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`` :term:`keyword`."
+msgstr ""
+"Un « tag » dans novelWriter est un mot ou une phrase que vous définissez "
+"comme appartenant à une rubrique. Les balises sont définies à l'aide de "
+"la commande ``@tag`` :term:`mot-clé`."
+
+#: ../../source/project_references.rst:55
+msgid "The basic format of a tag is ``@tag: tagName``."
+msgstr "Le format de base d'une balise est ``@tag: NomDuTag``."
+
+#: ../../source/project_references.rst:57
+msgid "An alternative format of a tag is ``@tag: tagName | displayName``."
+msgstr "Un autre format de balise est ``@tag: NomDuTag | NomAffiché``."
+
+#: ../../source/project_references.rst:59
+msgid "``tagName`` (Required)"
+msgstr "``NomDuTag`` (Requis)"
+
+#: ../../source/project_references.rst:60
+msgid ""
+"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."
+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 à ce document ou à une "
+"section du document."
+
+#: ../../source/project_references.rst:63
+msgid "``displayName`` (Optional)"
+msgstr "``NomAffiché`` (Optionnel)"
+
+#: ../../source/project_references.rst:64
+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 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."
+msgstr ""
+"Il s'agit d'un nom d'affichage facultatif utilisé pour la balise. 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 ``NomDuTag`` est utilisée dans ces titres, mais si "
+"vous utilisez un format abrégé en interne dans votre projet, vous pouvez "
+"utiliser ceci pour spécifier un format plus approprié pour les titres de "
+"votre manuscrit."
+
+#: ../../source/project_references.rst:69
+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 balise** par rubrique, et la balise "
+"doit être unique dans **tous** les documents du projet."
+
+#: ../../source/project_references.rst:72
+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."
+msgstr ""
+"Une fois qu'une balise 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 balises apparaîtront également dans la **Vue en plan** et dans "
+"le panneau des références sous le visualiseur de documents lorsqu'un "
+"document est ouvert dans le visualiseur."
+
+#: ../../source/project_references.rst:76
+msgid ""
+"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."
+msgstr ""
+"Le surligneur syntaxique vous indiquera que le mot-clé est correctement "
+"utilisé et que la balise est autorisée, c'est-à-dire qu'elle est unique. "
+"Les balises dupliquées devraient être détectées si l'index est à jour. "
+"Une balise non valide est signalée par une ligne verte et ne reçoit pas "
+"la même couleur que les balises valides."
+
+#: ../../source/project_references.rst:81
+msgid ""
+"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."
+msgstr ""
+"La balise est la seule partie de ces notes que novelWriter utilise. Le "
+"reste du contenu du document est là pour que vous puissiez l'utiliser "
+"comme bon vous semble. Bien entendu, le contenu des documents peut être "
+"ajouté au manuscrit ou à un document de synthèse. Si vous souhaitez "
+"compiler un seul document de toutes vos notes, vous pouvez le faire à "
+"partir de l'outil **Compiler le manuscrit**."
+
+#: ../../source/project_references.rst:88
+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 balises ne sont plus sensibles à la casse. Les balises sont affichées "
+"par défaut avec la majuscule utilisée lors de la définition de la balise, "
+"mais vous n'êtes pas obligé d'utiliser la même majuscule lorsque vous y "
+"faites référence ultérieurement."
+
+#: ../../source/project_references.rst:94
+msgid "Tags can have an optional display name for manuscript builds."
+msgstr ""
+"Les balises peuvent avoir un nom d'affichage facultatif pour les "
+"constructions de manuscrits."
+
+#: ../../source/project_references.rst:98
+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 balises 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/project_references.rst:101
+msgid "Example of a heading with a tag for a character of the story:"
+msgstr "Exemple d'un titre avec une tag pour un personnage de l'histoire :"
+
+#: ../../source/project_references.rst:111
+msgid ""
+"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`."
+msgstr ""
+"Lorsque cela est fait dans un document dans un :term:`Dossier racine` de "
+"type « Personnages “, la balise est automatiquement traitée comme un "
+"caractère disponible dans votre projet avec la valeur ” Jane », et vous "
+"pourrez y faire référence dans n'importe lequel de vos autres documents "
+"en utilisant les mots-clés de référence pour les personnages. Il "
+"apparaîtra également dans l'onglet Personnage du panneau Référence sous "
+"le visualiseur de document, et dans le menu d'auto-complétion de "
+"référence dans l'éditeur lorsque vous remplissez des références. Voir :"
+"ref:`a_ui_view` et :ref:`a_references_completer`."
+
+#: ../../source/project_references.rst:118
+msgid ""
+"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."
+msgstr ""
+"C'est le type de dossier racine qui définit la catégorie d'éléments de "
+"l'histoire sous laquelle la balise est indexée. Voir la section :ref:"
+"`a_proj_roots` pour une vue d'ensemble des types de dossiers racines "
+"disponibles. Ils sont également abordés dans la section suivante."
+
+#: ../../source/project_references.rst:126
+msgid "How to Use References"
+msgstr "Comment utiliser les références"
+
+#: ../../source/project_references.rst:128
+msgid ""
+"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."
+msgstr ""
+"Chaque en-tête de n'importe quel niveau de votre projet peut contenir des "
+"références à des balises définies dans les notes du projet. Ces "
+"références sont rassemblées par l'indexeur et utilisées pour générer la "
+"**Vue d'ensemble**, entre autres choses."
+
+#: ../../source/project_references.rst:132
+msgid ""
+"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."
+msgstr ""
+"Les références sont définies sous la forme d'un :term:`mot-clé` et d'une "
+"liste de balises correspondantes. Les mots-clés valides sont listés ci-"
+"dessous. Le format d'une ligne de référence est ``@keyword: value1, "
+"[value2] ... [valeurN]``. Tous les mots-clés de référence autorisent des "
+"valeurs multiples."
+
+#: ../../source/project_references.rst:136
+msgid "``@pov``"
+msgstr "``@pov``"
+
+#: ../../source/project_references.rst:137
+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 balise note dans un dossier racine de type **Personnages**."
+
+#: ../../source/project_references.rst:140
+msgid "``@focus``"
+msgstr "``@focus``"
+
+#: ../../source/project_references.rst:141
+msgid ""
+"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."
+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 balise note dans un dossier "
+"racine de type **Personnages**."
+
+#: ../../source/project_references.rst:145
+msgid "``@char``"
+msgstr "``@char``"
+
+#: ../../source/project_references.rst:146
+msgid ""
+"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/project_references.rst:150
+msgid "``@plot``"
+msgstr "``@plot``"
+
+#: ../../source/project_references.rst:151
+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 balise note dans un dossier racine de type "
+"**Intrigue**."
+
+#: ../../source/project_references.rst:154
+msgid "``@time``"
+msgstr "``@time``"
+
+#: ../../source/project_references.rst:155
+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 balise note dans un dossier racine de type **Chronologie**."
+
+#: ../../source/project_references.rst:158
+msgid "``@location``"
+msgstr "``@location``"
+
+#: ../../source/project_references.rst:159
+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 "
+"balise note dans un dossier racine de type **lieux**."
+
+#: ../../source/project_references.rst:162
+msgid "``@object``"
+msgstr "``@object``"
+
+#: ../../source/project_references.rst:163
+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/project_references.rst:166
+msgid "``@entity``"
+msgstr "``@entity``"
+
+#: ../../source/project_references.rst:167
+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 balise "
+"note dans un dossier racine de type **Entités**."
+
+#: ../../source/project_references.rst:170
+msgid "``@custom``"
+msgstr "``@custom``"
+
+#: ../../source/project_references.rst:171
+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/project_references.rst:174
+msgid "``@mention``"
+msgstr "``@mention``"
+
+#: ../../source/project_references.rst:175
+msgid ""
+"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."
+msgstr ""
+"Tout ce qui est mentionné, mais qui n'est pas présent dans la section "
+"actuelle. Il est destiné aux cas où vous révélez des détails sur un "
+"personnage ou un lieu dans une scène sans qu'il en fasse partie. Cela "
+"peut être utile pour vérifier la cohérence ultérieurement. N'importe "
+"quelle balise dans n'importe quel dossier de notes racine peut être "
+"listée sous mentions."
+
+#: ../../source/project_references.rst:180
+msgid "``@story``"
+msgstr "``@story``"
+
+#: ../../source/project_references.rst:181
+msgid ""
+"This is used when referencing a Novel Document, like a scene or chapter, "
+"from somewhere else in your project."
+msgstr ""
+"Cette fonction est utilisée pour référencer un document de roman, comme "
+"une scène ou un chapitre, à partir d'un autre endroit de votre projet."
+
+#: ../../source/project_references.rst:184
+msgid ""
+"The syntax highlighter will alert the user that the tags and references "
+"are used correctly, and that the tags referenced exist."
+msgstr ""
+"L'outil de mise en évidence de la syntaxe avertit l'utilisateur que les "
+"balises et les références sont utilisées correctement et que les balises "
+"référencées existent."
+
+#: ../../source/project_references.rst:189
+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 balises 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/project_references.rst:195
+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 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."
+msgstr ""
+"Si vous ajoutez une référence dans l'éditeur à une balise qui n'existe "
+"pas encore, vous pouvez cliquer dessus avec le bouton droit de la souris "
+"et sélectionner **Créer une note pour la balise**. Cela générera "
+"automatiquement une nouvelle note de projet avec la nouvelle balise "
+"définie. Pour que cela soit possible, un dossier racine pour cette "
+"catégorie de références doit déjà exister."
+
+#: ../../source/project_references.rst:200
+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/project_references.rst:205
+msgid ""
+"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."
+msgstr ""
+"Les notes de projet 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 voulez "
+"pouvoir naviguer d'une note à l'autre en cliquant, ou bien sûr si vous "
+"voulez simplement mettre en évidence que deux notes sont liées."
+
+#: ../../source/project_references.rst:211
+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/project_references.rst:215
+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/project_references.rst:234
+msgid "The References Auto-Completer"
+msgstr "L'auto-complétion des références"
+
+#: ../../source/project_references.rst:236
+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 de balise ou de "
+"référence à ajouter, puis, après l'ajout de ``:``, des références à "
+"partir de la liste des balises que vous avez déjà définies."
+
+#: ../../source/project_references.rst:240
+msgid ""
+"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."
+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. De nouvelles "
+"références peuvent être créées en cliquant dessus avec le bouton droit de "
+"la souris et en sélectionnant **Créer une note pour le tag** dans le menu."

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

@@ -0,0 +1,340 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 11:10+0100\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/project_structure.rst:5
+msgid "Novel Structure"
+msgstr "Structure du roman"
+
+#: ../../source/project_structure.rst:7
+msgid "This chapter covers the structure of a novel project."
+msgstr "Ce chapitre traite de la structure d'un projet de roman."
+
+#: ../../source/project_structure.rst:9
+msgid ""
+"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."
+msgstr ""
+"Il existe deux types de documents dans un projet, les **Documents de "
+"roman** et les **Notes de projet**. Les documents inédits actifs ne "
+"peuvent se trouver que dans un dossier racine de type **Nouveau**. Vous "
+"pouvez également les déplacer vers **Archives** et **Corbeille** bien "
+"sûr, où ils deviennent inactifs."
+
+#: ../../source/project_structure.rst:13
+msgid ""
+"The project tree can distinguish between the different heading levels of "
+"the novel documents using coloured icons, and optionally add emphasis on "
+"the label. Emphasis can be enabled in **Preferences**."
+msgstr ""
+"L'arborescence du projet peut distinguer les différents niveaux d'en-"
+"tête des nouveaux documents à l'aide d'icônes colorées, et "
+"éventuellement ajouter de l'emphase sur l'étiquette. L'accentuation peut "
+"être activée dans les **Préférences**."
+
+#: ../../source/project_structure.rst:21
+msgid "Importance of Headings"
+msgstr "Importance des titres"
+
+#: ../../source/project_structure.rst:23
+msgid ""
+"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."
+msgstr ""
+"Les sous-dossiers des dossiers racines n'ont aucun impact sur la "
+"structure du roman lui-même. La structure est plutôt dictée par le "
+"niveau des titres des documents."
+
+#: ../../source/project_structure.rst:26
+msgid ""
+"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."
+msgstr ""
+"Quatre niveaux de titres sont supportés, indiqués par le nombre de "
+"signes (``#``) précédant le titre. Voir aussi la section :ref:`a_fmt` "
+"pour plus de détails sur la syntaxe du balisage."
+
+#: ../../source/project_structure.rst:31
+msgid ""
+"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."
+msgstr ""
+"Les niveaux de titres ne sont pas seulement importants lors de la "
+"génération du manuscrit, ils sont également utilisés par l'indexeur lors "
+"de la construction de l'arborescence dans la **Vue d'ensemble** ainsi "
+"que dans l'**Arborescence du roman**. Chaque rubrique commence également "
+"une nouvelle région où de nouvelles étiquettes et références peuvent "
+"être définies. Voir :ref:`a_references` pour plus de détails."
+
+#: ../../source/project_structure.rst:36
+msgid ""
+"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:"
+msgstr ""
+"La syntaxe des quatre types de titres de base, et des trois types "
+"spéciaux, est listée dans la section :ref:`a_fmt_head`. La signification "
+"des quatre niveaux pour la structure de votre roman est la suivante :"
+
+#: ../../source/project_structure.rst:39
+msgid "**Heading Level 1: Partition**"
+msgstr "**Titre de niveau 1 : Section**"
+
+#: ../../source/project_structure.rst:40
+msgid ""
+"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`."
+msgstr ""
+"Ce niveau de titre signifie que le texte se réfère à un titre de niveau "
+"supérieur. Il est utile lorsque vous souhaitez diviser le manuscrit en "
+"livres, parties ou actes. Ces titres ne sont pas obligatoires. Le titre "
+"du roman lui-même doit utiliser le niveau de titre spécial ``#!`` "
+"couvert dans :ref:`a_fmt_head`."
+
+#: ../../source/project_structure.rst:44
+msgid "**Heading Level 2: Chapter**"
+msgstr "**Niveau de niveau 2 : Chapitre**"
+
+#: ../../source/project_structure.rst:45
+msgid ""
+"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."
+msgstr ""
+"Ce niveau de titre correspond à un chapitre. Chaque fois que vous voulez "
+"commencer un nouveau chapitre, vous devez ajouter un tel titre. Si vous "
+"choisissez de diviser votre manuscrit en un document par scène, vous "
+"avez besoin d'un seul document de chapitre avec seulement l'en-tête. "
+"Vous pouvez bien entendu ajouter un synopsis et des mots-clés de "
+"référence au document de chapitre. Si vous souhaitez ouvrir le chapitre "
+"par une citation ou un autre texte d'introduction qui ne fait pas partie "
+"d'une scène, c'est également dans ce document que vous placerez ce texte."
+
+#: ../../source/project_structure.rst:51
+msgid "**Heading Level 3: Scene**"
+msgstr "**Niveau de titre 3 : Scène**"
+
+#: ../../source/project_structure.rst:52
+msgid ""
+"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`."
+msgstr ""
+"Ce niveau de titre correspond à une scène. Vous devez fournir un texte "
+"de titre, mais celui-ci peut être remplacé par un séparateur de scène ou "
+"simplement ignoré lors de la construction de votre manuscrit. Si vous "
+"avez besoin de faire la distinction entre une scène dure et une scène "
+"douce, il existe un format alternatif pour les scènes que vous pouvez "
+"utiliser pour faire cette distinction. Le formatage est couvert dans :"
+"ref:`a_fmt_head`. Voir aussi :ref:`a_struct_heads_scenes`."
+
+#: ../../source/project_structure.rst:58
+msgid "**Heading Level 4: Section**"
+msgstr "**Niveau de titre 4 : Section**"
+
+#: ../../source/project_structure.rst:59
+msgid ""
+"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."
+msgstr ""
+"Ce niveau d'en-tête peut être utilisé pour diviser une scène, "
+"généralement appelée « section » dans la documentation et l'interface "
+"utilisateur. Ces sections peuvent être utiles si vous souhaitez changer "
+"de référence au milieu de la scène, par exemple si vous changez de point "
+"de vue. Vous êtes libre d'utiliser les sections comme vous le souhaitez, "
+"et vous pouvez les filtrer dans le manuscrit final."
+
+#: ../../source/project_structure.rst:64
+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:"
+"`a_fmt_break`."
+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 **Compiler "
+"le 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:`a_fmt_break`."
+
+#: ../../source/project_structure.rst:70
+msgid ""
+"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."
+msgstr ""
+"Il existe de nombreuses options pour traiter les titres de roman lors de "
+"la construction du manuscrit. Par exemple, les numéros de chapitre "
+"peuvent être appliqués automatiquement, de même que les numéros de scène "
+"si vous le souhaitez dans un projet de manuscrit. Vous pouvez également "
+"insérer des noms de personnages dans les titres de chapitres. Voir la "
+"page :ref:`a_manuscript` pour plus de détails."
+
+#: ../../source/project_structure.rst:77
+msgid ""
+"As of 2.6, the heading levels internally in novelWriter do not map "
+"directly to heading levels in manuscript documents. In manuscript "
+"documents, chapters are considered the top level heading, and partitions "
+"become plain text paragraphs with a larger font."
+msgstr ""
+"Depuis la version 2.6, les niveaux d'en-tête internes à novelWriter ne "
+"correspondent pas directement aux niveaux d'en-tête des documents "
+"manuscrits. Dans les documents manuscrits, les chapitres sont considérés "
+"comme l'en-tête de premier niveau, et les partitions deviennent des "
+"paragraphes de texte simple avec une police plus grande."
+
+#: ../../source/project_structure.rst:87
+msgid "Novel Title and Front Matter"
+msgstr "Titre du roman et page de garde"
+
+#: ../../source/project_structure.rst:89
+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 **Nouveau** avec le titre du roman. Vous devez modifier "
+"le code de format de l'en-tête de niveau 1 avec un ``!`` afin de le "
+"rendre comme un titre de document qui est exclu de toute table des "
+"matières automatique dans un document de construction de manuscrit."
+
+#: ../../source/project_structure.rst:94
+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/project_structure.rst:97
+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/project_structure.rst:113
+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/project_structure.rst:116
+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 also :ref:`a_fmt_break`."
+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 aussi :ref:`a_fmt_break`."
+
+#: ../../source/project_structure.rst:124
+msgid "Unnumbered Chapter Headings"
+msgstr "Titres des chapitres non numérotés"
+
+#: ../../source/project_structure.rst:126
+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 2 pour indiquer "
+"à l'outil de construction d'ignorer ces chapitres lors de l'ajout des "
+"numéros."
+
+#: ../../source/project_structure.rst:136
+msgid ""
+"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."
+msgstr ""
+"L'outil **Compiler le manuscrit** dispose également d'une fonction de "
+"formatage distincte pour ces titres de chapitre. Voir la page :ref:"
+"`a_manuscript` pour plus de détails. Lors de la construction d'un "
+"document d'un format qui supporte les sauts de page, les chapitres non "
+"numérotés peuvent également avoir un saut de page ajouté comme pour les "
+"chapitres normaux."
+
+#: ../../source/project_structure.rst:145
+msgid "Hard and Soft Scene Breaks"
+msgstr "Ruptures de scène dures et douces"
+
+#: ../../source/project_structure.rst:147
+msgid ""
+"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."
+msgstr ""
+"Si vous avez besoin de deux façons différentes de styliser les scènes "
+"dans votre manuscrit, par exemple si vous voulez insérer des séparateurs "
+"de scène différents pour les ruptures de scène douces et dures, il "
+"existe un format de scène alternatif disponible pour les titres de scène "
+"avec un `!` ajouté au code de formatage."
+
+#: ../../source/project_structure.rst:161
+msgid ""
+"There is a separate formatting feature for these titles in the "
+"**Manuscript Build** tool."
+msgstr ""
+"Il existe une fonction de formatage distincte pour ces titres dans "
+"l'outil **Compiler le manuscrit**."

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

@@ -0,0 +1,155 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2024-12-26 15:44+0100\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/tech_locations.rst:5
+msgid "File Locations"
+msgstr "Emplacement des fichiers"
+
+#: ../../source/tech_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/tech_locations.rst:16
+msgid "Configuration"
+msgstr "Configuration"
+
+#: ../../source/tech_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/tech_locations.rst:22 ../../source/tech_locations.rst:45
+msgid "The standard paths are:"
+msgstr "Les chemins standard sont les suivants :"
+
+#: ../../source/tech_locations.rst:24
+msgid "Linux: ``~/.config/novelwriter/novelwriter.conf``"
+msgstr "Linux : ``~/.config/novelwriter/novelwriter.conf``"
+
+#: ../../source/tech_locations.rst:25
+msgid "MacOS: ``~/Library/Preferences/novelwriter/novelwriter.conf``"
+msgstr "MacOS: ``~/Library/Preferences/novelwriter/novelwriter.conf``"
+
+#: ../../source/tech_locations.rst:26
+msgid ""
+"Windows: ``C:\\Users\\<USER>\\AppData\\Local\\novelwriter\\novelwriter."
+"conf``"
+msgstr ""
+"Windows: ``C:\\Users\\<USER>\\AppData\\Local\\novelwriter\\novelwriter."
+"conf``"
+
+#: ../../source/tech_locations.rst:28 ../../source/tech_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/tech_locations.rst:32 ../../source/tech_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/tech_locations.rst:39
+msgid "Application Data"
+msgstr "Données d'application"
+
+#: ../../source/tech_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/tech_locations.rst:47
+msgid "Linux: ``~/.local/share/novelwriter/``"
+msgstr "Linux: ``~/.local/share/novelwriter/``"
+
+#: ../../source/tech_locations.rst:48
+msgid "MacOS: ``~/Library/Application Support/novelwriter/``"
+msgstr "MacOS: ``~/Library/Application Support/novelwriter/``"
+
+#: ../../source/tech_locations.rst:49
+msgid "Windows: ``C:\\Users\\<USER>\\AppData\\Roaming\\novelwriter\\``"
+msgstr "Windows: ``C:\\Users\\<USER>\\AppData\\Roaming\\novelwriter\\``"
+
+#: ../../source/tech_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/tech_locations.rst:60
+msgid "``cache``"
+msgstr "``cache``"
+
+#: ../../source/tech_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/tech_locations.rst:63
+msgid "``icons``, ``syntax`` and ``themes``"
+msgstr "``icons``, ``syntax`` and ``themes``"
+
+#: ../../source/tech_locations.rst:64
+msgid ""
+"These folders are empty by default, but this is where the user can store "
+"custom theme files. See :ref:`a_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:`a_custom` pour "
+"plus de détails."

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

@@ -0,0 +1,281 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-28 21:52+0100\n"
+"PO-Revision-Date: 2025-01-28 21:58+0100\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/tech_source.rst:5
+msgid "Running from Source"
+msgstr "Executer depuis la source"
+
+#: ../../source/tech_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/tech_source.rst:15
+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/tech_source.rst:19
+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/tech_source.rst:31
+msgid "Dependencies"
+msgstr "Dépendances"
+
+#: ../../source/tech_source.rst:33
+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/tech_source.rst:37
+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/tech_source.rst:39
+msgid "``PyQt6`` – needed for connecting with the Qt6 libraries."
+msgstr "``PyQt6`` - nécessaire pour se connecter aux bibliothèques Qt6."
+
+#: ../../source/tech_source.rst:40
+msgid "``PyEnchant`` – needed for spell checking (optional)."
+msgstr ""
+"``PyEnchant`` - nécessaire pour la vérification orthographique "
+"(optionnel)."
+
+#: ../../source/tech_source.rst:42
+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 3.0 pour fonctionner sous Windows. Sous Linux, la "
+"version 2.0 fonctionne également très bien."
+
+#: ../../source/tech_source.rst:45
+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/tech_source.rst:53
+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/tech_source.rst:62
+msgid "Build and Install from Source"
+msgstr "Compiler et installer à partir des sources"
+
+#: ../../source/tech_source.rst:64
+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/tech_source.rst:71
+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/tech_source.rst:77
+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/tech_source.rst:83
+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/tech_source.rst:95
+msgid "Building the Translation Files"
+msgstr "Création des fichiers de traduction"
+
+#: ../../source/tech_source.rst:97
+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/tech_source.rst:102
+msgid "You can build the ``.qm`` files with:"
+msgstr "Vous pouvez construire les fichiers ``.qm`` avec :"
+
+#: ../../source/tech_source.rst:108
+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/tech_source.rst:112
+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/tech_source.rst:120
+msgid "Building the Example Project"
+msgstr "Construction du projet d'exemple"
+
+#: ../../source/tech_source.rst:122
+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/tech_source.rst:134
+msgid "Building the Documentation"
+msgstr "Élaboration de la documentation"
+
+#: ../../source/tech_source.rst:136
+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/tech_source.rst:143
+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/tech_source.rst:149
+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/tech_source.rst:152
+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/tech_source.rst:158
+msgid ""
+"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."
+msgstr ""
+"Cela créera la documentation sous forme de PDF en utilisant LaTeX. Le "
+"fichier sera ensuite copié dans le dossier assets et rendu disponible "
+"dans le menu **Aide** de novelWriter. Le système de construction de "
+"Sphinx a quelques dépendances supplémentaires lors de la construction du "
+"PDF. Veuillez consulter les `Sphinx Docs`_ pour plus de détails."

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

@@ -0,0 +1,407 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2024-12-26 17:00+0100\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/tech_storage.rst:5
+msgid "How Data is Stored"
+msgstr "Comment les données sont stockées"
+
+#: ../../source/tech_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/tech_storage.rst:13
+msgid "Project Structure"
+msgstr "Structure du projet"
+
+#: ../../source/tech_storage.rst:15
+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/tech_storage.rst:23
+msgid "Main Project File"
+msgstr "Fichier principal du projet"
+
+#: ../../source/tech_storage.rst:25
+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/tech_storage.rst:31
+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/tech_storage.rst:35
+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/tech_storage.rst:41
+msgid ""
+"A full project file format specification is available in the online "
+"documentation_."
+msgstr ""
+"Une spécification complète du format de fichier du projet est disponible "
+"dans la documentation en ligne_."
+
+#: ../../source/tech_storage.rst:45
+msgid ""
+"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."
+msgstr ""
+"Une description complète du format de fichier actuel est disponible dans "
+"le document :download:`File Format Spec 1.5 <fileformatspec15.pdf>`, "
+"disponible au format PDF."
+
+#: ../../source/tech_storage.rst:50
+msgid "Project Documents"
+msgstr "Documents de projet"
+
+#: ../../source/tech_storage.rst:52
+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/tech_storage.rst:57
+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/tech_storage.rst:63
+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/tech_storage.rst:68
+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/tech_storage.rst:73
+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/tech_storage.rst:78
+#, 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/tech_storage.rst:87
+msgid "The File Saving Process"
+msgstr "Le processus d'enregistrement des fichiers"
+
+#: ../../source/tech_storage.rst:89
+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/tech_storage.rst:96
+msgid "Project Meta Data"
+msgstr "Métadonnées du projet"
+
+#: ../../source/tech_storage.rst:98
+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/tech_storage.rst:103
+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/tech_storage.rst:108
+msgid "The Project Index"
+msgstr "L'index des projets"
+
+#: ../../source/tech_storage.rst:110
+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/tech_storage.rst:114
+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/tech_storage.rst:118
+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/tech_storage.rst:126
+msgid "Build Definitions"
+msgstr "Définitions des compilations"
+
+#: ../../source/tech_storage.rst:128
+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/tech_storage.rst:133
+msgid "Cached GUI Options"
+msgstr "Options de l'interface graphique mises en cache"
+
+#: ../../source/tech_storage.rst:135
+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/tech_storage.rst:139
+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/tech_storage.rst:144
+msgid "Custom Word List"
+msgstr "Liste des mots personnalisés"
+
+#: ../../source/tech_storage.rst:146
+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/tech_storage.rst:152
+msgid "Session Stats"
+msgstr "Statistiques de la session"
+
+#: ../../source/tech_storage.rst:154
+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/tech_storage.rst:159
+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/tech_tests.po

@@ -0,0 +1,160 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2024-12-26 17:30+0100\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/tech_tests.rst:5
+msgid "Running Tests"
+msgstr "Exécution des tests"
+
+#: ../../source/tech_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/tech_tests.rst:12
+msgid "Dependencies"
+msgstr "Dépendances"
+
+#: ../../source/tech_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/tech_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/tech_tests.rst:25
+msgid "Simple Test Run"
+msgstr "Test simple"
+
+#: ../../source/tech_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/tech_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/tech_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/tech_tests.rst:45
+msgid "Advanced Options"
+msgstr "Options avancées"
+
+#: ../../source/tech_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/tech_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/tech_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/tech_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/tech_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/tech_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/tech_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/tech_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_breakdown.po

@@ -0,0 +1,668 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 13:21+0100\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_breakdown.rst:5
+msgid "How it Works"
+msgstr "Comment ça marche"
+
+#: ../../source/usage_breakdown.rst:13
+msgid ""
+"The main features of novelWriter are listed in the :ref:`a_intro` chapter. In "
+"this chapter, we go into some more details on how they are implemented. This is "
+"intended as an overview. Later on in this documentation these features will be "
+"covered in more detail."
+msgstr ""
+"Les principales fonctionnalités de novelWriter sont listées dans le chapitre :"
+"ref:`a_intro`. Dans ce chapitre, nous entrons dans les détails de leur "
+"implémentation. Il s'agit d'une vue d'ensemble. Plus loin dans cette "
+"documentation, ces fonctionnalités seront abordées plus en détail."
+
+#: ../../source/usage_breakdown.rst:21
+msgid "GUI Layout and Design"
+msgstr "Mise en page et conception de l'interface graphique"
+
+#: ../../source/usage_breakdown.rst:23
+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/usage_breakdown.rst:26
+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/usage_breakdown.rst:31
+msgid ""
+"Most formatting features supported are available through convenient keyboard "
+"shortcuts. They are also 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:`a_kb` chapter."
+msgstr ""
+"La plupart des fonctions de formatage prises en charge sont accessibles par des "
+"raccourcis clavier pratiques. Ils sont également disponibles 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 se trouve dans le chapitre :ref:`a_kb`."
+
+#: ../../source/usage_breakdown.rst:37
+msgid ""
+"novelWriter is not intended to be a full office type word processor. It doesn't "
+"support images, links, tables, and other complex structures and objects often "
+"needed for such documents. Formatting is limited to headings, in-line basic text "
+"formats, text alignment, and a few other simple features."
+msgstr ""
+"novelWriter n'est pas conçu pour être un traitement de texte complet de type "
+"bureautique. Il ne prend pas en charge les images, les liens, les tableaux et "
+"autres structures et objets complexes souvent nécessaires pour de tels "
+"documents. Le formatage est limité aux titres, aux formats de texte de base en "
+"ligne, à l'alignement du texte et à quelques autres fonctions simples."
+
+#: ../../source/usage_breakdown.rst:42
+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/usage_breakdown.rst:48
+msgid ""
+"A number of new formatting options were added in 2.2 to allow for some special "
+"formatting cases. At the same time, a small formatting toolbar was added to the "
+"editor. It is hidden by default, but can be opened by pressing the button in the "
+"top--left corner of the editor header."
+msgstr ""
+"Un certain nombre de nouvelles options de formatage ont été ajoutées dans la "
+"version 2.2 pour permettre certains cas de formatage particuliers. En même "
+"temps, une petite barre d'outils de formatage a été ajoutée à l'éditeur. Elle "
+"est cachée par défaut, mais peut être ouverte en appuyant sur le bouton situé "
+"dans le coin supérieur gauche de l'en-tête de l'éditeur."
+
+#: ../../source/usage_breakdown.rst:54
+msgid "Project Tree and Editor View"
+msgstr "Arborescence du projet et vue de l'éditeur"
+
+#: ../../source/usage_breakdown.rst:58
+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/usage_breakdown.rst:60
+msgid ""
+"When the application is in **Project Tree View** mode, the work area of the main "
+"window 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'application est en mode **Arborescence du projet**, la zone de travail "
+"de la fenêtre principale est divisée 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/usage_breakdown.rst:64
+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/usage_breakdown.rst:70
+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 Focus** 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 Focus** est activé, tous les éléments "
+"de l'interface utilisateur autres que l'éditeur de document lui-même sont cachés."
+
+#: ../../source/usage_breakdown.rst:74
+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/usage_breakdown.rst:79
+msgid ""
+"You can now drag and drop documents from the project tree onto the editor or "
+"viewer panels to open them."
+msgstr ""
+"Vous pouvez désormais faire glisser et déposer des documents de l'arborescence "
+"du projet sur les panneaux de l'éditeur ou de l'afficheur pour les ouvrir."
+
+#: ../../source/usage_breakdown.rst:84
+msgid "Novel View and Editor View"
+msgstr "Vue du roman et vue de l'éditeur"
+
+#: ../../source/usage_breakdown.rst:88
+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/usage_breakdown.rst:90
+msgid ""
+"When the application is in **Novel Tree View** mode, the project tree is "
+"replaced by an overview of your novel structure for a specific Novel :term:`root "
+"folder`. Instead of showing individual documents, the tree now shows all "
+"headings of your novel text. This includes multiple headings within the same "
+"document."
+msgstr ""
+"Lorsque l'application est en mode **Arborescence du roman**, l'arborescence du "
+"projet est remplacée par une vue d'ensemble de la structure de votre roman pour "
+"un Novel :term:`dossier racine` spécifique. Au lieu de montrer des documents "
+"individuels, l'arbre montre maintenant tous les titres du texte de votre roman. "
+"Cela inclut les titres multiples au sein d'un même document."
+
+#: ../../source/usage_breakdown.rst:95
+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/usage_breakdown.rst:100
+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:`Outline of ...`. Vous pouvez également "
+"cliquer sur le bouton de l'icône du roman situé à côté."
+
+#: ../../source/usage_breakdown.rst:104
+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/usage_breakdown.rst:110
+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/usage_breakdown.rst:113
+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/usage_breakdown.rst:118
+msgid "Novel Outline View"
+msgstr "Vue d'ensemble du roman"
+
+#: ../../source/usage_breakdown.rst:122
+msgid "A screenshot of the Novel Outline View."
+msgstr "Capture d'écran de la vue d'ensemble du roman."
+
+#: ../../source/usage_breakdown.rst:124
+msgid ""
+"When the application is in **Novel Outline View** mode, the tree, editor and "
+"viewer are replaced by a large table that shows the entire novel structure with "
+"all the tags and references listed. Pretty much all collected meta data is "
+"available here in different columns."
+msgstr ""
+"Lorsque l'application est en mode **Vue d'ensemble du roman**, l'arbre, "
+"l'éditeur et l'afficheur sont remplacés par un grand tableau qui montre la "
+"structure complète du roman avec toutes les balises et les références listées. "
+"Pratiquement toutes les métadonnées collectées sont disponibles ici dans "
+"différentes colonnes."
+
+#: ../../source/usage_breakdown.rst:128
+msgid ""
+"You can select which novel root folder to display from the dropdown box, and you "
+"can select which columns to show or hide from the menu button. You can also "
+"rearrange the columns by drag and drop. The app remembers your column order and "
+"sizes between sessions, and for each individual project."
+msgstr ""
+"Vous pouvez sélectionner le dossier racine du roman à afficher dans la liste "
+"déroulante, et vous pouvez sélectionner les colonnes à afficher ou à masquer à "
+"l'aide du bouton de menu. Vous pouvez également réorganiser les colonnes par "
+"glisser-déposer. L'application mémorise l'ordre et la taille des colonnes d'une "
+"session à l'autre et pour chaque projet individuel."
+
+#: ../../source/usage_breakdown.rst:134
+msgid "Colour Themes"
+msgstr "Thèmes"
+
+#: ../../source/usage_breakdown.rst:136
+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/usage_breakdown.rst:139
+msgid ""
+"If you wish, you *can* create your own colour themes, and even have them added "
+"to the application. See :ref:`a_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:`a_custom_theme` pour plus de détails."
+
+#: ../../source/usage_breakdown.rst:142
+msgid ""
+"Switching the GUI colour theme does not affect the colours of the editor and "
+"viewer. They have separate colour 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 du visualiseur. Ils ont des couleurs séparées qui "
+"peuvent être sélectionnées à partir du paramètre « Thème de couleur du document "
+"» dans les **Préférences**. Elles sont séparées parce qu'il y a beaucoup plus "
+"d'options à choisir pour l'éditeur et le visualiseur."
+
+#: ../../source/usage_breakdown.rst:148
+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 le visualiseur."
+
+#: ../../source/usage_breakdown.rst:153
+msgid "Project Search"
+msgstr "Recherche dans un projet"
+
+#: ../../source/usage_breakdown.rst:155
+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."
+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. Un outil de recherche et de "
+"remplacement est disponible dans l'éditeur de documents et agit sur le document "
+"ouvert."
+
+#: ../../source/usage_breakdown.rst:163
+msgid "Switching Focus"
+msgstr "Changer de focus"
+
+#: ../../source/usage_breakdown.rst:165
+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/usage_breakdown.rst:169
+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/usage_breakdown.rst:172
+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/usage_breakdown.rst:179
+msgid "Project Layout"
+msgstr "Structure du projet"
+
+#: ../../source/usage_breakdown.rst:181
+msgid ""
+"This is a brief introduction to how you should structure your writing projects. "
+"All of this will be covered in more detail later."
+msgstr ""
+"Il s'agit d'une brève introduction à la manière dont vous devez structurer vos "
+"projets d'écriture. Nous reviendrons plus en détail sur ce sujet ultérieurement."
+
+#: ../../source/usage_breakdown.rst:184
+msgid ""
+"The main point of novelWriter is that you are free to organise your project "
+"documents as you wish into sub-folders or sub-documents, and split the text "
+"between these documents in whatever way suits you. All that matters to "
+"novelWriter is the linear order the documents appear at in the project tree (top "
+"to bottom). The chapters, scenes and sections of the novel are determined by the "
+"headings within those documents."
+msgstr ""
+"L'intérêt principal de novelWriter est que vous êtes libre d'organiser les "
+"documents de votre projet comme vous le souhaitez, dans des sous-dossiers ou des "
+"sous-documents, et de répartir le texte entre ces documents de la manière qui "
+"vous convient. Tout ce qui importe à novelWriter est l'ordre linéaire dans "
+"lequel les documents apparaissent dans l'arborescence du projet (de haut en "
+"bas). Les chapitres, scènes et sections du roman sont déterminés par les titres "
+"de ces documents."
+
+#: ../../source/usage_breakdown.rst:192
+msgid "An illustration of how heading levels correspond to the novel structure."
+msgstr ""
+"Illustration de la correspondance entre les niveaux de rubriques et la structure "
+"du roman."
+
+#: ../../source/usage_breakdown.rst:194
+msgid ""
+"The four heading levels, **Level 1** to **Level 4**, are treated as follows:"
+msgstr ""
+"Les quatre niveaux de rubrique, **niveau 1** à **niveau 4**, sont traités comme "
+"suit :"
+
+#: ../../source/usage_breakdown.rst:196
+msgid "**Level 1** is used for the novel title, and for partitions."
+msgstr "**Le niveau 1** est utilisé pour le titre du roman et pour les partitions."
+
+#: ../../source/usage_breakdown.rst:197
+msgid "**Level 2** is used for chapter tiles."
+msgstr "Le **niveau 2** est utilisé pour les titres de chapitres."
+
+#: ../../source/usage_breakdown.rst:198
+msgid "**Level 3** is used for scene titles -- optionally replaced by separators."
+msgstr ""
+"**Le niveau 3** est utilisé pour les titres de scènes, éventuellement remplacés "
+"par des séparateurs."
+
+#: ../../source/usage_breakdown.rst:199
+msgid ""
+"**Level 4** is for section titles within scenes, if such granularity is needed."
+msgstr ""
+"**Le niveau 4** est destiné aux titres de section à l'intérieur des scènes, si "
+"une telle granularité est nécessaire."
+
+#: ../../source/usage_breakdown.rst:201
+msgid ""
+"The project tree will select an icon for the document based on the first heading "
+"in it."
+msgstr ""
+"L'arborescence du projet sélectionnera une icône pour le document en fonction de "
+"la première rubrique qu'il contient."
+
+#: ../../source/usage_breakdown.rst:203
+msgid ""
+"This heading level structure is only taken into account for :term:`novel "
+"documents`. For :term:`project notes`, the heading levels have no structural "
+"meaning, and you are free to use them however you want. See :ref:`a_struct` and :"
+"ref:`a_references` for more details."
+msgstr ""
+"Cette structure de niveaux de rubriques n'est prise en compte que pour les :term:"
+"`documents du roman`. Pour :term:`notes de projet`, les niveaux d'en-tête n'ont "
+"pas de signification structurelle, et vous êtes libre de les utiliser comme vous "
+"le souhaitez. Voir :ref:`a_struct` et :ref:`a_references` pour plus de détails."
+
+#: ../../source/usage_breakdown.rst:209
+msgid ""
+"You can add documents as child items of other documents. This is often more "
+"useful than adding folders, since you anyway may want to have the chapter "
+"heading in a separate document from your individual scene documents so that you "
+"can rearrange scene documents freely without affecting chapter placement."
+msgstr ""
+"Vous pouvez ajouter des documents en tant qu'éléments enfants d'autres "
+"documents. C'est souvent plus utile que d'ajouter des dossiers, car vous pouvez "
+"de toute façon vouloir que l'en-tête de chapitre figure dans un document "
+"distinct de vos documents de scène individuels, afin de pouvoir réorganiser "
+"librement les documents de scène sans affecter l'emplacement des chapitres."
+
+#: ../../source/usage_breakdown.rst:216
+msgid ""
+"The heading levels for partitions, chapters and scenes only apply within "
+"novelWriter. When you generate your manuscript, chapters are considered as the "
+"topmost heading level, with scenes below it. Partitions are inserted as text "
+"elements in most formats."
+msgstr ""
+"Les niveaux d'en-tête pour les parties, les chapitres et les scènes ne "
+"s'appliquent qu'à novelWriter. Lorsque vous générez votre manuscrit, les "
+"chapitres sont considérés comme le niveau d'en-tête le plus élevé, et les scènes "
+"comme le niveau inférieur. Les partitions sont insérées comme des éléments de "
+"texte dans la plupart des formats."
+
+#: ../../source/usage_breakdown.rst:224
+msgid "Building a Manuscript"
+msgstr "Élaboration d'un manuscrit"
+
+#: ../../source/usage_breakdown.rst:226
+msgid ""
+"The project can at any time be assembled into a range of different formats "
+"through the **Build Manuscript** tool. Natively, novelWriter supports `Open "
+"Document`_, Microsoft Word Document (known as `Office Open XML`_), HTML5, and "
+"various flavours of Markdown. You can also generate a PDF document."
+msgstr ""
+"Le projet peut à tout moment être assemblé dans une gamme de formats différents "
+"grâce à l'outil **Compiler le manuscrit**. Nativement, novelWriter supporte "
+"`Open Document`_, Microsoft Word Document (connu sous le nom de `Office Open "
+"XML`_), HTML5, et diverses saveurs de Markdown. Vous pouvez également générer un "
+"document PDF."
+
+#: ../../source/usage_breakdown.rst:231
+msgid ""
+"The HTML5 format is suitable for conversion by a number of other tools like "
+"Pandoc_, or for importing into word processors if the Open Document or Word "
+"Document format isn't suitable. The Open Document format is supported by most "
+"office type applications, so is the Word Document format. In addition, printing "
+"is also possible."
+msgstr ""
+"Le format HTML5 peut être converti par un certain nombre d'autres outils tels "
+"que Pandoc_, ou importé dans des traitements de texte si les formats Open "
+"Document ou Word Document ne conviennent pas. Le format Open Document est pris "
+"en charge par la plupart des applications bureautiques, tout comme le format "
+"Word Document. En outre, l'impression est également possible."
+
+#: ../../source/usage_breakdown.rst:236
+msgid ""
+"For advanced processing, you can export the content of the project to a JSON "
+"file. This is useful if you want to write your own custom processing script in "
+"for instance Python, as the entire novel can be read into a Python dictionary "
+"with a couple of lines of code. The JSON file can be populated with either HTML "
+"formatted text, or with the raw text as typed it into the novel documents."
+msgstr ""
+"Pour un traitement avancé, vous pouvez exporter le contenu du projet vers un "
+"fichier JSON. Ceci est utile si vous souhaitez écrire votre propre script de "
+"traitement personnalisé, par exemple en Python, car le roman entier peut être lu "
+"dans un dictionnaire Python avec quelques lignes de code. Le fichier JSON peut "
+"être alimenté par du texte formaté en HTML ou par le texte brut tel qu'il a été "
+"tapé dans les documents du roman."
+
+#: ../../source/usage_breakdown.rst:241
+msgid "See :ref:`a_manuscript` for more details."
+msgstr "Voir :ref:`a_manuscript` pour plus de détails."
+
+#: ../../source/usage_breakdown.rst:245
+msgid ""
+"You can now define multiple build definitions in the **Build Manuscript** tool. "
+"This allows you to define specific settings for various types of draft "
+"documents, outline documents, and manuscript formats. See :ref:`a_manuscript` "
+"for more details."
+msgstr ""
+"Vous pouvez désormais définir plusieurs définitions de construction dans l'outil "
+"**Compiler un manuscrit**. Cela vous permet de définir des paramètres "
+"spécifiques pour différents types de projets de documents, de documents de "
+"synthèse et de formats de manuscrits. Voir :ref:`a_manuscript` pour plus de "
+"détails."
+
+#: ../../source/usage_breakdown.rst:253
+msgid "Project Storage"
+msgstr "Stockage du projet"
+
+#: ../../source/usage_breakdown.rst:255
+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. For a more technical description of what "
+"all the files mean and how they're organised, see the :ref:`a_storage` section."
+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. Pour une description plus technique de la signification de tous les "
+"fichiers et de leur organisation, voir la section :ref:`a_storage`."
+
+#: ../../source/usage_breakdown.rst:260
+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/usage_breakdown.rst:262
+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/usage_breakdown.rst:267
+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/usage_breakdown.rst:270
+#, fuzzy
+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/usage_breakdown.rst:276
+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/usage_breakdown.rst:283
+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 :term:`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 éditer manuellement les "
+"fichiers texte, par exemple dans le cadre d'une tâche automatisée, vous devez "
+"reconstruire le :term:`Index du projet` lorsque vous ouvrez à nouveau le projet."
+
+#: ../../source/usage_breakdown.rst:288
+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."

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

@@ -0,0 +1,562 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-27 10:21+0100\n"
+"PO-Revision-Date: 2025-01-27 11:19+0100\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_project.rst:5
+msgid "Project Views"
+msgstr "Vues du projet"
+
+#: ../../source/usage_project.rst:7
+msgid ""
+"This chapter covers in more detail the different project views available in "
+"novelWriter."
+msgstr ""
+"Ce chapitre couvre plus en détail les différentes vues de projet disponibles "
+"dans novelWriter."
+
+#: ../../source/usage_project.rst:11
+msgid "The **Project Content** tree as it appears when loading a sample project."
+msgstr ""
+"L'arborescence du **Contenu du projet** telle qu'elle apparaît lors du "
+"chargement d'un exemple de projet."
+
+#: ../../source/usage_project.rst:17
+msgid "The Project Tree"
+msgstr "L’arborescence du projet"
+
+#: ../../source/usage_project.rst:19
+msgid ""
+"The main window contains a project tree in the left-most panel. It shows the "
+"entire structure of the project, and has four columns."
+msgstr ""
+"La fenêtre principale contient l'arborescence du projet dans le panneau le plus "
+"à gauche. Elle montre la structure complète du projet et comporte quatre "
+"colonnes."
+
+#: ../../source/usage_project.rst:22
+msgid "**Column 1**"
+msgstr "**Colonne 1**"
+
+#: ../../source/usage_project.rst:23
+msgid ""
+"The first column shows the icon and label of each folder, document, or note in "
+"your project. The label is not the same as the heading title you set inside the "
+"document. However, the document's label will appear in the header above the "
+"document text itself so you know where in the project an open document belongs. "
+"The icon is selected based on the type of item, and for novel documents, the "
+"level of the first heading in the document text."
+msgstr ""
+"La première colonne affiche l'icône et l'étiquette de chaque dossier, document "
+"ou note de votre projet. L'étiquette n'est pas la même que le titre de l'en-"
+"tête que vous avez défini dans le document. Toutefois, l'étiquette du document "
+"apparaît dans l'en-tête, au-dessus du texte du document lui-même, afin que vous "
+"sachiez à quel endroit du projet appartient un document ouvert. L'icône est "
+"sélectionnée en fonction du type d'élément et, pour les nouveaux documents, du "
+"niveau du premier titre dans le texte du document."
+
+#: ../../source/usage_project.rst:29
+msgid "**Column 2**"
+msgstr "**Colonne 2**"
+
+#: ../../source/usage_project.rst:30
+msgid ""
+"The second column shows the word count of the document, or the sum of words of "
+"the child items for folders and documents with sub-documents. If the counts "
+"seem incorrect, they can be updated by rebuilding the :term:`project index` "
+"from the **Tools** menu, or by pressing :kbd:`F9`."
+msgstr ""
+"La deuxième colonne indique le nombre de mots du document, ou la somme des mots "
+"des éléments enfants pour les dossiers et les documents avec sous-documents. Si "
+"les décomptes semblent incorrects, ils peuvent être mis à jour en "
+"reconstruisant le :term:`index du projet` à partir du menu **Outils**, ou en "
+"appuyant sur :kbd:`F9`."
+
+#: ../../source/usage_project.rst:34
+msgid "**Column 3**"
+msgstr "**Colonne 3**"
+
+#: ../../source/usage_project.rst:35
+msgid ""
+"The third column indicates whether the document is considered active or "
+"inactive in the project. You can use this flag to indicate that a document is "
+"still in the project, but should not be considered an active part of it. When "
+"you run the **Build Manuscript** tool, you can include or exclude documents "
+"based on this flag. You can change this value from the right-click :term:"
+"`context menu`."
+msgstr ""
+"La troisième colonne indique si le document est considéré comme actif ou "
+"inactif dans le projet. Vous pouvez utiliser ce drapeau pour indiquer qu'un "
+"document est toujours dans le projet, mais qu'il ne doit pas être considéré "
+"comme une partie active de celui-ci. Lorsque vous exécutez l'outil **Compiler "
+"le manuscrit**, vous pouvez inclure ou exclure des documents en fonction de cet "
+"indicateur. Vous pouvez modifier cette valeur à partir du :term:`menu "
+"contextuel` en cliquant avec le bouton droit de la souris."
+
+#: ../../source/usage_project.rst:41
+msgid "**Column 4**"
+msgstr "**Colonne 4**"
+
+#: ../../source/usage_project.rst:42
+msgid ""
+"The fourth column shows the user-defined status or importance labels you've "
+"assigned to each project item. See :ref:`a_ui_tree_status` for more details on "
+"how to uses these labels. You can select these labels from the :term:`context "
+"menu`, and define them in **Project Settings**."
+msgstr ""
+"La quatrième colonne montre les étiquettes de statut ou d'importance définies "
+"par l'utilisateur que vous avez attribuées à chaque élément du projet.Voir :ref:"
+"`a_ui_tree_status` pour plus de détails sur l'utilisation de ces étiquettes."
+"Vous pouvez sélectionner ces étiquettes dans le :term:`menu contextuel`, et les "
+"définir dans **Réglages du projet**."
+
+#: ../../source/usage_project.rst:46
+msgid ""
+"Right-clicking an item in the project tree will open a context menu under the "
+"cursor, displaying a selection of actions that can be performed on the selected "
+"item."
+msgstr ""
+"Un clic droit sur un élément de l'arborescence du projet ouvre un menu "
+"contextuel sous le curseur, affichant une sélection d'actions pouvant être "
+"effectuées sur l'élément sélectionné."
+
+#: ../../source/usage_project.rst:49
+msgid "At the top of the project tree, you will find a set of buttons."
+msgstr "En haut de l'arborescence du projet, vous trouverez une série de boutons."
+
+#: ../../source/usage_project.rst:51
+msgid ""
+"The first button is a quick links button that will show you a dropdown menu of "
+"all the :term:`root folders<root folder>` in your project. Selecting one will "
+"move to that position in the tree. You can also activate this menu by pressing :"
+"kbd:`Ctrl+L`."
+msgstr ""
+"Le premier bouton est un bouton de liens rapides qui affiche un menu déroulant "
+"de tous les :term:`dossiers racines<root folder>` de votre projet. En "
+"sélectionnant l'un d'entre eux, vous vous déplacerez à la position "
+"correspondante dans l'arborescence. Vous pouvez également activer ce menu en "
+"appuyant sur :kbd:`Ctrl+L`."
+
+#: ../../source/usage_project.rst:54
+msgid ""
+"The next two buttons can be used to move items up and down in the project tree. "
+"This is the only way to move root folders."
+msgstr ""
+"Les deux boutons suivants permettent de déplacer des éléments vers le haut ou "
+"vers le bas dans l'arborescence du projet. C'est la seule façon de déplacer les "
+"dossiers racines."
+
+#: ../../source/usage_project.rst:56
+msgid ""
+"The next button opens a dropdown menu for adding new items to the tree. This "
+"includes root folders and template documents. You can also activate this "
+"dropdown menu by pressing :kbd:`Ctrl+N`."
+msgstr ""
+"Le bouton suivant ouvre un menu déroulant permettant d'ajouter de nouveaux "
+"éléments à l'arborescence. Cela inclut les dossiers racines et les documents "
+"modèles. Vous pouvez également activer ce menu déroulant en appuyant sur :kbd:"
+"`Ctrl+N`."
+
+#: ../../source/usage_project.rst:59
+msgid ""
+"The last button is a menu of further actions you can apply to the project tree."
+msgstr ""
+"Le dernier bouton est un menu d'actions supplémentaires que vous pouvez "
+"appliquer à l'arborescence du projet."
+
+#: ../../source/usage_project.rst:61
+msgid ""
+"Below the project tree you will find a small details panel showing the full "
+"information of the currently selected item. This panel also includes the latest "
+"paragraph and character counts in addition to the word count."
+msgstr ""
+"Sous l'arborescence du projet, vous trouverez un petit panneau de détails "
+"affichant les informations complètes de l'élément sélectionné. Ce panneau "
+"comprend également les derniers décomptes de paragraphes et de caractères, en "
+"plus du nombre de mots."
+
+#: ../../source/usage_project.rst:67
+msgid ""
+"If you want to set the label of a document to be the same as a header within "
+"it, you can right-click a header in the document when it is open in the editor "
+"and select :guilabel:`Set as Document Name` from the context menu."
+msgstr ""
+"Si vous souhaitez que l'étiquette d'un document soit identique à celle d'un en-"
+"tête, vous pouvez cliquer avec le bouton droit de la souris sur un en-tête du "
+"document lorsqu'il est ouvert dans l'éditeur et sélectionner :guilabel:`Définir "
+"comme nom du document` dans le menu contextuel."
+
+#: ../../source/usage_project.rst:75
+msgid "Splitting and Merging Documents"
+msgstr "Séparation et fusion de documents"
+
+#: ../../source/usage_project.rst:77
+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 **Transformer** 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/usage_project.rst:84
+msgid "Splitting Documents"
+msgstr "Découper des documents"
+
+#: ../../source/usage_project.rst:88
+msgid "The **Split Document** dialog."
+msgstr "La boîte de dialogue **découper un document**."
+
+#: ../../source/usage_project.rst:90
+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/usage_project.rst:95
+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/usage_project.rst:98
+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 :guilabel:`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 :"
+"guilabel:`Corbeille`."
+
+#: ../../source/usage_project.rst:103
+msgid "Merging Documents"
+msgstr "Fusionner des documents"
+
+#: ../../source/usage_project.rst:107
+msgid "The **Merge Documents** dialog."
+msgstr "La boîte de dialogue **Fusionner des documents**."
+
+#: ../../source/usage_project.rst:109
+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/usage_project.rst:114
+msgid ""
+"When merging documents in a folder, you only have the latter process is "
+"possible, so only the choice **Merge Documents in Folder** is available."
+msgstr ""
+"Lorsque vous fusionnez des documents dans un dossier, seul ce dernier processus "
+"est possible, de sorte que seul le choix **Fusionner les documents du dossier** "
+"est disponible."
+
+#: ../../source/usage_project.rst:117
+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."
+
+#: ../../source/usage_project.rst:124
+msgid "Document Importance and Status"
+msgstr "Importance et statut du document"
+
+#: ../../source/usage_project.rst:126
+msgid ""
+"Each document or folder in your project can have either a \"Status\" or "
+"\"Importance\" flag set. These are flags that you control and define yourself, "
+"and novelWriter doesn't use them for anything. To modify the labels, go to "
+"their respective tabs in **Project Settings**."
+msgstr ""
+"Chaque document ou dossier de votre projet peut avoir un indicateur « État » ou "
+"« Importance ». Ce sont des indicateurs que vous contrôlez et définissez vous-"
+"même, et novelWriter ne les utilise pas pour quoi que ce soit. Pour modifier "
+"les étiquettes, allez dans leurs onglets respectifs dans **Paramètres du "
+"projet**."
+
+#: ../../source/usage_project.rst:130
+msgid ""
+"The \"Status\" flag is intended to tag a :term:`novel document<novel "
+"documents>` as for instance a draft or as completed, and the \"Importance\" "
+"flag is intended to tag character notes, or other :term:`project notes`, as for "
+"instance a main, major, or minor character or story element."
+msgstr ""
+"L'indicateur « État » est destiné à marquer un :term:`document de roman<novel "
+"documents>` comme étant par exemple un brouillon ou comme étant terminé, et "
+"l'indicateur « Importance » est destiné à marquer des notes sur les "
+"personnages, ou d'autres :term:`notes de projet`, comme par exemple un "
+"personnage principal, majeur ou mineur, ou un élément de l'histoire."
+
+#: ../../source/usage_project.rst:134
+msgid ""
+"Whether a document uses a \"Status\" or \"Importance\" flag depends on which :"
+"term:`root folder` it lives in. If it's in a **Novel** type folder, it uses the "
+"\"Status\" flag, otherwise it uses an \"Importance\" flag."
+msgstr ""
+"L'utilisation de l'indicateur « État » ou « Importance » dépend du :term:"
+"`dossier racine` dans lequel se trouve le document. S'il se trouve dans un "
+"dossier de type **Roman**, il utilise l'indicateur « État », sinon il utilise "
+"l'indicateur « Importance »."
+
+#: ../../source/usage_project.rst:142
+msgid "Project Tree Drag & Drop"
+msgstr "Glisser-déposer de l'arborescence du projet"
+
+#: ../../source/usage_project.rst:144
+msgid ""
+"The project tree allows drag & drop to allow 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 **Compiler le manuscrit**."
+
+#: ../../source/usage_project.rst:150
+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/usage_project.rst:153
+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:`a_ui_tree_status`. 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 du roman** "
+"hors d'un dossier **roman**, il sera converti en **Notes 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 ” État "
+"». Voir :ref:`a_ui_tree_status`. L'ancienne valeur ne sera pas écrasée, et "
+"devrait être restaurée si vous la déplacez à nouveau à un moment donné."
+
+#: ../../source/usage_project.rst:160
+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 "
+"from 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 glissés et "
+"déposés. Si vous souhaitez les réorganiser, vous pouvez les déplacer vers le "
+"haut ou vers le bas à partir des 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/usage_project.rst:166
+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 l'afficheur pour les ouvrir."
+
+#: ../../source/usage_project.rst:172
+msgid "The Novel Tree View"
+msgstr "L'arborescence du roman"
+
+#: ../../source/usage_project.rst:176
+msgid "A screenshot of the Novel Tree View."
+msgstr "Capture d'écran de l'arborescence d'un roman."
+
+#: ../../source/usage_project.rst:178
+msgid ""
+"An alternative way to view the project structure is the novel view. You can "
+"switch to this view by selecting the :guilabel:`Novel View` button in the "
+"sidebar. This view is a simplified version of the view in the **Outline View**. "
+"It is convenient when you want to browse the structure of the story itself "
+"rather than the document files."
+msgstr ""
+"Une autre façon de visualiser la structure du projet est la vue roman. Vous "
+"pouvez passer à cette vue en sélectionnant le bouton :guilabel:`Vue Roman` dans "
+"la barre latérale. Cette vue est une version simplifiée de la vue **Vue "
+"d'ensemble du roman**. Elle est pratique lorsque vous souhaitez parcourir la "
+"structure de l'histoire elle-même plutôt que les fichiers du document."
+
+#: ../../source/usage_project.rst:185
+msgid ""
+"You cannot reorganise the entries in the novel view, or add any new documents, "
+"as that would imply restructuring the content of the document files 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 ""
+"Vous ne pouvez pas réorganiser les entrées dans la vue roman, ni ajouter de "
+"nouveaux documents, car cela impliquerait de restructurer le contenu des "
+"fichiers de 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/usage_project.rst:194
+msgid "The Novel Outline View"
+msgstr "Vue d'ensemble du roman"
+
+#: ../../source/usage_project.rst:198
+msgid "A screenshot of the Novel Outline View."
+msgstr "Capture d'écran de l'affichage du plan du roman."
+
+#: ../../source/usage_project.rst:200
+msgid ""
+"The project's **Novel Outline View** is available as another view option from "
+"the sidebar. The outline provides an overview of the novel structure, "
+"displaying a tree hierarchy of the elements of the novel, that is, the level 1 "
+"to 4 headings representing partitions, chapters, scenes and sections."
+msgstr ""
+"La **Vue d'ensemble du roman** du projet est disponible comme une autre option "
+"de vue dans la barre latérale. L'aperçu fournit une vue d'ensemble de la "
+"structure du roman, en affichant une hiérarchie arborescente des éléments du "
+"roman, c'est-à-dire les titres de niveau 1 à 4 représentant les partitions, les "
+"chapitres, les scènes et les sections."
+
+#: ../../source/usage_project.rst:205
+msgid ""
+"The document containing the heading can also be displayed as a separate column, "
+"as well as the line number where the heading is defined. Double-clicking an "
+"entry will open the corresponding document in the editor and switch to "
+"**Project Tree View** mode."
+msgstr ""
+"Le document contenant le titre peut également être affiché dans une colonne "
+"séparée, ainsi que le numéro de ligne où le titre est défini. Un double-clic "
+"sur une entrée ouvre le document correspondant dans l'éditeur et permet de "
+"passer en mode **Vue de l'arborescence du projet**."
+
+#: ../../source/usage_project.rst:209
+msgid ""
+"You can select which novel folder to display from the dropdown menu. You can "
+"optionally also choose to show a combination of all novel folders."
+msgstr ""
+"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/usage_project.rst:214
+msgid ""
+"Since the internal structure of the novel does not depend directly on the "
+"folder and document structure of the project tree, this view will not "
+"necessarily look the same, depending on how you choose to organise your "
+"documents. See the :ref:`a_struct` page for more details."
+msgstr ""
+"Comme la structure interne du roman ne dépend pas directement de la structure "
+"des dossiers et des documents de l'arborescence du projet, cette vue ne sera "
+"pas nécessairement la même, selon la façon dont vous choisissez d'organiser vos "
+"documents. Voir la page :ref:`a_struct` pour plus de détails."
+
+#: ../../source/usage_project.rst:218
+msgid ""
+"Various meta data and information extracted from :term:`tags<tag>` can be "
+"displayed in columns in the outline. A default set of such columns is visible, "
+"but you can turn on or off more columns from the menu button in the toolbar. "
+"The order of the columns can also be rearranged by dragging them to a different "
+"position. You column settings are saved between sessions on a per-project basis."
+msgstr ""
+"Diverses métadonnées et informations extraites de :term:`tags<tag>` peuvent "
+"être affichées dans des colonnes du plan. Un ensemble de ces colonnes est "
+"visible par défaut, mais vous pouvez activer ou désactiver d'autres colonnes à "
+"partir du bouton de menu de la barre d'outils. L'ordre des colonnes peut "
+"également être réorganisé en les faisant glisser vers une autre position. Les "
+"paramètres des colonnes sont sauvegardés entre les sessions, par projet."
+
+#: ../../source/usage_project.rst:225
+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/usage_project.rst:227
+msgid ""
+"The information viewed in the outline is based on the :term:`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 l'aperçu sont basées sur l'index du projet :"
+"term:`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/usage_project.rst:231
+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/usage_project.rst:234
+msgid ""
+"The **Synopsis** column of the outline view takes its information from a "
+"specially formatted comment. See :ref:`a_fmt_comm`."
+msgstr ""
+"La colonne **Synopsis** de la vue d'ensemble tire ses informations d'un "
+"commentaire spécialement formaté. Voir :ref:`a_fmt_comm`."
+
+#~ msgid ""
+#~ "You can drag and drop documents and regular folders, but not root folders. "
+#~ "If you select multiple items, they can only be dragged and dropped if they "
+#~ "are siblings. That is, they have the same parent item in the project. This "
+#~ "limitation is due to the way drag and drop is implemented in the user "
+#~ "interface framework novelWriter is built upon."
+#~ msgstr ""
+#~ "Vous pouvez faire glisser et déposer des documents et des dossiers "
+#~ "ordinaires, mais pas des dossiers racines. Si vous sélectionnez plusieurs "
+#~ "éléments, ils ne peuvent être glissés et déposés que s'ils sont apparentés. "
+#~ "C'est-à-dire qu'ils ont le même élément parent dans le projet. Cette "
+#~ "limitation est due à la façon dont le glisser-déposer est implémenté dans "
+#~ "l'interface utilisateur sur laquelle novelWriter est construit."

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

@@ -0,0 +1,977 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2024-12-27 14:27+0100\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_shortcuts.rst:5
+msgid "Keyboard Shortcuts"
+msgstr "Raccourcis clavier"
+
+#: ../../source/usage_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/usage_shortcuts.rst:11
+msgid "On MacOS, replace :kbd:`Ctrl` with :kbd:`Cmd`."
+msgstr "Sous MacOS, remplacez :kbd:`Ctrl` par :kbd:`Cmd`."
+
+#: ../../source/usage_shortcuts.rst:17
+msgid "Main Window Shortcuts"
+msgstr "Raccourcis de la fenêtre principale"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Shortcut"
+msgstr "Raccourci"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Description"
+msgstr "Description"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F1`"
+msgstr ":kbd:`F1`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the online user manual"
+msgstr "Ouvrir le manuel d'utilisation en ligne"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F5`"
+msgstr ":kbd:`F5`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Build Manuscript** tool"
+msgstr "Ouvrir l'outil **Compiler le manuscrit**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F6`"
+msgstr ":kbd:`F6`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Writing Statistics** tool"
+msgstr "Ouvrir l'outil **Statistiques d'écriture**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F8`"
+msgstr ":kbd:`F8`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Toggle **Focus Mode**"
+msgstr "Basculer **Mode focus**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F9`"
+msgstr ":kbd:`F9`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Re-build the project's index"
+msgstr "Reconstruire l'index du projet"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F11`"
+msgstr ":kbd:`F11`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Toggle full screen mode"
+msgstr "Basculer en mode plein écran"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+,`"
+msgstr ":kbd:`Ctrl+,`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Preferences** dialog"
+msgstr "Ouvrir la boîte de dialogue **Préférences**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+E`"
+msgstr ":kbd:`Ctrl+E`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+T`"
+msgstr ":kbd:`Ctrl+T`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Q`"
+msgstr ":kbd:`Ctrl+Q`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Exit novelWriter"
+msgstr "Quitter novelWriter"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+,`"
+msgstr ":kbd:`Ctrl+Maj+,`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Project Settings** dialog"
+msgstr "Ouvrir la boîte de dialogue **Paramètres du projet**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+O`"
+msgstr ":kbd:`Ctrl+Maj+O`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+S`"
+msgstr ":kbd:`Ctrl+Maj+S`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Save the current project"
+msgstr "Enregistrer le projet en cours"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+T`"
+msgstr ":kbd:`Ctrl+Maj+T`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Switch focus to the outline view"
+msgstr "Basculer vers la vue d'ensemble"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+W`"
+msgstr ":kbd:`Ctrl+Maj+W`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Close the current project"
+msgstr "Fermer le projet en cours"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Shift+F1`"
+msgstr ":kbd:`Maj+F1`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Shift+F6`"
+msgstr ":kbd:`Maj+F6`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Project Details** dialog"
+msgstr "Ouvrir la boîte de dialogue **Détails du projet**"
+
+#: ../../source/usage_shortcuts.rst:44
+msgid "Project Tree Shortcuts"
+msgstr "Raccourcis de l'arborescence du projet"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F2`"
+msgstr ":kbd:`F2`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Edit the label of the selected item"
+msgstr "Modifier le libellé de l'élément sélectionné"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Return`"
+msgstr ":kbd:`Retour`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the selected document in the editor"
+msgstr "Ouvrir le document sélectionné dans l'éditeur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Alt+Up`"
+msgstr ":kbd:`Alt+Haut`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Alt+Down`"
+msgstr ":kbd:`Alt+Bas`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Alt+Left`"
+msgstr ":kbd:`Alt+Gauche`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Jump to the parent item in the tree"
+msgstr "Sauter à l'élément parent dans l'arborescence"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Alt+Right`"
+msgstr ":kbd:`Alt+Droite`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+.`"
+msgstr ":kbd:`Ctrl+.`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the context menu on the selected item"
+msgstr "Ouvrir le menu contextuel de l'élément sélectionné"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+L`"
+msgstr ":kbd:`Ctrl+L`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Quick Links** menu"
+msgstr "Ouvrir le menu **Liens rapides**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+N`"
+msgstr ":kbd:`Ctrl+N`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the **Create New Item** menu"
+msgstr "Ouvrir le menu **Créer un nouvel élément**"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+O`"
+msgstr ":kbd:`Ctrl+O`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+R`"
+msgstr ":kbd:`Ctrl+R`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the selected document in the viewer"
+msgstr "Ouvrir le document sélectionné dans le visualisateur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Up`"
+msgstr ":kbd:`Ctrl+Haut`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Down`"
+msgstr ":kbd:`Ctrl+Bas`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+Del`"
+msgstr ":kbd:`Ctrl+Maj+Suppr`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Move the selected item to Trash"
+msgstr "Déplacer l'élément sélectionné vers la corbeille"
+
+#: ../../source/usage_shortcuts.rst:68
+msgid "Document Editor Shortcuts"
+msgstr "Raccourcis de l'éditeur de documents"
+
+#: ../../source/usage_shortcuts.rst:72
+msgid "Text Search Shortcuts"
+msgstr "Raccourcis de recherche de texte"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F3`"
+msgstr ":kbd:`F3`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Find the next occurrence of the search word"
+msgstr "Trouver la prochaine occurrence du mot recherché"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+F`"
+msgstr ":kbd:`Ctrl+F`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open search and look for the selected word"
+msgstr "Ouvrir la recherche et rechercher le mot sélectionné"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+G`"
+msgstr ":kbd:`Ctrl+G`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+H`"
+msgstr ":kbd:`Ctrl+H`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+1`"
+msgstr ":kbd:`Ctrl+Maj+1`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Replace selected occurrence, and move to the next"
+msgstr "Remplacer l'occurrence sélectionnée et passer à la suivante"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+G`"
+msgstr ":kbd:`Ctrl+Maj+G`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Find the previous occurrence of the search word"
+msgstr "Trouver l'occurrence précédente du mot recherché"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+F`"
+msgstr ":kbd:`Ctrl+Maj+F`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Shift+F3`"
+msgstr ":kbd:`Maj+F3`"
+
+#: ../../source/usage_shortcuts.rst:88
+msgid "Text Formatting Shortcuts"
+msgstr ""
+"Raccourcis de mise en forme du texteRaccourcis de mise en forme du texte"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+'`"
+msgstr ":kbd:`Ctrl+'`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+\"`"
+msgstr ":kbd:`Ctrl+\"`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+/`"
+msgstr ":kbd:`Ctrl+/`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+0`"
+msgstr ":kbd:`Ctrl+0`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+1`"
+msgstr ":kbd:`Ctrl+1`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block format to heading level 1"
+msgstr "Modifier le format du bloc au niveau de titre 1"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+2`"
+msgstr ":kbd:`Ctrl+2`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block format to heading level 2"
+msgstr "Modifier le format du bloc en titre de niveau 2"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+3`"
+msgstr ":kbd:`Ctrl+3`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block format to heading level 3"
+msgstr "Modifier le format du bloc en titre de niveau 3"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+4`"
+msgstr ":kbd:`Ctrl+4`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block format to heading level 4"
+msgstr "Modifier le format du bloc en titre de niveau 4"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+5`"
+msgstr ":kbd:`Ctrl+5`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block alignment to left-aligned"
+msgstr "Aligner le bloc à gauche"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+6`"
+msgstr ":kbd:`Ctrl+6`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block alignment to centred"
+msgstr "Aligner le bloc au centre"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+7`"
+msgstr ":kbd:`Ctrl+7`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Change block alignment to right-aligned"
+msgstr "Aligner le bloc à droite"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+8`"
+msgstr ":kbd:`Ctrl+8`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Add a left margin to the block"
+msgstr "Ajouter une marge gauche au bloc"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+9`"
+msgstr ":kbd:`Ctrl+9`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Add a right margin to the block"
+msgstr "Ajouter une marge droite au bloc"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+B`"
+msgstr ":kbd:`Ctrl+B`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+D`"
+msgstr ":kbd:`Ctrl+D`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+I`"
+msgstr ":kbd:`Ctrl+I`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+/`"
+msgstr ":kbd:`Ctrl+Maj+/`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+D`"
+msgstr ":kbd:`Ctrl+Maj+D`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:114
+msgid "Other Editor Shortcuts"
+msgstr "Autres raccourcis de l'éditeur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`F7`"
+msgstr ":kbd:`F7`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Re-run the spell checker on the document"
+msgstr "Réexécuter le correcteur orthographique sur le document"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Open the context menu at the current cursor location"
+msgstr "Ouvrir le menu contextuel à l'emplacement actuel du curseur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+A`"
+msgstr ":kbd:`Ctrl+A`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Select all text in the document"
+msgstr "Sélectionner tout le texte dans le document"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+C`"
+msgstr ":kbd:`Ctrl+C`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Copy selected text to clipboard"
+msgstr "Copier le texte sélectionné dans le presse-papiers"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`"
+msgstr ":kbd:`Ctrl+K`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Activate the insert commands (see list in :ref:`a_kb_ins`)"
+msgstr ""
+"Activer les commandes d'insertion (voir la liste dans :ref:`a_kb_ins`)"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+S`"
+msgstr ":kbd:`Ctrl+S`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Save the current document"
+msgstr "Enregistrer le document en cours"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+V`"
+msgstr ":kbd:`Ctrl+V`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Paste text from clipboard to cursor position"
+msgstr "Coller le texte du presse-papiers à la position du curseur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+W`"
+msgstr ":kbd:`Ctrl+W`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Close the current document"
+msgstr "Fermer le document en cours"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+X`"
+msgstr ":kbd:`Ctrl+X`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Cut selected text to clipboard"
+msgstr "Couper le texte sélectionné dans le presse-papiers"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Y`"
+msgstr ":kbd:`Ctrl+Y`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Redo latest undo"
+msgstr "Rétablir la dernière annulation"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Z`"
+msgstr ":kbd:`Ctrl+Z`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Undo latest changes"
+msgstr "Annuler les dernières modifications"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Backspace`"
+msgstr ":kbd:`Ctrl+Retour-arrière`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Delete the word before the cursor"
+msgstr "Supprimer le mot précédant le curseur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Del`"
+msgstr ":kbd:`Ctrl+Suppr`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Delete the word after the cursor"
+msgstr "Supprimer le mot après le curseur"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+F7`"
+msgstr ":kbd:`Ctrl+F7`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Toggle spell checking"
+msgstr "Vérifier l'orthographe"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Return`"
+msgstr ":kbd:`Ctrl+Retour`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+A`"
+msgstr ":kbd:`Ctrl+Maj+A`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Select all text in the current paragraph"
+msgstr "Sélectionner tout le texte du paragraphe en cours"
+
+#: ../../source/usage_shortcuts.rst:141
+msgid "Insert Shortcuts"
+msgstr "Raccourcis d'insertion"
+
+#: ../../source/usage_shortcuts.rst:143
+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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Space`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Espace`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a non-breaking space"
+msgstr "Insérer un espace insécable"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`_`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`_`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a long dash (em dash)"
+msgstr "Insérer un tiret long"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`.`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`.`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert an ellipsis"
+msgstr "Insérer un point de suspension"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`'`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`'`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a modifier apostrophe"
+msgstr "Insérer une apostrophe"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`*`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`*`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a list bullet"
+msgstr "Insérer une puce de liste"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`%`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`%`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a per mille symbol"
+msgstr "Insérer un symbole pour mille"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`~`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`~`"
+
+#: ../../source/usage_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/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`−`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`−`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a short dash (en dash)"
+msgstr "Insérer un tiret court"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`1`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`1`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a left single quote"
+msgstr "Insérer un guillemet simple gauche"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`2`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`2`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a right single quote"
+msgstr "Insérer un guillemet simple à droite"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`3`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`3`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a left double quote"
+msgstr "Insérer un double guillemet gauche"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`4`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`4`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a right double quote"
+msgstr "Insérer un double guillemet droit"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`C`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`C`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@char`` keyword"
+msgstr "Insérer un mot-clé ``@char``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`E`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`E`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert an ``@entity`` keyword"
+msgstr "Insérer un mot-clé ``@entity``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`F`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`F`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@focus`` keyword"
+msgstr "Insérer un mot-clé ``@focus``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`G`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`G`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@tag`` keyword"
+msgstr "Insérer un mot-clé ``@tag``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`H`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`H`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a short description comment"
+msgstr "Insérer un bref commentaire de description"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`L`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`L`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@location`` keyword"
+msgstr "Insérer un mot-clé ``@location``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`M`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`M`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@mention`` keyword"
+msgstr "Insérer un mot-clé ``@mention``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`O`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`O`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert an ``@object`` keyword"
+msgstr "Insérer un mot-clé ``@object``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`P`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`P`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@plot`` keyword"
+msgstr "Insérer un mot-clé `@plot``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`S`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`S`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a synopsis comment"
+msgstr "Insérer un commentaire de synopsis"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`T`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`T`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@time`` keyword"
+msgstr "Insérer un mot-clé ``@time``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`V`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`V`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@pov`` keyword"
+msgstr "Insérer un mot-clé ``@pov``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`X`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`X`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a ``@custom`` keyword"
+msgstr "Insérer un mot-clé ``@custom``"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+Space`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+Espace`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a thin non-breaking space"
+msgstr "Insérer un espace fin insécable"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+_`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+_`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a horizontal bar (quotation dash)"
+msgstr "Insérer une barre horizontale"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+'`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+'`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a prime"
+msgstr "Insérer une prime"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+\"`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+\"`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a double prime"
+msgstr "Insérer une double prime"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+*`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+*`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a flower mark (alternative bullet)"
+msgstr "Insérer une fleur (puce alternative)"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+−`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+−`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a hyphen bullet (alternative bullet)"
+msgstr "Insérer une puce à tiret (puce alternative)"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+D`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+D`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a division sign"
+msgstr "Insérer un signe de division"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+O`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+O`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a degree symbol"
+msgstr "Insérer un symbole de degré"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Ctrl+X`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Ctrl+X`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a times sign"
+msgstr "Insert a times sign"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+K`, :kbd:`Shift+Space`"
+msgstr ":kbd:`Ctrl+K`, :kbd:`Maj+Espace`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Insert a thin space"
+msgstr "Insérer un espace fin"
+
+#: ../../source/usage_shortcuts.rst:190
+msgid "Document Viewer Shortcuts"
+msgstr "Raccourcis de la fenêtre de visualisation des documents"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Move backward in the view history"
+msgstr "Reculer dans l'historique des vues"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Move forward in the view history"
+msgstr "Avancer dans l'historique des vues"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid ":kbd:`Ctrl+Shift+R`"
+msgstr ":kbd:`Ctrl+Maj+R`"
+
+#: ../../source/usage_shortcuts.rst:1
+msgid "Close the document viewer"
+msgstr "Fermer le panneau de visualisation des documents"

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

@@ -0,0 +1,242 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-21 19:37+0100\n"
+"PO-Revision-Date: 2025-01-22 13:30+0100\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_typography.rst:5
+msgid "Typographical Notes"
+msgstr "Notes typographiques"
+
+#: ../../source/usage_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:`a_kb_ins`."
+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 points de suspension, les "
+"espaces fins, etc. Tous ces symboles sont disponibles dans le menu "
+"**Insérer**, et via des raccourcis clavier. Voir :ref:`a_kb_ins`."
+
+#: ../../source/usage_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/usage_typography.rst:23
+msgid "Special Notes on Symbols"
+msgstr "Remarques spéciales sur les symboles"
+
+#: ../../source/usage_typography.rst:25
+msgid "This section contains additional notes on the available special symbols."
+msgstr ""
+"Cette section contient des notes supplémentaires sur les symboles spéciaux "
+"disponibles."
+
+#: ../../source/usage_typography.rst:29
+msgid "Dashes and Ellipsis"
+msgstr "Tirets et points de suspension"
+
+#: ../../source/usage_typography.rst:31
+msgid ""
+"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."
+msgstr ""
+"Lorsque la fonction de remplacement automatique est activée (voir :ref:"
+"`a_ui_edit_auto`), les traits d'union multiples sont automatiquement "
+"convertis en tirets courts et longs, et les trois points en points de "
+"suspension. Le dernier remplacement automatique peut toujours être annulé "
+"avec la commande d'annulation :kbd:`Ctrl+Z`, ramenant le texte à ce que vous "
+"aviez tapé avant le remplacement automatique."
+
+#: ../../source/usage_typography.rst:36
+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/usage_typography.rst:42
+msgid "Single and Double Quotes"
+msgstr "Guillemets simples et doubles"
+
+#: ../../source/usage_typography.rst:44
+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/usage_typography.rst:48
+msgid ""
+"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."
+msgstr ""
+"Normalement, le texte entre guillemets est mis en évidence par l'éditeur. Il "
+"s'agit d'une commodité pour mettre en évidence les dialogues entre les "
+"personnages. Cette fonctionnalité peut être désactivée dans les "
+"**Préférences** si elle n'est pas souhaitée."
+
+#: ../../source/usage_typography.rst:52
+msgid ""
+"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."
+msgstr ""
+"L'éditeur fait la distinction entre le texte entre guillemets droits et les "
+"symboles de guillemets sélectionnés par l'utilisateur. Cela permet au "
+"rédacteur de reconnaître les parties du texte qui n'utilisent pas les "
+"symboles de guillemets choisis. Deux fonctions pratiques du menu **Format** "
+"peuvent être utilisées pour reformater une section de texte sélectionnée avec "
+"les symboles de guillemets corrects."
+
+#: ../../source/usage_typography.rst:59
+msgid "Single and Double Prime"
+msgstr "Simple et double prime"
+
+#: ../../source/usage_typography.rst:61
+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/usage_typography.rst:70
+msgid "Modifier Letter Apostrophe"
+msgstr "Modificateur Lettre Apostrophe"
+
+#: ../../source/usage_typography.rst:72
+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/usage_typography.rst:76
+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/usage_typography.rst:82
+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."
+msgstr ""
+"Lors de l'exportation à l'aide de l'outil **Compiler un 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, cela n'a pas vraiment d'importance si vous ne les utilisez que "
+"pour corriger la mise en évidence de la syntaxe."
+
+#: ../../source/usage_typography.rst:88
+msgid "Special Space Symbols"
+msgstr "Symboles spéciaux d'espacement"
+
+#: ../../source/usage_typography.rst:90
+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 `thin space`_. 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/usage_typography.rst:95
+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/usage_typography.rst:97
+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/usage_typography.rst:100
+msgid ""
+"The thin and non-breaking spaces are converted to their corresponding HTML "
+"codes on export to HTML format."
+msgstr ""
+"Les espaces fins et insécables sont convertis en codes HTML correspondants "
+"lors de l'exportation au format HTML."

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

@@ -0,0 +1,448 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2024
+# This file is distributed under the same license as the novelWriter
+# package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: novelWriter 2.6b1\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2025-01-28 21:52+0100\n"
+"PO-Revision-Date: 2025-01-28 22:01+0100\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_writing.rst:5
+msgid "The Editor and Viewer"
+msgstr "L'éditeur et l'afficheur"
+
+#: ../../source/usage_writing.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/usage_writing.rst:15
+msgid "Editing a Document"
+msgstr "Édition d'un document"
+
+#: ../../source/usage_writing.rst:19
+msgid "A screenshot of the Document Editor panel."
+msgstr "Capture d'écran du panneau de l'éditeur de documents."
+
+#: ../../source/usage_writing.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. The "
+"editor uses a Markdown-like syntax for some features, and a novelWriter-"
+"specific syntax for others. The syntax format is described in the :ref:"
+"`a_fmt` chapter."
+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. Cela "
+"ouvrira le document dans l'éditeur de documents. L'éditeur utilise une "
+"syntaxe de type Markdown pour certaines fonctionnalités, et une syntaxe "
+"spécifique à novelWriter pour d'autres. Le format de la syntaxe est "
+"décrit dans le chapitre :ref:`a_fmt`."
+
+#: ../../source/usage_writing.rst:26
+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 focus**, 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/usage_writing.rst:31
+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/usage_writing.rst:37
+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/usage_writing.rst:40
+msgid ""
+"Any :term:`references<reference>` 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 ""
+"Tous les :term:`références<reference>` de l'éditeur peuvent être ouverts "
+"dans le visualiseur en déplaçant le curseur sur l'étiquette et en "
+"appuyant sur :kbd:`Ctrl+Retour`. Vous pouvez également faire un contrôle-"
+"clic avec votre souris."
+
+#: ../../source/usage_writing.rst:45
+msgid "Spell Checking"
+msgstr "Vérification de l'orthographe"
+
+#: ../../source/usage_writing.rst:47
+msgid ""
+"A third party library called Enchant is used for spell checking in the "
+"editor. The controls for spell checking can be 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/usage_writing.rst:51
+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 can 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 **Lexique du projet** disponible dans "
+"le menu **Outils**."
+
+#: ../../source/usage_writing.rst:58
+msgid ""
+"Generally, spell checking dictionaries are collected from your operating "
+"system, but on Windows they are not. See :ref:`a_custom_dict` for how to "
+"add spell checking dictionaries on Windows."
+msgstr ""
+"En général, les dictionnaires de vérification orthographique sont "
+"collectés à partir de votre système d'exploitation, mais ce n'est pas le "
+"cas sous Windows. Voir :ref:`a_custom_dict` pour savoir comment ajouter "
+"des dictionnaires de vérification orthographique sous Windows."
+
+#: ../../source/usage_writing.rst:63
+msgid "Editor Auto-Completer"
+msgstr "Auto-complétion de l'éditeur"
+
+#: ../../source/usage_writing.rst:65
+msgid ""
+"If you type the character ``@`` on a new line, a pop-up menu will appear "
+"showing the different available keywords. The list will shorten as you "
+"type. Once a keyword command has been selected or typed, the editor may "
+"suggest further options based on your project content. See :ref:"
+"`a_references_completer` for more details."
+msgstr ""
+"Si vous tapez le caractère ``@`` sur une nouvelle ligne, un menu "
+"contextuel apparaîtra, affichant les différents mots-clés disponibles. La "
+"liste se raccourcit au fur et à mesure que vous tapez. Une fois qu'un mot-"
+"clé a été sélectionné ou tapé, l'éditeur peut suggérer d'autres options "
+"basées sur le contenu de votre projet. Voir :ref:`a_references_completer` "
+"pour plus de détails."
+
+#: ../../source/usage_writing.rst:76
+msgid "Viewing a Document"
+msgstr "Visualisation d'un document"
+
+#: ../../source/usage_writing.rst:80
+msgid "A screenshot of the Document Viewer panel."
+msgstr "Capture d'écran de la visualisation de documents."
+
+#: ../../source/usage_writing.rst:82
+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/usage_writing.rst:87
+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/usage_writing.rst:92
+msgid ""
+"In the viewer :term:`references<reference>` become clickable links. "
+"Clicking them will replace the content of the viewer with the content of "
+"the document the reference points to."
+msgstr ""
+"Dans la fenêtre de visualisation, les :term:`références<reference>` "
+"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/usage_writing.rst:95
+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/usage_writing.rst:101
+msgid ""
+"At the bottom of the view panel there is 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 se trouve 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/usage_writing.rst:109
+msgid ""
+"The **References** panel relies on an up-to-date :term:`index<project "
+"index>` of the project. 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 :term:`index<project index>` à "
+"jour du projet. L'index est maintenu automatiquement. Cependant, si "
+"quelque chose manque ou semble erroné, l'index peut toujours être "
+"reconstruit en sélectionnant **Reconstruire l'index** dans le menu "
+"**Outils**, ou en appuyant sur :kbd:`F9`."
+
+#: ../../source/usage_writing.rst:116
+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."
+
+#: ../../source/usage_writing.rst:122
+msgid "Search & Replace"
+msgstr "Rechercher & Remplacer"
+
+#: ../../source/usage_writing.rst:126
+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/usage_writing.rst:128
+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/usage_writing.rst:131
+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/usage_writing.rst:135
+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/usage_writing.rst:144
+msgid ""
+"For more information on the capabilities of the Regular Expression "
+"option, see the Qt documentation for the `QRegularExpression <https://doc."
+"qt.io/qt-6/qregularexpression.html>`_ class."
+msgstr ""
+"Pour plus d'informations sur les possibilités de l'option Expression "
+"régulière, voir la documentation Qt pour la classe `QRegularExpression "
+"<https://doc.qt.io/qt-6/qregularexpression.html>`_."
+
+#: ../../source/usage_writing.rst:152
+msgid "Auto-Replace as You Type"
+msgstr "Remplacement automatique au fur et à mesure de la saisie"
+
+#: ../../source/usage_writing.rst:154
+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/usage_writing.rst:159
+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:"
+"`a_kb_ins`. 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 l'auto-remplacement, tous les symboles insérés par "
+"cette fonctionnalité sont également disponibles dans le menu :guilabel:"
+"`Insertion`, et via :ref:`a_kb_ins`. Vous pouvez également utiliser une "
+"configuration `Compose Key`_, ce qui signifie que vous n'avez pas du tout "
+"besoin de la fonction de remplacement automatique."
+
+#: ../../source/usage_writing.rst:163
+msgid ""
+"The editor is able to replace two and three hyphens with short and long "
+"dashes, triple points 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, les triples points par des points de suspension, "
+"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 faut 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/usage_writing.rst:171
+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 before it."
+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é avant lui."
+
+#: ../../source/usage_writing.rst:179
+msgid "Dialogue Highlighting"
+msgstr "Mise en évidence du dialogue"
+
+#: ../../source/usage_writing.rst:181
+msgid ""
+"The editor and viewer can optionally highlight character dialogue in your "
+"novel documents. By default, this feature is set to display text in "
+"double quotes as dialogue. In **Preferences**, you can change this to "
+"support various other dialogue markers that instead uses dashes to "
+"indicate dialogue, like those used in Spanish, Portuguese, Polish, etc."
+msgstr ""
+"L'éditeur et l'afficheur peuvent optionnellement mettre en évidence les "
+"dialogues des personnages dans les documents de votre roman. Par défaut, "
+"cette fonctionnalité est configurée pour afficher le texte entre "
+"guillemets comme dialogue. Dans les **Préférences**, vous pouvez modifier "
+"ce paramètre pour prendre en charge d'autres marqueurs de dialogue qui "
+"utilisent des tirets pour indiquer le dialogue, comme ceux utilisés en "
+"espagnol, en portugais, en polonais, etc."
+
+#: ../../source/usage_writing.rst:186
+msgid ""
+"Various styles are supported by changing the settings under \"Text "
+"Highlighting\" in **Preferences**."
+msgstr ""
+"Différents styles sont pris en charge en modifiant les paramètres sous « "
+"Surlignage du texte » dans **Préférences**."
+
+#: ../../source/usage_writing.rst:188
+msgid ""
+"It is also possible to include the dialogue highlighting in your "
+"manuscripts."
+msgstr ""
+"Il est également possible d'inclure la mise en évidence du dialogue dans "
+"vos manuscrits."
+
+#~ msgid ""
+#~ "The regular expression search is somewhat dependant on which version "
+#~ "of Qt your system has. If you have Qt 5.13 or higher, there is better "
+#~ "support for Unicode symbols in the search."
+#~ msgstr ""
+#~ "La recherche d'expressions régulières dépend quelque peu de la version "
+#~ "de Qt que vous avez sur votre système. Si vous avez Qt 5.13 ou plus, "
+#~ "la recherche prend mieux en charge les symboles Unicode."

docs/source/more_counting.rst

@@ -0,0 +1,98 @@
+.. _a_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.
+
+The counts provided in the app on the raw text is 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.
+
+
+Text Word Counts and Stats
+==========================
+
+These are the rules for the main counts available for for each document in a project.
+
+For all counts, the following rules apply.
+
+#. Short (–) and long (—) dashes are considered word separators.
+#. Any line starting with ``%`` or ``@`` is ignored.
+#. Trailing white spaces are ignored, including line breaks.
+#. Leading ``>`` and trailing ``<`` are ignored with any spaces next to them.
+#. Valid shortcodes and other commands wrapped in brackets ``[]`` are ignored.
+#. In-line Markdown syntax in text paragraphs is treated as part of the text.
+
+After the above preparation of the text, the following counts are available.
+
+**Character Count**
+   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.
+
+**Word Count**
+   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.
+
+**Paragraph Count**
+   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.
+
+
+Manuscript Counts
+=================
+
+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.
+
+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:
+
+#. Short (–) and long (—) dashes are considered word separators.
+#. Leading and trailing white spaces are generally included, but paragraph breaks are not.
+#. Hard line breaks within paragraph are considered white space characters.
+#. All formatting codes are ignored, including shortcodes, commands and Markdown.
+#. Scene and section separators are counted.
+#. Comments and meta data lines are counted after they are formatted.
+#. Headers are counted after they are formatted with custom formats.
+
+The following counts are available:
+
+**Headings**
+   The number of headings in the manuscript.
+
+**Paragraphs**
+   The number of body text paragraphs in the manuscript.
+
+**Words**
+   The number of words in the manuscript, including any comments and meta data text.
+
+**Words in Text**
+   The number of words in body text paragraphs, excluding all other text.
+
+**Words in Headings**
+   The number of words in headings, including inserted formatting like chapter numbers, etc.
+
+**Characters**
+   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.
+
+**Character in Text**
+   The number of characters in body text paragraphs. Paragraph breaks are not counted, but
+   in-paragraph hard line breaks are.
+
+**Characters in Headings**
+   The number of characters in headings.
+
+**Character in Text, No Spaces**
+   The number of characters in body text paragraphs considered part of a word or punctuation. That
+   is, white space characters are not counted.
+
+**Character in Headings, No Spaces**
+   The number of characters in headings considered part of a word or punctuation. That is, white
+   space characters are not counted.

docs/source/more_customise.rst

@@ -4,7 +4,7 @@
 Customisations
 **************
 
-.. _Enchant: https://abiword.github.io/enchant
+.. _Enchant: https://rrthomas.github.io/enchant/
 .. _Free Desktop: https://cgit.freedesktop.org/libreoffice/dictionaries/tree/
 
 There are a few ways you can customise novelWriter yourself. Currently, you can add new GUI themes,
@@ -34,9 +34,10 @@ and add dictionaries yourself.
 
 **Install Tool**
 
-A small tool to assist with this can be found under :guilabel:`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.
+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.
 
 **Manual Install**
 
@@ -80,14 +81,14 @@ modify it as you like.
   `novelwriter/assets/icons <https://github.com/vkbo/novelWriter/tree/main/novelwriter/assets/icons>`_.
 
 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 :guilabel:`Preferences`.
+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
 ``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 :guilabel:`Preferences` with the label you
+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
@@ -96,7 +97,7 @@ set as ``name`` inside the file.
    suitable one.
 
 
-Gustom GUI and Icons Theme
+Custom GUI and Icons Theme
 --------------------------
 
 A GUI theme ``.conf`` file consists of the following settings:
@@ -130,19 +131,26 @@ A GUI theme ``.conf`` file consists of the following settings:
    linkvisited     = 100, 100, 100
 
    [GUI]
-   statusnone      = 100, 100, 100
-   statussaved     = 100, 100, 100
-   statusunsaved   = 100, 100, 100
+   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.
 
-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
-colour values are RGB numbers on the format ``r, g, b`` where each is an integer from  to 255.
-Omitted values are not loaded and will use default values.
+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.
+
+.. versionadded:: 2.5
+   The ``fadedtext`` and ``errortext`` theme colour entries were added.
 
 
 Custom Syntax Theme
@@ -167,22 +175,37 @@ A syntax theme ``.conf`` file consists of the following settings:
    headertext     =   0,   0,   0
    headertag      =   0,   0,   0
    emphasis       =   0,   0,   0
-   straightquotes =   0,   0,   0
-   doublequotes   =   0,   0,   0
-   singlequotes   =   0,   0,   0
+   dialog         =   0,   0,   0
+   altdialog      =   0,   0,   0
+   note           =   0,   0,   0
    hidden         =   0,   0,   0
    shortcode      =   0,   0,   0
    keyword        =   0,   0,   0
+   tag            =   0,   0,   0
    value          =   0,   0,   0
+   optional       =   0,   0,   0
    spellcheckline =   0,   0,   0
    errorline      =   0,   0,   0
    replacetag     =   0,   0,   0
    modifier       =   0,   0,   0
+   texthighlight  = 255, 255, 255, 128
 
 In the Main section, you must define at least the ``name`` setting. The Syntax colour values are
-RGB numbers of the format ``r, g, b`` where each is an integer from  to 255. Omitted values default
-to black, except ``background`` which defaults to white,
+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.
+
+Omitted syntax colours default to black, except ``background`` which defaults to white, and
+``texthighlight`` which defaults to white with half transparency.
 
 .. versionadded:: 2.2
-   The `shortcode` syntax colour entry was added, so you need to update your custom themes if you
-   made any before version 2.2.
+   The ``shortcode`` syntax colour entry was added.
+
+.. versionadded:: 2.3
+   The ``optional`` syntax colour entry was added.
+
+.. versionadded:: 2.4
+   The ``texthighlight`` syntax colour entry was added.
+
+.. versionadded:: 2.5
+   The ``dialog``, ``altdialog``, ``note`` and ``tag`` syntax colour entries were added.
+   ``straightquotes``, ``doublequotes`` and ``singlequotes`` were removed.

docs/source/more_projectformat.rst

@@ -14,9 +14,7 @@ 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
@@ -24,16 +22,6 @@ where applicable.
    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/source/project_manuscript.rst

@@ -4,13 +4,16 @@
 Building the Manuscript
 ***********************
 
+.. _Pandoc: https://pandoc.org/
+
 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 :guilabel:`Manuscript Build` tool.
-You can activate it from the sidebar, the :guilabel:`Tools` menu, or by pressing :kbd:`F5`.
+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`.
 
 .. versionadded:: 2.1
+
    This tool is new for version 2.1. A simpler tool was used for earlier versions. The simpler tool
-   only allows you to define a single set of options for the build, but otherwise has much the same
+   only allows you to define a single set of options for the build, but otherwise had much the same
    functionality.
 
 
@@ -20,40 +23,61 @@ The Manuscript Build Tool
 =========================
 
 .. figure:: images/fig_manuscript_build.png
+   :width: 80%
 
-   The :guilabel:`Manuscript Build` tool main window.
+   The **Manuscript Build** tool main window.
 
-The main window of the :guilabel:`Manuscript Build` tool contains a list of all the builds you have
+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.
 
 
+Outline and Word Counts
+-----------------------
+
+.. figure:: images/fig_manuscript_build_outline.png
+   :width: 80%
+
+   The **Manuscript Build** tool main window with the **Outline** visible.
+
+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.
+
+A collapsible panel of word and character counts are also available below the preview document.
+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*.
+
+For a detailed description on how they are counted, see :ref:`a_counting`.
+
+
 .. _a_manuscript_settings:
 
 Build Settings
 ==============
 
-Each build definition can be edited by opening it in the :guilabel:`Manuscript Build Settings`
-dialog, either by double-clicking or by selecting it and pressing the edit button in the toolbar.
+Each build definition can be edited 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.
 
 .. tip::
-   You can keep the :guilabel:`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
-   by pressing the :guilabel:`Preview` button in the main :guilabel:`Manuscript Build` window.
-   When you're happy with the result, you can close the settings.
+
+   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 by pressing
+   the :guilabel:`Preview` button in the main **Manuscript Build** window. When you're happy with
+   the result, you can close the settings.
 
 
 Document Selection
 ------------------
 
 .. figure:: images/fig_build_settings_selections.png
+   :width: 80%
 
-   The :guilabel:`Selections` page of the :guilabel:`Manuscript Build Settings` dialog.
+   The **Selections** page of the **Manuscript Build Settings** dialog.
 
-The :guilabel:`Selections` page of the :guilabel:`Manuscript Build Settings` dialog allows you to
-fine tune which documents are included in the build. They are indicated by a green arrow 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.
+The **Selections** page of the **Manuscript Build Settings** dialog allows you to fine tune which
+documents are included in the build. They are indicated by a green arrow 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.
 
 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
@@ -63,17 +87,20 @@ In the figure, the green arrow icon and the blue pin icon indicates which docume
 and the red forbidden icon indicates that a document is explicitly excluded.
 
 
+.. _a_manuscript_settings_head:
+
 Formatting Headings
 -------------------
 
 .. figure:: images/fig_build_settings_headings.png
+   :width: 80%
 
-   The :guilabel:`Headings` page of the :guilabel:`Manuscript Build Settings` dialog.
+   The **Headings** page of the **Manuscript Build Settings** dialog.
 
-The :guilabel:`Headings` page of the :guilabel:`Manuscript Build Settings` dialog allows you to set
-how the headings in your :term:`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 like shown int he figure above.
+The **Headings** page of the **Manuscript Build Settings** dialog allows you to set how the
+headings in your :term:`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.
 
 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
@@ -84,7 +111,8 @@ Any text you add that isn't highlighted in colours will remain in your formatted
 ``{Title}`` will always be replaced by the text in the heading from your documents.
 
 You can preview the result of these format strings by clicking :guilabel:`Apply`, and then clicking
-:guilabel:`Preview` in the :guilabel:`Manuscript Build` tool main window.
+:guilabel:`Preview` in the **Manuscript Build** tool main window.
+
 
 Scene Separators
 ^^^^^^^^^^^^^^^^
@@ -99,13 +127,24 @@ the desired separator text as the format. If the format is any piece of static t
 be treated as a separator.
 
 
+.. _a_manuscript_settings_head_hard:
+
+Hard and Soft Scenes
+^^^^^^^^^^^^^^^^^^^^
+
+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.
+
+See :ref:`a_fmt_head` for more info on how to format headings in your text.
+
+
 Output Settings
 ---------------
 
-The :guilabel:`Content`, :guilabel:`Format` and :guilabel:`Output` pages of the
-:guilabel:`Manuscript Build Settings` dialog control a number of other settings for the output.
-Some of these only apply to specific output formats, which is indicated by the section headings on
-the settings pages.
+The **Content**, **Format** and **Output** pages of the **Manuscript Build Settings** dialog
+control a number of other settings for the output. Some of these only apply to specific output
+formats, which is indicated by the section headings on the settings pages.
 
 
 .. _a_manuscript_build:
@@ -114,12 +153,13 @@ Building Manuscript Documents
 =============================
 
 .. figure:: images/fig_build_build.png
+   :width: 80%
 
-   The :guilabel:`Manuscript Build` dialog used for writing the actual manuscript documents.
+   The **Manuscript Build** dialog used for writing the actual manuscript documents.
 
-When you press the :guilabel:`Build` button on the :guilabel:`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.
+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.
 
 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
@@ -139,21 +179,34 @@ Open Document Format
    flat version of the document format as a single XML file. Most rich text editors support the
    former, and only a few the latter.
 
+Microsoft Word Document Format
+   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.
+
+Portable Document Format (PDF)
+   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.
+
 novelWriter HTML
    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
+   is suitable for further processing by document conversion tools like Pandoc_, for importing in
    word processors, or for printing from browser.
 
+Standard/Extended Markdown
+   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.
+
 novelWriter Markup
    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.
 
-Standard/Extended Markdown
-   The Markdown format comes in both Standard and Extended flavour. The *only* difference in terms
-   of novelWriter functionality is the support for strikethrough text, which is not supported by
-   the Standard flavour.
+.. versionadded:: 2.6
+
+   Microsoft Word and PDF output options were added.
 
 
 Additional Formats
@@ -173,13 +226,14 @@ file can be imported directly into a Python dict object or a PHP array, to menti
 
 .. _a_manuscript_print:
 
-Print and PDF
-=============
+Printing
+========
 
 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.
 
 .. note::
+
    The paper format should in all cases default to whatever your system default is. If you want to
-   change it, you have to select it from the :guilabel:`Print Preview` dialog.
+   change it, you have to select it from the **Print Preview** dialog.

docs/source/project_overview.rst

@@ -1,112 +1,143 @@
 .. _a_proj:
 
-**************
-Novel Projects
-**************
+*****************
+Managing Projects
+*****************
 
-New projects can be created from the :guilabel:`Project` menu by selecting :guilabel:`New Project`.
-This will open the :guilabel:`New Project Wizard` that will assist you in creating a bare bone
-project suited to your needs.
+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 :guilabel:`Open Project`
-dialog. A project can be removed from this list by selecting it and pressing the :kbd:`Del` key or
-by clicking the :guilabel:`Remove` button.
+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.
 
-Project-specific settings are available in :guilabel:`Project Settings` in the :guilabel:`Project`
-menu. See further details below in the :ref:`a_proj_settings` section. Details about the project,
-including word counts, and a table of contents with word and page counts, is available through the
-:guilabel:`Project Details` dialog.
+.. 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 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 :guilabel:`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.
+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 :guilabel:`Novel` folder, no restrictions are applied by the
+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.
 
-:guilabel:`Novel`
+
+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.
 
-:guilabel:`Plot`
+**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 :guilabel:`Outline View`.
-   Tags in this folder can be references using the ``@plot`` keyword.
+   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.
 
-:guilabel:`Characters`
+**Characters**
    Character notes go in this root folder type. These are especially important if you want to use
-   the :guilabel:`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. Tags in this type of folder can be referenced using the ``@pov`` keyword for
+   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.
 
-:guilabel:`Locations`
+**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.
 
-:guilabel:`Timeline`
+**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.
 
-:guilabel:`Objects`
-   Important objects in the story, for instance objects that change hands often, can be tracked
-   here. Tags in this type of folder can be references using the ``@object`` 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.
 
-:guilabel:`Entities`
+**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.
 
-:guilabel:`Custom`
+**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 correspond to the categories of tags that can be used to reference them. For more
-information about the tags listed, see :ref:`a_references_references`.
+The root folders are closely tied to the tags and reference system. Each folder type corresponds to
+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 will be moved into a special :guilabel:`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.
+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 deleted from the :guilabel:`Project` menu, or by pressing
-:kbd:`Ctrl+Shift+Del`. Root folders can only be deleted when they are empty.
+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:
@@ -114,13 +145,33 @@ A document or a folder can be deleted from the :guilabel:`Project` menu, or by p
 Archived Documents
 ------------------
 
-If you don't want to delete a document, or put it in the :guilabel:`Trash` folder where it may be
-deleted accidentally, but still want it out of your main project tree, you can create an
-:guilabel:`Archive` root folder and move it there.
+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 :guilabel:`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.
+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.
+
+In addition to using folders. it is also 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:
@@ -129,17 +180,17 @@ 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 folder that
-aren't tracked in the core project file. These files, when discovered, are recovered and added back
-into the project.
+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 :guilabel:`Novel` root folder. Finally, if the :guilabel:`Novel`
-folder is missing, one will be created.
+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
@@ -151,18 +202,21 @@ be named after its internal key, which is a string of characters and numbers.
 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 folder. If you try to open
-a project which 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.
+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 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 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.
+
+   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
@@ -170,42 +224,33 @@ ignore this warning, and continue opening the project at your own risk.
    novelWriter will try to resolve project inconsistencies the next time you open the project.
 
 
-.. _a_proj_roots_dirs:
-
-Using Folders in the Project Tree
----------------------------------
-
-Folders, aside from 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_files:
 
 Project Documents
 =================
 
-New documents can be created from the toolbar in the :guilabel:`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.
+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 :guilabel:`Rename Item` from the :guilabel:`Project`
-menu, or by pressing :kbd:`F2`.
+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 items are available from the context menu that you can activate by
-right-clicking on an item in the tree. The :guilabel:`Transform` submenu includes options for
-converting, splitting, or merging items. See :ref:`a_ui_tree_split_merge` for more details on the
-latter two.
+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:
@@ -216,8 +261,8 @@ 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 :guilabel:`Project Tree` for any document selected in the
-project or novel trees.
+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.
@@ -225,7 +270,9 @@ 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 :guilabel:`Tools` menu, or by pressing :kbd:`F9`.
+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:
@@ -233,35 +280,36 @@ Either from the :guilabel:`Tools` menu, or by pressing :kbd:`F9`.
 Project Settings
 ================
 
-The :guilabel:`Project Settings` can be accessed from the :guilabel:`Project` menu, or by pressing
+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 :guilabel:`Settings` tab holds the project name, title, and author settings.
+The **Settings** tab holds the project name, author, and language settings.
 
-The :guilabel:`Project Name` can be set to a different value than the :guilabel:`Novel Title`. The
-difference between them is simply that the :guilabel:`Project Name` is used for the GUI (main
-window title) and for generating backup files. The intention is that the :guilabel:`Project Name`
-should remain unchanged throughout the project's lifetime, otherwise the name of exported files and
-backup files may change too.
+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.
 
-The :guilabel:`Novel Title` and :guilabel:`Authors` settings are used when building the manuscript,
-for some formats.
+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. You can also override the automatic backup setting. The
-project language can also be changed from the :guilabel:`Tools` menu.
+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 :guilabel:`Novel` can be given a *Status* label accompanied by a
-coloured icon, and each document or folder of the remaining types can be given an *Importance*
-label.
+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
@@ -269,9 +317,14 @@ use these to indicate at what stage of completion each novel document is, or how
 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.
 
+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.
+
 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.
 
@@ -299,22 +352,22 @@ 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 :guilabel:`Preferences`.
+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
-:guilabel:`Project Name` as defined in :ref:`a_proj_settings`.
+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 :guilabel:`Tools` menu.
-It is also possible to disable automated backups for a given project in
-:guilabel:`Project 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 :guilabel:`Project Name` must be set in
-   :guilabel:`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.
+   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:
@@ -327,16 +380,30 @@ total word counts of your novel documents and notes at the end of the session, p
 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 :guilabel:`Tools` menu under
-:guilabel:`Writing Statistics`. You can also launch it by pressing :kbd:`F6`, or find it on the
-sidebar.
+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 :guilabel:`Preferences`.
+   in **Preferences**.
+
+
+Session Timer
+-------------
+
+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.
+
+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.
+
+.. versionadded:: 2.6
+
+   As of version 2.6, clicking the timer text or icon in the status bar will toggle its visibility.

docs/source/project_references.rst

@@ -4,21 +4,22 @@
 Tags and References
 *******************
 
-In novelWriter there are no forms or tables to fill in to define the characters, locations and
-other elements of your story. Instead, you can mark your :term:`project notes` 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.
+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 explains in more detail how to use the tags and references system.
+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 novelWriter and select to "Fill the project with example files"
-   in the :guilabel:`New Project Wizard`. The example project contains several examples of tags and
-   references.
+   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:
@@ -31,14 +32,16 @@ documents, not the documents themselves. See :ref:`a_struct_heads` for more deta
 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 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.
+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.
 
-The implication here is that you can treat each heading as an independent element of your notes
-that can be referenced somewhere else. In order to make it possible to reference a header section,
-you need to assign it a tag.
+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. Or, you can lay out your plot in a single document and
+have a tag for each plot stage under separate headings.
 
 
 .. _a_references_tags:
@@ -47,43 +50,70 @@ 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 ``@tags`` :term:`keyword`. The full format of a tag is ``@tag: tagname``, where
-``tagname`` is an identifier of your choosing. You can only set *one* tag per heading, and the tag
-has to be unique across all documents in the project.
+by using the ``@tag`` :term:`keyword`.
 
-.. versionadded:: 2.2
-   Tags are now case insensitive.
+The basic format of a tag is ``@tag: tagName``.
 
-After the tags have been defined, they can then be referenced in the novel documents, or
-cross-referenced in other notes. they will also show up in the :guilabel:`Outline View` and in the
-back-reference panel when a document is opened in the viewer.
+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 syntax
-colour that valid tags do.
+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 :guilabel:`Manuscript Build` tool.
+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.
+
+.. 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.
 
 Example of a heading with a tag for a character of the story:
 
-.. code-block:: none
+.. code-block:: md
 
-   # Jane Doe
+   # Character: Jane Doe
 
-   @tag: Jane
+   @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, 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`.
+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
@@ -96,8 +126,8 @@ 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 :guilabel:`Outline View`, among
-other things.
+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
@@ -105,74 +135,86 @@ reference keywords allow multiple values.
 
 ``@pov``
    The point-of-view character for the current section. The target must be a note tag in a
-   :guilabel:`Character` type root folder.
+   **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 :guilabel:`Character`
-   type root folder.
+   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
-   :guilabel:`Character` type root folder. This should not include the point-of-view or focus
-   character if those references are used.
+   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
-   :guilabel:`Plot` type root folder.
+   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
-   :guilabel:`Timeline` type root folder.
+   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
-   :guilabel:`Locations` type root folder.
+   **Locations** type root folder.
 
 ``@object``
-   Objects present in the current section. The target must be a note tag in a :guilabel:`Object`
-   type root folder.
+   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 a
-   :guilabel:`Entities` type root folder.
+   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 :guilabel:`Custom`
-   type root folder. The custom folder are for any other category of notes you may want to use.
+   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.
+
+``@story``
+   This is used when referencing a Novel Document, like a scene or chapter, from somewhere else in
+   your project.
 
 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 :guilabel:`Rebuild Index` from the :guilabel:`Tools` menu.
-   In general, the index for a document is regenerated when it is saved, so this shouldn't normally
-   be necessary.
+   :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 :guilabel:`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.
+   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 :guilabel:`Outline View`, so referencing between notes is only
+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
-   :guilabel:`Manuscript Build` tool, the cross-references become clickable links in the exported
-   HTML document as well.
+   **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:: none
+.. code-block:: md
 
    ## Chapter 1
 
@@ -196,7 +238,7 @@ character ``@`` on a new line. It will first suggest tag or reference keywords f
 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
-:guilabel:`Create Note for Tag` from the menu.
+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

@@ -6,13 +6,13 @@ Novel Structure
 
 This chapter covers the structure of a novel project.
 
-There are two different types of documents in a project, :guilabel:`Novel Documents` and
-:guilabel:`Project Notes`. Novel documents can only live in a :guilabel:`Novel` type root folder.
-You can also move them to :guilabel:`Archive` and :guilabel:`Trash` of course.
+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 :guilabel:`Project Tree` can distinguish between the different header levels of the novel
-documents using coloured icons, and optionally add emphasis on the label, set in
-:guilabel:`Preferences`.
+The project tree can distinguish between the different heading levels of the novel documents using
+coloured icons, and optionally add emphasis on the label. Emphasis can be enabled in
+**Preferences**.
 
 
 .. _a_struct_heads:
@@ -27,47 +27,58 @@ Four levels of headings are supported, signified by the number of hashes (``#``)
 title. See also the :ref:`a_fmt` section for more details about the markup syntax.
 
 .. note::
-   The header levels are not only important when generating the manuscript, they are also used by
-   the indexer when building the outline tree in the :guilabel:`Outline View` as well as in the
-   :guilabel:`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 header types, and the two special header types, is listed in section
+   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:
 
-**Header Level 1: Partition**
-   This header level signifies that the text refers to a top level partition. This is useful when
+**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 header level ``#!`` covered in :ref:`a_fmt_head`.
+   The novel title itself should use the special heading level ``#!`` covered in :ref:`a_fmt_head`.
 
-**Header Level 2: Chapter**
-   This header level signifies a chapter level partition. 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 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.
 
-**Header Level 3: Scene**
-   This header level signifies a scene level partition. 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.
+**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`.
 
-**Header Level 4: Section**
-   This header level signifies a sub-scene level partition, usually called a "section" in the
+**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 just like with scene titles.
+   wish, and you can filter them out of the final manuscript.
 
-Page breaks are automatically added before level 1 and 2 headers when you build your project to a
-format that supports page breaks, or when you print the document directly from the
-:guilabel:`Manuscript Build` tool. If you want page breaks in other places, you have to specify
-them manually. See :ref:`a_fmt_break`.
+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:`a_fmt_break`.
 
 .. tip::
-   There are multiple options of how to process novel titles when building the manuscript. For
+
+   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. See the :ref:`a_manuscript` page for more details.
+   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.
+
+.. note::
+
+   As of 2.6, the heading levels internally in novelWriter do not map directly to heading levels in
+   manuscript documents. In manuscript documents, chapters are considered the top level heading,
+   and partitions become plain text paragraphs with a larger font.
+
+   .. versionadded:: 2.6
 
 
 .. _a_struct_heads_title:
@@ -75,18 +86,35 @@ them manually. See :ref:`a_fmt_break`.
 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 header format code with an ``!`` in order to
+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, like so:
+build document.
 
-``#! My Novel``
+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.
+
+This is the title page novelWriter generates automatically for a new project as of version 2.6:
+
+.. code-block:: md
+
+   Jane Doe[br]
+   Address 1[br]
+   Address 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.
 
 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
+``[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`.
 
 
@@ -96,18 +124,40 @@ 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 cam add an ``!`` to the level 2 header formatting code to tell the
-build tool to skip these chapters.
+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 Chapter Title``
+.. code-block:: md
 
-There is a separate formatting feature for such chapters in the :guilabel:`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 will have a page break added just like for
-normal chapters.
+   ##! Unnumbered Chapter Title
 
-.. Note::
-   Previously, you could also disable the automatic numbering of a chapter by adding an ``*`` as
-   the first character of the chapter title itself. This feature has been dropped in favour of the
-   current format in order to keep level 1 and 2 headers consistent. Please update your chapter
-   headings if you've used this syntax.
+   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/tech_locations.rst

@@ -4,7 +4,7 @@
 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.
@@ -15,10 +15,9 @@ file locations are described in this chapter.
 Configuration
 =============
 
-The general configuration of novelWriter, including everything that is in :guilabel:`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.
+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.
 
 The standard paths are:
 
@@ -40,9 +39,8 @@ Application Data
 ================
 
 novelWriter also stores a bit of data that is generated by the user's actions. This includes the
-list of recent projects form the :guilabel:`Open Project` dialog. Custom themes should also be
-saved here. The system paths are provided by the Qt QStandardPaths_ class and its
-``AppDataLocation`` value.
+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.
 
 The standard paths are:
 
@@ -56,3 +54,12 @@ user's username on Windows.
 .. note::
    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.
+
+The Application Data location also holds several folders:
+
+``cache``
+   This folder is used to save the preview data for the **Manuscript Build** tool.
+
+``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.

docs/source/tech_source.rst

@@ -36,12 +36,9 @@ 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 should be at least 5.10, but ideally 5.13 or higher for all features to work. For instance,
-searching using regular expressions with full Unicode support requires 5.13.
-
 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.
 
@@ -55,7 +52,7 @@ source, dependencies can still be installed from PyPi with:
 .. 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 renderring the SVG icons may be left out and needs to be installed manually. This is the
+   for rendering the SVG icons may be left out and needs to be installed manually. This is the
    case on for instance Arch Linux.
 
 
@@ -141,7 +138,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:
 
@@ -156,9 +153,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 :guilabel:`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/tech_storage.rst

@@ -4,8 +4,6 @@
 How Data is Stored
 ******************
 
-.. _documentation: https://docs.novelwriter.io/
-
 This chapter contains details of how novelWriter stores and handles the project data.
 
 
@@ -33,17 +31,10 @@ itself. It is important to keep this file backed up, either through the built-in
 your own backup solution.
 
 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 timesetamp is set in the meta section on line 2, and
+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
@@ -55,10 +46,10 @@ string. The documents are saved with a filename assembled from this handle and t
 ``.nwd``.
 
 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 :guilabel:`Show File Details` from the :guilabel:`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.
+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.
 
 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
@@ -91,11 +82,6 @@ If successful, the old data file is then removed, and the temporary file replace
 that the previously saved data is only replaced when the new data has been successfully saved to
 the storage medium.
 
-For the project XML file, a ``.bak`` file is in addition kept, which will always contain the
-previous version of the file, although when auto-save is enabled, they may have the same content.
-If the opening of a project file fails, novelWriter will automatically try to open the ``.bak``
-file instead.
-
 
 Project Meta Data
 =================
@@ -114,7 +100,7 @@ The Project Index
 
 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 :guilabel:`Tools` menu.
+the **Tools** menu.
 
 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
@@ -130,8 +116,8 @@ the index. If this too fails, you have likely encountered a bug.
 Build Definitions
 -----------------
 
-The build definitions from the :guilabel:`Manuscript Build` tool are kept in the
-``meta/builds.json`` file. If this file is lost, all custom build definitions are lost too.
+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.
 
 
 Cached GUI Options
@@ -149,17 +135,17 @@ Custom Word List
 ----------------
 
 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 :guilabel:`Tools` menu. If
-you lose this file, all your custom spell check words will be lost too.
+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.
 
 
 Session Stats
 -------------
 
 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
-:guilabel:`Writing Statistics` tool. If this file is lost, the history it contains is also lost,
-but it has otherwise no impact on the project.
+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.
 
 Each session is recorded as a JSON object on a single line of the file. Each session record is
 appended tot he file.

docs/source/usage_breakdown.rst

@@ -7,10 +7,12 @@ How it Works
 .. _Fusion: https://doc.qt.io/qt-6/gallery.html
 .. _Pandoc: https://pandoc.org/
 .. _Open Document: https://en.wikipedia.org/wiki/OpenDocument
+.. _Office Open XML: https://en.wikipedia.org/wiki/Office_Open_XML
+.. _version control: https://en.wikipedia.org/wiki/Version_control
 
 The main features of novelWriter are listed in the :ref:`a_intro` chapter. In this chapter, we go
 into some more details on how they are implemented. This is intended as an overview. Later on in
-this documentation, these features will be covered in more detail.
+this documentation these features will be covered in more detail.
 
 
 .. _a_breakdown_design:
@@ -21,26 +23,31 @@ GUI Layout and Design
 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.
 
-The main window does not have an editor toolbar like many other applications do. This reduces
-clutter, and since the documents are formatted with style tags, it is more or less redundant.
+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.
 
 Most formatting features supported are available through convenient keyboard shortcuts. They are
-also available in the main menu, 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:`a_kb` chapter.
+also 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:`a_kb`
+chapter.
 
 .. note::
    novelWriter is not intended to be a full office type word processor. It doesn't support images,
    links, tables, and other complex structures and objects often needed for such documents.
-   Formatting is limited to headers, emphasis, text alignment, and a few other simple features.
+   Formatting is limited to headings, in-line basic text formats, text alignment, and a few other
+   simple features.
 
 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 :guilabel:`Build Manuscript` tool, and a set of
+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.
 
 .. versionadded:: 2.2
+
    A number of new formatting options were added in 2.2 to allow for some special formatting cases.
-   At the same time, a small formatting toolbar was added in the editor. It is hidden by default,
-   but can be opened by pressing the three dots icon in the top right corner.
+   At the same time, a small formatting toolbar was added to the editor. It is hidden by default,
+   but can be opened by pressing the button in the top--left corner of the editor header.
 
 
 Project Tree and Editor View
@@ -50,51 +57,60 @@ Project Tree and Editor View
 
    A screenshot of the Project Tree and Editor View.
 
-When in :guilabel:`Project Tree View` mode, the main work area of the main window 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.
+When the application is in **Project Tree View** mode, the work area of the main window 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.
 
-An optional third panel on the right 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 as it will apply the
-formatting tags you have specified. The main purpose of the viewer is for viewing your notes next
-to your editor while you're writing.
+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.
 
-The editor also has a :guilabel:`Focus Mode` you can toggle either from the menu, from the icon in
-the editor's header, or by pressing :kbd:`F8`. When :guilabel:`Focus Mode` is enabled, all the user
-interface elements other than the document editor itself are hidden away.
+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.
+
+The project tree will highlight with a different background colour the document that is currently
+open in the editor.
+
+.. versionadded:: 2.6
+
+   You can now drag and drop documents from the project tree onto the editor or viewer panels to
+   open them.
 
 
-Novel Tree and Editor View
+Novel View and Editor View
 --------------------------
 
 .. figure:: images/fig_novel_tree_view.png
 
-   A screenshot of the Novel Tree View.
+   A screenshot of the Novel Tree and Editor View.
 
-When in :guilabel:`Novel Tree View` mode, the project tree is replaced by an overview of your novel
-structure for a specific Novel :term:`root folder`. Instead of showing individual documents, the
-tree now shows all headings of your novel text. This includes multiple headings within the same
-document.
+When the application is in **Novel Tree View** mode, the project tree is replaced by an overview of
+your novel structure for a specific Novel :term:`root folder`. Instead of showing individual
+documents, the tree now shows all headings of your novel text. This includes multiple headings
+within the same document.
 
-Each heading is indented according to the heading level. 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.
+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.
 
-If you have multiple Novel 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.
+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.
 
 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 :guilabel:`Preferences`.) You can also regenerate the whole novel
-view by pressing the refresh button at the top of the side panel.
+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.
 
-It is possible to show an optional third column in the novel view, The settings are available from
+It is possible to show an optional third column in the novel view. The settings are available from
 the menu button in the toolbar.
 
-If you click the arrow icon to the right of each item, a tooltip will pop out showing you all the
+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.
 
 
@@ -105,30 +121,56 @@ Novel Outline View
 
    A screenshot of the Novel Outline View.
 
-When in :guilabel:`Novel Outline View` mode, the tree, editor and viewer will be replaced by a
-large table that shows the entire novel structure with all the tags and references listed. Pretty
+When the application is in **Novel Outline View** mode, the tree, editor and viewer are replaced by
+a large table that shows the entire novel structure with all the tags and references listed. Pretty
 much all collected meta data is available here in different columns.
 
 You can select which novel root folder to display from the dropdown box, and you can select which
 columns to show or hide from the menu button. You can also rearrange the columns by drag and drop.
-The app will remember your column order and size between sessions, and for each individual project.
+The app remembers your column order and sizes between sessions, and for each individual project.
 
 
 Colour Themes
 -------------
 
-By default, novelWriter will use the colour theme provided by the Qt library, which is determined
-by the Fusion_ style setting. You can also choose between a standard dark and light theme that have
-neutral colours from :guilabel:`Preferences`. Other colour themes are also available. More themes
-can be contributed to novelWriter on GitHub.
+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**. 
+
+If you wish, you *can* create your own colour themes, and even have them added to the application.
+See :ref:`a_custom_theme` for more details.
 
 Switching the GUI colour theme does not affect the colours of the editor and viewer. They have
-separate colour themes called :guilabel:`Editor Themes`. They are separated because there are a lot
-more options to choose from for the editor and viewer.
+separate colour 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.
 
 .. note::
-   If you switch to 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.
+
+   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.
+
+
+Project Search
+--------------
+
+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.
+
+.. versionadded:: 2.4
+
+
+Switching Focus
+---------------
+
+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.
+
+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,
+
+These two shortcuts make it possible to jump between all these GUI elements without having to reach
+for the mouse or touchpad.
 
 
 .. _a_breakdown_project:
@@ -136,7 +178,7 @@ more options to choose from for the editor and viewer.
 Project Layout
 ==============
 
-This is a brief introduction to how you structure your writing projects. All of this will be
+This is a brief introduction to how you should structure your writing projects. All of this will be
 covered in more detail later.
 
 The main point of novelWriter is that you are free to organise your project documents as you wish
@@ -147,53 +189,62 @@ within those documents.
 
 .. figure:: images/fig_header_levels.png
 
-   An illustration of how header levels correspond to the novel structure.
+   An illustration of how heading levels correspond to the novel structure.
 
-The four heading levels (**H1** to **H4**) are treated as follows:
+The four heading levels, **Level 1** to **Level 4**, are treated as follows:
 
-* **H1** is used for the novel title, and for partitions.
-* **H2** is used for chapter tiles.
-* **H3** is used for scene titles -- optionally replaced by separators.
-* **H4** is for section titles within scenes, if such granularity is needed.
+* **Level 1** is used for the novel title, and for partitions.
+* **Level 2** is used for chapter tiles.
+* **Level 3** is used for scene titles -- optionally replaced by separators.
+* **Level 4** is for section titles within scenes, if such granularity is needed.
 
 The project tree will select an icon for the document based on the first heading in it.
 
-This header level structure is only taken into account for :term:`novel documents`. For
-:term:`project notes`, the header levels have no structural meaning, and you are free to use them
+This heading level structure is only taken into account for :term:`novel documents`. For
+:term:`project notes`, the heading levels have no structural meaning, and you are free to use them
 however you want. See :ref:`a_struct` and :ref:`a_references` for more details.
 
-.. versionadded:: 2.0
+.. tip::
+
    You can add documents as child items of other documents. This is often more useful than adding
    folders, since you anyway may want to have the chapter heading in a separate document from your
    individual scene documents so that you can rearrange scene documents freely without affecting
    chapter placement.
 
+.. versionadded:: 2.6
+
+   The heading levels for partitions, chapters and scenes only apply within novelWriter. When you
+   generate your manuscript, chapters are considered as the topmost heading level, with scenes
+   below it. Partitions are inserted as text elements in most formats.
+
 
 .. _a_breakdown_export:
 
-Building the Manuscript
-=======================
+Building a Manuscript
+=====================
 
 The project can at any time be assembled into a range of different formats through the
-:guilabel:`Build Manuscript` tool. Natively, novelWriter supports `Open Document`_, HTML5, and
-various flavours of Markdown.
+**Build Manuscript** tool. Natively, novelWriter supports `Open Document`_, Microsoft Word Document
+(known as `Office Open XML`_), HTML5, and various flavours of Markdown. You can also generate a PDF
+document.
 
 The HTML5 format is suitable for conversion by a number of other tools like Pandoc_, or for
-importing into word processors if the Open Document format isn't suitable. The Open Document format
-is supported by most Office type applications. In addition, printing is also possible. Print to PDF
-is available from the print dialog.
+importing into word processors if the Open Document or Word Document format isn't suitable. The
+Open Document format is supported by most office type applications, so is the Word Document format.
+In addition, printing is also possible.
 
-In addition, you can export the content of the project to a JSON file. This is useful if you want
-to write your own custom processing script in for instance Python, as the entire novel can be read
-into a Python dictionary with a couple of lines of code. The JSON file can be populated with either
-HTML formatted text, or with the raw text as typed into the novel documents.
+For advanced processing, you can export the content of the project to a JSON file. This is useful
+if you want to write your own custom processing script in for instance Python, as the entire novel
+can be read into a Python dictionary with a couple of lines of code. The JSON file can be populated
+with either HTML formatted text, or with the raw text as typed it into the novel documents.
 
 See :ref:`a_manuscript` for more details.
 
 .. versionadded:: 2.1
-   You can now define multiple build definitions in the :guilabel:`Build Manuscript` tool. This
-   allows you to define specific settings for various types of draft documents, outline documents,
-   and manuscript formats. See :ref:`a_manuscript` for more details.
+
+   You can now define multiple build definitions in the **Build Manuscript** tool. This allows you
+   to define specific settings for various types of draft documents, outline documents, and
+   manuscript formats. See :ref:`a_manuscript` for more details.
 
 
 .. _a_breakdown_storage:
@@ -203,8 +254,8 @@ Project Storage
 
 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 is stored in other folders below the project folder. For more technical
-details about what all the files mean and how they're organised, see the :ref:`a_storage` section.
+associated meta data are stored in other folders below the project folder. For a more technical
+description of what all the files mean and how they're organised, see the :ref:`a_storage` section.
 
 This way of storing data was chosen for several reasons.
 
@@ -216,17 +267,19 @@ 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. Also the JSON documents have line breaks and indents, which
-makes it easier to track them with version control software.
+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 :term:`Project Index` when you open

docs/source/usage_format.rst

@@ -6,14 +6,18 @@ Formatting Your Text
 
 The novelWriter text editor is a plain text editor that uses formatting codes for setting meta data
 values and allowing for some text formatting. The syntax is based on Markdown, but novelWriter is
-*not* a Markdown editor. It supports basic formatting like emphasis (italic), strong importance
-(bold) and strike through text, as well as four levels of headings. Form some further complex
+**not** a Markdown editor. It supports basic formatting like emphasis (italic), strong importance
+(bold) and strike through text, as well as four levels of headings. For some further complex
 formatting needs, a set of shortcodes can be used.
 
-In addition to formatting codes, novelWriter allows for comments, a synopsis tag, and a set of
+In addition to formatting codes, novelWriter allows for comments, a synopsis tag, and a number of
 keyword and value sets used for :term:`tags<tag>` and :term:`references<reference>`. There are also
 some codes that apply to whole paragraphs. See :ref:`a_fmt_text` for more details.
 
+URLs should also 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.
+
 
 .. _a_fmt_hlight:
 
@@ -30,12 +34,12 @@ dialogue in your text.
    An example of the colour highlighting of references. "Bob" is not defined, and "@blabla" is not
    a valid reference type.
 
-When you use the commands to set tags and references, these also change colour. Correct commands
+When you use the keywords to set tags and references, these also change colour. Correct keywords
 have a distinct colour, and the references themselves will get a colour if they are valid. Invalid
 references will get a squiggly error line underneath. The same applies to duplicate tags.
 
 There are a number of syntax highlighter colour themes available, both for light and dark GUIs. You
-can select them from :guilabel:`Preferences`.
+can select them from **Preferences**.
 
 
 .. _a_fmt_head:
@@ -45,7 +49,7 @@ Headings
 
 .. figure:: images/fig_header_levels.png
 
-   An illustration of how header levels correspond to the novel structure.
+   An illustration of how heading levels correspond to the novel structure.
 
 Four levels of headings are allowed. For :term:`project notes`, they are free to be used as you see
 fit. That is, novelWriter doesn't assign the different headings any particular meaning. However,
@@ -53,35 +57,45 @@ for :term:`novel documents` they indicate the structural level of the novel and
 correctly to produce the intended result. See :ref:`a_struct_heads` for more details.
 
 ``# Title Text``
-   Heading level one. For novel documents, the header level indicates the start of a new partition.
+   Heading level one. For novel documents, the level 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.
 
 ``## Title Text``
-   Heading level two. For novel documents, the header level indicates the start of a new chapter.
-   Chapter numbers can be inserted automatically when building the manuscript.
+   Heading level two. For novel documents, the level indicates the start of a new chapter. Chapter
+   numbers can be inserted automatically when building the manuscript.
 
 ``### Title Text``
-   Heading level three. For novel documents, the header level 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.
+   Heading level three. For novel documents, the level 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.
 
 ``#### Title Text``
-   Heading level four. For novel documents, the header level indicates the start of a new section.
-   Section titles can be replaced by separators or ignored completely when building the manuscript.
+   Heading level four. For novel documents, the level indicates the start of a new section. Section
+   titles can be replaced by separators or ignored completely when building the manuscript.
 
-For headers level one and two, adding a ``!`` modifies the behaviour of the heading:
+For headings level one through three, adding a ``!`` modifies the meaning of the heading:
 
 ``#! Title Text``
-   This tells the build tool that the level one heading is intended to be used for the novel's
-   main title, like for instance on the front page. When building the manuscript, this will use a
-   different styling and will exclude the title from, for instance, a Table of Contents in Libre
-   Office.
+   This tells the 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.
 
 ``##! Title Text``
    This tells the build tool to not assign a chapter number to this chapter title if automatic
-   chapter numbers are being used. Such titles are useful for a prologue for instance. See
-   :ref:`a_struct_heads_unnum` for more details.
+   chapter numbers are being used. Such titles are useful for prologues and epilogues for instance.
+   See :ref:`a_struct_heads_unnum` for more details.
+
+``###! Title Text``
+   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:`a_struct_heads_scenes` for more
+   details.
 
 .. note::
+
    The space after the ``#`` or ``!`` character is mandatory. The syntax highlighter will change
    colour and font size when the heading is correctly formatted.
 
@@ -99,37 +113,45 @@ In addition, the editor supports a few additional types of white spaces:
 
 * 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`.
+* Non-breaking thin space can be inserted with :kbd:`Ctrl+K`, :kbd:`Ctrl+Space`.
 
-These are all insert features, and the :guilabel:`Insert` menu has more. They are also listed
-in :ref:`a_kb_ins`.
+These are all insert features, and the **Insert** menu has more. The keyboard shortcuts for them
+are also listed in :ref:`a_kb_ins`.
 
 Non-breaking spaces are highlighted by the syntax highlighter with an alternate coloured
 background, depending on the selected theme.
 
 .. tip::
+
    Non-breaking spaces are for instance the correct type of space to separate a number from its
    unit. Generally, non-breaking spaces are used to prevent line wrapping algorithms from adding
    line breaks where they shouldn't.
 
+.. note::
+
+   You should not manually apply text indentation in your paragraphs in the editor. These can be
+   added automatically in the **Manuscript Build** tool if you want to have them in the manuscript.
+   Each new paragraph should be separated from the previous content by an empty line and with no
+   indentation.
+
 
 .. _a_fmt_emph:
 
-Text Emphasis
-=============
+Text Emphasis with Markdown
+===========================
 
-A minimal set of text emphasis styles are supported for text paragraphs.
+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 important text (bold).
+   The text is rendered as strongly emphasised text (bold).
 
 ``~~text~~``
    Strike through text.
 
-In Markdown guides it is often recommended to differentiate between strong importance and emphasis
+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
@@ -141,15 +163,16 @@ In addition, the following rules apply:
    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*
+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 plain paragraphs. Comments, titles, and meta data tags don't
+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 rendered 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
@@ -158,8 +181,8 @@ In addition, the following rules apply:
 
 .. _a_fmt_shortcodes:
 
-Extended Formatting with Shortcodes
-===================================
+Formatting with Shortcodes
+==========================
 
 For additional formatting options, you can use shortcodes. Shortcodes is a form of in-line codes
 that can be used to change the format of the text that follows and opening code, and last until
@@ -177,14 +200,22 @@ solved with simple Markdown-like formatting codes. Available shortcodes are list
    "``[i]text[/i]``",     "Text is rendered as italicised text."
    "``[s]text[/s]``",     "Text is rendered as strike through text."
    "``[u]text[/u]``",     "Text is rendered as underlined text."
+   "``[m]text[/m]``",     "Text is rendered as highlighted text."
    "``[sup]text[/sup]``", "Text is rendered as superscript text."
    "``[sub]text[/sub]``", "Text is rendered as subscript text."
 
 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 :guilabel:`Format` menu and in the editor toolbar, which can
-be activated by clicking the three dots in the editor header.
+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
 
@@ -194,59 +225,127 @@ be activated by clicking the three dots in the editor header.
 Comments and Synopsis
 =====================
 
-In addition to these standard Markdown features, novelWriter also allows for comments in documents.
-The text of a comment is ignored by the word counter. The text can also be filtered out when
-building the manuscript or viewing the document.
+In addition to the above formatting features, novelWriter also allows for comments in documents.
+The text of a comment is always ignored by the word counter. The text can also be filtered out
+when building the manuscript or viewing the document.
 
-If the first word of a comment is ``Synopsis:`` (with the colon included), the comment is treated
-in a special manner and will show up in the :ref:`a_ui_outline` in a dedicated column. The word
-``synopsis`` is not case sensitive. If it is correctly formatted, the syntax highlighter will
-indicate this by altering the colour of the word.
+The first word of a comment, followed by a colon, can be one of a set of modifiers that indicates
+the comment is intended for a specific purpose. For instance, if the comment starts with
+``Synopsis:``, the comment is treated in a special manner and will show up in the
+:ref:`a_ui_outline` in a dedicated column. The word ``synopsis`` is not case sensitive. If it is
+correctly formatted, the syntax highlighter will indicate this by altering the colour of the word.
 
-``% text ...``
+The different styles of comments are as follows:
+
+``% Your comment text ...``
    This is a comment. The text is not rendered by default (this can be overridden), seen in the
-   document viewer, or counted towards word counts.
+   document viewer, or counted towards word counts. It is intended for you to make notes in your
+   text for your own sake, whatever that may be, that isn't part of the story text. This is the
+   general format of a comment.
 
-``%Synopsis: text ...``
+``%Synopsis: Your synopsis text ...``
    This is a synopsis comment. It is generally treated in the same way as a regular comment, except
    that it is also captured by the indexing algorithm and displayed in the :ref:`a_ui_outline`. It
    can also be filtered separately when building the project to for instance generate an outline
    document of the whole project.
 
-``%Short: text ...``
-   This is a short description comment. It is identical to the synopsis comment, but is intended to
-   be used for project notes. The text shows up in the Reference panel below the document viewer in
-   the last column labelled :guilabel:`Short Description`.
+``%Short: Your short description ...``
+   This is a short description comment. It is identical to the synopsis comment (they are
+   interchangeable), but is intended to be used for project notes. The text shows up in the
+   Reference panel below the document viewer in the last column labelled **Short Description**.
+
+``%Footnote.<key>: Your footnote text ...``
+   This is a special comment assigned to a footnote marker. See :ref:`a_fmt_footnote` for how to
+   use them in your text.
 
 .. note::
+
    Only one comment can be flagged as a synopsis or short comment for each heading. If multiple
    comments are flagged as synopsis or short comments, the last one will be used and the rest
    ignored.
 
 
+.. _a_fmt_footnote:
+
+Footnotes
+=========
+
+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.
+
+The insert feature will add the footnote shortcode marker at the position of your cursor in the
+text, and create the associated footnote comment right after the paragraph, and 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 in the first place (1 in 810 000).
+
+This is what a footnote inserted into a paragraph may look like when completed:
+
+.. code-block:: md
+
+   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
+
+
+.. _a_fmt_ignore:
+
+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.
+
+Example:
+
+.. code-block:: md
+
+   %~ This text is ignored.
+
+   This text is a regular paragraph.
+
+
 .. _a_fmt_tags:
 
 Tags and References
 ===================
 
 The document editor supports a set of keywords used for setting tags, and making references between
-documents.
+documents based on those tags.
 
-Tags use the command ``@tag:`` to define a tag. The tag can be set once per section defined by a
-heading. Setting it multiple times under the same heading will just override the previous setting.
+You must use the keyword ``@tag:`` to define a tag. The tag can be set once per section defined by
+a heading. Setting it multiple times under the same heading will just override the previous
+setting.
 
 ``@tag: value``
-   A tag command followed by the tag value, like for instance the name of a character.
+   A tag keyword followed by the tag value, like for instance the name of a character.
 
 References can be set anywhere within a section, and are collected according to their category.
-References are in the form:
+References are on the form:
 
-``@keyword: value``
+``@keyword: value1, value2, ..., valueN``
    A reference keyword followed by a value, or a comma separated list of values.
 
 Tags and references are covered in detail in the :ref:`a_references` chapter. The keywords can be
-inserted at the cursor position in the editor via the :guilabel:`Insert` menu. If you start typing
-an ``@`` on a new line, and auto-complete menu will also pop up suggesting keywords.
+inserted at the cursor position in the editor via the **Insert** menu. If you start typing an ``@``
+on a new line, and auto-complete menu will also pop up suggesting keywords.
 
 
 .. _a_fmt_align:
@@ -254,8 +353,8 @@ an ``@`` on a new line, and auto-complete menu will also pop up suggesting keywo
 Paragraph Alignment and Indentation
 ===================================
 
-All documents have the text by default aligned to the left or justified, depending on your
-settings in :guilabel:`Preferences`.
+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
@@ -280,9 +379,41 @@ Examples:
    "``> 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 build tool as long as the format supports paragraph alignment.
+   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:
+
+.. 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.
+
+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
 
 
 .. _a_fmt_break:
@@ -290,37 +421,50 @@ Examples:
 Vertical Space and Page Breaks
 ==============================
 
-Adding more than one line break between paragraphs will *not* increase the space between those
+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 building the project. To add additional space between paragraphs, add the text
-``[VSPACE]`` on a line of its own, and the build tool will insert a blank paragraph in its place.
+``[vspace]`` on a line of its own, and the 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.
+instance, writing ``[vspace:3]`` will insert three blank paragraphs.
 
-Normally, the build tool will insert a page break before all headers of level one and for all
-headers of level two for novel documents, i.e. chapters, but not for project notes.
-
-If you need to add a page break somewhere else, put the text ``[NEW PAGE]`` on a line by itself
-before the text you wish to start on a new page.
-
-If you want page breaks for scenes and sections, you must add them manually.
+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]`` which has
+   to the text when exporting to HTML or Open Document. This means that a ``[new page]`` which has
    no text following it, it will not result in a page break.
 
 **Example:**
 
-.. code-block:: markdown
+.. code-block:: md
 
    This is a text paragraph.
 
-   [VSPACE:2]
+   [vspace:2]
 
    This is another text paragraph, but there will be two empty paragraphs
-   in-between them.
+   between them.
 
-   [NEWPAGE]
+   [new page]
 
-   This text will always start on a new page if the build format has pages.
+   This text will start on a new page if the build format has pages.
+
+
+.. _a_fmt_stats:
+
+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. You can generate the code for this 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.

docs/source/usage_project.rst

@@ -8,7 +8,7 @@ This chapter covers in more detail the different project views available in nove
 
 .. figure:: images/fig_project_tree_detailed.png
 
-   The Project Tree as it appears when loading a sample project.
+   The **Project Content** tree as it appears when loading a sample project.
 
 
 .. _a_ui_tree:
@@ -21,33 +21,32 @@ the project, and has four columns.
 
 **Column 1**
    The first column shows the icon and label of each folder, document, or note in your project. The
-   label is not the same as the title you set inside the document. However, the document's label
-   will appear in the header above the document text itself so you know where in the project an
-   open document belongs. The icon is selected based on the type of item, and for novel documents,
-   the level of the first header in the document text.
+   label is not the same as the heading title you set inside the document. However, the document's
+   label will appear in the header above the document text itself so you know where in the project
+   an open document belongs. The icon is selected based on the type of item, and for novel
+   documents, the level of the first heading in the document text.
 
 **Column 2**
    The second column shows the word count of the document, or the sum of words of the child items
    for folders and documents with sub-documents. If the counts seem incorrect, they can be updated
-   by rebuilding the :term:`project index` from the :guilabel:`Tools` menu, or by pressing
-   :kbd:`F9`.
+   by rebuilding the :term:`project index` from the **Tools** menu, or by pressing :kbd:`F9`.
 
 **Column 3**
    The third column indicates whether the document is considered active or inactive in the project.
    You can use this flag to indicate that a document is still in the project, but should not be
-   considered an active part of it. When you run the :guilabel:`Build Manuscript` tool, you can
-   include or exclude documents based on this flag. You can change this value from the
+   considered an active part of it. When you run the **Build Manuscript** tool, you can include or
+   exclude documents based on this flag. You can change this value from the right-click
    :term:`context menu`.
 
 **Column 4**
    The fourth column shows the user-defined status or importance labels you've assigned to each
    project item. See :ref:`a_ui_tree_status` for more details on how to uses these labels. You can
-   change these labels from the :term:`context menu`.
+   select these labels from the :term:`context menu`, and define them in **Project Settings**.
 
 Right-clicking an item in the project tree will open a context menu under the cursor, displaying
 a selection of actions that can be performed on the selected item.
 
-At the top of the tree, you will find a set of buttons.
+At the top of the project tree, you will find a set of buttons.
 
 * The first button is a quick links button that will show you a dropdown menu of all the
   :term:`root folders<root folder>` in your project. Selecting one will move to that position in
@@ -55,7 +54,8 @@ At the top of the tree, you will find a set of buttons.
 * The next two buttons can be used to move items up and down in the project tree. This is the only
   way to move root folders.
 * The next button opens a dropdown menu for adding new items to the tree. This includes root
-  folders. You can also activate this dropdown menu by pressing :kbd:`Ctrl+N`.
+  folders and template documents. You can also activate this dropdown menu by pressing
+  :kbd:`Ctrl+N`.
 * The last button is a menu of further actions you can apply to the project tree.
 
 Below the project tree you will find a small details panel showing the full information of the
@@ -63,6 +63,7 @@ currently selected item. This panel also includes the latest paragraph and chara
 addition to the word count.
 
 .. tip::
+
    If you want to set the label of a document to be the same as a header within it, you can
    right-click a header in the document when it is open in the editor and select
    :guilabel:`Set as Document Name` from the context menu.
@@ -73,10 +74,10 @@ addition to the word count.
 Splitting and Merging Documents
 -------------------------------
 
-Under the :guilabel:`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.
+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.
 
 
 Splitting Documents
@@ -84,17 +85,17 @@ Splitting Documents
 
 .. figure:: images/fig_project_split_tool.png
 
-   The :guilabel:`Split Document` dialog.
+   The **Split Document** dialog.
 
-The :guilabel:`Split Document by Header` 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.
+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.
 
 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.
 
-The source document *is not* deleted in the process, but you have the option to let the tool move
+The source document **is not** deleted in the process, but you have the option to let the tool move
 the source document to the :guilabel:`Trash` folder.
 
 
@@ -103,18 +104,18 @@ Merging Documents
 
 .. figure:: images/fig_project_merge_tool.png
 
-   The :guilabel:`Merge Documents` dialog.
+   The **Merge Documents** dialog.
 
 You have two options for merging documents that are child elements of another document. You can
-either :guilabel:`Merge Child Items into Self` and :guilabel:`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.
+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.
 
 When merging documents in a folder, you only have the latter process is possible, so only the
-choice :guilabel:`Merge Documents in Folder` is available.
+choice **Merge Documents in Folder** is available.
 
-In either case, the :guilabel:`Merge Documents` dialog will let you exclude documents you don't
-want to include, and it also lets you reorder them if you wish.
+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.
 
 
 .. _a_ui_tree_status:
@@ -123,16 +124,16 @@ Document Importance and Status
 ------------------------------
 
 Each document or folder in your project can have either a "Status" or "Importance" flag set. These
-are flags that you control and define yourself. novelWriter doesn't do anything with them at all.
-To modify the labels, go to their respective tabs in :guilabel:`Project Settings`.
+are flags that you control and define yourself, and novelWriter doesn't use them for anything. To
+modify the labels, go to their respective tabs in **Project Settings**.
 
 The "Status" flag is intended to tag a :term:`novel document<novel documents>` as for instance a
 draft or as completed, and the "Importance" flag is intended to tag character notes, or other
 :term:`project notes`, as for instance a main, major, or minor character or story element.
 
 Whether a document uses a "Status" or "Importance" flag depends on which :term:`root folder` it
-lives in. If it's in a :guilabel:`Novel` folder, it uses the "Status" flag, otherwise it uses an
-"Importance" flag. Some folders, like :guilabel:`Trash` and :guilabel:`Archive` allow both.
+lives in. If it's in a **Novel** type folder, it uses the "Status" flag, otherwise it uses an
+"Importance" flag.
 
 
 .. _a_ui_tree_dnd:
@@ -140,47 +141,48 @@ lives in. If it's in a :guilabel:`Novel` folder, it uses the "Status" flag, othe
 Project Tree Drag & Drop
 ------------------------
 
-The project tree allows drag & drop to a certain extent to allow 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 :guilabel:`Manuscript Build` tool.
+The project tree allows drag & drop to allow 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.
 
 .. versionadded:: 2.2
+
    You can now select multiple items in the project tree by holding down the :kbd:`Ctrl` or
    :kbd:`Shift` key while selecting items.
 
-You can drag and drop documents and regular folders, but not root folders. If you select multiple
-items, they can only be dragged and dropped if they are siblings. That is, they have the same
-parent item in the project. This is due to the way drag and drop is implemented in the user
-interface framework novelWriter is built upon.
-
-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 :guilabel:`Novel` root
-folder, its "Importance" setting will be switched with a "Status" setting. See
+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:`a_ui_tree_status`. The old value will not be overwritten though, and should be restored if
 you move it back at some point.
 
 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 from the arrow buttons at the top of the
-project tree, or by pressing :kbd:`Ctrl+Shift+Up` or :kbd:`Ctrl+Shift+Down` when they are selected.
+project tree, or by pressing :kbd:`Ctrl+Up` or :kbd:`Ctrl+Down` when they are selected.
+
+.. tip::
+
+   You can drag and drop documents onto the editor or viewer panel to open them.
 
 
 .. _a_ui_tree_novel:
 
-The Novel Tree
-==============
+The Novel Tree View
+===================
 
 .. figure:: images/fig_novel_tree_view.png
 
    A screenshot of the Novel Tree View.
 
-An alternative way to view the project structure is the novel tree. You can switch to this view by
-selecting the :guilabel:`Novel Tree View` button in the sidebar. This view is a simplified version
-of the view in the :guilabel:`Outline View`. It is convenient when you want to browse the structure
-of the story itself rather than the document files.
+An alternative way to view the project structure is the novel view. You can switch to this view by
+selecting the :guilabel:`Novel View` button in the sidebar. This view is a simplified version of
+the view in the **Outline View**. It is convenient when you want to browse the structure of the
+story itself rather than the document files.
 
 .. note::
-   You cannot reorganise the entries in the novel tree, or add any new documents, as that would
+
+   You cannot reorganise the entries in the novel view, or add any new documents, as that would
    imply restructuring the content of the document files 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.
@@ -188,26 +190,27 @@ of the story itself rather than the document files.
 
 .. _a_ui_outline:
 
-Project Outline View
-====================
+The Novel Outline View
+======================
 
 .. figure:: images/fig_outline_view.png
 
    A screenshot of the Novel Outline View.
 
-The project's :guilabel:`Outline View` is available as another view option from the sidebar. The
+The project's **Novel Outline View** is available as another view option from the sidebar. The
 outline provides an overview of the novel structure, displaying a tree hierarchy of the elements of
 the novel, that is, the level 1 to 4 headings representing partitions, chapters, scenes and
 sections.
 
 The document containing the heading can also be displayed as a separate column, as well as the line
 number where the heading is defined. Double-clicking an entry will open the corresponding document
-in the editor and switch to :guilabel:`Project Tree View` mode.
+in the editor and switch to **Project Tree View** mode.
 
 You can select which novel folder to display from the dropdown menu. You can optionally also choose
 to show a combination of all novel folders.
 
 .. note::
+
    Since the internal structure of the novel does not depend directly on the folder and document
    structure of the project tree, this view will not necessarily look the same, depending on how
    you choose to organise your documents. See the :ref:`a_struct` page for more details.
@@ -218,7 +221,8 @@ the menu button in the toolbar. The order of the columns can also be rearranged
 a different position. You column settings are saved between sessions on a per-project basis.
 
 .. note::
-   The :guilabel:`Title` column cannot be disabled or moved.
+
+   The **Title** column cannot be disabled or moved.
 
 The information viewed in the outline is based on the :term:`project index`. While novelWriter does
 its best to keep the index up to date when contents change, you can always rebuild it manually by
@@ -227,5 +231,5 @@ pressing :kbd:`F9` if something isn't right.
 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.
 
-The :guilabel:`Synopsis` column of the outline view takes its information from a specially
-formatted comment. See :ref:`a_fmt_comm`.
+The **Synopsis** column of the outline view takes its information from a specially formatted
+comment. See :ref:`a_fmt_comm`.

docs/source/usage_shortcuts.rst

@@ -20,22 +20,22 @@ Main Window Shortcuts
    :header: "Shortcut", "Description"
 
    ":kbd:`F1`",           "Open the online user manual"
-   ":kbd:`F5`",           "Open the :guilabel:`Build Manuscript` tool"
-   ":kbd:`F6`",           "Open the :guilabel:`Writing Statistics` tool"
-   ":kbd:`F8`",           "Toggle :guilabel:`Focus Mode`"
-   ":kbd:`F9`",           "Re-build the project index"
+   ":kbd:`F5`",           "Open the **Build Manuscript** tool"
+   ":kbd:`F6`",           "Open the **Writing Statistics** tool"
+   ":kbd:`F8`",           "Toggle **Focus Mode**"
+   ":kbd:`F9`",           "Re-build the project's index"
    ":kbd:`F11`",          "Toggle full screen mode"
-   ":kbd:`Ctrl+,`",       "Open the :guilabel:`Preferences` dialog"
-   ":kbd:`Ctrl+E`",       "Switch focus to the document editor"
-   ":kbd:`Ctrl+T`",       "Switch focus to the project/novel tree"
+   ":kbd:`Ctrl+,`",       "Open the **Preferences** dialog"
+   ":kbd:`Ctrl+E`",       "Switch or toggle focus for the editor or viewer"
+   ":kbd:`Ctrl+T`",       "Switch or toggle focus for the project tree or novel view"
    ":kbd:`Ctrl+Q`",       "Exit novelWriter"
-   ":kbd:`Ctrl+Shift+,`", "Open the :guilabel:`Project Settings` dialog"
-   ":kbd:`Ctrl+Shift+O`", "Open a project"
+   ":kbd:`Ctrl+Shift+,`", "Open the **Project Settings** dialog"
+   ":kbd:`Ctrl+Shift+O`", "Open the Welcome dialog to open or create a project"
    ":kbd:`Ctrl+Shift+S`", "Save the current project"
    ":kbd:`Ctrl+Shift+T`", "Switch focus to the outline view"
    ":kbd:`Ctrl+Shift+W`", "Close the current project"
    ":kbd:`Shift+F1`",     "Open the local user manual (PDF) if it is available"
-   ":kbd:`Shift+F6`",     "Open the :guilabel:`Project Details` dialog"
+   ":kbd:`Shift+F6`",     "Open the **Project Details** dialog"
 
 
 .. _a_kb_tree:
@@ -53,14 +53,13 @@ Project Tree Shortcuts
    ":kbd:`Alt+Left`",       "Jump to the parent item in the tree"
    ":kbd:`Alt+Right`",      "Jump to the first child item in the project tree"
    ":kbd:`Ctrl+.`",         "Open the context menu on the selected item"
-   ":kbd:`Ctrl+L`",         "Open the :guilabel:`Quick Links` menu"
-   ":kbd:`Ctrl+N`",         "Open the :guilabel:`Create New Item` menu"
-   ":kbd:`Ctrl+O`",         "Open selected document"
+   ":kbd:`Ctrl+L`",         "Open the **Quick Links** menu"
+   ":kbd:`Ctrl+N`",         "Open the **Create New Item** menu"
+   ":kbd:`Ctrl+O`",         "Open the selected document in the editor"
    ":kbd:`Ctrl+R`",         "Open the selected document in the viewer"
    ":kbd:`Ctrl+Up`",        "Move selected item one step up in the tree"
    ":kbd:`Ctrl+Down`",      "Move selected item one step down in the tree"
    ":kbd:`Ctrl+Shift+Del`", "Move the selected item to Trash"
-   ":kbd:`Ctrl+Shift+Z`",   "Undo the last move of a project item, if possible"
 
 
 .. _a_kb_editor:
@@ -76,11 +75,12 @@ Text Search Shortcuts
    :header: "Shortcut", "Description"
 
    ":kbd:`F3`",           "Find the next occurrence of the search word"
-   ":kbd:`Ctrl+F`",       "Open the search bar and search for the selected word, if any is selected"
+   ":kbd:`Ctrl+F`",       "Open search and look for the selected word"
    ":kbd:`Ctrl+G`",       "Find the next occurrence of the search word"
-   ":kbd:`Ctrl+H`",       "Open the search tool and populate with the selected word (Mac :kbd:`Cmd+=`)"
-   ":kbd:`Ctrl+Shift+1`", "Replace selected occurrence of the search word, and move to the next"
+   ":kbd:`Ctrl+H`",       "Open replace and look for the selected word (Mac :kbd:`Cmd+=`)"
+   ":kbd:`Ctrl+Shift+1`", "Replace selected occurrence, and move to the next"
    ":kbd:`Ctrl+Shift+G`", "Find the previous occurrence of the search word"
+   ":kbd:`Ctrl+Shift+F`", "Open project search and look for the selected word"
    ":kbd:`Shift+F3`",     "Find the previous occurrence of the search word"
 
 
@@ -92,21 +92,22 @@ Text Formatting Shortcuts
 
    ":kbd:`Ctrl+'`",       "Wrap selected text, or word under cursor, in single quotes"
    ":kbd:`Ctrl+""`",      "Wrap selected text, or word under cursor, in double quotes"
-   ":kbd:`Ctrl+/`",       "Toggle block format as comment"
-   ":kbd:`Ctrl+0`",       "Remove block formatting for block under cursor"
-   ":kbd:`Ctrl+1`",       "Change block format to header level 1"
-   ":kbd:`Ctrl+2`",       "Change block format to header level 2"
-   ":kbd:`Ctrl+3`",       "Change block format to header level 3"
-   ":kbd:`Ctrl+4`",       "Change block format to header level 4"
+   ":kbd:`Ctrl+/`",       "Toggle comment format for block or selected text"
+   ":kbd:`Ctrl+0`",       "Remove format for block or selected text"
+   ":kbd:`Ctrl+1`",       "Change block format to heading level 1"
+   ":kbd:`Ctrl+2`",       "Change block format to heading level 2"
+   ":kbd:`Ctrl+3`",       "Change block format to heading level 3"
+   ":kbd:`Ctrl+4`",       "Change block format to heading level 4"
    ":kbd:`Ctrl+5`",       "Change block alignment to left-aligned"
    ":kbd:`Ctrl+6`",       "Change block alignment to centred"
    ":kbd:`Ctrl+7`",       "Change block alignment to right-aligned"
    ":kbd:`Ctrl+8`",       "Add a left margin to the block"
    ":kbd:`Ctrl+9`",       "Add a right margin to the block"
-   ":kbd:`Ctrl+B`",       "Format selected text, or word under cursor, with strong emphasis (bold)"
-   ":kbd:`Ctrl+D`",       "Strike through selected text, or word under cursor"
-   ":kbd:`Ctrl+I`",       "Format selected text, or word under cursor, with emphasis (italic)"
-   ":kbd:`Ctrl+Shift+/`", "Remove block formatting for block under cursor"
+   ":kbd:`Ctrl+B`",       "Format selected text, or word under cursor, with bold"
+   ":kbd:`Ctrl+D`",       "Format selected text, or word under cursor, with strike through"
+   ":kbd:`Ctrl+I`",       "Format selected text, or word under cursor, with italic"
+   ":kbd:`Ctrl+Shift+/`", "Remove format for block or selected text"
+   ":kbd:`Ctrl+Shift+D`", "Toggle ignored text format for block or selected text"
 
 
 Other Editor Shortcuts
@@ -115,7 +116,7 @@ Other Editor Shortcuts
 .. csv-table::
    :header: "Shortcut", "Description"
 
-   ":kbd:`F7`",             "Re-run the spell checker"
+   ":kbd:`F7`",             "Re-run the spell checker on the document"
    ":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"
@@ -132,7 +133,6 @@ Other Editor Shortcuts
    ":kbd:`Ctrl+F7`",        "Toggle spell checking"
    ":kbd:`Ctrl+Return`",    "Open the tag or reference under the cursor in the viewer"
    ":kbd:`Ctrl+Shift+A`",   "Select all text in the current paragraph"
-   ":kbd:`Ctrl+Shift+I`",   "Import text to the current document from a text file"
 
 
 .. _a_kb_ins:
@@ -165,6 +165,7 @@ a key or key combination for the inserted content.
    ":kbd:`Ctrl+K`, :kbd:`G`",           "Insert a ``@tag`` keyword"
    ":kbd:`Ctrl+K`, :kbd:`H`",           "Insert a short description comment"
    ":kbd:`Ctrl+K`, :kbd:`L`",           "Insert a ``@location`` keyword"
+   ":kbd:`Ctrl+K`, :kbd:`M`",           "Insert a ``@mention`` keyword"
    ":kbd:`Ctrl+K`, :kbd:`O`",           "Insert an ``@object`` keyword"
    ":kbd:`Ctrl+K`, :kbd:`P`",           "Insert a ``@plot`` keyword"
    ":kbd:`Ctrl+K`, :kbd:`S`",           "Insert a synopsis comment"

docs/source/usage_typography.rst

@@ -11,7 +11,7 @@ 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 :guilabel:`Insert` menu, and via
+thin spaces, etc. All these symbols are available from the **Insert** menu, and via
 keyboard shortcuts. See :ref:`a_kb_ins`.
 
 This chapter provides some additional information on how novelWriter handles these symbols.
@@ -43,22 +43,22 @@ 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 :guilabel:`Preferences`.
+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
-:guilabel:`Preferences` if this feature isn't wanted.
+**Preferences** if this feature isn't wanted.
 
 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 :guilabel:`Format` menu
+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.
 
 
 Single and Double Prime
 ------------------------
 
-Both single and double prime symbols are available in the :guilabel:`Insert` menu. These symbols
+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
@@ -79,7 +79,7 @@ right single quotation marks, depending on the font. There is a Wikipedia articl
 `Modifier letter apostrophe`_ with more details.
 
 .. note::
-   On export with the :guilabel:`Build Manuscript` tool, these apostrophes will be replaced
+   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.
 

docs/source/usage_writing.rst

@@ -18,20 +18,22 @@ Editing a Document
 
    A screenshot of the Document Editor panel.
 
-To edit a document, double-click it in the project tree, or press the :kbd:`Return` key while
-having it selected. This will open the document in the document editor. The editor uses a
-Markdown-like syntax for some features, and a novelWriter-specific syntax for others. The syntax
-format is described in the :ref:`a_fmt` chapter.
+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. The editor uses a Markdown-like syntax for some features, and a novelWriter-specific syntax
+for others. The syntax format is described in the :ref:`a_fmt` chapter.
 
-The editor has a maximise button (toggles the :guilabel:`Focus Mode`) and a close button in the
+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, and a search button to open the search dialog.
+few buttons for applying text formatting, a drop down menu for navigating between headings, and a
+search button to open the search dialog.
 
 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 :guilabel:`Preferences`.
+be shown. This can be set in **Preferences**.
 
 .. tip::
+
    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.
 
@@ -39,16 +41,33 @@ Any :term:`references<reference>` in the editor can be opened in the viewer by m
 the label and pressing :kbd:`Ctrl+Return`. You can also control-click them with your mouse.
 
 
+Spell Checking
+--------------
+
+A third party library called Enchant is used for spell checking in the editor. The controls for
+spell checking can be found in the **Tools** menu. You can also set spell checking language in
+**Project Settings**.
+
+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 can the list of words can be
+edited from the **Project Word List** tool available from the **Tools** menu.
+
+.. note::
+
+   Generally, spell checking dictionaries are collected from your operating system, but on Windows
+   they are not. See :ref:`a_custom_dict` for how to add spell checking dictionaries on Windows.
+
+
 Editor Auto-Completer
 ---------------------
 
-If you type the character ``@`` on a new line, a context menu will appear showing the different
+If you type the character ``@`` on a new line, a pop-up menu will appear showing the different
 available keywords. The list will shorten as you type. Once a keyword command has been selected or
-typed, the editor may suggest further content based on your project content. See
+typed, the editor may suggest further options based on your project content. See
 :ref:`a_references_completer` for more details.
 
 .. versionadded:: 2.2
-   The auto-completer feature was added.
 
 
 .. _a_ui_view:
@@ -61,14 +80,14 @@ Viewing a Document
    A screenshot of the Document Viewer panel.
 
 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`, or select :guilabel:`View Document` in the menu or
-context menu. If you have a middle mouse button, middle-clicking on the document will also open it
-in the viewer.
+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.
 
 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` again 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.
+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.
 
 In the viewer :term:`references<reference>` become clickable links. Clicking them will replace the
 content of the viewer with the content of the document the reference points to.
@@ -76,21 +95,24 @@ content of the viewer with the content of the document the reference points to.
 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.
+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.
 
-At the bottom of the view panel there is a :guilabel:`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.
+At the bottom of the view panel there is 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.
 
 .. note::
-   The :guilabel:`References` panel relies on an up-to-date :term:`index<project index>` of the
-   project. The index is maintained automatically. However, if anything is missing, or seems wrong,
-   the index can always be rebuilt by selecting :guilabel:`Rebuild Index` from the
-   :guilabel:`Tools` menu, or by pressing :kbd:`F9`.
+
+   The **References** panel relies on an up-to-date :term:`index<project index>` of the project.
+   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`.
 
 .. versionadded:: 2.2
+
    The reference panel was redesigned and the additional tabs added.
 
 
@@ -117,12 +139,10 @@ document when reaching the end. There is also a switch that will try to match th
 when the replacement is made. That is, it will try to keep the word upper, lower, or capitalised to
 match the word being replaced.
 
-The regular expression search is somewhat dependant on which version of Qt your system has. If you
-have Qt 5.13 or higher, there is better support for Unicode symbols in the search.
-
 .. seealso::
+
    For more information on the capabilities of the Regular Expression option, see the Qt
-   documentation for the `QRegularExpression <https://doc.qt.io/qt-5/qregularexpression.html>`_
+   documentation for the `QRegularExpression <https://doc.qt.io/qt-6/qregularexpression.html>`_
    class.
 
 
@@ -132,10 +152,10 @@ Auto-Replace as You Type
 ========================
 
 A few auto-replace features are supported by the editor. You can control every aspect of the
-auto-replace feature from :guilabel:`Preferences`. You can also disable this feature entirely if
-you wish.
+auto-replace feature from **Preferences**. You can also disable this feature entirely if you wish.
 
 .. tip::
+
    If you don't like auto-replacement, all symbols inserted by this feature are also available in
    the :guilabel:`Insert` menu, and via :ref:`a_kb_ins`. You may also be using a `Compose Key`_
    setup, which means you may not need the auto-replace feature at all.
@@ -147,6 +167,22 @@ always accurate. Especially distinguishing between closing single quote and apos
 tricky for languages that use the same symbol for these, like English does.
 
 .. tip::
+
    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 before it.
+
+
+.. _a_ui_edit_dialogue:
+
+Dialogue Highlighting
+=====================
+
+The editor and viewer can optionally highlight character dialogue in your novel documents. By
+default, this feature is set to display text in double quotes as dialogue. In **Preferences**, you
+can change this to support various other dialogue markers that instead uses dashes to indicate
+dialogue, like those used in Spanish, Portuguese, Polish, etc.
+
+Various styles are supported by changing the settings under "Text Highlighting" in **Preferences**.
+
+It is also possible to include the dialogue highlighting in your manuscripts.

docs/source/writing_story.rst

@@ -0,0 +1,69 @@
+.. _a_story_structure:
+
+************************
+Story Structure Comments
+************************
+
+
+As of version 2.7, story structure annotations using the ``%story`` style of comment is supported.
+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.
+
+Here's an example:
+
+.. code-block:: md
+
+   %story.term: text
+
+.. versionadded:: 2.7
+
+
+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:
+
+.. 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.

i18n/README.md

@@ -18,7 +18,7 @@ When contributing translations, keep the following things in mind.
 
 * For descriptive labels and dialog boxes, make sure you do _not_ change the meaning of the text
   when you translate it from English. The user must receive the same instructions or information
-  regardless of language. This is improtant, otherwise the documentation will be inconsistent with
+  regardless of language. This is important, otherwise the documentation will be inconsistent with
   the user interface and it will become a lot more difficult to handle user issues and questions.
 * If you think a label or description is misleading or incomplete, please file an issue report. The
   correct way to handle such changes is to change the text in the code first, which will then be
@@ -35,7 +35,7 @@ Linguist, or updating the translations for an already existing supported languag
 
 There are two areas relevant to localisation:
 
-* The Qt5 GUI translation files, which consists of `nw_XX.ts` files. This is the bulk of the
+* The Qt GUI translation files, which consists of `nw_XX.ts` files. This is the bulk of the
   translation work.
 * The `project_XX.json` files. See [Project Localisation](#project-localisation) below.
 
@@ -43,9 +43,9 @@ The `XX` in the file name corresponds to the language and country code for the t
 instance `en_GB` for British English.
 
 
-## Qt5 GUI Localisation
+## Qt GUI Localisation
 
-You will need the translation tool Qt 5 Linguist on your system.
+You will need the translation tool Qt Linguist on your system.
 
 For Ubuntu/Debian, run:
 
@@ -53,7 +53,7 @@ For Ubuntu/Debian, run:
 sudo apt install qttools5-dev-tools
 ```
 
-See also [Qt Linguist Manual: Translators](https://doc.qt.io/qt-5/linguist-translators.html).
+See also [Qt Linguist Manual: Translators](https://doc.qt.io/qt-6/linguist-translators.html).
 
 
 ### Workflow
@@ -89,13 +89,12 @@ For instance, the French translation uses the language code `fr_FR`, so its tran
 be `nw_fr_FR.ts`
 
 Note: The `qtlupdate` command needs the `lupdate` tool provided by PyQt6, which uses the latest
-TS file format. The tool in PyQt5 generates an older file format. On Debian/Ubuntu it is provided
-by the package `pyqt6-dev-tools`.
+TS file format. On Debian/Ubuntu it is provided by the package `pyqt6-dev-tools`.
 
 
 ### Edit the Translation File in Qt Linguist
 
-The `i18n/nw_XX.ts` file can be edited with the Qt Linguist application provided by Qt 5. This is
+The `i18n/nw_XX.ts` file can be edited with the Qt Linguist application provided by Qt. This is
 by far easier than manually editing the `.ts` file.
 
 Please select "English" and "United Kingdom" as the _source_ language if prompted by Qt Linguist.