From: Matthieu C. <cho...@gm...> - 2012-02-26 13:45:57
|
Hi, I replaced i18n by localization. About moving localization props in plugins I didn't think a lot about it. And I don't understand from where does come the "disabled by default?" question and what is it about ? 2012/2/25 Kazutoshi Satoda <k_s...@f2...> > Matthieu Casanova wrote: > >> 2012/2/23 Kazutoshi Satoda<k_s...@f2...> >> >>> Naming: >>> >> (snip) > > I know "i18n" means "internationalization". But the contents of the >>> above directory seem for "localization". Thus, the name should be "l10n" >>> instead? >>> >> (snip) > > Here, http://en.wikipedia.org/wiki/**Internationalization_and_** >> localization<http://en.wikipedia.org/wiki/Internationalization_and_localization> >> the definitions >> I see for internationalization is a software that is able to use a range >> of >> Locales and localization is adaptation of a software to one locale. >> So jEdit would be only localized if there was a French jEdit, an English >> jEdit, a German jEdit, here we can change the language. >> >> But in fact I really don't know if it is localized or internationalized. >> If >> you think that i10n is a better definition I can change it. >> > > Your change, which make jEdit ready for localization, is said to be a > major part of i18n. However, the .props files are said to be localizing > jEdit for specific locales (at runtime). > > I still suggest changing "i18n" to "l10n", or just "localized" without > numeronym. > > > Should .props be in jedit.jar ?: >> >>> The .props files are in jedit.jar. I think it may be better to put them >>> out of .jar so that they can be tweaked or updated without core release. >>> >> >> That's right. In fact I just had an idea : >> A few days ago I changed things in plugin loading to have a better >> handling >> of the case when you have a plugin in the install folder and the same one >> in the .jedit folder (only the newest is loaded). >> In that case jEdit could be installed with plugins like QuickNotepad. >> And French and German localization files could be provided by plugins that >> would be installed with jEdit, but it would be easy to update them through >> plugin manager without releasing a new jEdit (because I think there will >> often be some delay to have the localized files up to date). >> > > That sounds a very different form from the current implementation. Are > you willing to replace the implementation? Or, is the current > implementation capable to work as such (and I'm missing something in > that case)? > > Disabled by default?: >>> >> (snip) > > +# if lang.usedefaultlocale is true, the lang.current is not used >>>> +lang.usedefaultlocale=true >>>> +lang.current=en >>>> \ No newline at end of file >>>> >>>> I think that if the .props file for user locale exists at the time of >>> install, it should be enabled by default because those who want >>> translation are likely unable to find the option in options dialog. >>> >>> "No newline at end of file" should be fixed. >>> >>> I'll fix it. >> About that, did you see the Checkstyle plugin on svn ? >> I wrote a new Checkstyle plugin from scratch but didn't release it yet. >> And >> it contains by default two style definitions : the Sun coding style, and a >> jEdit's coding style. >> It can help follow our coding style rules It is probably not perfect yet >> and I need some feedback about it. >> > > I have no idea about Checkstyle plugin. Please fix "No newline ..." > anyway you want. For me, it is not related to a coding style things. > > I want you answer about "Disabled by default?" design question. > > > Maybe, a design proposal/discussion (including naming and separate > update) on jedit-devel should be taken before? > > -- > k_satoda > |