On Fri, 17 Jul 2009, Frederik Ramm wrote:
I propose to split up the build process so that it builds a special
version for each language. In addition, we can keep building the
all-languages version for those in a true multilingual environment (or
those on a fat pipe who would rather not be bothered). That would be the
easiest way to tackle the problem. I'm not an ant guru but I think even
I could do that.
Sure this would be easy (BTW you forget that we don't use ant for the
release). But also here I have some doubts. First I agree with the
description of Ævar who says that users not necessarily will download the
right version.
Second it should be clear that everything discussed here would only be
available for tested at all (like e.g. Windows installer, MacOS version
and WebStart are also).
The easiest way to produce language separation is usage of "zip -d" to
remove the unwanted parts.
If someone is willing to do the necessary work to improve the webstart
stuff regarding separate language files (and plugins) I happily will help
to integrate it on the server (maybe also get a real-Java-acceptable
Thawte certificate.
For the normal download version I see no reason at the moment. We probably
have 15 new versions a year which makes 80MB download if you get all
versions. This is nothing compared to the data going from and to josm in
some more or less active sessions (especially if you use WMS or related
plugins).
From my point as openSUSE packager language separation would not be
useful. The RPM packages would contain the complete data set anyway.
(I also like the Web Start idea but I have burnt my fingers with that on
Linux using non-Sun Java installations in the past so I'm not sure how
far I want to trust it; plus I am unsure how good this works when you're
offline?)
Well, WebStart is new for me too. When I had to do with Java first time 10
years ago an applet was the (only?) choice and I can't remember there have
been standalone apps. Also the security settings have been a pain. It
seems Webstart is somewhere inbetween the standalone fullpowered josm and
the restricted world of Java which I knew about.
A final note: Could we postpone this discussion until next week? I will
have a look at some improvements in the way the data is stored. Maybe the
storage of the texts can be improved a lot compared to current situation.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
_______________________________________________
josm-dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/josm-dev
