Hello,
On 17/01/14 08:11, Andras Timar wrote:
Yes, I think we can allow localization/transliteration for all filter
names. It is up to the translators to keep the proper names. I trust
the community. :)
Here I touched only the once that are implemented in writerperfect
module. There is still
I know that I risk to become a piece of hamburger asking for this, but I
will try anyway :)
I would love to add for 4.2.1 a new feature (AbiWord import filter). The
only problem is that it would mean one new string AbiWord Document for
4.2.1. OTOH, there are already WordPerfect Document and many
Martin,
On 16/01/14 17:36, Martin Srebotnjak wrote:
I support inclusion of this new feature and there is no big issue since
there will be enough time to localize it for 4.2.1.
My question is: why not into 4.2.0? We have 3 day to translate and 1
string is not a nightmare.
You motivated me and
Hello,
On 16/01/14 21:46, Martin Srebotnjak wrote:
So I guess these filter strings will be localizable by 4.2.1, as a patch
to a bug that marks all these strings unlocalizable?
Ouch, I did not realize that thing since ages. The WordPerfect filter
for instance is there since 2004/2005 :)
Now
Andras,
On 16/01/14 21:18, Andras Timar wrote:
Content of value xml:lang=x-default tag is not extracted for
translation, you need to use xml:lang=en-US. Same applies to all of
your exotic filters. So actually you did not add a new string for
translation. But you may want to enable translation
Hi *,
for the upcoming new version 4.1.0, the RC1 builds now start to be
available on pre-releases. This build is slated to be first release
candidate build on the way towards 4.1.0, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#4.1_release
Hi *,
for the upcoming new version 4.0.4, the RC2 builds now start to be
available on pre-releases. This build is slated to be second release
candidate build on the way towards 4.0.4, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#4.0.4_release
Hi *,
for the upcoming new version 4.1.0, we today upload a second beta2
build that is feature-complete. For further milestones on the
way towards 4.1.0, please refer to our release plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#4.1_release
Builds are now being uploaded to a
Hi *,
for the upcoming new version 4.0.3, the RC2 builds now start to be
available on pre-releases. This build is slated to be second release
candidate build on the way towards 4.0.3, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#4.0.3_release
Hi *,
for the upcoming new version 4.0.3, the RC1 builds now start to be
available on pre-releases. This build is slated to be first release
candidate build on the way towards 4.0.3, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#4.0.3_release
Hi *,
for the upcoming new version 3.6.6, the RC2 builds now start to be
available on pre-releases. This build is slated to be second release
candidate build on the way towards 3.6.6, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#3.6_release
Hi *,
for the upcoming new version 4.0.2, the RC2 builds now start to be
available on pre-releases. This build is slated to be second release
candidate build on the way towards 4.0.2, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#4.0.2_release
Hi *,
for the upcoming new version 3.6.6, the RC1 builds now start to be
available on pre-releases. This build is slated to be first release
candidate build on the way towards 3.6.6, please refer to our release
plan timings here:
http://wiki.documentfoundation.org/ReleasePlan#3.6_release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi *,
for the upcoming new version 4.0.0, the RC3 builds now start to be
available on pre-releases. This build is slated to be third release
candidate build on the way towards 4.0.0, please refer to our release
plan timings here:
Hello, good people,
We had a problem with version numbes in the libreoffice-3.6.5.1 tag and
also there is one additional commit in the libreoffice-3-6-5 branch that
fixes a regression in 3.6.5rc1. Therefore we will tag today (rather
sooner then later) 3.6.5 rc2 from the libreoffice-3-6-5 branch.
Hi all,
there have been created the libreoffice-3-6-5 branch. It will be used
for fine tuning of the 3.6.5 release.
The following rules apply:
+ preferably just translation or blocker fixes
+ only cherry-picking from libreoffice-3-6 branch
+ 2 additional reviews needed;
Hi *,
for the upcoming new version 4.0.0, the first public ALPHA1 builds now
start to be available on pre-releases. This build is intended for alpha
and beta testers and will not be available on the mirrors or linked from
our web-site. As for the steps towards the 4.0.0 release, please refer
to
On 13/09/12 09:57, Fridrich Strba wrote:
candidate build on the way towards 3.6.1, please refer to our release
Naturally, towards 3.6.2 as you already for sure figured out. I am very
bad with numbers :)
F.
--
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems? http
18 matches
Mail list logo
