1478 - Support Sharing Of Localizations Between Projects

[01 10:32] <sylvanaar> ckknight can localizations be shared between projects?
[01 10:32] <sylvanaar> without manual import/export
[01 10:33] <ckknight> not without import/export
[01 10:33] <nicoli_s> nooooooooooo
[01 10:33] <ckknight> got a use case?
[01 10:33] <sylvanaar> yes - i want to have fail translation strings for libfail in a common location
[01 10:33] <sylvanaar> but, not in the library
[01 10:34] <sylvanaar> so someone using libfail - could use the strings, and they would remain current as libfail was updated
[01 10:35] <sylvanaar> not to mention - they would be more likely to exist in the first place if they were centralized
[01 10:35] <ckknight> hmm
[01 10:36] <ckknight> file a ticket under localization
[01 10:36] <ckknight> I know how to add support sanely
[01 10:36] <sylvanaar> ok
[01 10:36] <ckknight> I'll add another keyword to @localization@ to specify project

User	When	Change
sylvanaar	Mon, 01 Jun 2009 14:39:19	Create

You must login to post a comment. Don't have an account? Register to get one!

1 comment

- #1
adjo Sat, 20 Jun 2009 15:20:08
this would make localization so much easier!

could be expanded to:
- all projects on curseforge sharing the same string database
- libbabble integration

1 comment

Facts

Last updated on: 09 Jan 2010
Reported on: 01 Jun 2009
Status: New - Issue has not had initial review yet.
Type: Enhancement - A change which is intended to better the project in some way
Priority: Medium - Normal priority.
Component: Localization