SUPPORT US. If mindat.org is important to you, click here to donate to our Fall 2019 fundraiser!
Log InRegister
Home PageAbout MindatThe Mindat ManualHistory of MindatCopyright StatusWho We AreContact UsAdvertise on Mindat
Donate to MindatCorporate SponsorshipSponsor a PageSponsored PagesMindat AdvertisersAdvertise on Mindat
Learning CenterWhat is a mineral?The most common minerals on earthInformation for EducatorsMindat ArticlesThe ElementsBooks & Magazines
Minerals by PropertiesMinerals by ChemistryAdvanced Locality SearchRandom MineralRandom LocalitySearch by minIDLocalities Near MeSearch ArticlesSearch GlossaryMore Search Options
Search For:
Mineral Name:
Locality Name:
Keyword(s):
 
The Mindat ManualAdd a New PhotoRate PhotosLocality Edit ReportCoordinate Completion ReportAdd Glossary Item
Mining CompaniesStatisticsUsersMineral MuseumsMineral Shows & EventsThe Mindat DirectoryDevice Settings
Photo SearchPhoto GalleriesNew Photos TodayNew Photos YesterdayMembers' Photo GalleriesPast Photo of the Day GalleryMineral Photography

Improving Mindat.orgI can't change locality strings in native language. Why?

3rd Oct 2019 22:08 UTCPeter Andresen Expert

I have just edited some norwegian localities, to get a more precise sublevel locality. This include the inportant locality Sagåsen, wich is not in Mørje. Mørje is an area in Tvedalen, Larvik - very close to Sagåsen, but different sublocalities. Several other localities have been organized to more precise sublocalities in this area. The problem now is that I'm not able to do the same change in the norwegian language!

Why?

3rd Oct 2019 22:30 UTCMartin Rich Expert

Have the same problem for Austrian localities. The field for local language is deprecated, so there are now two different locality strings in the English and in the German version.

16th Oct 2019 16:15 UTCUwe Kolitsch Manager

Jolyon made the way to change/correct locality names in original language consistent, but at the same time very complicated and not easy to figure out (one first has to re-add all the local names higher up in the hierarchy and choose a language (or languages) for each; only recently a "language importer" tool has improved and somewhat simplified the process).
Please try: 
 

17th Oct 2019 00:26 UTCMartin Rich Expert

Some days or so ago I tried this for an Austrian locality, but with no success. Is somewhere a manual about this?
 

17th Oct 2019 10:01 UTCUwe Kolitsch Manager

Which locality?
Was there an error message or did the name just not appear afterwards?

19th Oct 2019 01:23 UTCMartin Rich Expert

Sorry Uwe for the late reply.
There was not an error message, but it did not appear. I'm sure that I did some wrong (a noodle working with computer).

The description from Jolyon below, if I understand correct, is for already existing entries in the local language line. But if I make a change in the English version (in the lowest level of hierarchy), how is it possible to bring this change in the local language field?

Here the examples:
Uwe, we talked about this locality.

I added in a bracket the name which appears in the map of the land surveying office. The first name seems in use of the locals.

This locality was located in a wrong valley. It is definitely in the Tauern valley and not in the Felber valley so this locality is now in an other state of Austria; a misintepretation of the reference, you can find this prospect in the IRIS database. I tried to change it also in the local language field, but with no success. Now I can see the field for local language is (automatically?) lost.

17th Oct 2019 11:48 UTCJolyon Ralph Founder

The problem now is that I'm not able to do the same change in the norwegian language!Why?
Because it doesn't work like this. The translation is only for the current level. Add the translated name at that level (and if it's exactly the same in Norwegian as English you can enter the same in as a Norwegian string too).

The best way to start is make sure that Norway is translated in to Norwegian (probably is), then go down each of the subregions, ideally using the new tool which searches Wikipedia for all translations, and then when you finally get to your locality of interest it should be easy to add in the correct translation.

The old field is simply there now to copy & paste the relevent part into the new language system.

17th Oct 2019 11:53 UTCJolyon Ralph Founder

09921270015713095634664.png
So, here's how to fix these.

From the 'Name in original/local language' field, copy the first part, the name of the locality without region, then paste it into the 'Add/Edit Language' box below, selecting Norwegian from the language list and 'Important regionally' if it's an important language for the country, and I'm guessing Norwegian is important in Norway :)  If you were adding the arabic translation you wouldn't select that!



17th Oct 2019 11:53 UTCJolyon Ralph Founder

00348070015713096245027.png
When it's saved, this is how it appears on the locality page.

17th Oct 2019 11:55 UTCJolyon Ralph Founder

Now, if you'd really prefer 'Porsgrunn' to be 'Porsgrunn  kommune' in the Norwegian strings that's easy - just go to the Porsgrunn page, and edit the language string for Norwegian that's been automatically entered from Wikipedia.

19th Oct 2019 18:22 UTCUwe Kolitsch Manager

Jolyon: there seems to be a serious bug:

I had added the local name
Pletschen (Bleksen)
to the locality mentioned by Martin (https://www.mindat.org/loc-44371.html),
but it's now erroneously shown as "Pletschen (Bleksen), Salzburg, Österreich" (the local locality names higher up in the hierarchy were already present). Clearing caches of everything including Salzburg didn't help.

19th Oct 2019 19:30 UTCJolyon Ralph Founder

Seems to be ok to me? It's in Salzburg right? I'm guessing the translations haven't been added for the intermediate levels.

19th Oct 2019 20:31 UTCUwe Kolitsch Manager

It should read
Pletschen (Bleksen), Anlauftal, Gasteiner Tal, Hohe Tauern, Salzburg, Österreich


>I'm guessing the translations haven't been added for the intermediate levels.

As I wrote:
(the local locality names higher up in the hierarchy were already present).
EDIT: Sorry, no - they were missing - will add them.
EDIT 2: Now it looks ok.

 
Mineral and/or Locality  
Mindat.org is an outreach project of the Hudson Institute of Mineralogy, a 501(c)(3) not-for-profit organization. Public Relations by Blytheweigh.
Copyright © mindat.org and the Hudson Institute of Mineralogy 1993-2019, except where stated. Most political location boundaries are © OpenStreetMap contributors. Mindat.org relies on the contributions of thousands of members and supporters.
Privacy Policy - Terms & Conditions - Contact Us Current server date and time: November 17, 2019 22:06:44
Go to top of page