Error / Typo in the GERMAN Version of the Documentation - "Automatic file naming" / "Automatische Dateibenennung"
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the German HandBrake 1.3.0-1.3.3 documentation page for “Automatische Dateibenennung,” specifically the “Behandlung von MP4 Dateiendung” paragraph, and compare it with the English wording. Correct the negation so it states that there is no difference, then review the rendered German passage against the proposal.
Written by the indexing model from the issue text.
Description
Hi there,
I found an Error / Typo in the latest Release of the Documentation (Current German Version: [HandBrake 1.3.0-1.3.3] https://handbrake.fr/docs/de/1.3.0/).
In the Part "Automatic file naming", in German "Automatische Dateibenennung".
I'll list the corresponding Paragraph in "MP4 File Extension Handling" / "Behandlung von MP4 Dateiendung"
In English:
"You can simply change the file extension between .mp4 and .m4v as the file is exactly the same. There are no differences in the content or container itself."
In German:
"Du kannst einfach die Dateiendung zwischen .mp4 und .m4v ändern da die Datei exakt gleich ist. Es gibt einen Unterschied im Inhalt oder im Container selbst."
Result:
In the English Version ist stated, that there is NO DIFFERENCE. In the German Version it is stated, that there IS A DIFFERENCE.
Proposal:
Change the German Version by adding a Letter. In this Case the Letter "k" to negate the given Statement like the following:
"Du kannst einfach die Dateiendung zwischen .mp4 und .m4v ändern da die Datei exakt gleich ist. Es gibt keinen Unterschied im Inhalt oder im Container selbst."
Thank you all for your continuous Supports and Efforts the bring this beautiful Product to the World ...
- Dominant language
- Shell
- Stars
- 268
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HandBrake/HandBrake-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
HandBrake/HandBrake-docs#272 ·
-
Improvement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
HandBrake/HandBrake-docs#232 · 1 comment ·
-
Improvement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
HandBrake/HandBrake-docs#204 · 1 reaction ·
-
Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
HandBrake/HandBrake-docs#199 ·
-
Correction Needed
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
HandBrake/HandBrake-docs#189 · 3 comments ·
All issues in HandBrake/HandBrake-docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
astral-sh/python-build-standalone#1293 ·
-
package-update
Difficulty 1/5 Under an hour Newbie friendliness 90/100
oSoWoSo/vOid_Community_repOsitory#185 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carbon-language/carbon-lang#7821 ·