CSV Format Issues
Fix CSV encoding, formatting, and column issues for successful translation.
CSV Requirements
WooTUI expects:
- Encoding: UTF-8 (not ANSI, ISO-8859-1, or Windows-1252)
- Delimiter: Comma
,(not semicolon;) - Line breaks: LF or CRLF (not CR only)
- WPML columns:
Meta: _wpml_import_source_language_code,Meta: _wpml_import_language_code,Meta: _wpml_import_translation_group
Encoding Issues
Garbled Characters (ñ, é, ü, etc.)
Problem: Special characters appear as ñ, é, or question marks
Cause: CSV not in UTF-8 encoding
Solution:
Google Sheets (Recommended):
- Upload CSV to Google Sheets
- File → Download → Comma-separated values (.csv)
- Google Sheets always exports UTF-8
LibreOffice Calc:
- Open CSV in LibreOffice Calc
- File → Save As
- File type: "Text CSV (.csv)"
- Character set: Unicode (UTF-8)
- Field delimiter:
,(comma) - Save
Windows Notepad:
- Open CSV in Notepad
- File → Save As
- Encoding: UTF-8
- Save
Microsoft Excel often breaks UTF-8 encoding. Use Google Sheets or LibreOffice instead!
Missing WPML Columns
"Missing required columns" Error
Problem: WooTUI needs WPML columns but they're not in CSV
Solution:
-
Verify WPML is installed:
- Go to WordPress → Plugins
- Check "WPML Multilingual CMS" and "WPML WooCommerce Multilingual" are active
-
Check WPML WooCommerce integration:
- WPML → WooCommerce Multilingual
- Ensure integration is enabled
-
Re-export with all columns:
- WooCommerce → Products → Export
- Select "All columns"
- Download CSV
- Open in text editor and verify columns starting with
Meta: _wpml_import_*are present
Attribute Column Issues
Attribute Names or Values Not Translating
Problem: Attributes appear incorrectly after translation
Causes & Solutions:
Inconsistent Formatting:
# Bad - mixed delimiters
Attribute 1 Value(s)
"Red, Blue; Green"
# Good - consistent commas
Attribute 1 Value(s)
"Red, Blue, Green"
Extra Spaces:
# Bad
"Red , Blue , Green"
# Good
"Red, Blue, Green"
Wrong Column Count:
- Each attribute needs 4 columns: Name, Value(s), Visible, Default
- Missing columns will cause errors
Empty vs NULL Values
How WooTUI Handles Empty Fields
Empty string (""):
- Column exists but has no value
- WooTUI preserves as empty in translation
NULL placeholder (NULL_columnName):
- WooTUI uses this internally to maintain CSV structure
- You shouldn't see these in output (if you do, it's a bug)
Empty fields in source CSV will remain empty in translated CSV. This is intentional—don't translate what doesn't exist!
Delimiter Issues
Semicolon Delimiters
Problem: CSV uses ; instead of ,
Solution:
- Open CSV in Google Sheets or LibreOffice
- Import with semicolon delimiter
- Export as CSV with comma delimiter
Quotes and Escaping
Broken Quotes in Descriptions
Problem: Product descriptions with quotes cause parsing errors
CSV Standard: Quotes inside quoted fields must be doubled
Example:
# Bad
Description
"This is a "premium" product"
# Good
Description
"This is a ""premium"" product"
Solution:
- Don't manually edit CSVs with complex quotes
- Let Google Sheets or LibreOffice handle escaping
- Or use a CSV validator tool
Validating Your CSV
Online Validators
- CSVLint - Check for formatting errors
- CSV Validator - Detailed validation
Manual Check
Open CSV in text editor (not Excel) and verify:
- First line has column headers
- Each row has same number of columns
- Special characters display correctly
- No random line breaks in middle of fields
Best Practices
1. Always Use UTF-8
Before translating:
- Export from WooCommerce
- Open in Google Sheets
- Re-export as CSV (ensures UTF-8)
2. Don't Edit in Excel
Excel breaks:
- UTF-8 encoding
- Leading zeros in SKUs
- Date formats
Use Google Sheets or LibreOffice Calc instead.
3. Keep Backups
Before any CSV editing:
products_original_2025-01-20.csv
products_edited_2025-01-20.csv
4. Test with Small Sample
Before translating 1000 products:
- Extract 5 rows to test CSV
- Translate test CSV
- Verify format is correct
- Then translate full catalog
Next Steps
- Common Errors - Other troubleshooting tips
- Exporting from WooCommerce - Export best practices