I don't think that we can just remove features.
I general it is quite difficult to remove features in an Open Source
project, cause as soon as you start a discussion about it on the mailing
list there will be always somebody that tells you he needs that feature.

The current language editing also has its advandtages. For example: You
have all labels in a single XML file (so its easier to translate), you can
export and import those at runtime, you can modify wording at runtime.
Having the labels spread in many .property files does require to recompile
the complete app for every label changed. And to translate the files you
would need some extra tools to have those labels editable also for Non-Java
programers. Property files are not UTF8 save. That means a Russian property
file contains nothing human readable but only something like:

\u00EF\u00BF\u00BD

So, I am not a real fan of the i18n possibilities with .property files.
Having them in XML has a lot of advantages and importing them into the DB
makes it possible to edit them at runtime.

Sebastian

2012/10/14 Maxim Solodovnik <[email protected]>

> I ain't implemented backup/restore. I thought users will use command line
> instead.
> I also thought we can get rid of language editor in favor of wicket
> language files :)
> On Oct 14, 2012 4:52 PM, "[email protected]" <[email protected]>
> wrote:
>
>> Hi Maxim,
>>
>> sounds great!
>> I currently study some of the upload form components in Wicket.
>>
>>
>>
>> 2012/10/14 Maxim Solodovnik <[email protected]>
>>
>>> https://code.google.com/p/red5/issues/detail?id=284&q=label%3AType-Defect
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> [email protected]
>>
>


-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
[email protected]

Reply via email to