On 4 September 2013 16:21, Jürgen Schmidt <jogischm...@gmail.com> wrote:
> On 9/4/13 4:13 PM, janI wrote: > > On 4 September 2013 13:59, Herbert Duerr <h...@apache.org> wrote: > > > >> On 04.09.2013 11:15, j...@apache.org wrote: > >> > >>> Author: jani > >>> Date: Wed Sep 4 09:13:51 2013 > >>> New Revision: 1519953 > >>> > >>> URL: http://svn.apache.org/r1519953 > >>> Log: > >>> update to UTF-8 > >>> > >> > >> Great, thanks! And kudos to Tsutomu too! > >> > >> But I noticed that in the l10n40 branch the *.po files of all languages > >> are checked in amidst the main source code in the main/languages > directory. > >> Wouldn't it be better to keep all these 600 megabytes of localization > data > >> separate, e.g. in extras/ where it used to be? > >> > > > > In my opinion po files are just as much source as any other part of main, > > and not something extra. > > > > When using the argument "extra", we should move quit a lot of modules > away > > from main, since they are not compiled into our release (at least as far > as > > what I can see). > > > > main/languages and main/l10ntools forms together with a couple of other > > modules (like i18n( our integrated international part, The intention of > the > > new toolset is to make a deeper integration and not push it further away. > > > > That's fine but po files can be seen nevertheless a little bit different > because they contain the translated data. > > I believe the main argument is that you can better split the source and > the default for developers is to build en-US only. Why checking out 600 > MB if I don't build it at all? But this is probably an implementation > detail only and can be changed at any time n demand. > If people dont want to do a checkout both svn and git offers ignore possibilities. But I cannot see a stable build enviroment, that detect if "extras" is downloaded and at same revision as the sources, thats an interesting challenge. dont forget that our sources (at least .src, .xhp etc) are tightly connected to the .pot files in templates, which again are tightly connected to our .po files. To me this a lot more than an implementation detail, its a matter of how the build system works. Even a en-US developer, should run "build --genPO" to verify that the strings marked for translation are valid for translation. I dont have a apple macbook, so I dont like to check out the modules for apple and we can continue like that. It boils down to one simple question "Do we have 1 product, or a main product (en-US, with/without apple) with a number of inferior parts" " My opinion is clear, we have 1 product, and all our sources needed to build a release (excluding third party, since its not our sources) should be kept within main. For that reason I continue integrating genLang with languages in main in the l10n40 branch. We will of course sometime in the future discuss it l10n40 is something we want in trunk and if not it will not be merged. > > And if we have many more things that are not used at all we should think > about removing them. > mwiki extension, Crashrep, reportbuilder, javainstaller2 are the ones I remember, when I integrated --genPO in build.pl, I found about 15 modules that are not build in either windows/ubuntu releases. rgds jan I. > Juergen > > > > > rgds > > jan I. > > > > > >> Herbert > >> > >> > ------------------------------**------------------------------**--------- > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org< > dev-unsubscr...@openoffice.apache.org> > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
