[Po4a-devel] [po4a-Bugs][313322] latex format can not recognize custom environments

Bugs item #313322, was changed at 31/08/2011 07:45 by David Prévot You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=31... Status: Open Priority: 3 Submitted By: Cristian Consonni (cristiancantoro-guest) Assigned to: Nobody (None) Summary: latex format can not recognize custom environments Category: None Group: None Resolution: None Initial Comment: I don't know if this is more a feature request than a bug report, anyway I was creating a po file with po4a-gettextize and got the following $ po4a-gettextize -f latex -m mbe1intro.tex -p olo.po mbe1intro.tex:101: (po4a::tex) ambiente «myVerbatim2» sconosciuto \begin{myVerbatim2} [...] this is the definition of the environment: \DefineVerbatimEnvironment% {myVerbatim2}% {Verbatim}% {fontfamily=courier,fontseries=b,frame=single,rulecolor=\color{blue}} The problem was resolved by commenting all the occurrences of the environment. Cristian p.s: the original tex file has been downloaded from: [1]http://www.csulb.edu/~woollett/mbe1intro.tex ---------------------------------------------------------------------- Date: 31/08/2011 17:10 Message: Hi, By the way I already had a few issues using inline comments, and better results declaring customization in an extra file. e.g.: $ po4a-gettextize -f latex -m mbe1intro.tex -p olo.po -o definitions="custom" where the custom files contains lines like: % po4a: environment myVerbatim2 Regards David ---------------------------------------------------------------------- Comment By: Nicolas FRANÇOIS (nekral-guest) Date: 31/08/2011 16:50 Message: Hello, This is intended to be supported. Did you try any of the TeX module options? (e.g. -o no_wrap="myVerbatim2") Or did you try to define the environment in the TeX file for po4a. For example: % po4a: environment myVerbatim2 or % po4a: verbatim environment myVerbatim2 (see man Locale::Po4a::TeX for more info) ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=31...