New english constants for translation

bradymiller wrote on Saturday, May 23, 2009:

hey,
Just set up these new english constants in the translaion spreadsheet. This is a sorted list to help the translators find these new constants. Please post any responses in below forum:
https://sourceforge.net/forum/forum.php?thread_id=3279061&forum_id=202506

LIST OF NEW ENGLISH CONSTANTS:
A unique value to identify this field, not visible to the user
Abortion-Related Categories
Add new note
Additional history notes
Additional Notes
Addr Bk
Addr Book
Alcohol consumption
Allow Email
Allow Mail Message
Allow SMS
Allow Voice Message
Append to this note
Appt-Enc
Armenian
Asian
Asthma
Auth/notes
Billing Code for Requested Service
Billing codes
Black
Blank Forms
Breast Disease
Caffeine consumption
Calendar View
Cash Rec
Caucasian
Chart Activity
Chart Trk
Charts Out
Check All
checkbox list
checkbox w/ text
Chinese
Choices
City Name
Client Profile - New Clients
Client Profile - Unique Clients
Collections
Complications by Service Provider
constants
Contact Lenses
Contraceptive Complication (specify)
Contraceptives Start
Counseling activities
Coupon
Current
Current Consultation
Current Patient
Custom
Date contraceptive services initially provided
Date of referral
Date of reply
Depression
Destroyed
Direct Mail
Distribution
Divorced
Document/Imaging Store
Domestic Partner
Dutch
Edit Allergies
Effectiveness
Emergency Phone
Employee
Employer Name
English
Ethnicity or Race
Exam and test results
Exam results
Exams/Tests
External ID
External Referral
External referral?
Fax/Scan
Fibroids
File Room
Final Diagnosis
Final diagnosis by specialist
Findings
Findings by specialist
French
Front Rec
Gall Bladder Condition
Games/Events Missed
German
grams
Heart Disease
Hebrew
High
HIPAA Notice Received
Hispanic
Homeless or similar?
Homeless, etc.
Hypertension
Immunize
Include Vitals
Include vitals data?
Incomplete Abortion Treatment
Indigents
Induced Abortion
Infertility
Injury Surveillance
Interpreter needed?
Inventory
Language:
Leave Message With
Level of urgency
License/ID
List
list box
list box w/ add
Low
Married
Medical Abortion
Medium
mg/2cc
mg/3cc
mg/4cc
Migrant or seasonal worker?
Mobile Phone
Name/Value
New Allergy
New Consultation
New Enctr
New Pt
New Visit
New/Search
Newspaper
Norwegian
Ofc Notes
Organizations
Other (specify)
Other/Generic Abortion-Related
Patient allergies
Patient Printed Report
Pharmacy
PID (Pelvic Inflammatory Disease)
Pmt Method
Post-Abortion Care
Post-Abortion Counseling
Postal Code
Pre-Abortion Consultation
Preferred Language
Prescriptions and/or referrals by specialist
Prescriptions/Referrals
Presumed Diagnosis
Presumed diagnosis by specialist
Previous Consultations
Previous History/Screening
Price Level
Print this note
Problems/Issues
Providers
Providers NPI
Pt Notes
Pt Notes/Auth
Pt Report
Radio
Reason for referral
Recommendations
Recommendations by specialist
Refer By
Referral Card
Referral Date
Referral To
Referrer Diagnosis
reg_re
Reply From
Requested Service
Risk Factors
Risk Level
Russian
Rx
Sales
Search or Add Patient
Secondary Insurance Provider
Separated
Service provided by specialist
Services Provided
Severe Migraine
Sickle Cell
Single
Slovak
Spanish
Squads
SRH Referrals
Standard
Start Date at This Clinic
State/Locality
Stats
Stength and Conditioning
Street and Number
Swedish
T.V.
Team Injury Overview
Team Roster View
Tertiary Insurance provider
text-date
textarea
textbox
textbox list
The label that appears to the user on the form
The translated label that will appear on the form in current language
The translated Title that will appear in current language
The translation of description in current language
Thrombosis/Stroke
Tobacco use
Transact
Transactions/Referrals
Translation
Unique SP
Upcoming Appointments
User Defined
Varicose Veins
View Allergies
Walk-In
Warning: A visit was already created for this patient today!
Warning: Patient ID is not unique!
Where may related scanned or paper documents be found?
Who
Who replied?
Widowed
$
(More)

blankev wrote on Sunday, May 24, 2009:

Brady,

you added new constants and this changed the old sort order (key_sort_field), used to implement consistency with the definitions.

We have to make a "be carefull note" for those of us that use CSV/TEXT file for import.

Both lang_constants AND lang_definitions HAVE TO BE IMPORTED as one interrelated entity. You have to import both constants and definitions of the same development/translation spot.

Do you change this in your/ main-translation manual or should all Translators do this in the Language manuals?

I encountered many doubles or at least constants that seem to be doubles. RX and Rx and most probably Constants with an space at the end or some other oddity that make them special for translation…

I wonder how thing work out for the list an lay-out tables if users start to include their own expansions of the lists… delete and replace…You included all text from the used list and LAYOUT. But what happens if you delete a LABEL and change the text with a different meaning? Example: City is translated into "stad" but what if I change City into Barrio in the Layout or List and this has to be translated as "buurt" … I have to chack this and let you know as soon as I have real time answers from Demo version.

Pimm

bradymiller wrote on Sunday, May 24, 2009:

hey,

  So we don’t drive people insane by needing to scroll through above list, put your responses in the language translation forum:
https://sourceforge.net/forum/forum.php?thread_id=3279061&forum_id=202506

  Your correct. The three tables (languages, constants, definitions) come as a set.  At some point when complete, can think about how to allow customization yet still get benefit of upgrading to the official translations. Using the current tables in previous openemr versions is experimental, and I’m actually shying away from recommending using these tables in previous versions of openemr.  I’m a bit worried because of encoding inconsistencies in previous openemr versions(can cause problems with the special non-english characters if want to upgrade database to 100% UTF8 in future). Still working on a safe method to use them in previous versions.

  The lists/layout translation stuff is a bit awkward, but I think required if we really want to say we support internationalization.  For example, I can’t imagine considering OpenEMR fully internationalized if a chinese person had to deal with english demographics and history stuff out of the box. Then were forcing users to in effect create/translate their demographics, history forms, and lists before being useful (Imagine if we asked our windows users to do this -> Joe would likely have a few things to say about that…); a formidable task.

  In your scenario, if you changed City into Barrio in the layout or list menu it would be translated to buurt if there was a defintion for Barrio in the language tables; otherwise you’d just get Barrio.  Of course, you could always just put buurt in there.

  The one nice thing about the layout/lists translations is that we’ll be able to say one of OpenEMR’s features is support for multi-lingual clinics; that should add another 1 or 2 users to the base…

-brady