| | 72 | === Localization === |
| | 73 | Items being passed to the manager by way of the server scheduler or core client will now be identified by a item identifier. The item identifier will be appended to the of the project's master url and we used as the item's GUID. |
| | 74 | |
| | 75 | Item identifier rules: |
| | 76 | * Item identifiers start at 1. |
| | 77 | * Item identifiers should not be removed from the item list and cannot be removed if no longer used. |
| | 78 | * Items should be enclosed in the _("Test Message") macro syntax. |
| | 79 | * Item parameters are enclosed in ‘{}’ braces with an index to the position in which the parameter should replace the marker. |
| | 80 | |
| | 81 | When new items are added poEdit or some other string extraction tool should be used to update the BOINC-Server-Messages.pot template file. After the localization process has been completed the resulting BOINC-Server-Messages.mo file should be shipped with the client software. |
| | 82 | |
| | 83 | A string in need of localization would look like this: |
| | 84 | {{{ |
| | 85 | _("This client needs {1} of additional memory. {2} detected in total.") |
| | 86 | }}} |
| | 87 | |
| | 88 | After translation it could look like this: |
| | 89 | {{{ |
| | 90 | _("Your computer has {2} of total detected memory, but the client needs an additional {1} in order to be assigned work.") |
| | 91 | }}} |
| | 92 | |
| | 93 | The client software should replace the positional markers with the optional parameter values specified for the message. |
| | 94 | |
| 180 | | === Localizing Server Messages === |
| 181 | | Messages being passed to the client by way of the server will now be identified by a message identifier. |
| 182 | | |
| 183 | | Message identifier rules: |
| 184 | | * Message identifiers start at 1. |
| 185 | | * Message identifiers should not be removed from the message list and cannot be removed if no longer used. |
| 186 | | * Messages should be enclosed in the _("Test Message") macro syntax. |
| 187 | | * Message parameters are enclosed in ‘{}’ braces with an index to the position in which the parameter should replace the marker. |
| 188 | | |
| 189 | | When new messages are added poEdit or some other string extraction tool should be used to update the BOINC-Server-Messages.pot template file. After the localization process has been completed the resulting BOINC-Server-Messages.mo file should be shipped with the client software. |
| 190 | | |
| 191 | | A string in need of localization would look like this: |
| 192 | | {{{ |
| 193 | | _("This client needs {1} of additional memory. {2} detected in total.") |
| 194 | | }}} |
| 195 | | |
| 196 | | After translation it could look like this: |
| 197 | | {{{ |
| 198 | | _("Your computer has {2} of total detected memory, but the client needs an additional {1} in order to be assigned work.") |
| 199 | | }}} |
| 200 | | |
| 201 | | The client software should replace the positional markers with the optional parameter values specified for the message. |
| 202 | | |