Re: PSPP-BUG: [bug #35882] Syntax examples in documentation should be marked as CODE.

[Eliana]

Dear John,

I do not believe that just marking syntax examples with CODE tags will
suffice.  It will help, but tokens and commands are sprinkled
throughout the discussion paragraphs in the manual and will need to be
marked with CODE tags as well.  You may well intend to do this as part
of the task, but I thought I would mention it as the discussion is
separate from the examples, as I understand it.

Eliana

On 3/18/12, John Darrington <address@hidden> wrote:
> URL:
>   <http://savannah.gnu.org/bugs/?35882>
>
>                  Summary: Syntax examples in documentation should be marked
> as
> CODE.
>                  Project: PSPP
>             Submitted by: jmd
>             Submitted on: Sun 18 Mar 2012 09:15:37 AM CET
>                 Category: Documentation
>                 Severity: 5 - Average
>                   Status: None
>              Assigned to: None
>              Open/Closed: Open
>          Discussion Lock: Any
>                  Release: None
>                   Effort: 0.00
>
>     _______________________________________________________
>
> Details:
>
>  Eliana <address@hidden> reports:
>
> Sorry, the web interface is too hard for me to use.
>
> Add html  CODE tags to html versions of the  manual.   Those are html tags
> that tell translation engines not to translate the text indicated.
>
> Without those tags, translation engines happily translate commands into the
> foreign language, totally disregarding their sanctity and rendering the
> translation very confusing and possibly erroneous in some cases
>
> Adding these tags is not a  trivial project, but
> requires no knowledge of any foreign language, and I believe would render
> the
> online manual a meaningful document for a larger portion of the
> international
> community without requiring  translating separate manuals for each language.
>
> But it will require proofing of the translated pages to spot any items that
> needed code tags which have not been generated - translation engines
> definitely also translate   abbreviations and special characters. and add
> unexpected punctuation marks inappropriately.
>
> Proofing is easier if someone knows the foreign language, but if you know
> the
> manual contents, you will see things that look wrong even if you do not know
> the foreign language.
>
>
>
>
>
>     _______________________________________________________
>
> Reply to this item at:
>
>   <http://savannah.gnu.org/bugs/?35882>
>
> _______________________________________________
>   Message sent via/by Savannah
>   http://savannah.gnu.org/
>
>