View Single Post
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#317
@PamNor, I think that the bug is in libosmscout location index code and I have submitted the issue to the library. It seems that it's not very common bug and I haven't been influenced by it when testing with several other countries. I know that Norway used to work just recently since I have been in Oslo and used it. So, it looks like its a rather specific case.

In case of geocoder-nlp import, I am using libosmscout to import data from OSM-based PBF and, after that, transverse location index to feed geocoder-nlp importer. So, even if we don't use libosmscout in the default profile, I am using it for the import.

One option is to to downgrade to libosmscout version that was used earlier. If it works and I or libosmscout developers cannot fix the issue fast, I'll make new map import for libosmscout and geocoder-nlp with the older version.

Let me look into it a bit longer, may take few days.

If anyone has seen degradation in the recent version, please let me know.

@Zeta: thank you! The screenshots were made using lbt's screenshot app on device. That way it can be done with the morning coffee.

It would be great to get tutorials and manual translated - that should help the users. Whether its too soon to advertise in the wider audience, I don't know. I presume many know already and I guess the server should hold it, there have been no feedback from @MartinK.

However, before advertising, I must fix the import bug as seen for Norway. (see more specific replies below)

Originally Posted by Zeta View Post
Rinigus,

I started translation of the english user manual to French.

So far, I have only translated the index.md (https://github.com/Sagittarii/osmsco...01b02a3f51d286).

I also tried to reorder the docs directory to make it easier to navigate when there will be several translations, along the original english files :
* move the english pages to docs/en (to locate easily what needs to be translated, and because even if it is the default one, it is still a language among all)
* move the css file to docs/assets/ (that is the name I usually find in web stuff, but I am opened to suggestion)
* added the html files for french (not yet translated), but keeping the same filenames as in english, to easily check if some files are missing/new when doing translations, and so that only the /en/, /fr/,... part has to change in the url to make it easy to point to other languages without having to translate the filenames.

This can be seen in the following commit: https://github.com/Sagittarii/osmsco...01b02a3f51d286
which gives the tree seen in : https://github.com/Sagittarii/osmsco...ee/master/docs

I updated the path to js and css stuff in the new /en/ directory, so that the html files there should run correctly after these moves.
Excellent, lets move these.

Originally Posted by Zeta View Post
I kept the fullPage.js dir at the docs root, but we could put it in assets/ too ?
Would be good to move it too, just note that its submodule.

Originally Posted by Zeta View Post
Also, there is a missing index at the docs root to select the language now.
Yes, that's needed too. It could be also redirect to English with en/index.md listing all languages. But I am open to any option.

Originally Posted by Zeta View Post
What do you think of this ? If you like it, I can put a pull request for you to integrate this changed structure before other translators start working on it.

Web is not my specialty, so if someone knows better than me, please help us !
I think its a great way and let's optimize the directory tree to make it simple for others.
 

The Following 4 Users Say Thank You to rinigus For This Useful Post: