You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The open file format and ecosystem for localization (i18n)
@@ -89,6 +89,6 @@ There are many ways you can contribute to inlang! Here are a few options:
89
89
- Create issues every time you feel something is missing or goes wrong
90
90
- Upvote issues with 👍 reaction so we know what the demand for a particular issue to prioritize it within the roadmap
91
91
92
-
If you would like to contribute to the development of the project, please refer to our [Contributing guide](https://github.com/opral/monorepo/blob/main/CONTRIBUTING.md).
92
+
If you would like to contribute to the development of the project, please refer to our [Contributing guide](https://github.com/opral/inlang/blob/main/CONTRIBUTING.md).
Copy file name to clipboardExpand all lines: blog/update-on-inlang-v2/index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ og:description: "Accelerating both inlang and lix by prioritizing lix."
5
5
6
6
Dear inlang community,
7
7
8
-
The release of the inlang SDK v2 (variant support) is blocked until we have a 1.0 release of the lix version control system. We are prioritizing [lix](https://lix.opral.com/) so we can unblock v2. Which means:
8
+
The release of the inlang SDK v2 (variant support) is blocked until we have a 1.0 release of the lix version control system. We are prioritizing [lix](https://lix.dev/) so we can unblock v2. Which means:
9
9
10
10
- The release of the inlang SDK v2 is likely postponed until Jan/Feb next year.
11
11
@@ -33,19 +33,19 @@ You can try out a CSV file demo of lix [here](https://csv.lix.opral.com/).
33
33
34
34
What makes globalization of software complicated is the required coordination effort. Designers need to know that translators updated translations to adjust their UIs, developers need to redeploy the app if translations change, auditors need to know that a message has changed, … the list goes on.
35
35
36
-
It was clear in March 2022 [[RFC 01](https://github.com/opral/monorepo/blob/c3ea483c6b6de65f8f05b211e06cbd53f73054b1/inlang/blog/notes-on-git-based-architecture.md)] that solving globalization of software requires version control to coordinate changes between teams. It was also clear that [git is unsuited for applications](https://github.com/opral/monorepo/blob/c3ea483c6b6de65f8f05b211e06cbd53f73054b1/inlang/blog/git-as-sdk.md#but-git-as-back-end-is-not-perfect), and we would have to develop lix.
36
+
It was clear in March 2022 [[RFC 01](https://github.com/opral/inlang/blob/c3ea483c6b6de65f8f05b211e06cbd53f73054b1/inlang/blog/notes-on-git-based-architecture.md)] that solving globalization of software requires version control to coordinate changes between teams. It was also clear that [git is unsuited for applications](https://github.com/opral/inlang/blob/c3ea483c6b6de65f8f05b211e06cbd53f73054b1/inlang/blog/git-as-sdk.md#but-git-as-back-end-is-not-perfect), and we would have to develop lix.
37
37
38
38

39
39
40
40
Version control is required to reduce the coordination effort and automate globalization pipelines.
41
41
42
42
## Git slowed lix and inlang down
43
43
44
-
We [initially built lix on top of Git](https://github.com/opral/monorepo/blob/c3ea483c6b6de65f8f05b211e06cbd53f73054b1/inlang/blog/notes-on-git-based-architecture.md), thinking that we ease adoption and benefit from Git’s decade-long development. That turned out to be false. We delayed building differentiating lix technologies. I gave a [presentation last week that delaying differentiating technology leads to a death trap for startups](https://samuelstroschein.substack.com/p/dont-delay-building-differentiating). A vicious cycle of building around git instead of building what differentiates lix occurred, consuming most engineering resources. Among the workarounds that we did because of git:
44
+
We [initially built lix on top of Git](https://github.com/opral/inlang/blob/c3ea483c6b6de65f8f05b211e06cbd53f73054b1/inlang/blog/notes-on-git-based-architecture.md), thinking that we ease adoption and benefit from Git’s decade-long development. That turned out to be false. We delayed building differentiating lix technologies. I gave a [presentation last week that delaying differentiating technology leads to a death trap for startups](https://samuelstroschein.substack.com/p/dont-delay-building-differentiating). A vicious cycle of building around git instead of building what differentiates lix occurred, consuming most engineering resources. Among the workarounds that we did because of git:
45
45
46
-
- we [needed to develop a git-compatible persistency layer](https://github.com/opral/monorepo/issues/1844) to deliver multi-variant support (gendering, pluralization, etc). It took more than 6 months and ended up getting canceled.
46
+
- we [needed to develop a git-compatible persistency layer](https://github.com/opral/inlang/issues/1844) to deliver multi-variant support (gendering, pluralization, etc). It took more than 6 months and ended up getting canceled.
47
47
48
-
- were [about to build a custom database](https://github.com/opral/monorepo/issues/1772) to sync git, filesystem, and app state
48
+
- were [about to build a custom database](https://github.com/opral/inlang/issues/1772) to sync git, filesystem, and app state
Copy file name to clipboardExpand all lines: docs/architecture.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Inlang's architecture has three layers: storage, data model, and plugins.
14
14
15
15
## Storage
16
16
17
-
An `.inlang` file is a SQLite database with built-in version control via [Lix](https://lix.opral.com). One portable file containing all your translations, settings, and change history.
17
+
An `.inlang` file is a SQLite database with built-in version control via [Lix](https://lix.dev). One portable file containing all your translations, settings, and change history.
"Inlang lint rules have been removed for the CLI v3 after the major lix and inlang SDK update to be replaced by a new validation system that generalizes beyond inlang and to reduce the scope of the update."
14
14
);
15
15
log.info(
16
-
"Upvote https://github.com/opral/lix-sdk/issues/239 to re-introduce linting."
16
+
"Upvote https://github.com/opral/lix/issues/239 to re-introduce linting."
Copy file name to clipboardExpand all lines: packages/plugins/i18next/CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@
112
112
113
113
### Breaking changes
114
114
115
-
- Lint rules are now polyfilled (and therefore may work different), as we are currently reworking how lint rules are working with [Lix Validation Rules](https://lix.opral.com).
115
+
- Lint rules are now polyfilled (and therefore may work different), as we are currently reworking how lint rules are working with [Lix Validation Rules](https://lix.dev).
116
116
- The `messageId` parameter in the `extractMessages` function has been renamed to `bundleId`. This change is due to the new API in Sherlock v2. If you are using the `extractMessages` function, please update the parameter name to `bundleId`.
0 commit comments