CLDR-17566 converting translation general p2

docs/site/TEMP-TEXT-FILES/miscellaneous-person-name-formats.txt

@@ -8,5 +8,4 @@ Starting out
 Name Order For Locales
 AuxiliaryItems
 Sample Name Fields For X
-Name Patterns
-Person Names Guide
+Name Patterns

docs/site/TEMP-TEXT-FILES/time-zones-and-city-names.txt

@@ -16,6 +16,27 @@ Summer (daylight) time, such as "Atlantic Daylight Time"
 Generic time, such as "Atlantic Time". This is used for recurring times (such as in a Calendar program) that change between summer and winter.
 Time Zone Patterns
 The following special patterns are used in formatting timezones.
+Name	English Pattern	English_Example	Meaning	
+gmtFormat	GMT{0}
+or
+GMT{ HOURS_FROM_GMT }	GMT -2:00	GMT Pattern. Modify this field if the format for GMT time uses different letters, such as HUA+0200 for GMT+02:00 , or if the letters GMT occur after the time. Make sure you include the {0} ; that is where the actual time value will go!	
+gmtZeroFormat	GMT	GMT	GMT Zero Pattern. This field must be consistent with the GMT Pattern.	
+hourFormat	+HH:mm;-HH:mm	GMT -02:00	GMT Hours Pattern. This field controls the format for the time used with the GMT Pattern. It contains two patterns separated by a ";". The first controls positive time values (and zero), and the second controls the negative values. So to get GMT+02.00 for positive values, and GMT-02.00 for negative values, you'd use +HH.mm;-HH.mm.	
+regionFormat	{0} Time
+or
+{ COUNTRY } Time / { CITY } Time	Bolivia Time	Location-Based Time Zone Pattern. For generic references to time zones, the country is used if possible, composed with a pattern that in English appears as "{0} Time ". Thus a time zone may appear as "Malaysia Time " or " Hora de Malasia". If the country has multiple time zones, then a city is used to distinguish which one, thus "Argentina (La Rioja) Time ".
+Some languages would normally have grammatical adjustments depending on what the name of the city is. For example, one might need "12:43 pm Tempo d' Australia" but "12:43 pm Tempo de Paris". In that case, there are two approaches:
+1. Use "{0}", which will give results like "12:43 pm Australia" and "12:43 pm Paris", or
+2. Use a "form-style" phrasing such as " Tempo de: {0}", which will give results like "12:43 pm Tempo de: Australia" and "12:43 pm Tempo de: Paris".	
+regionFormat-standard	{0} Standard Time
+or
+{ COUNTRY } Standard Time / { CITY } Standard Time	Bolivia Standard Time		
+regionFormat-daylight	{0} Daylight Time
+or
+{ COUNTRY } Daylight Time / { CITY } Daylight Time	Bolivia Daylight Time		
+fallbackFormat	{1} ({0})
+or
+{ METAZONE_NAME } ({ CITY })	Central Time ( Cancun )	Metazone Name with Location Pattern. This field is usually not translated. This field to control the formatting of ambiguous metazone name name. When a set of metazone's generic names are shared by multiple different zones and GMT offset at the given time in a zone is different from other zones using the same metazone, this format pattern is used to distinguish the zone from others. In the pattern, {0} will be replaced by location name (either country or city) and {1} will be replaced with the metazone's name.	
 City Names
 Please choose the most neutral grammatical form of the city name. The city name will typically be used to indicate a timezone, either in a menu, or in formatting a time.
 In a few cases, what is included in the list of cities for translation is actually a country name, such as the following. In those cases, use the name of the country instead.

docs/site/TEMP-TEXT-FILES/transforms.txt

@@ -1,7 +1,25 @@
 Transforms
 Transforms describe ways of converting text. Most often these are transliterations, converting one script to another, such as:
+Source	Transliteration
+キャンパス	kyanpasu
+Αλφαβητικός Κατάλογος	Alphabētikós Katálogos
+биологический	biologicheskij
 For those, the name of the language or script is used.
 There are a few others that have special purposes, listed below. Note that whatever translation is used, it should be short (a few words at most).
 For the specialized acronyms (marked with *):
 If your language uses Latin letters, you probably want to leave this alone unless there is a well-known name in your language.
-For non-Latin, you should transcribe this into your alphabet, and if the name is not commonly understood, add the English in parentheses, such as "XXX (BGN)" or  "XXX (UNGEGN)".
+For non-Latin, you should transcribe this into your alphabet, and if the name is not commonly understood, add the English in parentheses, such as "XXX (BGN)" or "XXX (UNGEGN)".
+Code	Description
+BGN*	Transliterations according to the US BGN.
+UNGEGN*	Transliterations according to the UN Group of Experts on Geographical Names.
+Numeric	Numeric conversions.
+Tone	Linguistic tone such as used in Chinese.
+Accents	Accents, such as in ö or é.
+Publishing	Forms of characters more appropriate for publishing. Examples:
+‘ or ’ or …
+rather than generic ASCII characters like:
+' or ... (three periods).
+Jamo	The name for the units of the Korean alphabet.
+Pinyin	The name for the standard romanization (transliteration into Latin letters) for the Chinese language.
+Fullwidth	Full-width or "wide" characters, such as Ａ and ォ
+Halfwidth	Half-width or "narrow" characters, such as A and ｫ

docs/site/translation/time-zones-and-city-names.md

@@ -71,6 +71,7 @@ Timezones may also have a simpler format, depending on the language, such as:
 The city name may also be used in formatted times, such as:
 
 - 12:51 AM France Time (Paris)
+
 **Unique Names**
 
 City names must be unique. See [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names) for techniques.