> These reports provide a clear view of the changes made by the reviewer, and can be useful to learn the style and terminology used in the project. > We also added a switch to generate HTML diff files that show word-oriented differences. It adds the command if it's not present, or updates it if the specified encoding is different from UTF-8. > Since we changed the output encoding to UTF-8, now the script checks if the `=encoding utf8` command (or an equivalent command for a different encoding) is present. > Shows source and target pods side-by-side to easily spot formatting differences > Gets all the pod files from the Perl distribution and adds them to the OmegaT project source folder > We added more functionality to the post-processing script (see below), new utilities, and renamed some scripts for consistency. > * Total documents: 167 (100 in core docs) > Status of our v5.16 track (currently v5.16.1): We only added four of them, since `perltoc.pod` is generated automagically from the source pods that are being translated. > The word count increased because we discovered 5 additional pod files that are generated automatically during setup (`perlapi`, `perlintern`, `perlmodlib`, `perltoc`, and `perluniprops`). > 4 : `perlvar.pod`, line 1337, bad filehandle `print_pods()` is used only to call `POD2::Base`'s `print_pods()` method. As for `print_pod()`, we covered the two possible call types for this method (class method and object method). To align the actual behavior of `POD2:Base` with the functionality described in this module's documentation we had to cover the case where this method is called as a class method and the case where it is called as an object method. To fix it, the offending characters (those with diacritic marks) were removed from the string returned by this method. As a result, it couldn't find the documentation section requested by the user when using `perldoc` with the `-f` switch. Since `perldoc` does not decode the text string returned by this method, it couldn't filter the `perlfunc.pod` introduction. ![]() > Code changes were implemented in `ES.pm` to fix some issues related to `POD2::Base`: In order to do so, we configured our translation tool (OmegaT) to generate utf-8-encoded output, and modified the post-processing script to check if the `=encoding utf8` command is present in the pod documents, and add it in case it is missing. > As mentioned in a previous report, v5.16.0 fixed the issues that prevented displaying correctly the extended characters in UTF-8 encoded files using `perldoc` in the console, so we have switched back to UTF-8. Translated files not included in the distribution were also updated to v5.16.1. It was a swift operation, since only one document changed (`perlhist.pod`). ![]() *Enrique Nell and Joaquin Ferrero reported:* Spanish Localization of the Perl Core Documentation - Grant Report #3
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |