Thanks to ${webdev_link} for hosting ${lily_site}.' => '', + '
Thanks to ${webdev_link} for hosting ${lily_site}.' => 'Grazie a ${webdev_link} per l\'hosting di ${lily_site}.', }; $LY_LANGUAGES->{'ja'} = { @@ -1094,6 +1094,25 @@ sub lilypond_css_lines ($$) $Texi2HTML::THISDOC{'CSS_LINES'} .= "\n"; } } + + ## This section makes the manual name visible to CSS through the body tag + ## so that styles can be applied per manual. It will add the manual + ## directory name (e.g., 'notation' or 'learning') as a CSS class, as well + ## as a development status. + + # Parse the input file name to determine the manual we're dealing with. + my ($docu_dir, $docu_name) = split_texi_filename ($Texi2HTML::THISDOC{'input_file_name'}); + + # Hard-coded value to indicate if this is a development version + # ('devStatus') or stable version ('stableStatus') + # TODO: Figure out how to automatically set this value based on the even/odd minor revision number or some other mechanism. + $documentstatus = 'devStatus'; + + # Create the extra information for the
tag. + # For example, the development Notation reference in English + # will output in HTML as + $Texi2HTML::Config::BODYTEXT = 'lang="' . $Texi2HTML::THISDOC{current_lang} . '" class="' . $docu_name . ' ' . $documentstatus . '"'; + } @@ -1512,7 +1531,7 @@ sub generate_ly_toc_entries($$$$$) 'introduction' => [2, 2, 2, 2, 3, 3, 4, 4], 'download' => [2, 2, 2, 3, 3, 4], 'manuals' => [1, 1, 1, 2, 2, 2, 3, 3, 3, 3, 3, 4, 4, 4], - 'community' => [1, 1, 1, 2, 2, 2, 2, 3, 3, 3, 4], + 'community' => [1, 1, 1, 2, 2, 2, 2, 3, 3, 3, 4, 4], ); my $addColor = "colorDefault"; while (($top_section, $color_indices) = each %color_maps) { @@ -1682,7 +1701,7 @@ sub lilypond_print_toc_div ($$) print $fh '