honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/common/locales/global/vi.js

93 lines
2.9 KiB
JavaScript
Raw Normal View History

build: generate global locale files (#33523) This commit contains the global locale files generated by the change to the CLDR `extract.js` tool, from the previous commit. PR Close #33523
2019-10-31 15:33:00 -04:00
/**
* @license
* Copyright Google Inc. All Rights Reserved.
*
* Use of this source code is governed by an MIT-style license that can be
* found in the LICENSE file at https://angular.io/license
*/
// THIS CODE IS GENERATED - DO NOT MODIFY
// See angular/tools/gulp-tasks/cldr/extract.js
(function(global) {
global.ng = global.ng || {};
global.ng.common = global.ng.common || {};
global.ng.common.locales = global.ng.common.locales || {};
fix(common): `locales/global/*.js` are not ES5 compliant (#36342) Although this code has been part of Angular 9.x I only noticed this error when upgrading to Angular 9.1.x because historically the source locale data was not injected when localizing, but as of angular/angular-cli#16394 (9.1.0) it is now included. This tipped me off that my other bundles were not being built properly, and this change allows me to build a valid ES5 bundle (I have also added a verification step to my build pipeline to alert me if this error appears again in any of my bundles). I found the `locales/global/*.js` file paths being referenced by the `I18nOptions` in @angular-devkit/build-angular/src/utils/i18n-options.ts, and following that it looks like it is actually loaded and used in @angular-devkit/build-angular/src/utils/process-bundle.ts. I saw the function `terserMangle` does appear that it is likely aware of the build being ES5, but I'm not sure why this is not producing a valid ES5 bundle. This change updates `tools/gulp-tasks/cldr/extract.js` to produce ES5 compliant `locales/global/*.js` and that fixes my issue. However, I am not sure if @angular-devkit/build-angular should be modified to produce a valid ES5 bundle instead or if the files could be TypeScript rather than JavaScript files. A test that a valid ES5 bundle is produced would be helpful, and I hope this is reproducible and not some issue with my config. PR Close #36342
2020-03-30 19:02:19 -04:00
var u = undefined;
build: generate global locale files (#33523) This commit contains the global locale files generated by the change to the CLDR `extract.js` tool, from the previous commit. PR Close #33523
2019-10-31 15:33:00 -04:00
function plural(n) { return 5; }
build(common): generate correct "global" locale files (#33662) PR Close #33662
2019-11-12 03:25:54 -05:00
global.ng.common.locales['vi'] = [
build: generate global locale files (#33523) This commit contains the global locale files generated by the change to the CLDR `extract.js` tool, from the previous commit. PR Close #33523
2019-10-31 15:33:00 -04:00
'vi',
[['s', 'c'], ['SA', 'CH'], u],
[['SA', 'CH'], u, u],
[
['CN', 'T2', 'T3', 'T4', 'T5', 'T6', 'T7'],
['CN', 'Th 2', 'Th 3', 'Th 4', 'Th 5', 'Th 6', 'Th 7'],
[
'Chủ Nhật', 'Thứ Hai', 'Thứ Ba', 'Thứ Tư', 'Thứ Năm', 'Thứ Sáu',
'Thứ Bảy'
],
['CN', 'T2', 'T3', 'T4', 'T5', 'T6', 'T7']
],
u,
[
['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12'],
[
'thg 1', 'thg 2', 'thg 3', 'thg 4', 'thg 5', 'thg 6', 'thg 7', 'thg 8', 'thg 9', 'thg 10',
'thg 11', 'thg 12'
],
[
'tháng 1', 'tháng 2', 'tháng 3', 'tháng 4', 'tháng 5', 'tháng 6', 'tháng 7',
'tháng 8', 'tháng 9', 'tháng 10', 'tháng 11', 'tháng 12'
]
],
[
['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12'],
[
'Thg 1', 'Thg 2', 'Thg 3', 'Thg 4', 'Thg 5', 'Thg 6', 'Thg 7', 'Thg 8', 'Thg 9', 'Thg 10',
'Thg 11', 'Thg 12'
],
[
'Tháng 1', 'Tháng 2', 'Tháng 3', 'Tháng 4', 'Tháng 5', 'Tháng 6', 'Tháng 7',
'Tháng 8', 'Tháng 9', 'Tháng 10', 'Tháng 11', 'Tháng 12'
]
],
[['tr. CN', 'sau CN'], ['Trước CN', 'sau CN'], u],
1,
[6, 0],
['dd/MM/y', 'd MMM, y', 'd MMMM, y', 'EEEE, d MMMM, y'],
['HH:mm', 'HH:mm:ss', 'HH:mm:ss z', 'HH:mm:ss zzzz'],
['{0}, {1}', u, '{0} {1}', u],
[',', '.', ';', '%', '+', '-', 'E', '×', '‰', '∞', 'NaN', ':'],
['#,##0.###', '#,##0%', '#,##0.00 ¤', '#E0'],
refactor: update locales with extracted currency codes (#32584) The locale data extraction has been modified to include the default currency code in the generated locale data. This commit updates these generated files accordingly. PR Close #32584
2019-12-14 05:39:42 -05:00
'VND',
build: generate global locale files (#33523) This commit contains the global locale files generated by the change to the CLDR `extract.js` tool, from the previous commit. PR Close #33523
2019-10-31 15:33:00 -04:00
'₫',
'Đồng Việt Nam',
{
'AUD': ['AU$', '$'],
'JPY': ['JP¥', '¥'],
'THB': ['฿'],
'TWD': ['NT$'],
fix(common): update CLDR generated files to 36.0.0 (#33584) PR Close #33584
2019-11-07 13:01:44 -05:00
'USD': ['US$', '$'],
'XXX': []
build: generate global locale files (#33523) This commit contains the global locale files generated by the change to the CLDR `extract.js` tool, from the previous commit. PR Close #33523
2019-10-31 15:33:00 -04:00
},
feat: update the locale files (#33556) PR Close #33556
2019-11-17 11:56:14 -05:00
'ltr',
build: generate global locale files (#33523) This commit contains the global locale files generated by the change to the CLDR `extract.js` tool, from the previous commit. PR Close #33523
2019-10-31 15:33:00 -04:00
plural,
[
[
['nửa đêm', 'tr', 'sáng', 'chiều', 'tối', 'đêm'],
['nửa đêm', 'TR', 'sáng', 'chiều', 'tối', 'đêm'], u
],
[
['nửa đêm', 'trưa', 'sáng', 'chiều', 'tối', 'đêm'],
['nửa đêm', 'TR', 'sáng', 'chiều', 'tối', 'đêm'],
['nửa đêm', 'trưa', 'sáng', 'chiều', 'tối', 'đêm']
],
[
'00:00', '12:00', ['04:00', '12:00'], ['12:00', '18:00'], ['18:00', '21:00'],
['21:00', '04:00']
]
]
];
})(typeof globalThis !== 'undefined' && globalThis || typeof global !== 'undefined' && global ||
typeof window !== 'undefined' && window);