12 commits

Author	SHA1	Message	Date
Jonas Jenwald	ea55e8bf41	Update l10n files	2021-12-26 11:19:19 +01:00
Jonas Jenwald	822856e044	Update l10n files	2021-10-31 09:56:41 +01:00
Jonas Jenwald	32ad677f9c	Update l10n files	2021-09-19 09:43:15 +02:00
Jonas Jenwald	aad0316137	Update l10n files	2021-07-25 10:31:40 +02:00
Jonas Jenwald	d3ed3761bc	Update l10n files	2021-04-18 11:24:51 +02:00
Jonas Jenwald	6e2ae2264b	Remove the unused "loading_error_indicator" l10n string (PR 2719 follow-up) ... This l10n string has been completely unused ever since PR 2719, which is now *eight* years ago.	2021-02-12 13:12:37 +01:00
Jonas Jenwald	09442351b8	Update l10n files	2021-01-24 08:43:09 +01:00
Jonas Jenwald	54eeaba014	Update l10n files	2020-09-06 11:51:34 +02:00
Jonas Jenwald	ba8c5bde5f	Update l10n files	2020-08-23 10:10:38 +02:00
Jonas Jenwald	ed01158127	Update l10n files	2020-02-21 17:40:08 +01:00
Jonas Jenwald	b663cec383	[Firefox] Stop fetching the chrome.properties files during gulp importl10n (PR 9566 follow-up) ... With the removal of the (standalone) Firefox building code in PR 9566 (a year and a half ago), these files are now completely unused in the GitHub repository[1]. Hence it doesn't really seem necessary to keep fetching them with `gulp importl10n`, and the existing files in the `l10n` folder can also be removed (thanks to version control, they're easy enough to restore should the need ever arise). The patch also allows an additional simplification, for the `gulp locale` and `gulp mozcentral` commands, since it's now possible to stop writing `l10n` files to the `extensions/firefox/` folder and instead just copy them similar to other build targets. --- [1] They're obviously still used in `mozilla-central`, for fallback messages displayed through `PdfStreamConverter.jsm`, but that doesn't make it necessary to keep them *here* as far as I'm concerned.	2019-10-17 12:27:11 +02:00
Jonas Jenwald	8d74a9ae7f	Update l10n files	2019-10-06 18:12:29 +02:00