Trim lines ending with superfluous whitespace

This commit is contained in:
luzpaz
2024-12-22 12:57:15 +00:00
committed by Chris Hennes
parent b0a29fde31
commit 2902ea4995
28 changed files with 48 additions and 48 deletions

View File

@@ -696,7 +696,7 @@
</property>
<property name="toolTip">
<string>Shape of line end caps. The default (round) should almost
always be the right choice. Flat or square caps are useful
always be the right choice. Flat or square caps are useful
if you are planning to use a drawing as a 1:1 cutting guide.
</string>
</property>

View File

@@ -1,8 +1,8 @@
osifont license:
osifont license:
osifont-lgpl3fe.ttf is used under one or more of the following licenses:
- GNU GPL licence version 3 with GPL font exception,
- GNU GPL licence version 2 with GPL font exception,
osifont-lgpl3fe.ttf is used under one or more of the following licenses:
- GNU GPL licence version 3 with GPL font exception,
- GNU GPL licence version 2 with GPL font exception,
- GNU LGPL licence version 3 with GPL font exception.

View File

@@ -1,6 +1,6 @@
# ASME Y14.2-2008 line element definitions
# NOTE: ASME Y14.2-2008 explicitly does not define the lengths of line elements,
# but recommends lengths that "depict the appropriate line convention commensurate
# but recommends lengths that "depict the appropriate line convention commensurate
# with the drawing size and scale". The values used here are generally those
# from ISO128.
# NOTE: saving this file from a spreadsheet program (like LibreOffice Calc) may
Can't render this file because it contains an unexpected character in line 3 and column 31.

View File

@@ -1,7 +1,7 @@
This folder (`locale`) contains translations for [TechDraw workbench templates](https://wiki.freecad.org/TechDraw_Templates) in the parent `Templates` folder.
The name of each `locale` subfolder represents a language, which follows [IETF BCP 47 standardized codes](https://en.wikipedia.org/wiki/IETF_language_tag). The original TechDraw templates in the parent folder are written using American English (`en-US`).
As such, the most basic name for a locale subfolder will include an [ISO 639 language code](https://en.wikipedia.org/wiki/ISO_639) (e.g. `de` for German). If it's necessary, additional subtags can be added to describe language variants. For instance variants spoken in a particular country, or a specific script. Those subtags are combinable and are based in other standards.
As such, the most basic name for a locale subfolder will include an [ISO 639 language code](https://en.wikipedia.org/wiki/ISO_639) (e.g. `de` for German). If it's necessary, additional subtags can be added to describe language variants. For instance variants spoken in a particular country, or a specific script. Those subtags are combinable and are based in other standards.
The most common additional subtag is an additional country code to describe a regional variant of the language (e.g. `de-DE` for German spoken in Germany, `es-AR` for Spanish spoken in Argentina, or `zh-CN` for Simplified Chinese in Mainland China). Country subtags are based on [the ISO 3166-1 standard's country codes](https://en.wikipedia.org/wiki/ISO_3166-1).