No language files were found in templates dir for selected language!

English forums
1

Hi,

Im trying to “Create new language”, but i get this message:
"Attention: No language files were found in templates dir for selected language!"
I made a copy of “en” folder and renamed it to “dk”. Edited the content of the files to: “$sLangName = “Danish”;” and then created the new language, but i get this error and the store has almost nothing translated, like:

        WIDGET_SERVICES_HELP
        WIDGET_SERVICES_LINKS
        WIDGET_SERVICES_GUESTBOOK
        WIDGET_SERVICES_BASKET
        WIDGET_SERVICES_ACCOUNT
        WIDGET_SERVICES_NOTICELIST
        WIDGET_SERVICES_MYWISHLIST
        WIDGET_SERVICES_PUBLICWISHLIST

If i put any of these into lang.php(they are translated in map.php) and translate them, then it works for that single word. still gives that error tho

whats wrong? :slight_smile:

2

Hello gnomic,

where did you get the Danish lang files from? Do you know about the community translation project we started here:
http://translate.oxidforge.org/

You’ll find more information about lang files here

Danish is pretty new for this project - contributed by topconcepts - 23% translated and still map and flag files are missing. If you want, you can register to the translation center and help with translating.

Regards

3

Hi Marco,

i didnt get them from anywhere. I have been working on them myself.

i have looked at that site, but still no idea, whats wrongs. taking another look, until someone might have an idea, how to help me

4

there are several places for language files, maybe you changed / added in the wrong folder?

5

I think i got it now. Im not sure how this child theme thing work. I wasnt enough to have the /dk folder+files in my child theme folder, but i also needed them in azure? but if i need to show a background image, that i only have in the childtheme, then it works fine, to have “background:url(…/…/img/something.png) no-repeat;” in oxid.css why?

@Marco i might help out with the translation, when i get some sparetime.

6

wow, i really dont hope they do this to often! pretty annoying you have to start all over with everything, because they decide to make changes… atleast make it easy for us…

PAGE_INFO_CONTACT_TITLECONTACT, has been changed to ‘CONTACT’… fair enough, it makes sense, but come on, now i have to go through every single thing again…

edit: they know what is being translated, why not make a system, that looks at the old translations and combine them, to make a new one. simple right? then you will probably be left with some news once, since they added some, but then the system will highlight them, and tell me to translate those… did they make this? or am i doing something wrong? this just seems stupid

7

What I could do for you (depending on your shop version) is to import all of your translations into the translation center and to hand you out all files you would need.

Deal?

8

Many hours of work in those translations( made in 4.6.x i think its called), and i would need them in 4.7.4. But sure, we are here to help out each other and get more people into oxid.
Sure, deal :slight_smile:
But people should be able to edit my translations, since they might not be 100% correct. Btw, i probably didnt translate all of them, since i didnt need all of them, for my store. But i had most of them.
How do we do this?

9

?characters

10

Sorry for the delay @gnomic. Had a very hard week end including a funeral and a confirmation.

Could you please pack all translated files you have and send them to my email address? See my PN. I will do what I can to import them into the translation center where for Danish we already have 24% translated. Hope your contribution will increase this rate a bit :slight_smile:
Everybody has access to it and can help working on untranslated phrases as well as correcting the existing ones.

Regards

11

No worries, thanks a lot for responding. I will send the files shortly :slight_smile:

12

There should be 160 + 26 keys left, until we reach 100% of the [B]front end(template)[/B]. When we reach this, Marco will upload the package to OXID eXchange, as he did with several other languages. I will continue the work on it, pretty soon, so this can be done :slight_smile:

13

good news - thanks for help!

14

I dont know how to translate these, since it looks like no other country(en,de, etc.) did so. They just wrote the same:

OXAMITEMID, OXAMTASKID, OXBLFIXEDPRICE, OXICON, OXSUBCLASS, OXVARSELECT

Should i just do the same?

15

Hello gnomic,

thanks for this one. I opened up a bug record:
https://bugs.oxid-esales.com/view.php?id=5101

This keys are not used in tpl files and are not language dependend. So pls. leave them out in translations.

Cheers

16

Oh - and just to let you know: besides this unnecessary keys that shall be removed, @gnomic finished the translations for the entire store front. Thank you very much mate!
After I did the export you can now download the package from translate.oxidforge.org as a complete package with all languages, just remove the unnecessary languages, copy them to your OXID eShop installation and follow the rest of the steps to activate your language. Everything shall be in place now.

Let us know!

17

Sounds good, thanks a lot :slight_smile: