PageNofM problem
-
- Posts: 29
- Joined: Thu Jul 07, 2016 2:06 pm
PageNofM problem
PageNOfM is not localizing after upgrade from 2016.1 to 2016.2
Some machines are rendering without word "Página" (page in portuguese) and is rendering only "1 de 40" for example.
Some other machines are rendering without localizing, and is rendering "Page 1 of 40" for example.
The web server is the same for all machines and is configured correct for pt-BR.
The viewer is set for pt-BR also. Previous version 2016.1 works fine.
Some machines are rendering without word "Página" (page in portuguese) and is rendering only "1 de 40" for example.
Some other machines are rendering without localizing, and is rendering "Page 1 of 40" for example.
The web server is the same for all machines and is configured correct for pt-BR.
The viewer is set for pt-BR also. Previous version 2016.1 works fine.
-
- Posts: 29
- Joined: Thu Jul 07, 2016 2:06 pm
Re: PageNofM problem
I uninstalled 2016.2 and reinstall 2016.1 version 2016.1.20.0 and PageNOfM works ok. The problem is with version 2016.2.
Re: PageNofM problem
Hello.
We have made an improvement.
The improvement will be available in our next official release only.
You could manually edit the localization file to fix the issue. Please, find the PageNOfM there.
Thank you.
We have made an improvement.
The improvement will be available in our next official release only.
You could manually edit the localization file to fix the issue. Please, find the PageNOfM there.
Thank you.
-
- Posts: 29
- Joined: Thu Jul 07, 2016 2:06 pm
Re: PageNofM problem
I am already using a pt-BR.xml file.
The problem is that when I upgrade to 2016.2, the file is not being considered anymore.
I use the tag GlobalizationFile at viewer markup.
The problem is that when I upgrade to 2016.2, the file is not being considered anymore.
I use the tag GlobalizationFile at viewer markup.
Re: PageNofM problem
Hello.
Then you should change the PageNOfM in your localization file.
Please, find all PageNOfM in the localization file and check its value.
Thank you.
Then you should change the PageNOfM in your localization file.
Please, find all PageNOfM in the localization file and check its value.
Thank you.
-
- Posts: 29
- Joined: Thu Jul 07, 2016 2:06 pm
Re: PageNofM problem
Look, localization works fine with version 2016.1.20.
The file pt-BR.xml is the same and I verified all tags and translate all of them.
The file pt-BR.xml is the same and I verified all tags and translate all of them.
Re: PageNofM problem
Hello.
So, you have solved your issue, right?
Let us know if you need our help.
Thank you.
So, you have solved your issue, right?
Let us know if you need our help.
Thank you.
-
- Posts: 29
- Joined: Thu Jul 07, 2016 2:06 pm
Re: PageNofM problem
Hi,
Actually this problem is driving me crazy. Now sometimes works, sometimes not, with the same report.
I open report and is in English, then I close and open again, it´s in Portuguese!!!
The xml is correct, IIS globalization too. And is occurring with version 2016.1.20 too.
To workaround the problem I changed PageNofM and I am using the following expression: Página {PageNumber} de {TotalPageCount}
Actually this problem is driving me crazy. Now sometimes works, sometimes not, with the same report.
I open report and is in English, then I close and open again, it´s in Portuguese!!!
The xml is correct, IIS globalization too. And is occurring with version 2016.1.20 too.
To workaround the problem I changed PageNofM and I am using the following expression: Página {PageNumber} de {TotalPageCount}
Re: PageNofM problem
Hello.
The localization of the PageNofM is in the two different sections of the localization file.
Please, find the both and check them.
Thank you.
The localization of the PageNofM is in the two different sections of the localization file.
Please, find the both and check them.
Thank you.