Hi,
the initial concern was about a page on the wiki in french that was older
than the english one, and with significant differences in a list of tags
(still landuse=basin rather than the new natural=water), the change on
the english page was made more than 1 year ago !
the translate extension
On Fri, Jul 25, 2014 at 4:26 AM, Andreas Goss andi...@t-online.de wrote:
But that concept is not really reality. There a dozen for German pages which
are completely different from the English one, but both cover that topic in
a way that is usefull for people who get to that page.
The main
Hi all,
As for improving translation tasks on OSM wiki, how would you feel about
the Mediawiki Translate extension ?
https://www.mediawiki.org/wiki/Extension:Translate
I won't explain how important translated content is for non-english people
looking for reference or documentation.
This
As for improving translation tasks on OSM wiki, how would you feel about
the Mediawiki Translate extension ?
I'm against any kind of automatic translation tool, which will just
cause more errors. When I look up a word I'm usually at least presented
with more than one translation.
Also this
What we really need is people actually editing the Wiki in the first
place and in my opinion the best way to get people to do so would be a
better editor: https://www.mediawiki.org/wiki/VisualEditor
There's an issue for this on trac [1] but the main problem is that the
extension moved from
extension moved from requiring mediawiki 1.23 to requiring mediawiki 1.24
which is still in development.
Can't you just use the old version that worked with 1.23?
__
openstreetmap.org/user/AndiG88
wiki.openstreetmap.org/wiki/User:AndiG88
Hi Andreas,
I agree with you about the automatic translation tool and that wasn't my
point.
Contributors should always translate documents by themselves without using
any automatic tool.
Nevertheless, some features of the extension would bring us some comfort
when dealing with translation topic.
Hi,
On 07/24/2014 08:22 PM, Andreas Goss wrote:
Also this seems geared towards 1:1 translations, which in the
OpenStreetMap Wiki often isn't the reality, because some things are
different from country to country. Or for example usefull combinations
or see also might be different.
Fully
2014-07-24 22:47 GMT+02:00 Frederik Ramm frede...@remote.org:
I wonder if it might be better to do what Wikipedia have done - instead
of having one Wiki where the same articles exist in different languages
(and often with wildly different content), have a Wiki for every
language where the
Hi,
On 07/24/2014 11:05 PM, François Lacombe wrote:
According to you, we'd better split OSM in several projects, one for
each country and data consumers will do the rest.
This would be interesting but it is not what I said. I said, let's have
different Wikis for different languages.
It is
As a somewhat regular translator, I would like to say something.
My gut feeling is that we shouldn't separate the wiki into different ones,
but I can say there are some considerable issues on the model we have right
now.
Often when I am going to translate an article, I try to improve it, but
In my opinion we should try to keep the different language pages as similar
as possible - that is, they should aim to be just translations of one
another. My reason behind this is that OpenStreetMap is a community and
data project. We need to work together and use common tagging so that
developers
On 25.07.2014 01:04, Rob Nickerson wrote:
In my opinion we should try to keep the different language pages as
similar as possible - that is, they should aim to be just translations
of one another. My reason behind this is that OpenStreetMap is a
community and data project. We need to work
+1
Language is not the same thing as country. There could well be
French-speaking people mapping in England, English in Spain, Spanish in
Egypt, Arabic-speakers in Turkey, Turks in Germany, etc.
Steve
On 25/07/2014 00:04, Rob Nickerson wrote:
In my opinion we should try to keep the
Using the same Wiki with language namespacing implements the concept of
very close translations - the structure is the same for everyone, and
the translator is just expected to fill in the blanks. I don't believe
that this will lead to high-quality documentation; I believe this will
be at
If there is country specific information about a tag then I would like
to be aware of it, as it could be useful for other countries/languages too.
And if I open a DE:feature I would like to be presentet with the
information relevant to my country in the first place.
If I open
16 matches
Mail list logo
