[josm-dev] multiline entry in template (was: sac_scale in JOSM - RFC for change of translation)
On Tue, Nov 30, 2010 at 11:04 AM, Sebastian Klein wrote: Btw.: You can use html markup to create a multiline entry, e.g. htmliWanderweg/ibrnbsp;nbsp;ausgeglichene Steigung, Absturzgefahrbrnbsp;nbsp;nicht ausgeschlossen/html (The height of the sac_scale field in the preset dialog will grow accordingly, but I would fix this little flaw later.) I've tried that locally for one entry, but with somewhat mixed results, see http://img146.imageshack.us/img146/7209/josmtemplatesacscale.gif 1. after selecting the entry from the list, the raw html text shows up in the text item (see screenshot). How to prevent this? 2. the text is editable. So if the user changes the default text, this (usually invalid) text is put into the tag value. Is this behaviour intended? (3. as you've said, the height grows.) br, Georg ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] sac_scale in JOSM - RFC for change of translation
On Mon, Nov 29, 2010 at 5:59 PM, Dirk Stöcker openstreet...@dstoecker.dewrote: I had a look at the description and they are pretty straighforward. I see no problem to express each of the steps in 3 to 4 words. Why not simply doing so? That would fit perfectly in the selection box without needing too much changes. Here we go, these are my proposals for translation: German: hiking=Einfacher Spazier- oder Wanderweg mountain_hiking=Wanderweg demanding_mountain_hiking=schwieriger Wanderweg alpine_hiking=schwieriger alpiner Steig demanding_alpine_hiking=schwieriger alpiner Steig, Kletterstellen difficult_alpine_hiking=schwieriger, gefährlicher alpiner Steig, Kletterstellen English (some native speaker might want to comment on these, please. See http://wiki.openstreetmap.org/wiki/Key:sac_scale for what I was trying to express): hiking=promenade or simple hiking trail mountain_hiking=hiking trail demanding_mountain_hiking=difficult, exposed hiking trail alpine_hiking=difficult, exposed hiking trail. Hands needed demanding_alpine_hiking=difficult, exposed hiking trail with climbing difficult_alpine_hiking=difficult, hazardous br, Georg ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] sac_scale in JOSM - RFC for change of translation
On Thu, Nov 25, 2010 at 10:14 AM, Dirk Stöcker wrote: If your descriptions are so misleading, then find others. OSM is no read the wiki and when you understood it start project. It is a start and work project. When your classification is misleading, so users use it wrong in your eyes, then classifications needs to be reworked. These classifications follow an international, established standard which is already in place outside of OSM. It makes no sense changing these itself. No. The grades are translated as well and they have a easy definition. In usage of these is in no way accurate. Yes and no. True, german translations are in place, but no translations for english itself, it's just gradeN and this seems to work ok. Actually I oppose this solution, as it is against the basic idea of how OSM works. I don't think it's against the basic idea and changing these translations back to T1-T6 has been discussed positively on german, italian and austrian mailing lists. But I get your point, we will try to find a more user-friendly solution. But back to my previous question: is it possible to put a link to the wiki right at the sac_scale list of values? Not only to generic path wiki at the bottom of the template window. @Martin: I don't like the idea of removing sac_scale from the path template, this would just remove sac_scale from new hiking paths, as novice mappers wouldn't know about the tag at all. br, Georg ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] sac_scale in JOSM - RFC for change of translation
Dear readers of OSM tagging and josm-dev lists, after some discussion on german and italian mailing lists it has been proposed to change the display values of sac_scale in JOSM's path template to T1 ... T6 (see http://wiki.openstreetmap.org/wiki/Key:sac_scale for description, http://gis.638310.n2.nabble.com/Unzahlige-Wege-mit-sac-scale-bzw-trail-visibility-die-komplett-falsch-eingetragen-ist-td5749700.htmlfor discussion in German). Reasoning behind this proposed change was the hope to motivate the mapper to read the wiki to get the meaning behind T4 etc. instead of drawing quick and wrong conclusions out of the rather misleading textual values of alpine_hiking etc. So this would be shown in a similar way as tracktype (grade1-5) in the track template. Thus we hope to improve the quality of the sac_scale tag, which is in rather bad condition in some areas. Please comment if you object to this change JOSM's path template. Second question to josm-dev: Am I right in thinking that this can be completely done in launchpad ( https://translations.launchpad.net/josm/trunk/+pots/josm/de/+translate?batch=10show=allsearch=hiking )? Best regards, Georg ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] sac_scale in JOSM - RFC for change of translation
On Wed, Nov 24, 2010 at 9:36 PM, Stefan wrote: You want to increase quality by removing information? Are you sure? At best you will achieve a decrease in the sac_scale usage. If any, add more information to josm, not less. If the description is misleading, then change the description. Add examples. Add links to the wiki. Relying on the users to actively search information because it is withhold from him on purpose? Doesn't sound encouraging to me. I see your point, but if you look at the template it's not possible to put a long description in the list of values for sac_scale. And the current information is misleading, so the idea has been better none than wrong. There is already a link to the wiki at the bottom of the template window, which links to path and from there to sac_scale. If somebody can tell me how, I would also add a link to the sac_scale directly at the list of values for sac_scale, please advise. And we are already relying on the users to actively search for the meaning of tracktype = gradeN, so this seems to work ok and is feasible. I'm also not totally happy with this solution, but we didn't come to any better one during the discussion. br, Georg ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] EPSG:31287 projection
On Tue, Oct 12, 2010 at 1:25 PM, Sebastian Klein basti...@googlemail.com wrote: On the at-mailing list, there where reports about an offset of a view meters. Have the reasons been investigated? Could be a jmapproj bug or incorrect wms... I think it's a jmapproj problem. Using this WMS in Merkaartor with the same proj4 parameters does not show any offset. br, Georg ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
