Now we're getting somewhere. You see the dump there the desList & description entry. There could also be titleList and title entries.

These entries are parsed and what the addon does is look into the file /Libs/EnKai/locales/localizationRU.lua and look for a pattern setup in lang.mapIdentifiers.

Now you just need to get the pattern right for that part of the text in the above mentioned entries which can enable the addon to identify the entry.

Cheers
N.

I think I found the problem Switched my client to Russian and made the neccessary changes to get it running. One problem was that for some strange reason in the Russian client there could be an entry without name property. So I included a check for that.

Now in my client there's still ? for mailbox but if you mouse over the entry it shows the Russian text in Cyrillic.

Here you'll find a modified version of the addon with everything ready for Russian:

http://www.filedropper.com/nkcartographer-russian-alpha

Also I suggest that you install my addon nkDebug. If nkDebug is installed automatically some debug dumps are send to chat. For unknown entries it will dump what data it was able to gather. This helps a lot.

Hope this helps to fix the problems and make it possible for you to do the translation.

Cheers
N.

I only just notice what needs to be done to properly make it work in Russian. I excluded Russian and French in so many places, some more changes are needs. Sorry I hadn't thought about that earlier.

English names makes it much easier. In this case simply copy the contents of the file /Libs/EnKai/locales/localizationEN.lua to the ...RU.lua version.

That way you should have a baseline. However at the top of the file you need to modify the following line:

line 11 - if ( Inspect.System.Language() == "English" ) then

to

if ( Inspect.System.Language() == "Russian" ) then

Also you will need to modify line 11 in the file localizationEN.lua:

from:

if ( Inspect.System.Language() ~= "German" and Inspect.System.Language() ~= "French" ) then

to:

if ( Inspect.System.Language() == "French" or Inspect.System.Language() == "English" ) then

otherwise the English file would overrule the Russian one.

Finally if you look at the English file you'll find the entry on line 218:

{ pattern="Stylist", type = "VARIA.STYLIST", name = "DESC1"},

The text 'Stylist' will be looked for and if present like in the tooltip this will trigger the type.

Hope this helps.

Cheers
N.

Ahh I forgot to write that you need to add the new Russian language file to the list of files to load. This is done in the RiftAddon.toc file which you'll find in the Cartographer base directory and the Lib\EnKai directory.

In there you'll find a section called RunOnStartup = {

Simply add a new line like you'll find there already is for German and English language.

Cheers
N.

artifact recording was bugged and is fixed in nkCartographer V1.1.3

Cheers
N.

Thanks I'll look into this. The thing with the translation is that the addon relies on text patterns to recognize what the Rift API is reporting to be shown. Here's what I wrote a French guy willing to do the French translation.

Thanks for the offer. It would be really awesome to have a french translation. It is however not simple. There's the user interfaces which is defined in the file \locales\localizationXX.lua where XX is the language. It would be localizationFR.lua for French.

You'd have to change the line 55 in main.lua so that French is no longer filtered: if syslang ~= "German" and syslang ~= "English" then .. Simply remove lines 55 - 58.

Then comes complicated part. As the Rift API does not report much map related information I need to parse the title and description and do same pattern recognition to find out what's what. This is done in the file /Libs/EnKai/locales/localizationXX.lua (Same as abvove so localizationFR.lua) If you look at the French and the English file you'll see that the entries lang.mapPatterns, lang.mapIdentifiers, lang.mapIdentifiersGeneric, lang.mapIdentifiersExcludeLevel and lang.mapIdentifiersVendors are missing in the French file. Now these are the important parts for the map translation.

For a start simply copy these over from the English file. You'll end up with a loot of ? on the map as the addon cannot yet find out what an entry is in French client. There are simply entries like for example: Mailbox. This is an easy translation but it has to be exactely what the tooltip is showing if you mouse over the ? on the map.

Entries like pattern="Minor (%a+) Rift %(Active%)" are more complicated. The addon extracts information from the text. The placeholder (%a+) tells the addon to extract something from the text at this position. This would be the type of the Rift like Fire, Water, etc. Again check the tooltip. Then the detail info egExValues = lang.mapPatterns.RIFT tells the addon to look into the mapPatterns entry to find out what for example the text Fire would relate to (FIRE in this example).

The %(Active%) is written this way because special chars need the % in front to differentiate it from the extract bracket. I hope this is understandable.

Now another special case is: pattern="(%a+)[ ]?[G|g]lory",

Here the [ ]? means that there could be a space at this position but must not. Then [G|g] means either a capital or lowercase G.

Finally there are the special chars in the French language same like the Umlaute in German. For this (%a+) will not work. You'll need to build an entry like this: ([%aäüöÜÖÄ]+). Of course the öäü etc. needs to be replaced by the French special chars like àéè etc.

I hope you're still interested allthough it's a bit more complicated than you maybe thought. Let me know what you think abou this.

Cheers
N.

Artifacts is implemented and tested. Could be a new bug is which hasn't been reported, yet. Which client language do you play with?

Maybe you turned of the 'show artifact' option in the configuration.

Cheers
N.