roadmap 1.2.1, build_osm osmgetbmap can't work correctly

View: New views
9 Messages — Rating Filter:   Alert me  

roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by ZhaoAlexander :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hi, all
I am a newbie, but when I use build_osm I find in php osmgetbmap,
the server is define as www.openstreetmap.org, but I check it from www.openstreetmap.org wiki, it seems that
the server is set as api.openstreetmap.org.
and the path is /api/0.6/map.
 
the original code is like this.
$server = "www.openstreetmap.org";
//$server = "osmxapi.informationfreeway.org";
//$server = "openstreetmap.gryph.de";
$path = "/api/0.5/map";
 
 
is that mean we need to change it to new address?
and from my fedora11, if I don't change the address, it will return forbidden 403 error.
 
 
Thank you.


使用新一代 Windows Live Messenger 轻松交流和共享! 立刻下载!
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by Paul Fox-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

zhaoalexander wrote:
 >
 > Hi, all
 >
 > I am a newbie, but when I use build_osm I find in php osmgetbmap,
 >
 > the server is define as www.openstreetmap.org, but I check it from www.openstreetmap.org wiki, it seems that
 >
 > the server is set as api.openstreetmap.org.
 >
 > and the path is /api/0.6/map.

you should change the 0.5 you find in the code to be 0.6.  the
open streetmap project changed their protocol, and didn't preserve
backward compatibility.

paul

 >
 >  
 >
 > the original code is like this.
 >
 > $server = "www.openstreetmap.org";
 > //$server = "osmxapi.informationfreeway.org";
 > //$server = "openstreetmap.gryph.de";
 > $path = "/api/0.5/map";
 >
 >  
 >
 >  
 >
 > is that mean we need to change it to new address?
 >
 > and from my fedora11, if I don't change the address, it will return forbidden 403 error.
 >
 >  
 >
 >  
 >
 > Thank you.
 >
 > _________________________________________________________________
 > Messenger°²È«±£»¤ÖÐÐÄ£¬Ãâ·ÑÐÞ¸´ÏµÍ³Â©¶´£¬±£»¤Messenger°²È«£¡
 > http://im.live.cn/safe/part 2     text/plain                 389
 > ------------------------------------------------------------------------------
 > Enter the BlackBerry Developer Challenge  
 > This is your chance to win up to $100,000 in prizes! For a limited time,
 > vendors submitting new applications to BlackBerry App World(TM) will have
 > the opportunity to enter the BlackBerry Developer Challenge. See full prize  
 > details at: http://p.sf.net/sfu/Challengepart 3     text/plain                 176
 > _______________________________________________
 > Roadmap-general mailing list
 > Roadmap-general@...
 > https://lists.sourceforge.net/lists/listinfo/roadmap-general

