-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessiblity to tourists #8
Comments
You may need to separate labels from the rest, like they do in http://toposm.com. this though makes it harder to use the tileserver in 3rd party applications. |
We can create two sets of tiles, one in English and one in Hebrew. |
I have made a version of the hiking rule set with English label, to create my INT offline map file in English. I will make a PR with it (I will first merge it with the recent changes of the Hebrew rules from the master). |
I know this may seen a lot to ask but adding an English rules file will probably make it harder for us to maintain the current rules file as we will need to remember to add every change to both files. |
I understand the problem. I'll look into it, but that won't happen before I get back from my vacation. Do you prefer I PR the en rules, just so people can have a look at them, or should I hold off anyway? |
I don't think someone is anxious to get the English rules file so I wouldn't hurry with a PR. |
I like the idea of having a Maperipy script create the name tag to be used by Maperitive in order to enable easy language switching. Perhaps the script can be configured to take a sequence of languages in descending order of priority. For example, the "en;he;_" language sequence will direct the script to take the English name tag, if it exists, otherwise, the Hebrew name tag, if it exists, or else, take the name tag, it it exists. This idea is based on the work of the Multilingual Map Test. Unfortunately, this site is currently not working. By the way, in order to avoid conflicts with existing tags, we can start using our own tag namespace, such as maperitive:name or ihm:name. |
@HarelM Do you have a preference for where to store the English tiles for the two maps? I suppose the map language will change when changing the interface language. |
Ideally I would say the the tiles should be stored in a folder with a language code (i.e. /he/tiles/... /en-US/tiles/...) but I know that changing the current tiles folder is problematic. |
With all respect to structure, and you know I have, I have greater respect to backward compatibility and avoiding disruptions to users. In short, I'd rather not move the existing tiles, as many people and applications use the current paths. For the English tiles, I thought of using Instead of changing the definition of existing layers, perhaps we may have 2 layers for each map - one for every language. Can the layers UI avoid showing a layer without removing its definition? |
Everything is possible :-). Let me know when you have a working example and I'll see if I can play around and see how it works. |
I'm OK with If we use We can create a junction/symbolic link for use by the Site's code. IMO and experience, elegance is not a good justification for inflicting incompatibility on users by removing the current addresses. Each user must feel he/she gets something for the price of incompatibility. |
We can keep the current addresses as our definition of "defalt" tiles. Current address /tiles will be linked (not by the user but by us) to /he/tiles. If we decide to change the default it is up to us. |
Actually, all tile directories are virtual directories in IIS. There is no need for creating any links in the server's file system. As for the map generation process, I'll use a slight modification of your suggestion and rename the "Site" directory to "Hebrew" and create the English tiles under the "English" directory. |
Great! let me know when I can start playing with it. |
I'm not sure how relevant the feature is, but currently this map is not accessible to tourists.
making English tiles or English labels tiles would help in this direction.
The text was updated successfully, but these errors were encountered: