bimplus-webcomponents 0.0.228 → 0.0.229-pu.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,105 +0,0 @@
|
|
|
1
|
-
# Localization Workflow
|
|
2
|
-
|
|
3
|
-
This repository is a Git submodule used by depending projects to provide localization strings for the Bimplus domain.
|
|
4
|
-
|
|
5
|
-
## Responsibilities
|
|
6
|
-
|
|
7
|
-
| Task | Owner |
|
|
8
|
-
|------|-------|
|
|
9
|
-
| Define and maintain `strings_en.json` | Development team |
|
|
10
|
-
| Translate all other language files (`strings_de.json`, `strings_fr.json`, etc.) | Documentation / Localization team |
|
|
11
|
-
|
|
12
|
-
---
|
|
13
|
-
|
|
14
|
-
## Workflow
|
|
15
|
-
|
|
16
|
-
### 1. Adding or changing English strings
|
|
17
|
-
|
|
18
|
-
English (`strings_en.json`) is the **source language** and the only file maintained directly in this repository by the development team.
|
|
19
|
-
|
|
20
|
-
After modifying `strings_en.json`, copy the updated file **manually** to the localization share:
|
|
21
|
-
|
|
22
|
-
```
|
|
23
|
-
\\devpool-ahq\PM_Projects\15_160_Bim+ Web\Localization\bim-client\
|
|
24
|
-
```
|
|
25
|
-
|
|
26
|
-
Notify the documentation team that new or changed strings are available for translation.
|
|
27
|
-
|
|
28
|
-
---
|
|
29
|
-
|
|
30
|
-
### 2. Receiving translated files
|
|
31
|
-
|
|
32
|
-
Once the documentation team has finished a translation, they will place the updated language file(s) back in the same network share:
|
|
33
|
-
|
|
34
|
-
```
|
|
35
|
-
\\devpool-ahq\PM_Projects\15_160_Bim+ Web\Localization\bim-client\
|
|
36
|
-
```
|
|
37
|
-
|
|
38
|
-
Copy the updated language file(s) from the share into this repository, replacing the existing file(s):
|
|
39
|
-
|
|
40
|
-
```
|
|
41
|
-
strings_cs.json – Czech
|
|
42
|
-
strings_de.json – German
|
|
43
|
-
strings_es.json – Spanish
|
|
44
|
-
strings_fr.json – French
|
|
45
|
-
strings_it.json – Italian
|
|
46
|
-
strings_nl.json – Dutch
|
|
47
|
-
strings_ro.json – Romanian
|
|
48
|
-
strings_ru.json – Russian
|
|
49
|
-
strings_tr.json – Turkish
|
|
50
|
-
strings_us.json – English (US)
|
|
51
|
-
```
|
|
52
|
-
|
|
53
|
-
Commit and push the changes to this repository:
|
|
54
|
-
|
|
55
|
-
```bash
|
|
56
|
-
git add strings_*.json
|
|
57
|
-
git commit -m "chore(i18n): update translations from localization team"
|
|
58
|
-
git push
|
|
59
|
-
```
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
### 3. Updating the submodule in depending projects
|
|
64
|
-
|
|
65
|
-
Every project that consumes this repository as a Git submodule must update its submodule reference after new translations are pushed.
|
|
66
|
-
|
|
67
|
-
Run the following commands inside the depending project repository:
|
|
68
|
-
|
|
69
|
-
```bash
|
|
70
|
-
# Navigate to the submodule folder (adjust path if needed)
|
|
71
|
-
cd <path-to-submodule>
|
|
72
|
-
|
|
73
|
-
# Pull the latest changes in the submodule
|
|
74
|
-
git pull origin <branch>
|
|
75
|
-
|
|
76
|
-
# Go back to the root of the depending project
|
|
77
|
-
cd <root-of-depending-project>
|
|
78
|
-
|
|
79
|
-
# Stage the updated submodule reference
|
|
80
|
-
git add <path-to-submodule>
|
|
81
|
-
|
|
82
|
-
git commit -m "chore(i18n): update lang-module submodule"
|
|
83
|
-
git push
|
|
84
|
-
```
|
|
85
|
-
|
|
86
|
-
Repeat this for every project that uses the `lang-module` submodule.
|
|
87
|
-
|
|
88
|
-
---
|
|
89
|
-
|
|
90
|
-
## Language file format
|
|
91
|
-
|
|
92
|
-
All string files are plain JSON objects where each key is prefixed with `_` and the value is the translated string. Example (`strings_en.json`):
|
|
93
|
-
|
|
94
|
-
```json
|
|
95
|
-
{
|
|
96
|
-
"_Ok": "OK",
|
|
97
|
-
"_Cancel": "Cancel",
|
|
98
|
-
"_Save": "Save"
|
|
99
|
-
}
|
|
100
|
-
```
|
|
101
|
-
|
|
102
|
-
- **Do not** change keys — they are referenced directly in the application code.
|
|
103
|
-
- **Do not** translate or modify `strings_en.json` — that is the responsibility of the development team.
|
|
104
|
-
- New keys must always be added to `strings_en.json` first before any translation is requested.
|
|
105
|
-
- New keys must follow this naming convention: start with `_`, separate each word with `_`, capitalize only the first word, and use lowercase for all subsequent words. Example: `_Drawing_2D_use_crop_tool_description`.
|
|
@@ -1,105 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
applyTo: "**"
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Cowork Localization String Reference
|
|
6
|
-
|
|
7
|
-
Epic: [ACDC-33629](https://nemetschekprime.atlassian.net/browse/ACDC-33629)
|
|
8
|
-
|
|
9
|
-
This file documents all localization string keys used across the Cowork feature screens.
|
|
10
|
-
Use this as a reference when implementing UI labels to ensure consistency and avoid adding duplicate keys.
|
|
11
|
-
|
|
12
|
-
---
|
|
13
|
-
|
|
14
|
-
## Cowork Project List (table columns & breadcrumb)
|
|
15
|
-
|
|
16
|
-
| UI label | Key | Value |
|
|
17
|
-
|---|---|---|
|
|
18
|
-
| Cowork projects (breadcrumb) | `_Cowork_projects` | "Cowork projects" |
|
|
19
|
-
| Project name | `_Project_Name` | "Project name" |
|
|
20
|
-
| Author | `_Author` | "Author" |
|
|
21
|
-
| Project type | `_Project_type` | "Project type" |
|
|
22
|
-
| Date created | `_Date_Created` | "Date created" |
|
|
23
|
-
| Address | `address` | "Address" |
|
|
24
|
-
| Size | `size` | "Size" |
|
|
25
|
-
|
|
26
|
-
---
|
|
27
|
-
|
|
28
|
-
## Cowork Project Properties Panel
|
|
29
|
-
|
|
30
|
-
| UI label | Key | Value |
|
|
31
|
-
|---|---|---|
|
|
32
|
-
| Properties | `_Portal_Properties` | "Properties" |
|
|
33
|
-
| Image | `_image` | "Image" |
|
|
34
|
-
| Project details (section header) | `_Project_details` | "Project details" |
|
|
35
|
-
| Name | `_Name` | "Name" |
|
|
36
|
-
| Description | `_Description` | "Description" |
|
|
37
|
-
| Created on | `createdOn` | "Created on" |
|
|
38
|
-
| Address (section header) | `address` | "Address" |
|
|
39
|
-
| Street | `street` | "Street" |
|
|
40
|
-
| Zip | `zip` | "ZIP" |
|
|
41
|
-
| City | `city` | "City" |
|
|
42
|
-
| Country | `country` | "Country" |
|
|
43
|
-
|
|
44
|
-
---
|
|
45
|
-
|
|
46
|
-
## Backup Documents List (table columns & breadcrumb)
|
|
47
|
-
|
|
48
|
-
| UI label | Key | Value |
|
|
49
|
-
|---|---|---|
|
|
50
|
-
| Backups (breadcrumb) | `_Backups` | "Backups" |
|
|
51
|
-
| Name | `_Name` | "Name" |
|
|
52
|
-
| Size | `size` | "Size" |
|
|
53
|
-
| Created on | `createdOn` | "Created on" |
|
|
54
|
-
| Modified on | `_Modified_on` | "Modified on" |
|
|
55
|
-
|
|
56
|
-
---
|
|
57
|
-
|
|
58
|
-
## Backup Document Properties Panel
|
|
59
|
-
|
|
60
|
-
| UI label | Key | Value |
|
|
61
|
-
|---|---|---|
|
|
62
|
-
| Backup details (section header) | `_Backup_details` | "Backup details" |
|
|
63
|
-
| File name | `_Filename` | "File name" |
|
|
64
|
-
| Description | `_Description` | "Description" |
|
|
65
|
-
| Version | `_Version` | "Version" |
|
|
66
|
-
| Created on | `createdOn` | "Created on" |
|
|
67
|
-
| Owner | `_Owner` | "Owner" |
|
|
68
|
-
| Owner Company | `_Owner_company` | "Owner Company" |
|
|
69
|
-
| Modified by User | `_Modified_by_user` | "Modified by User" |
|
|
70
|
-
| Modified by Company | `_Modified_by_company` | "Modified by Company" |
|
|
71
|
-
|
|
72
|
-
---
|
|
73
|
-
|
|
74
|
-
## Backup Settings Page
|
|
75
|
-
|
|
76
|
-
| UI label | Key | Value |
|
|
77
|
-
|---|---|---|
|
|
78
|
-
| Backup Settings (page title) | `_Backup_settings` | "Backup Settings" |
|
|
79
|
-
| Activate | `_Activate` | "Activate" |
|
|
80
|
-
| Backup Start | `_Backup_Start` | "Backup Start" |
|
|
81
|
-
| Backup Repetition | `_Backup_Repetition` | "Backup Repetition" |
|
|
82
|
-
| Every … Days (combined) | `_Every__days` | "every %@ days" |
|
|
83
|
-
| Days (standalone label) | `_Days` | "Days" |
|
|
84
|
-
| Save | `_Save` | "Save" |
|
|
85
|
-
| Reset | `_Reset` | "Reset" |
|
|
86
|
-
|
|
87
|
-
> **Note on "Every … Days":** Use `_Every__days` when the number is embedded in a single string (e.g. "every 3 days"). Use `_Days` as a standalone label if the dropdown sits between two separate labels.
|
|
88
|
-
|
|
89
|
-
---
|
|
90
|
-
|
|
91
|
-
## Old-style keys (no `_` prefix)
|
|
92
|
-
|
|
93
|
-
Several keys in this feature use the legacy key format without a `_` prefix. These pre-date the current naming convention and must not be renamed, as they are referenced in production code.
|
|
94
|
-
|
|
95
|
-
| Key | Value |
|
|
96
|
-
|---|---|
|
|
97
|
-
| `author` | "Author" |
|
|
98
|
-
| `createdOn` | "Created on" |
|
|
99
|
-
| `modifiedAt` | "Modified" |
|
|
100
|
-
| `size` | "Size" |
|
|
101
|
-
| `address` | "Address" |
|
|
102
|
-
| `street` | "Street" |
|
|
103
|
-
| `zip` | "ZIP" |
|
|
104
|
-
| `city` | "City" |
|
|
105
|
-
| `country` | "Country" |
|