=---------------------
 paul fox, pgf@... (arlington, ma, where it's 55.8 degrees)


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by ZhaoAlexander :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hi,
Thank you.
And I am trying to translate the QT4 gui raodmap into Chinese, but it seems that the original roadmap_lang factory is one solution, but according to
Qt interface, there is a better way to using QT lingust to do this kind of job(but this will ruin the lang factory).
is there some schedule in internationalize?
if there is, it is better to make this interface to all gui, or I will just translate it in QT4 gui.
 
 
Thank you.

 

> To: roadmap-general@...
> Date: Wed, 8 Jul 2009 23:03:30 -0400
> From: pgf@...
> Subject: Re: [Roadmap-general] roadmap 1.2.1, build_osm osmgetbmap can't work correctly
>
> zhaoalexander wrote:
> >
> > Hi, all
> >
> > I am a newbie, but when I use build_osm I find in php osmgetbmap,
> >
> > the server is define as www.openstreetmap.org, but I check it from www.openstreetmap.org wiki, it seems that
> >
> > the server is set as api.openstreetmap.org.
> >
> > and the path is /api/0.6/map.
>
> you should change the 0.5 you find in the code to be 0.6. the
> open streetmap project changed their protocol, and didn't preserve
> backward compatibility.
>
> paul
>
> >
> >
> >
> > the original code is like this.
> >
> > $server = "www.openstreetmap.org";
> > //$server = "osmxapi.informationfreeway.org";
> > //$server = "openstreetmap.gryph.de";
> > $path = "/api/0.5/map";
> >
> >
> >
> >
> >
> > is that mean we need to change it to new address?
> >
> > and from my fedora11, if I don't change the address, it will return forbidden 403 error.
> >
> >
> >
> >
> >
> > Thank you.
> >
> > _________________________________________________________________
> > Messenger°²È«±£»¤ÖÐÐÄ£¬Ãâ·ÑÐÞ¸´ÏµÍ³Â©¶´£¬±£»¤Messenger°²È«£¡
> > http://im.live.cn/safe/part 2 text/plain 389
> > ------------------------------------------------------------------------------
> > Enter the BlackBerry Developer Challenge
> > This is your chance to win up to $100,000 in prizes! For a limited time,
> > vendors submitting new applications to BlackBerry App World(TM) will have
> > the opportunity to enter the BlackBerry Developer Challenge. See full prize
> > details at: http://p.sf.net/sfu/Challengepart 3 text/plain 176
> > _______________________________________________
> > Roadmap-general mailing list
> > Roadmap-general@...
> > https://lists.sourceforge.net/lists/listinfo/roadmap-general
>
> =---------------------
> paul fox, pgf@... (arlington, ma, where it's 55.8 degrees)
>


更多热辣资讯尽在新版MSN首页! 立刻访问!
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by Paul Fox-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


zhaoalexander wrote:
 >
 > And I am trying to translate the QT4 gui raodmap into Chinese,
 > but it seems that the original roadmap_lang factory is one
 > solution, but according to
 > Qt interface, there is a better way to using QT lingust to do
 > this kind of job(but this will ruin the lang factory).
 > is there some schedule in internationalize?

we don't have much of a schedule for anything, at the moment.

 >
 > if there is, it is better to make this interface to all gui,
 > or I will just translate it in QT4 gui.

it would be much better to use a generic scheme, and not a scheme
tied to a specific gui.  i don't know if the current roadmap_lang.c
scheme is a rich enough scheme for the future, but hopefully
there's some scheme (e.g., GNU gettext?) that we could use.

paul
=---------------------
 paul fox, pgf@... (arlington, ma, where it's 58.8 degrees)

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by Pablo Rogina :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


 > And I am trying to translate the QT4 gui raodmap into Chinese,
 > but it seems that the original roadmap_lang factory is one
 > solution, but according to
 > Qt interface, there is a better way to using QT lingust to do
 > this kind of job(but this will ruin the lang factory).
 > is there some schedule in internationalize?

we don't have much of a schedule for anything, at the moment.

 >
 > if there is, it is better to make this interface to all gui,
 > or I will just translate it in QT4 gui.

it would be much better to use a generic scheme, and not a scheme
tied to a specific gui.  i don't know if the current roadmap_lang.c
scheme is a rich enough scheme for the future, but hopefully
there's some scheme (e.g., GNU gettext?) that we could use.

Please let me disagree with Paul. If you are interested in using the Qt 4.x GUI of Roadmap, please do you and us a big favor and stick to the translation tools (tr() method, Linguist, lupdate, lrelease) provided by Qt. That way any developer used to Qt will pick the translation schema in a second, without need to worry about a different way to translate.
And thinking in the near term, although there's no schedule as mentioned by Paul, we can think of Qt as the basic/default/unified GUI for Roadmap since Qt is already available for Windows, Linux, Mac, Windows CE (mobile) and S60 (Symbian). So using the Qt tools will save you time and effort!

My 2 cents.

PS: Don't forget about the capability of Qt to work with .po files too!
findtr: extracts information about text to be translated. It recognizes the tr() constructs described above and produces a file in ".po" format.
msg2qm: converts translated .po files to ".qm" Qt message files (a Qt-specific binary format)

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by ZhaoAlexander :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hi,
Now, I am using QMap to make a pair about original english text and tr(string).
and using lupate and lrelease can make ts to qm files, and with that qm files, it can display other characters.

it seems that it can work fine.



Date: Thu, 9 Jul 2009 23:00:16 -0300
From: pablojr@...
To: roadmap-general@...
Subject: Re: [Roadmap-general] roadmap 1.2.1, build_osm osmgetbmap can't work correctly


 > And I am trying to translate the QT4 gui raodmap into Chinese,
 > but it seems that the original roadmap_lang factory is one
 > solution, but according to
 > Qt interface, there is a better way to using QT lingust to do
 > this kind of job(but this will ruin the lang factory).
 > is there some schedule in internationalize?

we don't have much of a schedule for anything, at the moment.

 >
 > if there is, it is better to make this interface to all gui,
 > or I will just translate it in QT4 gui.

it would be much better to use a generic scheme, and not a scheme
tied to a specific gui.  i don't know if the current roadmap_lang.c
scheme is a rich enough scheme for the future, but hopefully
there's some scheme (e.g., GNU gettext?) that we could use.

Please let me disagree with Paul. If you are interested in using the Qt 4.x GUI of Roadmap, please do you and us a big favor and stick to the translation tools (tr() method, Linguist, lupdate, lrelease) provided by Qt. That way any developer used to Qt will pick the translation schema in a second, without need to worry about a different way to translate.
And thinking in the near term, although there's no schedule as mentioned by Paul, we can think of Qt as the basic/default/unified GUI for Roadmap since Qt is already available for Windows, Linux, Mac, Windows CE (mobile) and S60 (Symbian). So using the Qt tools will save you time and effort!

My 2 cents.

PS: Don't forget about the capability of Qt to work with .po files too!
findtr: extracts information about text to be translated. It recognizes the tr() constructs described above and produces a file in ".po" format.
msg2qm: converts translated .po files to ".qm" Qt message files (a Qt-specific binary format)


立刻下载 MSN 保护盾,保障Messenger 安全稳定! 现在就下载!
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by Pablo Rogina :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Now, I am using QMap to make a pair about original english text and tr(string).
and using lupate and lrelease can make ts to qm files, and with that qm files, it can display other characters.

it seems that it can work fine.

Do you plan to contribute it to CVS? I don't see now why you need a separate QMap but reading the code maybe I can get the idea.
Anyway, please remember that you can always derive the class QTranslator to modify it as needed (providing extensions through the method translate() 

Pablo


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by ZhaoAlexander :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hi,
sure, but I don't know how to add it into that CVS, and it seems that only the menu can display, translate them all, I think it will take more time.
I just make it like this,
from file roadmap_start.c I can find the english text which will be used in QT4 GUI.
I add one QMAP<QString, QString> translateMap, and make it like translateMap["..."]=QObject::tr("...");
this will cost time, but I don't find a better way.
and using lupdate and lrelease to fix that tr context, and translate it to other languages.
in the qt4 main, using translate.loadtranslate(...)
 
Alex.
 

Date: Sun, 12 Jul 2009 21:33:54 -0300
From: pablojr@...
To: roadmap-general@...
Subject: Re: [Roadmap-general] roadmap 1.2.1, build_osm osmgetbmap can't work correctly


Now, I am using QMap to make a pair about original english text and tr(string).
and using lupate and lrelease can make ts to qm files, and with that qm files, it can display other characters.

it seems that it can work fine.

Do you plan to contribute it to CVS? I don't see now why you need a separate QMap but reading the code maybe I can get the idea.
Anyway, please remember that you can always derive the class QTranslator to modify it as needed (providing extensions through the method translate() 

Pablo



与任何您希望的人分享您的回忆。 任何您希望的人。
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general

Re: roadmap 1.2.1, build_osm osmgetbmap can't work correctly

by Paul Fox-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

pablo wrote:
 > > it would be much better to use a generic scheme, and not a scheme
 > > tied to a specific gui.  i don't know if the current roadmap_lang.c
 > > scheme is a rich enough scheme for the future, but hopefully
 > > there's some scheme (e.g., GNU gettext?) that we could use.
 >
 >
 > Please let me disagree with Paul. If you are interested in using the Qt 4.x
 > GUI of Roadmap, please do you and us a big favor and stick to the
 > translation tools (tr() method, Linguist, lupdate, lrelease) provided by Qt.

you're saying you'll introduce translation at the toolkit layer?
why would you do this?  there's already been work done on
roadmap_lang.c, which is useful with any desktop toolkit.  are
you planning on discarding the roadmap_lang work?  perhaps it's
not a complete solution, but the gettext utilities are also
available.  so this makes no sense to me.  why is translation and
localization in a desktop-specific API?

 > That way any developer used to Qt will pick the translation schema in a
 > second, without need to worry about a different way to translate.
 > And thinking in the near term, although there's no schedule as mentioned by
 > Paul, we can think of Qt as the basic/default/unified GUI for Roadmap since
 > Qt is already available for Windows, Linux, Mac, Windows CE (mobile) and S60
 > (Symbian). So using the Qt tools will save you time and effort!

no, using the QT tools will keep users of other desktops from taking
advantage of your translation work.

perhaps QT is, indeed, the way to go these days.  it certainly
wasn't a few years ago, but perhas that has changed.  but forcing
it by implementing features in QT with no regard for the current
desktop-neutral architecture seems a bit premature.

paul
=---------------------
 paul fox, pgf@... (arlington, ma, where it's 70.3 degrees)

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Roadmap-general mailing list
Roadmap-general@...
https://lists.sourceforge.net/lists/listinfo/roadmap-general