You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be nice to propose Zawgyi-to-Unicode fixes directly in iD and JSOM. This would be easier for users, and it would give a bit more exposure. Both editors already ingest various other edit suggestions from the Osmose project. Osmose has an API for uploading externally detected issues, but it also runs its own nightly pipeline that can be extended with trivial Python plug-ins.
Because the implementation would be trivial, I took the liberty to suggest adding a Zawgyi detector to Osmose. Of course I don’t know whether they’ll actually do this, but I thought it’d be good to post this here, just for information.
Thanks for making the plugin, I suggest we can deprecate this repo and make some READMEs or OSM blog post with instructions on how to use Osmose to QA Zawgyi
I think it would be nice to propose Zawgyi-to-Unicode fixes directly in iD and JSOM. This would be easier for users, and it would give a bit more exposure. Both editors already ingest various other edit suggestions from the Osmose project. Osmose has an API for uploading externally detected issues, but it also runs its own nightly pipeline that can be extended with trivial Python plug-ins.
Because the implementation would be trivial, I took the liberty to suggest adding a Zawgyi detector to Osmose. Of course I don’t know whether they’ll actually do this, but I thought it’d be good to post this here, just for information.
osm-fr/osmose-backend#2442
The text was updated successfully, but these errors were encountered: