Reviewing the translation template: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
No edit summary
 
(5 intermediate revisions by one other user not shown)
Line 11: Line 11:
! comment
! comment
|-
|-
| Mailing Code: = Zip Code?
| Mailing Code = Zip Code
| this is usually a reference to table p_mailing: http://openpetraorg.sourceforge.net/dbdoc/index.html?table=p_mailing&group=mailing. When a gift is received, and you know the donor has given because you have sent him a special letter, the mailing code which clearly identifies that letter, can be entered with the gift.
| this is usually a reference to table p_mailing: http://openpetraorg.sourceforge.net/dbdoc/index.html?table=p_mailing&group=mailing. When a gift is received, and you know the donor has given because you have sent him a special letter, the mailing code which clearly identifies that letter, can be entered with the gift.
|-
|-
Line 37: Line 37:
| (trailing 0 = --*)
| (trailing 0 = --*)
| this is about the lblPartnerKeyNonExactMatch on partner find.
| this is about the lblPartnerKeyNonExactMatch on partner find.
|-
| Text Preview / Text Output
| please add Text Output to not to be translated Text Preview is displayed for the tab of the text preview when looking at a report
|-
|-
| Select Zoom
| Select Zoom
Line 46: Line 43:
| Extract
| Extract
| Extracts are a list of partners. They are used as a result from a special filter. For example you can filter all partners that have given more then 50 euros in the past 6 months, and put all their partner keys and addresses into an extract, and send a mailing to all those people.
| Extracts are a list of partners. They are used as a result from a special filter. For example you can filter all partners that have given more then 50 euros in the past 6 months, and put all their partner keys and addresses into an extract, and send a mailing to all those people.
|-
| eg. "TEN,01","TEN,02"
| will not be translated
|-
|-
| Depth
| Depth
Line 60: Line 54:
|-
|-
| No gifts in year:
| No gifts in year:
| correct
| donors who didn't give gift during the year
|-
|-
| SYBUNT
| SYBUNT
Line 121: Line 115:
| PETRAServer is running and listening @ {0}:{1}
| PETRAServer is running and listening @ {0}:{1}
| Status message telling you that the Petraserver is listening on a certain IP Address and certain port. those two values will be inserted into the placeholders {0} and {1}
| Status message telling you that the Petraserver is listening on a certain IP Address and certain port. those two values will be inserted into the placeholders {0} and {1}
|-
| Exception occured during manual load of Client AppDomain: {0}
| will not be translated. This is quite an internal error, when there are huge problems with the server. they don't need translation.
|-
|-
| You do not have access to Partners of Partner Class 'ORGANISATION' that are 'Foundations'!
| You do not have access to Partners of Partner Class 'ORGANISATION' that are 'Foundations'!
Line 130: Line 121:




Fixed items(comments are already applied in the source code:
Fixed items(comments are already applied in the source code):
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
Line 141: Line 132:
| this.FDelegateGetPartnerShortName could not be called!
| this.FDelegateGetPartnerShortName could not be called!
| will not be translated. should probably be changed in csharp\ICT\Petra\Client\MPartner\Gui\UC_PartnerEdit_TopPart.ManualCode.cs to not call Catalog.GetString
| will not be translated. should probably be changed in csharp\ICT\Petra\Client\MPartner\Gui\UC_PartnerEdit_TopPart.ManualCode.cs to not call Catalog.GetString
|-
| Exception occured during manual load of Client AppDomain: {0}
| will not be translated. This is quite an internal error, when there are huge problems with the server. they don't need translation.
|-
| Text Preview / Text Output
| please add Text Output to not to be translated Text Preview is displayed for the tab of the text preview when looking at a report
|-
| eg. "TEN,01","TEN,02"
| will not be translated
|}
|}

Latest revision as of 07:19, 23 September 2015

The following table shows comments to some items that may be unclear for translators. Feel free to add items that are unclear for you and we'll add a comment to it later on.

If an entry doesn't need translation, please add "will not be translated" and wef'll add the entry later to \trunk\i18n\donottranslate.po

