On Mon, Nov 13, 2017, at 07:47 AM, José Fournier wrote:
> I am trying to tune a tool to convert docbookXML strings into asciidoc
> strings in zanata (see
> https://pagure.io/fork/jaaf64/docbookXML2asciidoc). At the moment I can
> easily convert strings using this method but I always stumble where the
> source string contains this particular sequence:
> I cannot figure out what this stands for.
This is a method of causing text formatting (bold, underline, etc.) to
show up when it is wrapped in an HTML span for further rendering.
I have figured out how to eliminate this bit of ugly, but it is not
something I can fully apply today. I don't want to make sweeping format
changes the day before GA.
Instead, please ignore this from an translation perspective and I hope
it will disappear soon.
PS: Tracking ticket here:
> Could somebody tell me what it is and show me a few example of how it
> renders in the final doc?
> Thanks in advance
> trans mailing list -- trans(a)lists.fedoraproject.org
> To unsubscribe send an email to trans-leave(a)lists.fedoraproject.org
Dear language teams,
because Fedora release is next week, you'll probably go check how well
our websites are translated :)
This is a good practice! Go translate! (in fact, go often, because in
the last days, there always is a lot of tiny fixes).
But you'll also find a "Fedora Budget Site", which is a first test from
Brian for asciidoc website.
After discussing this with him, you should most probably not translate
this at the moment, as is it a work in progress thing that won't be
published anytime soon (and isn't up to date).
@docs and @websites, Brian asked me to add you in CC for info. This
makes this message a multi mailing one, please only respond to
I don't remember when this project was added to the official list, I
suggest to temporary remove it.
We also had Fedora Cubes, when was it removed? Any reason for this?
Have a nice day,
Hi docs friends, can I tell you a little bit about myself, and join your
I'm an IT professional (currently employed by Red Hat) and help my
customers evaluate and adopt open-source technologies including GNU/Linux,
virtualization, storage, and automation. I consider myself moderately
skilled and have achieved certifications in Cisco networking, VMware
virtualization, and Red Hat systems administration. I'm live near Salt
Lake City, Utah, United States (Mountain timezone.) Right now I'd like to
start by improving the accuracy of various wiki pages, authoring new pages,
and bringing older pages up to date.
Thanks for your consideration,
$ gpg2 --fingerprint 2222306C
pub rsa2048 2017-11-03 [SC]
B2F0 3B94 006C 8746 B9CB 7691 B512 ECBC 2222 306C
uid [ultimate] John Call <johnsimcall(a)gmail.com>
sub rsa2048 2017-11-03 [E]
Name: Porfirio Páiz
Location: Managua, Nicaragua
Student: System Engineering and Information Technologies.
About You: Hello. I started using Free Libre and OpenSource Software
in 2011, Fedora 15 was my very first Linux distribution and since then
I have being using it as my main operating system in all my boxes. I
have contributed to the local Fedora Community in Nicaragua since 2013
mostly on Installs Fest or giving some basic technical support to new
comers on the local mailing list.
You and the Fedora Project: Recently I got interested in the process
of writing technical documentation and all the tools used on it. So
for this matter I decided to
learn about contributing to the official Fedora Documentation Team.
Later I will try to
join other teams of interest like Fedora Packaging Team and the Fedora
I'm really interested on the work in process related with `Turning
Legacy Docs into User-Story-Based Content` and the migration of
old/legacy documentation to the new AsciiDoc.
These two post motivated me to contribute to the documentation team:
Also I noticed the lack of easy to get started documentation for
non-techie people on the Fedora Atomic Project, I want to learn more
about this, how to get started with it and so I hope to contribute
writing docs in the new `User-Story-Based Content` way for this.
See you in the next Fedora doc meeting.
GPG Key ID: 2ABCCCE2
GPG Key fingerprint: BED1 B648 79C7 3661 BAE4 7718 BC7A 671C 2ABC CCE2
Polite as usual,
Now that we are on the new asciidoc/asciibinder system I was thinking
about the release notes RPM and the fact that the it was generated by
publican. Last I check the RPM is still a blocker for releases, and as
it stands now, we don't have a way to make this with the new source
My personal preference would be to remove this as a requirement for
releases, but this needs to be discussed with a larger group of people
as I don't think we can just say this is not longer a release criteria.
I am not sure who we need to talk with (FESCo? RelEng?), but before we
talk to them we need to have a discussion about it here and figure out
what the docs team would like to see done so that we are talking with