I created a new ôòøguix-patchesôòù mailing lists ~48h ago on Savannah.
I just created it by hand. Assaf is looking into the PHP<->Savannah
linkage/breakage. --best, karl.
Update of sr #108948 (project administration):
Open/Closed:Open => Closed
___
Follow-up Comment #1:
Hi Ludo - well, rms's confirmation doesn't seem to be in that thread, but I'll
take your
Is it sufficiently machine readable so that one could extract the
information automatically?
There have been various efforts over many years to make the Directory
machine-readable, in its many implementations. I do not know where they
stand today.
Out of the ~303 packages in ftp.gnu.
> It's unfortunate that the GNU project doesn't maintain certain metadata
> such as the license for each project.
To the best of my knowledge, the Directory is intended to have that
information (and plenty of other things too), although I don't doubt
that plenty of updates are needed. In
So, are we to change the source format of blurb items to HTML?
It seems ugly to me in principle, but if the consensus is that that is
the most useful approach, ok, I won't object (i.e., will install the
patch :). I don't have strong feelings about it.
karl
So, are we to change the source format of blurb items to HTML?
It seems ugly to me in principle, but if the consensus is that that is
the most useful approach, ok, I won't object (i.e., will install the
patch :). I don't have strong feelings about it.
karl
What would you prefer?
I prefer plain text, but I don't feel that strongly about it, as such.
about not introducing HTML markup in the translated text?
If the "translation" you're referring to is the home-pkgblurbs.html file
which the web translators work with, that is (obviously) specif
What would you prefer?
I prefer plain text, but I don't feel that strongly about it, as such.
about not introducing HTML markup in the translated text?
If the "translation" you're referring to is the home-pkgblurbs.html file
which the web translators work with, that is (obviously) specif
I thought you guys didn't want these hypothetical TP translators to see
HTML. If you do, fine, we can make the original be HTML, at least as
far as the internal text goes, which is the only concern here afaik.
Brandon and I wrote the blurbs in plain text simply because it seemed
natural; everythi
I thought you guys didn't want these hypothetical TP translators to see
HTML. If you do, fine, we can make the original be HTML, at least as
far as the internal text goes, which is the only concern here afaik.
Brandon and I wrote the blurbs in plain text simply because it seemed
natural; everythi
http://cvs.savannah.gnu.org/viewvc/*checkout*/gnumaint/pkgblurbs.txt
Looking at www/server, it seems there are currently some translations
of the blurbs for ru, fr, de, ja (just judging by file sizes).
I suggest the path of least resistance is to take these web translations
as the source for
make sure the copyright notice still shows up in Info,
HTML, and PS/PDF
It's always good to check, but like I said, that is exactly why I
invented @copying in the first place (back in 2002). I wrote about it
in the Texinfo manual.
I think it was not working for you (if indeed it wasn't)
I donôòùt know how to keep the @ifinfo trick
I see no need for @ifinfo. It has no effect inside @titlepage anyway,
since @titlepage ... @end titlepage is ignored for Info output.
nearly the same (more on that later) copyright notice
is repeated three times.
1) @copying should come
And yeah, there could be a single macro since the two always go
together.
Why is a macro needed at all?
(vs. just using text inside @copying).
ôòùd have to make
sure Guix can have .po files in the end
I believe that is what you'll get with GNUN (the web translators). What
I imagine is that you would be getting the .po from www instead of tp,
with no other difference in the process.
We'll have to talk with Ineiev about the det
What do you think about this change?
Sorry, I don't understand what problem you're trying to solve.
Why are you separating copyright text and license text?
Can you send me the whole file (beginning of it, anyway)?
The diff is hard to read.
As for the @itemize of names, I would suggest exp
Should the transltion be done in Womb?
I don't think that would be practical.
These descriptions (in HTML form) will end up on www.gnu.org. Therefore
the web translators (not the TP translators) will be translating them.
I believe po format is involved and thus could conceivably be used
wi
17 matches
Mail list logo
