Skip to content

[TASK] Apply pre-commit whitespace fixes #166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
linawolf merged 1 commit into from
Sep 8, 2026
Merged

[TASK] Apply pre-commit whitespace fixes #166

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .editorconfig
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,4 @@ max_line_length = 80
# Makefile
[{Makefile,**.mk}]
# Use tabs for indentation (Makefiles require tabs)
indent_style = tab
indent_style = tab
1 change: 0 additions & 1 deletion .github/workflows/backport.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,3 @@ jobs:
secrets:
APP_ID: ${{ secrets.APP_ID }}
APP_PRIVATE_KEY: ${{ secrets.APP_PRIVATE_KEY }}

6 changes: 3 additions & 3 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@

## Create Issues

* If you find something missing or something is wrong in this manual, you are welcome to write an issue describing the problem.
* If you can, please try to fix the problem yourself.
* For minor changes, it is not necessary to create an issue first.
* If you find something missing or something is wrong in this manual, you are welcome to write an issue describing the problem.
* If you can, please try to fix the problem yourself.
* For minor changes, it is not necessary to create an issue first.

## Make changes (create pull requests)

Expand Down
1 change: 0 additions & 1 deletion Documentation/CoreSupport/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,3 @@ Core support for localization

Tca/Index
Permissions/Index

1 change: 0 additions & 1 deletion Documentation/CoreSupport/Tca/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,4 +212,3 @@ Each field may contain special instructions which will affect the "localize"
command. Most important is the
:ref:`"l10n\_mode" field <t3tca:columns-properties-l10n-mode>` with which,
for example, a field can be entirely excluded from the translation process.

2 changes: 1 addition & 1 deletion Documentation/Includes.rst.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,4 +31,4 @@

.. By default, code blocks use PHP syntax highlighting

.. highlight:: php
.. highlight:: php
10 changes: 5 additions & 5 deletions Documentation/PageTranslations/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@ Translating pages
=================

In order to translate a page in the page tree, create a
copy of it with a new language relation. Use the module :guilabel:`Page` and on the top of the right side
:guilabel:`Language Comparison` and the lower dropdown :guilabel:`Create a new translation of this page`.
copy of it with a new language relation. Use the module :guilabel:`Page` and on the top of the right side
:guilabel:`Language Comparison` and the lower dropdown :guilabel:`Create a new translation of this page`.
As soon as you choose a language of this dropdown the translation process will start with the copy of this page.

The page copy will be generated in the default language with page property fields like `title` or `description` prefixed by a text similar to "[Translate to Language X:]".
The translated content needs to be put here, replacing the placeholder text (including the prefix and
The page copy will be generated in the default language with page property fields like `title` or `description` prefixed by a text similar to "[Translate to Language X:]".
The translated content needs to be put here, replacing the placeholder text (including the prefix and
the copied default language contents).

Select the :guilabel:`Language Comparison` function in the upper menu bar of the
:guilabel:`Web > Page` module. Then use the select box to create a new
translation of the page:
Expand Down