https://issues.apache.org/ooo/show_bug.cgi?id=74236
--- Comment #31 from orcmid <[email protected]> --- (In reply to hrajko from comment #19) > hrajko --> SBA > maybe I must explain for YOU ;) > Slovak republic is for you little fish.. maybe, yes, u're right. Fly shit on > map > of europe :-D . But in our law, is RTF main editable text document format and > using ODF(odt) has secondary priority. And that's the point of reason, > converting between this two formats. If ooo doesn't have this feature without > problems, then newer be accepted like an alternative. > > hrajko --> brko > This bug exists long time ago before I reporting on this place. This is heart-breaking. I think there is a misunderstanding about what it takes to improve interoperability among language groups, software, products, etc. This is not about priority to Slovak republic. It is about the capabilities and capacity available on the OpenOffice.org team (now the Apache OpenOffice and LibreOffice teams). It is important that users in different communities and technical contexts (keyboards, displays, computers, software) and operating skills report their problems. But identifying the existence of a problem from its symptoms and finding a correctable cause are different things. The first difficulty is confirmation of the problem in a clear manner. This already requires cooperation of those having the problem in helping to understand what the *specific* difficulty is. (Most reports just make general claims that then have to be researched.) That takes more work on the part of people who have their own work to do and who have encountered a barrier to what matters to them. And it takes work on the part of the project members to help clarify and establish what that difficulty is in specific terms. But without that, there is not much way forward. Now, with Apache OpenOffice and with LibreOffice, the developers are all volunteers and finding someone with the capacity, skills, and available attention to determine the underlying cause and propose repairs is not assured. It is more complicated when the problems require domain knowledge of how documents created in a particular language community are expected to work. The developers with deep understanding with the internal workings of the software must rely on user volunteers in the affected language or cultural community to help understand the symptoms and confirm that a solution works and causes no other harm. It is similar for how translations are obtained for the internationalization of the software, by finding experts in the local language who are also willing and able to work on an internationalization project for the software. There are multiple kinds of domain knowledge required to bring together in identifying and solving many problems involving international use of the software. It may be that the population of the Slovak Republic is small and that makes finding contributors with the time and energy more difficult. It is the absence of such connections that limits action, not any intentional neglect for a particular community. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
