parate the
> different contexts, to be able to give a different translation for the
> different contexts.
po4a does a pretty good job at showing the "context". I seem to remember that
it gives the texi "code" as context. As far as I can tell from my conversion of
the Emacs manuals, that's generally sufficient.
But if Texinfo as a format could add comments *for* the translators and such
comments could be picked by converters, that would be great.
--
Jean-Christophe Helary @brandelune
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
g-cellspacing-valign-and-align-in-html5-tables
So yes. Removing it would not be a bad thing.
--
Jean-Christophe Helary @brandelune
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
. This would lead to
>
>
>
>
> span.t => font-family: monospace;
>
> Does it looks ok?
Yes.
--
Jean-Christophe Helary @brandelune
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
> On Jan 17, 2022, at 1:24, Gavin Smith wrote:
>
> On Fri, Jan 14, 2022 at 11:16:09AM +0900, Jean-Christophe Helary wrote:
>> Would it be possible to have the Texinfo manual available as a PO file as
>> the UI files are ?
>>
>> https://translationproject
rs to provide a POT file:
https://translationproject.org/html/maintainers.html
The po4a utility allows for texi files handling in the PO format:
https://po4a.org
It's just one command away to generate a POT file fo the manual.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot
> On Jan 12, 2022, at 22:50, Patrice Dumas wrote:
>
> Hello,
>
> Currently in HTML the information that an @command is a @small variant
> is completly lost. Shouldn't the small variant be added in the classes
> together with the normal variant?
Please do so.
> On Jan 6, 2022, at 20:56, Eli Zaretskii wrote:
>
>> From: Jean-Christophe Helary
>> Date: Thu, 6 Jan 2022 18:31:44 +0900
>> Cc: Werner LEMBERG ,
>> bug-texinfo@gnu.org
>>
>>>> I'd love to have a recommendation not to use tags that add
> On Jan 6, 2022, at 18:12, Eli Zaretskii wrote:
>
>> From: Jean-Christophe Helary
>> Date: Thu, 6 Jan 2022 17:27:18 +0900
>> Cc: bug-texinfo@gnu.org
>>
>> I'd love to have a recommendation not to use tags that add arbitrary English
>> string
ish
strings :-)
Unless there is a working (easy to use and well documented) mechanism to
localize said strings.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
f which CSS was needed and only outputing the CSS block after the rest
> of the file has been generated:
Since the CSS block appears in all the files, wouldn't it be better to output
it in an individual CSS file and link to that file from the HTML, like
--css-ref does ?
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
> On Dec 27, 2021, at 9:14, Patrice Dumas wrote:
>
> On Mon, Dec 27, 2021 at 08:38:37AM +0900, Jean-Christophe Helary wrote:
>>
>>
>>> is the "anchor" tag which can represent either
>>> the source or destination of a link (maybe confusing te
for using this way. I don't feel strongly either way whether
> or is better but your argument against seems valid.
The accepted way to specify a target is just to use "id" in any element. It
seems to me that adding an "invisible" just to set a location before the
element that is the location is adding unnecessary cruft to the html output.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
now we can have a target on the "Electron" id that affects the
whole H4 and not an empty span that's probably only used for navigation
purposes.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
> On Dec 22, 2021, at 16:19, Jean-Christophe Helary
> wrote:
>
>
>
>> On Dec 22, 2021, at 4:00, Gavin Smith wrote:
>>
>> On Tue, Oct 19, 2021 at 08:30:59PM +0900, Jean-Christophe Helary wrote:
>>>>> When running "make docs" to pro
> On Dec 22, 2021, at 4:00, Gavin Smith wrote:
>
> On Tue, Oct 19, 2021 at 08:30:59PM +0900, Jean-Christophe Helary wrote:
>>>> When running "make docs" to produce the emacs manuals HTML sets with the
>>>> following options:
>>>>
>&
sefont, big, center, dir, font, frame, frameset, isindex, noframes, strike, tt
W3C Working Group publishes "HTML5 differences from HTML 4",[120] which
provides a complete outline of additions, removals and changes between HTML 5
and HTML 4.
Also https://www.w3.org/TR/ht
nd correctly) trying to have exported
documents validate properly in general, but to have some kind of internal
validation now while he develops the new output.
Once that is acquired, and we can declare that texinfo output is whatever form
of HTML that's been chosen here I fail to see why using "html" is wrong or
problematic.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
> On Dec 19, 2021, at 11:01, Jacob Bachmeyer wrote:
>
> Gavin Smith wrote:
>> On Fri, Dec 17, 2021 at 09:08:24AM +0900, Jean-Christophe Helary wrote:
>>
>>> Is there a place *now* where HTML4 is a requirement ? HTML5 is the only
>>> *current* standa
s
> preferable for "web applications", such as a Web-based JavaScript Info
> reader. XHTML 1.1 is required for epub standards conformance.
Is there a place *now* where HTML4 is a requirement ? HTML5 is the only
*current* standard and does not specifically target web applicatio
> On Nov 28, 2021, at 20:15, Gavin Smith wrote:
>
> On Wed, Nov 24, 2021 at 08:59:30AM +0900, Jean-Christophe Helary wrote:
>> Good morning everybody,
>>
>> I’ll be making a shot presentation about translating the Emacs manuals in
>> OmegaT next Saturda
ttps://emacsconf.org/2021/talks/omegat/
It will be in broken English, with English/French/Japanese captions :-)
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
ToC just ToC.html so that it never
>> conflicts with any concept index file?
>
> For HTTP, index.html is a special name that is the file returned if
> no filename component was present in the URL.
You're right. So that the other index that needs to be named in a different
fashion.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
at it never
conflicts with any concept index file?
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
> On Oct 19, 2021, at 8:41, Jean-Christophe Helary
> wrote:
> For the layout itself and the overall text width, @media directives are a
> nice addition. They allow the menu to be turned into a column instead of
> being a broken line as it would be today, etc. I wrote someth
> On Oct 19, 2021, at 9:22, Gavin Smith wrote:
>
> On Tue, Oct 19, 2021 at 08:12:28AM +0900, Jean-Christophe Helary wrote:
>> Also, with translators trying to work on texinfo documents, it is actually a
>> problem to have such strings pop-up in sentences. And it is not
olumn instead of being a
broken line as it would be today, etc. I wrote something in the past. It worked
pretty well but I must have broken it at one point...
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
, in particular."
Also, with translators trying to work on texinfo documents, it is actually a
problem to have such strings pop-up in sentences. And it is not practical to
have catalogs of translations of "see" that include the translation in the
proper position (for ex. in Japa
; setting and eventually a "@media"
directive in the css to handle.
for ex:
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
weird customizations. Moreover, I've been seeing the
> same or related problems in other phones over the years too.
>
> Best regards,
> Carlos
> phone.jpeg>
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
Sorry I had missed that mail.
> On Jan 24, 2020, at 19:47, Gavin Smith wrote:
>
> On Fri, Jan 24, 2020 at 12:44:59AM +0900, Jean-Christophe Helary wrote:
>> To make sure that the output HTML has the proper anchors for use as CSS
>> selectors, it would be nice to distingu
> On Jan 24, 2020, at 19:42, Gavin Smith wrote:
>
> It makes it much easier if you do not send patches in a zip file: just
> sent the patches as attachments.
Apologies for that. I won't do that next time.
Jean-Christophe Helary
---
The (seemingly) French string used in the Small Caps description is not
grammatically correct.
If that was not intended, here is a patch.
<>
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
atters is that there is a final decision by the maintainer so that the
new version can be declared "most probably bug free" :)
Jean-Christophe
> On Jan 3, 2020, at 4:03, Gavin Smith wrote:
>
> On Thu, Dec 26, 2019 at 10:17:28PM +0900, Jean-Christophe Helary wrote:
>> I w
g but some others are clearly errors.
Thank you for your work.
<>
Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune
35 matches
Mail list logo
