RTL text word-wraps in reverse order #1515
Comments
|
Author: tom[at]compton.nu I've just looked at that link at it appears to be rendering in the way you say is correct - it is rendered as " " at the moment. Are you seeing something different? |
|
Author: Esperanza36 No, first we must have (refugee camp) |
|
Author: tom[at]compton.nu In that case I think the problem is that the tagging is wrong. If I look at that node in my web browser by going to http://www.openstreetmap.org/browse/node/327387610 then my browser renders it (in both the name and name:ar tags) as " " but you seem to be saying it should be the other way round? So is my browser also getting the rendering wrong? or are you saying it should be rendered differently on the map to when written as a string? |
|
Author: Esperanza36 The tag is ok : http://www.openstreetmap.org/browse/node/327387610 The problem is that on the first line on mapnik rendering (no problem with osmander) and not On the second line instead of we should have I use Mozilla ... |
|
Author: tom[at]compton.nu OK. So what you're saying is that the words on the map should be rendered in a different order to the words when written as a string? Why is that? Is the issue that there is a line break and that in arabic you read lines from bottom to top rather than top to bottom? |
|
Author: Esperanza36 In Arabic, we read lines from top to bottom ;) |
|
Author: tom[at]compton.nu Aha... I get it now... This is a mapnik problem though, so it will need to be raised in the mapnik trac as it isn't something in our code base that is wrong. |
|
Author: tom[at]compton.nu I have raised this in the mapnik trac as http://trac.mapnik.org/ticket/189. |
|
Author: Ldp #2182 has been marked as duplicate of this ticket. |
|
Author: jahudie[at]gmail.com It is really about time to take care of this issue. Please check if you could fix this bug somehow that was opened. |
|
Author: TomH As I explained in the previous comment, this is not something we have have any control over - it is an issue with the mapnik software we use to render the map. We have reported the issue upstream so if you want to moan (which would be bad form anyway for Open Source Software) then you should do so at http://trac.mapnik.org/ticket/189 as moaning here will achieve nothing. |
|
Author: dimka I've submitted a "quick and dirty" patch upstream. Can it be incorporated in the main OSM mapnik layer? |
|
Author: Ldp Only if/when it is fixed upstream, and in due time. Submitting a "quick and dirty" patch upstream isn't going to magically make everything alright in the main OSM mapnik layer all by itself and overnight. It's currently still at 0.7.2-dev, so any fixes in trunk will be off limits until such a time we switch over to mapnik trunk. Nevertheless, thanks for taking a look at fixing this upstream. |
|
Author: dimka Replying to [comment:15 Ldp]:
I hope that when the mapnik team finishes all the necessary tests, the patch can be incorporated into the 0.7 line and not wait for the Mapnik2 release. In that case, will it be possible to update the downstream version of mapnik running on the main OSM site? Please understand that this is a very annoying bug - people see many labels messed up the first time they open OSM. |
|
Author: TomH Getting it in to 0.7 is supremely irrelevant as I believe we have been running mapnik 2 for some time now, |
|
Author: Ldp Replying to [comment:17 TomH]:
Correct, but I've falsely assumed it would need a stylesheet element to activate, and in that case, our 0.7- style XML is still relevant. Upon reviewing the patch, it seems that's not needed. This would mean we could get the patch active on osm.org once it's accepted into mapnik trunk. |
|
Author: dimka The patch has just been committed to Mapnik trunk (http://trac.mapnik.org/changeset/3365). |
|
Author: dimka Please consider applying the patch. |
|
Author: Esperanza36 Please consider applying the patch. This bug is VERY annoying for my arabs friends. Thanks in advance |
|
Author: amire80 Now this also affects the official Mobile Wikipedia app, which is switching from Google to OSM. |
|
Author: Ldp Replying to [comment:23 amire80]:
Then the persons making that Mobile Wikipedia app can fix it by upgrading their mapnik, right? |
|
Author: dimka No change is apparent on OSM.org |
|
Author: Ldp Replying to [comment:26 dimka]:
That's because the mapnik version there hasn't been updated yet, but I understand the good mapnik folks hope to have a new release soon. |
|
Author: mariotomo any news? when is mapnik scheduled to be updated on OSM? http://osm.org/go/btJRqQa5Y-- |
|
Author: TomH We plan to reload the rendering database in the next few weeks with an ODBL clean planet, and I believe Jon plans to upgrade mapnik at the same time. |
|
Author: sdoerr Replying to [comment:29 TomH]:
Did this happen? The word-wrap issue with Arabic still seems to be there, e.g. (currently in the news) [http://www.openstreetmap.org/browse/node/2072091143 In Amenas]. |
|
Author: TomH Not yet no, it is still in the planning stages as it is a major update of software and hardware. |
|
Author: TomH The reload was done a few months ago - could you check if this is now fixed? |
|
Author: yrtimid[at]gmail.com The hebrew word-wrap looks good now. |
Reporter: Esperanza36
[Submitted to the original trac issue database at 10.50pm, Tuesday, 20th January 2009]
There is a problem with Arabic names rendering on Mapnik, only for areas, like hospitals, public buildings, parks names ... and not for street names.
Words are correctly rendered, but they are not in the good order (last are first).
For instance here : http://www.openstreetmap.org/?lat=31.42411&lon=34.33985&zoom=15&layers=B000FTF
(good one)
is on OSM the contrary
The text was updated successfully, but these errors were encountered: