cộng hơn 1000 trang.
https://wiki.documentfoundation.org/Documentation/Publications
2012/03/30
Tài liệu LibreOffice 3.4
Tài liệu Writer, Impress, Calc, Math, Base, Draw của LibreOffice. Tổng
cộng hơn 1000 trang.
cộng hơn 1000 trang.
2012/03/28
Fwd: [HanoiLUG] Openoffice Write password protect
Không rõ có phần mềm nào recover được .odt password không nhỉ?
---------- Forwarded message ----------
From: Tri Nguyen Dinh
From: Tri Nguyen Dinh
Mình đang có 1 file làm ra từ Write trong openoffice chạy trên Ubuntu , file save dưới dạng .odt nhưng bị mất passwd ,cán bộ nào có cao kiến gì giúp mình 1 cái ,
I have one file with .odt extension . made from openoffice running on Ubuntu. The file have passwd protected but I forgot the paswd . Can you show me how can I remove the passwd to open my file.
2012/03/27
LibreOffice @ Google Summer of Code
Bạn sinh viên nào muốn chơi GSoC (Google Summer of Code) với LibreOffice thì liên hệ mình nhá.
http://blog.documentfoundation.org/2012/03/26/libreoffice-google-summer-of-code/
Năm trước đội LibreOffice do mình làm mentor ở Mùa Hè Sáng Tạo20 11 đạt giả 3
-> http://www.olp.vn/mhst/thong-tin
http://blog.documentfoundation.org/2012/03/26/libreoffice-google-summer-of-code/
Năm trước đội LibreOffice do mình làm mentor ở Mùa Hè Sáng Tạo20 11 đạt giả 3
-> http://www.olp.vn/mhst/thong-tin
---------- Forwarded message ----------
From: Italo Vignoli
Date: Tue, Mar 27, 2012 at 17:02
Subject: [tdf-announce] LibreOffice @ Google Summer of Code
To: TDF Announce <announce@documentfoundation.org>
So, it is here again! The wonderful time of spring. Projects that were
lucky enough to be selected by Google look for talented students. And
students that care enough about open source try to find a matching project.
LibreOffice was selected as a mentoring organization for Google Summer
of Code again this year. And today, it is the first day when students
can submit their applications.
Read the entire article on TDF blog: http://wp.me/p1byPE-gv
From: Italo Vignoli
Date: Tue, Mar 27, 2012 at 17:02
Subject: [tdf-announce] LibreOffice @ Google Summer of Code
To: TDF Announce <announce@documentfoundation.org>
So, it is here again! The wonderful time of spring. Projects that were
lucky enough to be selected by Google look for talented students. And
students that care enough about open source try to find a matching project.
LibreOffice was selected as a mentoring organization for Google Summer
of Code again this year. And today, it is the first day when students
can submit their applications.
Read the entire article on TDF blog: http://wp.me/p1byPE-gv
Dùng PDF. Đừng dùng .doc khi gửi file đính kèm.
Tất nhiên PDF tốt hơn nhiều so với .doc khi gửi file đính kèm
- An toàn hơn
- Nhìn sao in vậy (.doc xem khác trên viewer, editor khác nhau (ngay cả với MS Office khác phiên bản))
- Vẫn edit được .pdf khi cần với LibreOffice
- An toàn hơn
- Nhìn sao in vậy (.doc xem khác trên viewer, editor khác nhau (ngay cả với MS Office khác phiên bản))
- Vẫn edit được .pdf khi cần với LibreOffice
---------- Forwarded message ----------
From: Simon Phipps
Subject: [libreoffice-marketing] Editable PDFs
I think editable PDFs are one of the miracles of LibreOffice, and I found so few people know about them that I decided to write about them today on ComputerWorld:
http://blogs.computerworlduk.com/simon-says/2012/03/the-magic-of-editable-pdfs/index.htm
Feel free to pass on the link, or if you don't want to do that, the instructions in the (editable!) PDF at http://wmk.me/Hb9y3y
Improvements welcome - that file is on GitHub so send me a pull request :-)
Cheers,
S.
From: Simon Phipps
Subject: [libreoffice-marketing] Editable PDFs
I think editable PDFs are one of the miracles of LibreOffice, and I found so few people know about them that I decided to write about them today on ComputerWorld:
http://blogs.computerworlduk.com/simon-says/2012/03/the-magic-of-editable-pdfs/index.htm
Feel free to pass on the link, or if you don't want to do that, the instructions in the (editable!) PDF at http://wmk.me/Hb9y3y
Improvements welcome - that file is on GitHub so send me a pull request :-)
Cheers,
S.
2012/03/22
Từ điển Vietlex 2011
... có thêm từ Hán Việt chua bên cạnh.
Sent from my Android. Appologies for the brevity.
2012/03/08
Private Discussions: Don't do it
Chào các bác,
Em thấy nội dung khá hay, quan trọng trong xây dựng cộng đồng nên chia sẻ lại:
Không tạo các kênh trao đổi bí mật
"Making important decisions in private is like spraying contributor repellant on your project."
Xem: http://producingoss.com/en/setting-tone.html
"Avoid Private Discussions
Even after you've taken the project public, you and the other founders will often find yourselves wanting to settle difficult questions by private communications among an inner circle. This is especially true in the early days of the project, when there are so many important decisions to make, and, usually, few volunteers qualified to make them. All the obvious disadvantages of public list discussions will loom palpably in front of you: the delay inherent in email conversations, the need to leave sufficient time for consensus to form, the hassle of dealing with naive volunteers who think they understand all the issues but actually don't (every project has these; sometimes they're next year's star contributors, sometimes they stay naive forever), the person who can't understand why you only want to solve problem X when it's obviously a subset of larger problem Y, and so on. The temptation to make decisions behind closed doors and present them as faits accomplis, or at least as the firm recommendations of a united and influential voting block, will be great indeed.
Don't do it.
As slow and cumbersome as public discussions can be, they're almost always preferable in the long run. Making important decisions in private is like spraying contributor repellant on your project. No serious volunteer would stick around for long in an environment where a secret council makes all the big decisions. Furthermore, public discussion has beneficial side effects that will last beyond whatever ephemeral technical question was at issue:
The discussion will help train and educate new developers. You never know how many eyes are watching the conversation; even if most people don't participate, many may be tracking silently, gleaning information about the software.
The discussion will train you in the art of explaining technical issues to people who are not as familiar with the software as you are. This is a skill that requires practice, and you can't get that practice by talking to people who already know what you know.
The discussion and its conclusions will be available in public archives forever after, enabling future discussions to avoid retracing the same steps. See the section called "Conspicuous Use of Archives" in Chapter 6, Communications.
Finally, there is the possibility that someone on the list may make a real contribution to the conversation, by coming up with an idea you never anticipated. It's hard to say how likely this is; it just depends on the complexity of the code and degree of specialization required. But if anecdotal evidence may be permitted, I would hazard that this is more likely than one would intuitively expect. In the Subversion project, we (the founders) believed we faced a deep and complex set of problems, which we had been thinking about hard for several months, and we frankly doubted that anyone on the newly created mailing list was likely to make a real contribution to the discussion. So we took the lazy route and started batting some technical ideas back and forth in private emails, until an observer of the project[10] caught wind of what was happening and asked for the discussion to be moved to the public list. Rolling our eyes a bit, we did—and were stunned by the number of insightful comments and suggestions that quickly resulted. In many cases people offered ideas that had never even occurred to us. It turned out there were some very smart people on that list; they'd just been waiting for the right bait. It's true that the ensuing discussions took longer than they would have if we had kept the conversation private, but they were so much more productive that it was well worth the extra time.
Without descending into hand-waving generalizations like "the group is always smarter than the individual" (we've all met enough groups to know better), it must be acknowledged that there are certain activities at which groups excel. Massive peer review is one of them; generating large numbers of ideas quickly is another. The quality of the ideas depends on the quality of the thinking that went into them, of course, but you won't know what kinds of thinkers are out there until you stimulate them with a challenging problem.
Naturally, there are some discussions that must be had privately; throughout this book we'll see examples of those. But the guiding principle should always be: If there's no reason for it to be private, it should be public.
Making this happen requires action. It's not enough merely to ensure that all your own posts go to the public list. You also have to nudge other people's unnecessarily private conversations to the list too. If someone tries to start a private discussion, and there's no reason for it to be private, then it is incumbent on you to open the appropriate meta-discussion immediately. Don't even comment on the original topic until you've either successfully steered the conversation to a public place, or ascertained that privacy really was needed. If you do this consistently, people will catch on pretty quickly and start to use the public forums by default."
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus, twitter: vuhung, MSN: vuhung16.
http://www.facebook.com/nguyenvuhung
http://nguyen-vu-hung.blogspot.com/
Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/
Vietnamese LibreOffice: http://libo-vi.blogspot.com/
Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/
Em thấy nội dung khá hay, quan trọng trong xây dựng cộng đồng nên chia sẻ lại:
Không tạo các kênh trao đổi bí mật
"Making important decisions in private is like spraying contributor repellant on your project."
Xem: http://producingoss.com/en/setting-tone.html
"Avoid Private Discussions
Even after you've taken the project public, you and the other founders will often find yourselves wanting to settle difficult questions by private communications among an inner circle. This is especially true in the early days of the project, when there are so many important decisions to make, and, usually, few volunteers qualified to make them. All the obvious disadvantages of public list discussions will loom palpably in front of you: the delay inherent in email conversations, the need to leave sufficient time for consensus to form, the hassle of dealing with naive volunteers who think they understand all the issues but actually don't (every project has these; sometimes they're next year's star contributors, sometimes they stay naive forever), the person who can't understand why you only want to solve problem X when it's obviously a subset of larger problem Y, and so on. The temptation to make decisions behind closed doors and present them as faits accomplis, or at least as the firm recommendations of a united and influential voting block, will be great indeed.
Don't do it.
As slow and cumbersome as public discussions can be, they're almost always preferable in the long run. Making important decisions in private is like spraying contributor repellant on your project. No serious volunteer would stick around for long in an environment where a secret council makes all the big decisions. Furthermore, public discussion has beneficial side effects that will last beyond whatever ephemeral technical question was at issue:
The discussion will help train and educate new developers. You never know how many eyes are watching the conversation; even if most people don't participate, many may be tracking silently, gleaning information about the software.
The discussion will train you in the art of explaining technical issues to people who are not as familiar with the software as you are. This is a skill that requires practice, and you can't get that practice by talking to people who already know what you know.
The discussion and its conclusions will be available in public archives forever after, enabling future discussions to avoid retracing the same steps. See the section called "Conspicuous Use of Archives" in Chapter 6, Communications.
Finally, there is the possibility that someone on the list may make a real contribution to the conversation, by coming up with an idea you never anticipated. It's hard to say how likely this is; it just depends on the complexity of the code and degree of specialization required. But if anecdotal evidence may be permitted, I would hazard that this is more likely than one would intuitively expect. In the Subversion project, we (the founders) believed we faced a deep and complex set of problems, which we had been thinking about hard for several months, and we frankly doubted that anyone on the newly created mailing list was likely to make a real contribution to the discussion. So we took the lazy route and started batting some technical ideas back and forth in private emails, until an observer of the project[10] caught wind of what was happening and asked for the discussion to be moved to the public list. Rolling our eyes a bit, we did—and were stunned by the number of insightful comments and suggestions that quickly resulted. In many cases people offered ideas that had never even occurred to us. It turned out there were some very smart people on that list; they'd just been waiting for the right bait. It's true that the ensuing discussions took longer than they would have if we had kept the conversation private, but they were so much more productive that it was well worth the extra time.
Without descending into hand-waving generalizations like "the group is always smarter than the individual" (we've all met enough groups to know better), it must be acknowledged that there are certain activities at which groups excel. Massive peer review is one of them; generating large numbers of ideas quickly is another. The quality of the ideas depends on the quality of the thinking that went into them, of course, but you won't know what kinds of thinkers are out there until you stimulate them with a challenging problem.
Naturally, there are some discussions that must be had privately; throughout this book we'll see examples of those. But the guiding principle should always be: If there's no reason for it to be private, it should be public.
Making this happen requires action. It's not enough merely to ensure that all your own posts go to the public list. You also have to nudge other people's unnecessarily private conversations to the list too. If someone tries to start a private discussion, and there's no reason for it to be private, then it is incumbent on you to open the appropriate meta-discussion immediately. Don't even comment on the original topic until you've either successfully steered the conversation to a public place, or ascertained that privacy really was needed. If you do this consistently, people will catch on pretty quickly and start to use the public forums by default."
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus, twitter: vuhung, MSN: vuhung16.
http://www.facebook.com/nguyenvuhung
http://nguyen-vu-hung.blogspot.com/
Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/
Vietnamese LibreOffice: http://libo-vi.blogspot.com/
Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/
2012/03/07
Rethinking the IT field saves Danish's Ministry of Transport for 1 ½ million. annually
Đan Mạch dùng cloud mail thay thế Exchange, LibreOffice thay Microsoft Office, thin client (VMView để load Windows 7 từ VMWare server) và tiết kiệm $1.5M hàng năm.
Họ làm được, sao mình không làm được nhỉ?
---
At a time when most ministries dismiss employees in order to save money, solve the Ministry of Transport a large part of the economic challenges through innovation in the IT field. Magenta is an external supplier and consultant on the project, among other things, aims to extend the lifetime of the current PCs with 3 years. The agent is virtual desktops with Libre Office.
Họ làm được, sao mình không làm được nhỉ?
---
At a time when most ministries dismiss employees in order to save money, solve the Ministry of Transport a large part of the economic challenges through innovation in the IT field. Magenta is an external supplier and consultant on the project, among other things, aims to extend the lifetime of the current PCs with 3 years. The agent is virtual desktops with Libre Office.
From the home office employee can connect to its own virtual PC over the Internet via an SMS passcode option.
In the long term goal is for Outlook and Exchange replaced with a cloud-based email solution. It is awaiting a legal settlement.
Business case
The annual cost
Before: Exchange with the file server and webmail 277,000
Now: Cloud-mail (400 kr. / User / year) 60,000
Savings 217,000
Before: Operation of ERMS (KMD) 1200000
Currently: Operation of ERMS (TDC) 300 000
Savings 900,000
Before: Laptops 7,000 kr. / Machine x 50 machines / year 350,000
Now: Thin clients around. 1,500 kr. / Machine x 25 machines / year 37,500
Savings 312,500
Before: MS Office (SA) 1.500 kr. / User / year 225,000
Now: Libre Office 500 kr. / User / year 75,000
Savings 150,000
Total annual savings, ca. £ 1,580,000
Details
Ministry of Transport's PC configuration is based on virtual desktops, hosted on servers at an external supplier. The Ministry has chosen VMView from VMWare.
The primary applications on the virtual desktop are:
OS: Windows 7
Libre Office
Chrome browser
EDRMS system F2
In the decentralized desktop is installed dual boot. The primary boot sector that is Linux based, is merely designed to load VMView client and connect to the VMWare server to start the virtual desktop.
The secondary boot option consists of a standard Ubuntu Linux among others Libre Office, Firefox and Chrome. Ministry of Transport's ERMS system F2 requires Windows, which is why the choice of Windows as an operating system on the virtual desktop.
Ubuntu Linux is installed as a back-up for the virtual desktop, so users can work even in situations where the virtual desktop is down or inaccessible. If an employee is on the road, Ubuntu Linux is started and used, but from the home office staff has direct access to their own virtual desktop over the Internet. The virtual desktop can also be accessed from tablets, etc.
On the hardware side, the Transportation Ministry has chosen to retain the existing PCs that otherwise stood before replacement. The lifespan of PCs expected to be extended from three to six years. Eventually it is possible to replace PCs with thin clients.
Chinh phu Duc chinh thuc cong nhan LibreOffice
Chính phủ Đức chính thức công nhận The Documentation Foundation và LibreOffice.
Giờ đây, LibreOffice được bảo vệ bằng luật pháp ở Đức cũng như các
nước khác như Anh, Pháp.
Giờ đây, LibreOffice được bảo vệ bằng luật pháp ở Đức cũng như các
nước khác như Anh, Pháp.
Xem: https://joinup.ec.europa.eu/news/berlins-recognition-document-foundation-boost-libreoffice
The recognition by the state of Berlin of The Document Foundation will
be a boost to the use by public administrations of LibreOffice, a free
and open source suite of office productivity tools, expects Florian
Effenberger, chairman of the new foundation.
The Document Foundation was approved by the state of Berlin on 17
February. It was registered in Berlin by the community involved with
LibreOffice, previously organised as OpenOffice.org. The world-wide
group considered starting the foundation in either England, France or
Germany. The latter country's laws provide the best long-term
protection of the foundation's objectives, explains Effenberger. "The
law protects is so well, that the foundation cannot, for example, drop
its primary focus, free office software, or decide to make it a
for-profit organisation."
In Germany, creating a foundation involves a legal check by a state
administration, and the LibreOffice community sought advise in three
of the countries' sixteen states; Bavaria, Hesse and Berlin. The first
two had concerns with recognising a foundation with the unusual
requirements for a membership element: new members need to have
contributed to the development of LibreOffice for at least three
months, and commit to continue supporting it for at least six more
months. "We also started out with more than 140 members from all over
the world, and all three states thought that was unusual too."
After explaining the foundations' aims and rules to all three states,
the group settled in Berlin. "It was the most open to our approach."
Effenberger expects that over time, the presence of the foundation in
Berlin will make a difference for this state's use of this type of
software. "It will make more public administrators aware that they can
foster open standards and free and open source."
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype:
vuhung16plus, twitter: vuhung, MSN: vuhung16.
http://www.facebook.com/nguyenvuhung
http://nguyen-vu-hung.blogspot.com/
Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/
Vietnamese LibreOffice: http://libo-vi.blogspot.com/
Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/
2012/03/04
A few things about Microsoft core fonts
---------- Forwarded message ----------
From: Nguyễn Vũ Hưng
From: Nguyễn Vũ Hưng
Hi anh Thành,
2012/3/4 Nguyễn Hữu Thành <huuthanh.ng@gmail.com>:
> Trong MS Office dân ta thường để bộ chữ sẵn là TimeNewRomance còn
> trong Ubuntu thì không có bộ chữ ấy nếu không cài thêm gói
> ubuntu-restricted-extras?
Đúng thế anh ạ, nhưng cài ubuntu-restricted-extras[3] thì ngoài MS core fonts ra
còn nhiều thứ linh tinh cũng vào theo nữa.
Cái font mình cần là đây:
ttf-mscorefonts-installer
> Nó là bộ chữ độc quyền của M$?
Nói chính xác hơn: MS phân phối MS core fonts, nhưng EULA chỉ cấm tái
phân phối tới người dùng
có bất kỳ thay đổi nào[1].
Anh em FOSS đã lách luật[2]
[1] http://en.wikipedia.org/wiki/Ubuntu-restricted-extras
[2] http://corefonts.sourceforge.net/
[3] http://corefonts.sourceforge.net/eula.htm
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype:
vuhung16plus, twitter: vuhung, MSN: vuhung16.
http://www.facebook.com/nguyenvuhung
http://nguyen-vu-hung.blogspot.com/
Học tiếng Nhật: http://hoc-tiengnhat.blogspot.com/
Vietnamese LibreOffice: http://libo-vi.blogspot.com/
Mozilla & Firefox tiếng Việt: http://mozilla-vi.blogspot.com/
LibreOffice sau 18 thang
Sau 18 tháng phát triển, LibreOffice hùng mạnh với 400 người đóng góp
(contributor), trong đó có hơn 50 nhà phát triển (developer) và 2000
ngàn tình nguyện viên.
(contributor), trong đó có hơn 50 nhà phát triển (developer) và 2000
ngàn tình nguyện viên.
The bright future of LibreOffice
By Open Sources
Created 2012-03-02 03:00AM
February 2012 was a coming-of-age for the LibreOffice open source
productivity suite [1]. Multiple announcements show the project is
well-supported and thriving. But what of the future?
Formed out of Oracle's neglect of the OpenOffice.org project [2] by a
community uprising in 2010, LibreOffice quickly gathered a critical
mass of developers to work on it, drawn from a diverse set of
backgrounds and motivations. They hunkered down on the tasks that had
been hard to address while the project was in the hands of Sun
Microsystems (where I was once employed), such as removing unused code
from the project's two-decade legacy or making it possible for a
beginner to get involved through Easy Hacks [3]. A year and a half
later, there's much to show for their efforts, yet so much more to do.
[ Find out how LibreOffice 3.5 rates in the InfoWorld Test Center
review [4] by Neil McAllister and his previous in-depth comparison of
the 3.3 versions of LibreOffice and OpenOffice.org [5]. | Subscribe to
InfoWorld's Open Source newslettter [6] to ensure you don't miss any
open source content. ]
February saw multiple significant events. The most important was the
release of LibreOffice 3.5, full of subtle improvements and a few
larger features such as support for Microsoft Visio files. InfoWorld's
Neil McAllister summed it up in his review [1]:
If you were expecting a revamp on the scale of Office 2007, you'll
be disappointed. For all the work that has gone into the new version,
most of it is under the hood. Still, if you're a current
OpenOffice.org or LibreOffice user, you should waste little time in
upgrading to this version, which is more stable and user friendly than
ever.
Supported on a wide range of platforms (including Windows, OS X,
GNU/Linux and BSD) this is mature code -- with all that implies,
including a need for the very latest ideas to show up. So a second
significant event was a demonstration at Europe's FOSDEM conference by
community member Michael Meeks of LibreOffice Online, a port of
LibreOffice that delivers office productivity to the browser. Add an
early preview by developer Tor Lillqvist of a port of LibreOffice to
an Android tablet [7], and it's clear that giving the community
control of the project has opened up scope for multiple independent
innovations.
A news release from the project early in February [8] offered insight
into where this energy is coming from. The community now has more than
400 contributors, including 50 core developers, with over 2,200
volunteers providing bug reports. How did that happen in only 18
months?
The key was another February event, the incorporation of The Document
Foundation [9] (TDF) as an independent legal entity. Promised by the
original founders of LibreOffice, TDF is intended to provide an
inviolable safe haven for development of LibreOffice and its
innovative new relatives. The community around LibreOffice was clearly
highly motivated by this independence, having donated $66,000 in small
payments [10] in just seven days back in 2011 to serve as the core
capital of an exceptionally stable German nonprofit. No one calls the
shots at LibreOffice apart from the developers, and TDF was created to
make sure things stayed that way even as the project is adopted by
corporate sponsors.
The most recent news underlines the wisdom of that approach. Last week
saw Intel join TDF's advisory board [11] and commit to distribution of
LibreOffice for Windows through its AppUp store. Corporate supporters
like Intel will undoubtedly be very welcome, but ensuring that every
contributor genuinely has a voice in the project remains a priority.
That has to be the key lesson to draw from LibreOffice. Successful
open source communities are places where every participant is able to
aspire to their own vision within the context of collaboration. People
participate in open source projects to meet personal goals, not just
to be philanthropic [12]. They must have room to be allowed to meet
their needs, including making money without the permission of other
community participants. When a single company is in control -- by
design or simply by being the only one who shows up -- that ability is
stifled and participation is limited. This was a takeaway from the
failure of Symbian and is hopefully one that HP understands as it
tries to migrate WebOS over to open source [13].
Where next for LibreOffice? To continue this success, the project will
need to encourage the nascent innovation seen in the Web and Android
editions. It's time for a refresh of the user interface (although not
to slavishly follow Microsoft Office), for the addition of
collaboration features, and for the inclusion of cloud integration,
all of which will need developer focus.
Today's bring-your-own-device revolution [14] provides the ideal
opportunity for an open source productivity suite to finally gain
corporate traction; to be the package of choice, LibreOffice needs to
build on this solid base and deliver the capabilities that enable it.
Time will tell if it can pull off the feat. Given the amazing rescue
of OpenOffice.org by the LibreOffice community, I have high hopes it
will.
This article, "The bright future of LibreOffice [15]," was originally
published at InfoWorld.com [16]. Read more of the Open Sources blog
[17] and follow the latest developments in open source [18] at
InfoWorld.com. For the latest business technology news, follow
InfoWorld.com on Twitter [19].
Đăng ký:
Bài đăng (Atom)