I am doing a translation for portuguese Brazil, and I notice that many of the itens already translated, when I open to make a different text, it has a complete diferente text that was showing at the firs window of the tool. But the worst part is, every time I change the text at the Request a new password, I get an error, that blocks me from doing anything else, and the portugese window do not show any longer, at the translation tool and the site itself:
Parse error: parse error, unexpected T_STRING in /home/restricted/home/xxxyyy/public_html/phpGedView/languages/lang.pt-br.php on line 585
Now, to correct I have to upload a new/fresh php file. Does anyone knows how to solf this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you're using the Translator tools, you MUST permit full control at the ./languages folder, and you MUST also set full permissions on each file in that folder.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you check into the permissions, I think you'll find that you don't have them set correctly. PhpGedView itself needs to be able to read, write, modify, delete, create, etc. within that directory.
These would be the same permissions that you set on the ./index and ./media folders.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I had not set permission, I would not be able to access the tool, right? So, if I am able to access and do some translation, the permission are set correctly. So, again, permission are not the problem. The worst problem is when I modify the text already translated "Request a new password". After I chance this, the tool is blocked, the portuguese are not shown anymore, and the access to admin is also blocked. The only solution is to replace the lang.pt-br.php file, and making me lose all that I have translated. So, again, if this is a case of permission, please tell me exactly what kind and how to set this permission, because it must be different then I have set (777). Or I'll just wait for a new build of the program.
Thansk,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ricardo:
Please e-mail me a copy of the already-translated Portuguese language file and also the Portuguese text that you indend to use in place of the "Request a new password" message.
I would like to try this on my system. It's possible that the Portuguese language file you're working on has an internal data structure error.
I can see that this is very frustrating for you, but I'm certain this problem can be resolved.
You are quite correct about permissions: that can't possibly be the problem. However, I'd just like to remind you that until now you have not clearly described what's happening.
Please send the e-mail and attachment to
g dot kroll at keldine dot ca
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, 777 is the correct permission set. But since I had to replace the file with a fresh one, all the work was lost, so, I stop translating, because the problem keeps happening. So, again, permissions are not the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Translator Tool requires a large (much more than usual) amount of memory. You must be sure to run PGV with at least 32 Mb memory allowed. You set this on the Configuration page that you access from the Admin menu.
Did you know that PGV's translation tool makes a backup copy of the language file you're working on?
This backup copy is created at the start of the translation session. If you're working on the Facts file, which is called 'facts.pt-br.php', the corresponding backup file is called 'facts.pt-br.php.old'. An existing backup copy is replaced by the new one.
The key to your lost work is to frequently (every 30 minutes or so) exit from the Translator Tool and then start it up again. This effectively saves the work you did up to that point. To recover your work, you delete the file you were working on and rename the '...old' file accordingly.
The 'Close Window without Reloading' button allows you to work much more quickly, but you should use the regular 'Close Window' button from time to time. This button is what records your changes into the language file. The 'Close Window without Reloading' button saves your changes in memory (NOT to the file you're working on).
Be sure to NOT use the 'Close Window without Reloading' button (use the regular 'Close Window button instead) when you wish to exit from the Translator Tool.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ricardo:
It seems that my description of the backup process is incorrect.
The backup file is created when you open a text for translation. If you click 'Save', your changes are saved to the main file immediately. They are copied to the backup file when the next text is opened.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ricardo:
I've encountered the 'lost work' problem too, but the '....old' file was OK.
In my case, the problem happend when I used Crimson Editor to make the same change to a whole lot of language variables. I was working on the German text and wanted to change 'E-Mail' to 'Mail', which has become the commonly used term for 'e-mail' in German.
Immediately after that, I started the language edit tool and proceeded to work away. After a while, I got a fatal error message about not being able to write to the language file. Prior to that, I noticed that a lot of the work had disappeared and the file size had become about 64 Kb, where previously it was around 192 Kb.
I determined that the problem WAS file permissions. The file I was working on no longer had the required full permissions, and had been set to read-only. I believe this was caused by Crimson Editor. In fact, when I checked the file's permissions, I was informed by Linux that I couldn't change the permissions - the file was still in use.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I dont know what to say, every time I check the permissions, they are the same 777.
This Crimson Editor, is the one form the phpGedView? If it isn't, I do not use it, I only used the one form admin.
As per the old file, well, when the problem occured, I replace the lang file, so all was lost. Now, I have not yet started to work on the translation, because I am affraid to lose all the work again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am doing a translation for portuguese Brazil, and I notice that many of the itens already translated, when I open to make a different text, it has a complete diferente text that was showing at the firs window of the tool. But the worst part is, every time I change the text at the Request a new password, I get an error, that blocks me from doing anything else, and the portugese window do not show any longer, at the translation tool and the site itself:
Parse error: parse error, unexpected T_STRING in /home/restricted/home/xxxyyy/public_html/phpGedView/languages/lang.pt-br.php on line 585
Now, to correct I have to upload a new/fresh php file. Does anyone knows how to solf this?
BTW, the version is V4.2 beta
If you're using the Translator tools, you MUST permit full control at the ./languages folder, and you MUST also set full permissions on each file in that folder.
Permissions are not the problem. They have been given, otherwise, I would not be able to have acess to it.
Ricardo,
You can access the folder with just read and execute permissions (555), but you need to include write permissions (777) to actually change anything.
So, any other possible ideias to correct the problem? Besides permissions?
If you check into the permissions, I think you'll find that you don't have them set correctly. PhpGedView itself needs to be able to read, write, modify, delete, create, etc. within that directory.
These would be the same permissions that you set on the ./index and ./media folders.
If I had not set permission, I would not be able to access the tool, right? So, if I am able to access and do some translation, the permission are set correctly. So, again, permission are not the problem. The worst problem is when I modify the text already translated "Request a new password". After I chance this, the tool is blocked, the portuguese are not shown anymore, and the access to admin is also blocked. The only solution is to replace the lang.pt-br.php file, and making me lose all that I have translated. So, again, if this is a case of permission, please tell me exactly what kind and how to set this permission, because it must be different then I have set (777). Or I'll just wait for a new build of the program.
Thansk,
Ricardo:
Please e-mail me a copy of the already-translated Portuguese language file and also the Portuguese text that you indend to use in place of the "Request a new password" message.
I would like to try this on my system. It's possible that the Portuguese language file you're working on has an internal data structure error.
I can see that this is very frustrating for you, but I'm certain this problem can be resolved.
You are quite correct about permissions: that can't possibly be the problem. However, I'd just like to remind you that until now you have not clearly described what's happening.
Please send the e-mail and attachment to
g dot kroll at keldine dot ca
Yes, 777 is the correct permission set. But since I had to replace the file with a fresh one, all the work was lost, so, I stop translating, because the problem keeps happening. So, again, permissions are not the problem.
The Translator Tool requires a large (much more than usual) amount of memory. You must be sure to run PGV with at least 32 Mb memory allowed. You set this on the Configuration page that you access from the Admin menu.
Did you know that PGV's translation tool makes a backup copy of the language file you're working on?
This backup copy is created at the start of the translation session. If you're working on the Facts file, which is called 'facts.pt-br.php', the corresponding backup file is called 'facts.pt-br.php.old'. An existing backup copy is replaced by the new one.
The key to your lost work is to frequently (every 30 minutes or so) exit from the Translator Tool and then start it up again. This effectively saves the work you did up to that point. To recover your work, you delete the file you were working on and rename the '...old' file accordingly.
The 'Close Window without Reloading' button allows you to work much more quickly, but you should use the regular 'Close Window' button from time to time. This button is what records your changes into the language file. The 'Close Window without Reloading' button saves your changes in memory (NOT to the file you're working on).
Be sure to NOT use the 'Close Window without Reloading' button (use the regular 'Close Window button instead) when you wish to exit from the Translator Tool.
Ricardo:
It seems that my description of the backup process is incorrect.
The backup file is created when you open a text for translation. If you click 'Save', your changes are saved to the main file immediately. They are copied to the backup file when the next text is opened.
Ricardo:
I've encountered the 'lost work' problem too, but the '....old' file was OK.
In my case, the problem happend when I used Crimson Editor to make the same change to a whole lot of language variables. I was working on the German text and wanted to change 'E-Mail' to 'Mail', which has become the commonly used term for 'e-mail' in German.
Immediately after that, I started the language edit tool and proceeded to work away. After a while, I got a fatal error message about not being able to write to the language file. Prior to that, I noticed that a lot of the work had disappeared and the file size had become about 64 Kb, where previously it was around 192 Kb.
I determined that the problem WAS file permissions. The file I was working on no longer had the required full permissions, and had been set to read-only. I believe this was caused by Crimson Editor. In fact, when I checked the file's permissions, I was informed by Linux that I couldn't change the permissions - the file was still in use.
Well, I dont know what to say, every time I check the permissions, they are the same 777.
This Crimson Editor, is the one form the phpGedView? If it isn't, I do not use it, I only used the one form admin.
As per the old file, well, when the problem occured, I replace the lang file, so all was lost. Now, I have not yet started to work on the translation, because I am affraid to lose all the work again.