Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Translations update

2011-02-27
2012-10-17
1 2 > >> (Page 1 of 2)
  • Hi,
    as we are approaching the release of tmx 2.0.1, I'd like to ask all willing to
    update translations.
    Thanks !

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-02-28

    Matthieu and I are working on the French one. It'll be available soon.

    But I have a remark on it: in the last (SVN 1707M) version of TmX, messages of
    a (successful) compilation in the 'messages' window are much more verbose than
    in 2.0 version. Maybe it is preferable (in order to let the user know some
    things about the compilation process, for example location of the involved
    packages) but, IMHO, beginners were happy when the messages were just:

    Process started
    Process exited normally

    Anyway, about translation, though the opening message 'Process started: %1' is
    translated (its item is activated in Qt linguist), the closing one 'Process
    exited normally' isn't: its item is deactivated (in gray) in Qt linguist. It
    could be nice if the latter could be reactivated.

     
  • okay, i changed the behaviour so that the complete messages are only shown in
    the log tab, if the user changes to it during compile

     
  • I changed the message behaviour for these beginners because I have seen
    many forum posts saying nothing more than "My document doesn't compiles.
    What's wrong? This is the log: Process started Process exited with
    errors"....
    (it also was the easiest way to show the state of the preview compilation)

    okay, i changed the behaviour so that the complete messages are only
    shown in the log tab, if the user changes to it during compile

    Doesn't work here (starting compiling always automatically changes to
    the message tab)

     
  • i did not change the behaviour that it always switches to message viewer.
    Maybe that should be changed as well.
    Now you could switch to the log viewer during longer compiles to follow the
    messages

    another suggestion may be to change to log/error view automatically if errors
    occurred ?

     
  • Oh, you were talking about the displayed stdout messages, I thought you
    meant the display of the full called command.

    But your change was wrong, the stdout messages aren't shown in the log,
    so it makes no sense to print them if they are hidden.

    another suggestion may be to change to log/error view automatically if
    errors occurred ?

    It does that here

    And if you find a string like "xx" or "12" in the translation file,
    please don't translate it, but ask if it really is expected to be a
    translatable string. (the German translation would have triggered an
    assert)

     
  • but here again we closed the circle.
    There should not appear more messages than necessary (i.e. started process
    xyz, ended normally)

    For latex commands all kinds of "log" messages appear on stdout ... (which is
    not desired)

     
  • For latex commands all kinds of "log" messages appear on stdout ...
    (which is not desired)
    Well, some people want to see it. (e.g.
    http://www.golatex.de/texmakerx-t2196,start,105.html)

    Those who don't want it, can disable it by adding > /dev/null to the
    command line.

     
  • For latex commands all kinds of "log" messages appear on stdout ...
    (which is not desired)
    Well, some people want to see it. (e.g.
    http://www.golatex.de/texmakerx-t2196,start,105.html)

    Those who don't want it, can disable it by adding > /dev/null to the
    command line.

     
  • ehenriques
    ehenriques
    2011-03-05

    The string 'commentTodo' (highlight config) isn't enabled for translation.

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-05

    Those who don't want it, can disable it by adding > /dev/null to the command
    line.

    IMHO, it is too much difficult for beginners.

    And, if I'm right, the (nice) default behavior of TmX is that, in 'Messages'
    window, just 'Process started' and 'Process exited normally' messages are
    displayed only when no errors occur. In case of errors, they are automatically
    displayed in this window so I don't understand beginners who just say "My
    document doesn't compiles. What's wrong?"...

    Regards.

     
  • I added an option for it

    And, if I'm right, the (nice) default behavior of TmX is that, in 'Messages'
    window, just 'Process started' and 'Process exited normally' messages are
    displayed
    only when no errors occur.

    This only works if the called program declares it messages correctly

     
  • Any other important bugs left?

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-13

    French translation is almost done. Could you precise the meaning of the
    following source text:

    1. "something" , in the QApplication context (with "CodeSnippet" developer comment)

    2. "prio" in the QFormatConfig context: do you mean "priority"?

    3. "commentTodo" (in one "word"?) in the QFormatConfig context.

    About the new (and nice!) feature about master/slave files, if I'm right,
    parent file must be compiled at least once before one can start compilation
    just in the child file(s). IMHO, this should be explained in the documentation
    (and also the fact that this works with either \include-d or \input-ed child
    files). Anyway, it could be nice for parent/child files to appear differently
    when TmX has understood the relation between them (in order to let the user be
    sure he may start the compilation from the child file).

     
  • 2) is abbreviated "priority"
    3) you can make two words of it (it is the highlighting format for "%TODO ..."

    master/slave recognition should work without any preconditions. How exactly
    does it fail ?

     
    1. was wrong and should be in the CodeSnippet-context.
      It is the default value inserted in completed commands (e.g. in \url{})
    2. yes, the column is very small and it could look ugly if the word gets
      to long
     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-13

    2) is abbreviated "priority"

    OK.

    3) you can make two words of it (it is the highlighting format for "%TODO ..."
    

    OK.

    master/slave recognition should work without any preconditions. How exactly does it fail ?
    

    Steps:

    1. Menu File -> New from Template... (Article (French))
    2. Between \begin{document} and \end{document}, insert:

    \include{child}

    1. Save as parent.tex
    2. Menu File -> New and insert:

    foo

    1. Save as child.tex
    2. Press F6 (in child.tex)

    Two errors occur:

    1. ligne 1: Missing \begin{document}. f
      ligne 0: Emergency stop

    (BTW, should this "f" character be here?)

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-13

    BTW,

    I suggest that TmX defines default shortcuts for "Comment" and "Uncomment"
    commands (numerous beginners asked for this and, as they were beginners I
    didn't want to bother them with shortcuts configuration). Ctrl-T and Ctrl-U
    are available.

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-13

    Another points:

    1. In "LaTeX" menu, there is a "Tabular environment" submenu. But, in 6 tabular related entries, only 2 concern environments and 4 concern commands. So maybe another submenu title should be considered.

    2. May I take the liberty to add translations after some entries, for instance part, chapter, section, subsection, etc. or tiny, scriptsize, etc.?

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-14

    One more point :)

    LaTeX provides 2 "huge" font sizes: "Huge" and "huge" but, if I'm right, the
    latter is missing in TmX.

    Regards.

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-14

    1. May I take the liberty to add translations after some entries, for instance part, chapter, section, subsection, etc. or tiny, scriptsize, etc.?

    In fact, this is impossible because it leads to too much large drop-down lists
    "part" and "tiny" in the GUI. Sigh...

     
  • (BTW, should this "f" character be here?)

    This should just be copied from the LaTeX log; if it wants a f there...

    1. In "LaTeX" menu, there is a "Tabular environment" submenu. But, in
      6 tabular related entries, only 2 concern environments and 4 concern
      commands.

    It's only called "tables" in the German translation

    LaTeX provides 2 "huge" font sizes: "Huge" and "huge" but, if I'm
    right, the latter is missing in TmX.
    I suggest that TmX defines default shortcuts for "Comment" and
    "Uncomment" commands (numerous beginners asked for this and, as they
    were beginners I didn't want to bother them with shortcuts
    configuration). Ctrl-T and Ctrl-U are available.

    okay.

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-14

    Hi,

    all the points I let you know (in this thread) seem to be okay now:
    congratulations and many thanks!

    One extra point is rather strange: despite they are translated in the
    texmakerx_fr.ts file (since a long time), and despite the release of this file
    and the compilation of TmX (via sudo sh BUILD.sh), "Inline math mode $...$"
    and "Display math mode \" items aren't translated in the GUI (menu "Maths"). I
    didn't notice any problem with the other source texts. Could you please check
    if this problem arise for you (BTW, what's the better way to send you the
    texmakerx_fr.ts file?).

    Regards.

     
  • could you attach the file to this list ?

     
  • Denis Bitouzé
    Denis Bitouzé
    2011-03-14

    could you attach the file to this list ?

    Well,

    through the list, responding leads to '"SourceForge.net"
    noreply@sourceforge.net' which isn't a valid address I guess and, through
    the SourceForge forum (BTW, much less efficient than a traditional mailing
    list), I couldn't see any way to attach files...

     
1 2 > >> (Page 1 of 2)