Context Navigation

Changes between Initial Version and Version 1 of Ticket #3876, comment 27

initial	v1
7	7	The new system creates complexities which may be ok for Core development, but many plugin and theme developers looking to use the new system will struggle to prepare their sources. I know this, because I'm already beginning to hear from them.
8	8
9		Ensuring file references match production code will cause some people problems. (e.g. `src/library/component.js` won't match `dist/prod.js`). I know this has been considered because WP handles `.min.js`, but there are many common practices that won't produce that result~~. U~~sing command line tools to generate PHP files with `/* references: */` seems like unnecessary wrangling for simple cases.
	9	Ensuring file references match production code will cause some people problems. (e.g. `src/library/component.js` won't match `dist/prod.js`). I know this has been considered because WP handles `.min.js`, but there are many common practices that won't produce that result, and using command line tools to generate PHP files with `/* references: */` seems like unnecessary wrangling for simple cases.
10	10
11	11	I agree that following WordPress standards is a fair requirement for being GlotPress-compatible, and I support that. However, in this case I feel like the requirements are unnecessarily restrictive and error-prone.