"e.V." -> "e. V." #1234
Labels
No labels
duplicate
enhancemenet
privacypolicy
enhancement
enhancement
bylaws
enhancement
tos
help wanted
invalid
question
reviewed
wontfix
No milestone
No assignees
8 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Codeberg/org!1234
Loading…
Reference in a new issue
No description provided.
Delete branch "keysmashes/org:push-yqztqtqypnrz"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per the bylaws/Satzung, "e.V." (without a space) is the correct spelling, I think.This touches several documents including the ToU but I hope it can be merged without too much hassle...
The correct spelling is "e. V.", ideally with a non-breaking space. https://www.duden.de/rechtschreibung/e__V_
Closing per above comment.
I assume this was prompted by some inconsistency somewhere else, so fixing it in the other direction is likely still good.
Indeed it is, I'd rather reopen this and leave this as a change request.
Please use e. V. instead for consistency (or feel free to close this PR if you don't feel like working on it more) :)
aiming for "e. V." everywhere seems like a substantially bigger task, but I will do it for this repo at least, at some point :)
amongst other places, "e.V." is used at https://docs.codeberg.org/getting-started/what-is-codeberg and in the readme of https://codeberg.org/Codeberg-e.V. (plus in the description text of several repos there, which I cannot file a PR about)
yeah no biggie, we can take it slowly and easily - but i apologize for the mismatched expectation there, this has been on our minds for a bit lowkey
"e. V." -> "e.V."to "e.V." -> "e. V."dbde09b946to6b7b525f05Updated this PR!
I've used
e. V.with a literal non-breaking space character, bute. V.(to avoid something that looks like a regular space but isn't) is also a possibility in Markdown, I think. Any preference?I prefer if documents are also readable in plaintext editors, because that's how folks normally edit markdown.
@fnetX wrote in #1234 (comment):
I second that. Use the Unicode non-breaking space.
@ -9,3 +9,3 @@Der gemeinnützig und frei als Open-Source entwickelte Code, der unsere moderne Kommunikation im Internet, und unser modernes, vernetztes Leben erst möglich macht, und selbst die Produkte öffentlich bezahlter Forschung werden in private und kommerziell betriebene Plattformen eingespeist, deren Programm und Bestand von außen nicht kontrollierbar ist, deren Kontrolle nicht einmal versucht wird.Als Codeberg e.V. sind wir der Überzeugung, dass der Entwicklungsprozess, die Dokumentation und Kommunikation, an der die Entwickler Freier Software teilnehmen, eine ebenfalls freie und gemeinnützig betriebene Plattform verdienen, um die Offenheit und den Bestand freier Software für alle Zukunft zu garantieren.Als Codeberg e. V. sind wir der Überzeugung, dass der Entwicklungsprozess, die Dokumentation und Kommunikation, an der die Entwickler Freier Software teilnehmen, eine ebenfalls freie und gemeinnützig betriebene Plattform verdienen, um die Offenheit und den Bestand freier Software für alle Zukunft zu garantieren.Here, there is a non-breaking space also between Codeberg and e. V.
Do we want to have these everywhere, too? Maybe makes sense?
I think between the "e." and the "V." it's the most important, it can be split before that in my opinion.
I just pushed a change to consistently use a regular space, not nbsp, between "Codeberg" and "e. V."
Please take note that the spelling (with/without space) is reflected in the entry within the Vereinsregister.
I think we are registered as e.V. (without spaces)
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.