Fossil SCM
Moved the "artifact" vs "artifact" point in the JSON API doc intro into a new section within the contribution doc.
Commit
e50d27077553f36b497e553e473f8e2f87c7b766d5627c0deec8f2bee2e99645
Parent
40715d84bc430e5…
2 files changed
+27
-1
-3
+27
-1
| --- www/contribute.wiki | ||
| +++ www/contribute.wiki | ||
| @@ -88,11 +88,37 @@ | ||
| 88 | 88 | primary benefit to the project leader, followed by him at release time, |
| 89 | 89 | but contributors are encouraged to run through its steps when making |
| 90 | 90 | major changes, since if the change doesn't pass this checklist, it won't |
| 91 | 91 | be included in the next release. |
| 92 | 92 | |
| 93 | -<h2>5.0 See Also</h2> | |
| 93 | +<h2>5.0 UI and Documentation Language</h2> | |
| 94 | + | |
| 95 | +The Fossil project uses American English in its web interface and | |
| 96 | +documentation. Until there is some provision for translating the UI and | |
| 97 | +docs into other languages and dialects, we ask that you do not commit | |
| 98 | +changes that conflict with this. | |
| 99 | + | |
| 100 | +We aren't opposed to such a project, but it would be a huge amount of | |
| 101 | +work, which no one's stepped up to do yet. Not only is each individual | |
| 102 | +translation a large ongoing job its own right, there is no | |
| 103 | +infrastructure for it yet, so the first few translations will be harder | |
| 104 | +than any future translation built on that infrastructure. | |
| 105 | + | |
| 106 | +More immediately, we're likely to reject, revert, or rework commits that | |
| 107 | +use other English dialects. One example that comes up occasionally is | |
| 108 | +"artefact" versus "artifact." The UI and docs use the American English | |
| 109 | +spelling pervasively, so you have poor options if you insist on | |
| 110 | +"artefact:" | |
| 111 | + | |
| 112 | + * attempt to slip one-off changes by your peers | |
| 113 | + * attempt to change all American English usages to Commonwealth English | |
| 114 | + * make the Fossil UI and docs translatable, then contribute a | |
| 115 | + Commonwealth English translation | |
| 116 | + | |
| 117 | +Only the latter is likely to succeed. | |
| 118 | + | |
| 119 | +<h2>6.0 See Also</h2> | |
| 94 | 120 | |
| 95 | 121 | * [./build.wiki | How To Compile And Install Fossil] |
| 96 | 122 | * [./makefile.wiki | The Fossil Build Process] |
| 97 | 123 | * [./tech_overview.wiki | A Technical Overview of Fossil] |
| 98 | 124 | * [./adding_code.wiki | Adding Features To Fossil] |
| 99 | 125 |
| --- www/contribute.wiki | |
| +++ www/contribute.wiki | |
| @@ -88,11 +88,37 @@ | |
| 88 | primary benefit to the project leader, followed by him at release time, |
| 89 | but contributors are encouraged to run through its steps when making |
| 90 | major changes, since if the change doesn't pass this checklist, it won't |
| 91 | be included in the next release. |
| 92 | |
| 93 | <h2>5.0 See Also</h2> |
| 94 | |
| 95 | * [./build.wiki | How To Compile And Install Fossil] |
| 96 | * [./makefile.wiki | The Fossil Build Process] |
| 97 | * [./tech_overview.wiki | A Technical Overview of Fossil] |
| 98 | * [./adding_code.wiki | Adding Features To Fossil] |
| 99 |
| --- www/contribute.wiki | |
| +++ www/contribute.wiki | |
| @@ -88,11 +88,37 @@ | |
| 88 | primary benefit to the project leader, followed by him at release time, |
| 89 | but contributors are encouraged to run through its steps when making |
| 90 | major changes, since if the change doesn't pass this checklist, it won't |
| 91 | be included in the next release. |
| 92 | |
| 93 | <h2>5.0 UI and Documentation Language</h2> |
| 94 | |
| 95 | The Fossil project uses American English in its web interface and |
| 96 | documentation. Until there is some provision for translating the UI and |
| 97 | docs into other languages and dialects, we ask that you do not commit |
| 98 | changes that conflict with this. |
| 99 | |
| 100 | We aren't opposed to such a project, but it would be a huge amount of |
| 101 | work, which no one's stepped up to do yet. Not only is each individual |
| 102 | translation a large ongoing job its own right, there is no |
| 103 | infrastructure for it yet, so the first few translations will be harder |
| 104 | than any future translation built on that infrastructure. |
| 105 | |
| 106 | More immediately, we're likely to reject, revert, or rework commits that |
| 107 | use other English dialects. One example that comes up occasionally is |
| 108 | "artefact" versus "artifact." The UI and docs use the American English |
| 109 | spelling pervasively, so you have poor options if you insist on |
| 110 | "artefact:" |
| 111 | |
| 112 | * attempt to slip one-off changes by your peers |
| 113 | * attempt to change all American English usages to Commonwealth English |
| 114 | * make the Fossil UI and docs translatable, then contribute a |
| 115 | Commonwealth English translation |
| 116 | |
| 117 | Only the latter is likely to succeed. |
| 118 | |
| 119 | <h2>6.0 See Also</h2> |
| 120 | |
| 121 | * [./build.wiki | How To Compile And Install Fossil] |
| 122 | * [./makefile.wiki | The Fossil Build Process] |
| 123 | * [./tech_overview.wiki | A Technical Overview of Fossil] |
| 124 | * [./adding_code.wiki | Adding Features To Fossil] |
| 125 |
| --- www/json-api/intro.md | ||
| +++ www/json-api/intro.md | ||
| @@ -168,8 +168,5 @@ | ||
| 168 | 168 | - **Timestamps:** For portability, this API uses UTC Unix epoch |
| 169 | 169 | timestamps. (`time_t`) They are the most portable time representation out |
| 170 | 170 | there, easily usable in most programming environments. (In |
| 171 | 171 | hindsight, we might better have used a higher-precision time format, |
| 172 | 172 | but changing that now would break API compatibility.) |
| 173 | -- **Artifact vs. Artefact:** both are correct vis-a-vis the | |
| 174 | - english language but Fossil consistently uses the former, so we’ll | |
| 175 | - use that. | |
| 176 | 173 |
| --- www/json-api/intro.md | |
| +++ www/json-api/intro.md | |
| @@ -168,8 +168,5 @@ | |
| 168 | - **Timestamps:** For portability, this API uses UTC Unix epoch |
| 169 | timestamps. (`time_t`) They are the most portable time representation out |
| 170 | there, easily usable in most programming environments. (In |
| 171 | hindsight, we might better have used a higher-precision time format, |
| 172 | but changing that now would break API compatibility.) |
| 173 | - **Artifact vs. Artefact:** both are correct vis-a-vis the |
| 174 | english language but Fossil consistently uses the former, so we’ll |
| 175 | use that. |
| 176 |
| --- www/json-api/intro.md | |
| +++ www/json-api/intro.md | |
| @@ -168,8 +168,5 @@ | |
| 168 | - **Timestamps:** For portability, this API uses UTC Unix epoch |
| 169 | timestamps. (`time_t`) They are the most portable time representation out |
| 170 | there, easily usable in most programming environments. (In |
| 171 | hindsight, we might better have used a higher-precision time format, |
| 172 | but changing that now would break API compatibility.) |
| 173 |