Hello! My task is to mark the texts in the following files: private.py, roster.py and subscribe.py I've had problems marking texts in these files. The biggest question for me is that in my files there are messages to the syslog, like this LogStdErr("error", "private") Must I mark these texts like the other translatable text? And the other problem is connected with the form.has.key("something"), something=UserOptions or Digest or Membership Management, etc. The problem here is that the "something string" must be marked and then translated in other files. So I think I should mark it, but in the other way, it is a variable (it tells something to form.has.key), and we must not change any variable. Opinion, suggestion? Szilard Vizi ------------- mailto:vizisz@freemail.hu UIN:10676592
Vizi Szilard wrote:
Hello!
My task is to mark the texts in the following files: private.py, roster.py and subscribe.py
Uf! I did a mistake sending this message to other person telling: "Please, stop marking your files. I have done it yet. I want to give patches to Barry tonight. Cheers" Sorry by this mistake :-(
I've had problems marking texts in these files. The biggest question for me is that in my files there are messages to the syslog, like this LogStdErr("error", "private") Must I mark these texts like the other translatable text?
I don not mark strings intented to Mailing list manager.
And the other problem is connected with the form.has.key("something"), something=UserOptions or Digest or Membership Management, etc. The problem here is that the "something string" must be marked and then translated in other files. So I think I should mark it, but in the other way, it is a variable (it tells something to form.has.key), and we must not change any variable.
"something" should not be marked. BTW: I have discovered a bug in template patches. I told to insert i18n stuff inside them. Well, in listinfo <MM-Subscribe-Form-Start> must be under i18n stuff, like: <MM-lang-form-start><MM-displang-box> <MM-list-langs> <MM-form-end> <MM-Subscribe-Form-Start> Cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------# # Solo se que cada vez se menos :-| # #----------------------------------------------#
On Thu, 30 Nov 2000, Vizi Szilard wrote:
Hello!
My task is to mark the texts in the following files: private.py, roster.py and subscribe.py
I've had problems marking texts in these files. The biggest question for me is that in my files there are messages to the syslog, like this LogStdErr("error", "private")
You should only be marking user visible error messages. Text for critical/fatal error messages is best left untranslated. When people send in bug reports about these sort of problems, we want the developer to be able to understand them. If these types of error messages are in a language the developer can't understand, then they are much less useful.
Must I mark these texts like the other translatable text?
And the other problem is connected with the form.has.key("something"), something=UserOptions or Digest or Membership Management, etc. The problem here is that the "something string" must be marked and then translated in other files.
It should only be marked where it needs to be translated for display to the user. If the actual string is set somewhere else, then we might need something similar to the gettext_noop() dummy function/macro used in C.
So I think I should mark it, but in the other way, it is a variable (it tells something to form.has.key), and we must not change any variable.
James.
participants (3)
-
James Henstridge -
Juan Carlos Rey Anaya -
Vizi Szilard