Macarlos1

[Macarlos1]

Hi

Hmm strange. If it wouldn’t be in the relevant directory, I think that I wouldn’t be even able to see any translation updates partially as I do now. It seems like the problem is in some other area.

Let me try to finish translation first and produce *.mo files again. If that won’t help I’ll get back to you.

As per this threat. Please kindly keep it open, or if not possible – close it and I’ll open a new one if that won’t help either.

Thank you!

Karl

[Macarlos1]

This reply has been set as private.

[Macarlos1]

Hi,

I’ve followed your instructions and it seems like it helped a bit as there are more sentences which I was able to translate now, though – on the other hand – there are still some parts that are in English despite of these actions.

If you look on screenshot “1”, there are some phrases that actually changed after translation.

In screenshot “2” and “3” however, there are still these which I’m not able to translate even if I delete and recreate each .po .mo and .pot file in appropriate location (as suggested by yourself) and set permissions to 777. All of these sentences I’m referring to at the moment (cause there might be more in other places) which are *untouchable*, are located in bottom section of profile page on my website.

I’ve searched through all of plugin translations in loco translate, and the only place all of these sentences exist is sweetdate theme .po and .mo.

Any idea what might be wrong here?

Attachments:

You must be logged in to view attached files.

[Macarlos1]

This reply has been set as private.

[Macarlos1]

Hi k3m,

I’ve got a similar issue currently. My translations of Sweetdate theme are not appearing on the webpage. Could you let me know what have you done to solve your problem?

[Macarlos1]

This reply has been set as private.

[Macarlos1]

This reply has been set as private.

[Macarlos1]

This reply has been set as private.

[Macarlos1]

This reply has been set as private.

[Macarlos1]

This reply has been set as private.

[Macarlos1]

Hi Andrei,

Thanks for your answer. The issue is a bit more complicated (yet solvable in my opinion), as there is no common wording to satisfy the need of this search in current configuration. Unlike in English, the forms of words in Polish are changing under different circumstances as you’ve mentioned. If functionality of these two fields is not separated to provide different outcomes, then the entire experience will going to be a bit odd. Since this is the number one feature which is going to be used by all potential users, I cannot afford it to look unprofessionally I’m afraid.

The split should work as follows.

Field – “I am a:”, (Polish: “Jestem:”) – needs to allow to choose only:

Mężczyzną
Kobietą

And the other one – “I’m looking for a”, (Polish: “Szukam:”) – has to give the following as the outcome:

Mężczyzny
Kobiety

Thanks!
Karl

[Macarlos1]

Hi Radu,

Yes, thank you!

Karl

[Macarlos1]

Hello Again Team,

I’ve apparently managed to solve the problem for myself. There is one very helpful too available on below webpage.

http://jsonlint.com/?reformat=no

Thank you anyway.

[Author]

Posts