-
The Fred |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Usually every core element has their own translation strings. So for the core I would say no. For your own plugins it would be important, that it would not be changed soon. So if you have a look at, when that string was changed the last time it's 9 years ago. So IMO it would be safe to use it. 2 years ago I did upload a translateabl-plugins branch to my repo. It's now a 1000 commits behind master ;) I would have to review it and create a draft-PR. So the vercel-bot would be able to create a test-version. Edit: Here's the old draft PR, which has no preview #5418 |
Beta Was this translation helpful? Give feedback.
-
Hi @tw-FRed while @pmario is correct in general, the specific example you gave of the "Contents" tab and the "Contents" menu bar item does seem to be a case where the meaning is exactly the same, and so the string could be reused. |
Beta Was this translation helpful? Give feedback.
Usually every core element has their own translation strings. So for the core I would say no. For your own plugins it would be important, that it would not be changed soon.
So if you have a look at, when that string was changed the last time it's 9 years ago. So IMO it would be safe to use it.
2 years ago I did upload a translateabl-plugins branch to my repo. It's now a 1000 commits behind master ;) I would have to review it and create a draft-PR. So the vercel-bot would be able to create a test-version.
Edit: Here's the old draft PR, which has no preview #5418