Translation of the author's name

ojs
Tags: #<Tag:0x00007f67178185a0>

#72

Thanks again, @bozana, this sounds encouraging :slight_smile:


#73

Dear @litvinovg

I am using the multi-language codes for about 2 months.It works very good. Today I have faced a problem which I don not what to do.
While using citation plug-in, name of the authors are not shown in non of two languages of the website. See image below:
image

Names are shown correctly in other parts. But not in the citation. Would please help. Thanks


#74

Dear @litvinovg

I am using multi-language codes too. There is a bug I do not know what to do. While adding a reviewer, the name of the reviewer is not shown. Not in English and not in the second language. Names are set in both languages for the users.


and in second language:


#75

Dear @Frosty,
It seems you haven’t applied citation plugin modifications. https://github.com/litvinovg/citationStyleLanguage/commit/49f006adf01a7d4315f424ce7e998d9a5d0cfdaa
It should work like that https://pj.iph.ras.ru/index.php/ph_j/article/view/944


#76

Dear @MJB,
It was a problem until https://github.com/litvinovg/pkp-lib/commit/4fd7e9ffcf4ff0ee054f8927c19c9b5efa708bf4
So I suggest you to get latest updates.


#77

Dear @litvinovg

Thanks for your prompt reply. I fixed new code but I have face new problem when I tried this. Article page is not loaded and a white page is shown.
This error is shown in error log:
PHP Fatal error: Uncaught exception 'Seboettg\CiteProc\Exception\CiteProcException' with message 'Illegal argument. Name has no family name.' in /home/journalo/public_html/jims/plugins/generic/citationStyleLanguage/lib/vendor/seboettg/citeproc-php/src/Seboettg/CiteProc/Util/NameHelper.php:115

It seems it is because if some author have no family name (admin was not have family name). I fixed that. I hope this kind of problem face not again.

Thanks for your help again


#78

Dear @litvinovg

Thanks for your prompt reply. That was very helpful.

Best Regards


#79

Dear @litvinovg

I have one more question. Would you please help again.

In the registration new user, in registrationForm.tpl file, for name field the always primary language name and family name is taken from new user:

<input class="form-control" name="firstName[{$primaryLocale|escape}]" id="firstName" value="{$firstName.$primaryLocale|escape}" maxlength="40" placeholder={translate key="user.FistNamePlaceHolder"} type="text">

I want to add another field and get second language name and family name. What code should I have add to this .tpl file.
Probably I have add some code to PKPUser.inc.php and PKPUserDAO.inc.php ?

Thank alot
Best Regards


#80

Dear @Frosty,
That should help you https://github.com/litvinovg/pkp-lib/commit/51d710d418d168aba0098b1f1856f8296dc6b76c


#81

Dear mr. Litvinov
Hello
Sorry for dilitant question,
these changes apply to registered authors or authors of articles?


#82

These changes for both registered users and authors of articles.


#83

Hi @bozana, @litvinovg,

Thank you SOOO much for all your efforts in making our dreams come true :smiley:

Now when the PRs seem to be merged we have two questions:

  1. We would like to test it, but so far we’ve been using setup packages. So would it be enough to just install OJS from the git repository to make this functionality available for testing purposes?
  2. The issue is closed, but hasn’t been scheduled for the OJS 3.2 release (as it seemed to be planned before). May we still hope? :slight_smile:

#84

Hi @Ph_We

Maybe I/we can create a package from the current muster branch for you to work with…
I assigned it to the OJS/OMP 3.2. These changes will surely go to 3.2 i.e. to the first release that will be made from the master branch, which should be 3.2.

Best,
Bozana


#85

Hi @bozana,

I think, it would be ideal if we could use such a package over, say, the OJS 3.1.1-1 (or OJS 3.1.1-2?). In this case we could test it on a clone with 19 different multilingual journals, which would be a good real-life environment for testing.


#86

Hi @Ph_We

Hmmm… I am not sure I understand :blush: What do you mean?

Thanks!
Bozana


#87

I thought by a package you meant a kind of a patch for the current release. But we would be happy with any package you could give us :crazy_face:


#88

@Ph_We, do you have a possibility and/or would you maybe rather try to use git? – just to check… :slight_smile:


#89

We tried it, but in our case that was equal to installing from git over the instance already installed from packages. And that led to some additional issues, we did not know how to deal with.

I hope to test this with all those 19 journals we already have running. That is why I was so glad when you told me you could make a package from the master branch :slight_smile:

Or would it be easier to fresh install it using git and then to move the journals there?


#90

Hi, @bozana, @litvinovg! Thank you very much for solving this problem tosome extend. I have implemented your changes in the OJS 3.1.0.1 but failed in OJS 3.1.1-2. Could you comfirm that your script can be incormarated in the latest version?


#91

Hi @Santa

The changes were made for the master branch i.e. for the coming OJS 3.2 version/release. Master and ojs-stable-3_1_1 branch differ, and from that time of the implementation till now even more, so there might be conflicts. Thus it might not be easily applied on 3.1.1-2.

Best,
Bozana