- We have a style repository that is used for building a wide range of product manuals, all of them in CHM and PDF.
- This repository contains some styles with names in Brazilian Portuguese, mainly because these styles are used by several colleagues and we wanted to make them easy to recognize and apply. Therefore, a style used for a historical table, for example, is named as "Tabela de Histórico", which is "Historical Table" in Portuguese.
- When building these manuals to CHM, we deselected the Export Style Names option on Configuration - Publishing Options - Microsoft HTML Help - HTML Export Options, so that these names are transformed into CSS-compatible names, we believed, because this option works fine with CHM files.
- When we started to test the HTML format, the same Export Style Names option is used for this output, but now on Configuration - Publishing Options - Webhelp - HTML Export Options. When opening the corresponding HTML files, the style of that table is actually renamed to "TabeladeHistórico", which is not a valid CSS name, thus the table does not show any style.
- We don't know why CHMs display that table correctly, because the style is renamed to "TabeladeHistórico" as well, but that apparently does not affect the resulting file. We know CHM is an old unsupported format, but as far as we know, it uses Windows web browser engine to render pages and that problem should be visible there.
- We thought this Export Style Names option worked similar to the way topic IDs are created, that is, only valid characters are accepted.
- If we change the name of the style on the repository, will all projects using it automatically get that new name or we must open all projects and change all those references to the new name?