translation-base-seed-sync

Run the sync-i18n-base-seed.ps1 PowerShell script from the repository root. It scans UI, BLL, and SERVICIOS code for Form, Dialog, and Error keys, updates translation-seeds/base.es.json, and regenerates the auto-generated block in script_bd.sql.

Add the key in your UI or service code using a Form..., Dialog..., or Error... prefix, then run the sync script. New keys appear in base.es.json with the key itself as a placeholder value, which you then replace with the real Spanish text.

No, the block between the BEGIN and END AUTO-GENERATED I18N BASE SEED markers must not be edited by hand. All changes flow from base.es.json through the sync script, which is the only supported way to regenerate that block.

sqlcmd ODBC 15.x stops processing silently with exit code 0 when it reaches the !! line, leaving the database without translations. Run the script from SSMS 19/22 in SQLCMD Mode or via setup-database.ps1, which strips the !! line from a temporary copy.

The file translation-seeds/base.es.json is the single source of truth for the base Spanish language. The SQL script only references it via OPENROWSET, and all key types including Dialog, Error, Warning, Confirm, Success, and Grid keys belong in that JSON file.