You can also do a full text search with Notepad++ on the *.cs files in csharp\ICT\Petra and see where the strings are used, that might give you a clue if it should be translated or not, and what the context is (if the source doesn't appear yet anyway in launchpad)

item comment
Mailing Code = Zip Code this is usually a reference to table p_mailing: http://openpetraorg.sourceforge.net/dbdoc/index.html?table=p_mailing&group=mailing. When a gift is received, and you know the donor has given because you have sent him a special letter, the mailing code which clearly identifies that letter, can be entered with the gift.
R.List Items this is on the PartnerFind_Options screen. you can sort items to the right or to the left side. That screen does not even open yet from the Partner Find screen, I have deactivated it for some reason, I think it was not completely working without Petra.
L.List Items see above.
Exact Partner &Key Match this is on the Partner Find screen
&Bulk Address Report this is for mass mailing, you want to get a bulk of addresses, ie. a huge number of addresses
Mails&ort Label Print Mailsort: this seems to be a UK thing: http://en.wikipedia.org/wiki/Mailsort
Todo something that still needs to be implemented/realized
Key Partner Data this is displayed on top of the partner edit screen, and is meant as a group heading for the most important data pieces of the partner, ie. Name, partner key, partner class, partner status, etc.
(trailing 0 = --*) this is about the lblPartnerKeyNonExactMatch on partner find.
Select Zoom This is also on the preview window for reports. it is a combobox for seleting "Fit to Window", "100%", "75%", "50%"
Extract Extracts are a list of partners. They are used as a result from a special filter. For example you can filter all partners that have given more then 50 euros in the past 6 months, and put all their partner keys and addresses into an extract, and send a mailing to all those people.
Depth This is often used on the screens where you define parameters for a report: do you want a default, or a summary, or a detail report. This is the depth of the report.
FD Income by Fund FD stands for financial development, ie. to get the numbers of past donations and to understand what the donors want and what they are interested in. The FD Income by Fund report shows how much money has come in for which fund, eg. how much money did we get for Finland, Sweden, or Turkey?
Lapsed Donor Report lapsed donors are donors who have previously given, but we have not received any donations anymore for a while. We have not completely lost them yet, but we might need to send them a letter to remind them that we are still here...
No gifts in year: donors who didn't give gift during the year
SYBUNT SYBUNT = Some Year But Unfortunately Not This Year.
'Gift given in year' must be less than 'No gifts in year' This is related to a validation error message: wrong year entered, the donor has first to have given in some year, and in the following year has stopped giving
Top Middle Bottom These are for radio buttons, for top donor, middle donor, bottom donor, for the TopDonorReport.
New Interest Category We have categories for grouping interests. so it is a new catgory that should be created.
New Partner Interest this is about the interest, that should be created for a partner. he is interested in ... cars.
Value One Direction: this is about the exchange rates. The value for GBP to USD is one direction, USD to GBP the other direction.
Charged Field Report this is about conferences, and participants are coming from several countries and fields. The fields are charged for the participants that they are sending, and the participants pay directly to the field, and the field forwards to money to the conference organisers. The conference organisers know what money to charge to each field, by this report.
Sign Off Lines: this is also for the field reports for a conference. Should we print a line for the signature, so it can be signed with a pen by the one responsible to pay
If charged field is not set: Same report parameter screen: what should we do if we don't know which field to charge because it is not set on the participant's record
Fellowship Groups The participants of a conference are organised into smaller groups during the conference, for talking in a more smaller setting
Discovery Groups similar to Fellowship groups. Probably this is conference specific. you might translate it with "small groups 2"
Find Conference / Conference Find May the second phrase be "conference found"? The conference find screen has the title "Conference Find". It would be better both are "Find Conference"
Old Field Key: this is for gift adjustments when the recipient has changed fields, ie. the money should not go to the previous, old field, but go to the current place where the recipient is working.
Parsing the hash value of the batch The hash value is a checksum of the amounts in the batch. usually just a sum of all amounts.
Use Ta&x Acct+CC This is on the Accounts Payable module. For an invoice that we have to pay. Should we use the tax account and cost centre for this invoice detail? there seems to be a hard coded combination of account and cost centre for taxes.
Misc Defaults Accounts Payable. Edit Supplier. Miscellaneous defaults: several defaults, that should be used on invoices from this supplier.
Form Letters form letters are the same thing as mail merge, for sending many letters with predefined context, sometimes with custom content per recipient. http://en.wikipedia.org/wiki/Mail_merge
FinDev {0} {1} This is used on the main screen, for the Financial Development task item. {0} and {1} will be filled with the number and the name of the ledger that the financial development module should be opened for.
SYBUNT Report Related to the same thing as above. About donors that have stopped giving. LYBUNT = Last Year But Unfortunately Not This Year; SYBUNT = Some Year But Unfortunately Not This Year.
PETRAServer is running and listening @ {0}:{1} Status message telling you that the Petraserver is listening on a certain IP Address and certain port. those two values will be inserted into the placeholders {0} and {1}
You do not have access to Partners of Partner Class 'ORGANISATION' that are 'Foundations'! some users won't have access to edit partners that are foundations. Foundations are a special type of organisation. They usually are important donors, and they should not be approached by any user in the office, but only by the person that has been assigned to do that job.


Fixed items(comments are already applied in the source code):

item comment
guages): This may be the last part of the following line? 'Speaks (Languages):' Speaks (Lan- Yes, that's true. The correct string would be: Speaks (Languages):
this.FDelegateGetPartnerShortName could not be called! will not be translated. should probably be changed in csharp\ICT\Petra\Client\MPartner\Gui\UC_PartnerEdit_TopPart.ManualCode.cs to not call Catalog.GetString
Exception occured during manual load of Client AppDomain: {0} will not be translated. This is quite an internal error, when there are huge problems with the server. they don't need translation.
Text Preview / Text Output please add Text Output to not to be translated Text Preview is displayed for the tab of the text preview when looking at a report
eg. "TEN,01","TEN,02" will not be translated