[dev] [Fwd: Re: [users] What does this mean?]
It was suggested I ask this question here (from the users list). Please reply to me personally as I am not currently a member of the dev list (not sure I should be...). Thanks. mhr Forwarded Message From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Mark Hull-Richter [EMAIL PROTECTED] Subject: Re: [users] What does this mean? Date: Sat, 29 Sep 2007 22:52:34 -0400 On Saturday 29 September 2007 16:45:45 Mark Hull-Richter wrote: I recently upgraded my CentOS 5.0 OO installation to OO 2.3.0, and when I try to open a doc from the command line, I get this message: (soffice:24182): Gtk-WARNING **: Unable to locate theme engine in module_path: bluecurve, What module path is it looking in that it does not find my bluecurve theme? Try asking here dev@openoffice.org
[dev] [Fwd: Re: [qa-dev] Tinderbox in EIS]
Hi there! If I understood Kay Ramme correctly there is demand to discuss on how to react to tinderbox build breaks in development (which are now visible in EIS also) on this list, so I am forwarding a mail from the qa list to this list here. Kind regards, Bernd ---BeginMessage--- Kay Ramme - Sun Germany - Hamburg wrote: Hey, Hey Kay, I am glad that I read the QA list ... :-) So, I just found out, that since Bernds mail, changes in a CWS need to be Tinderbox compatible. Mmm, -Bernd, change acceptance isn't your biggest strength, is it? (No flame intended, I promise you a beer if you are offended :-) Well, I am not offended at all. Tinderboxes have not been MY invention they did exists for quite some time know. All I did was to react to the community request to make them more visible by integrating their result into EIS. What to do with this enhanced visibility is NOW up for discussion and that´s just started here. I didn´t start a process or introduced a rule or a change all I did was to make stuff others in the community do more visible. If you think we need rules on how to react to the results of their work, well that´s fine and a good thing, let´s go ahead and discuss on what we would like to do next here. But, even after I have read the mails, I am not sure how to work with this respectively to avoid build breakers in practical life. E.g. I just set my latest CWS to Ready for QA, despite the MacOSX being red. I had somewhat a of clue what went wrong, but was not really able to fix it, as I had no machine at hand. So, my question is, what is the suggested approach to address such issues? I currently see three options: -a- ignore it, does not seem to be choice -b- find somebody e.g. with a Mac and ask him/her to look at the problem -c- write an issue for the Mac port owner IMHO that´s kind of a general question on how to develop when you are developing in an Open Source environment. Someone else can show you that what you just did might have a problem somewhere your options are than to try to analyse that potential problem yourself or to seek help or to ignore it it depends. If you are not a MAC expert and the potential problem is a MAC specific one the answer could be too seek help from the community. Tinderbox build breaks and people pointing you at them by writing comments about them into issues or CWS comments are just one of many possible ways on how you can get feedback. And to be sure on things it might of course also be the case that you didn´t introduce a problem at all and it´s the testcase being wrong eg. the tinderbox is not setup correctly, this is something which might happen with tinderboxes as well as with any other type of automated testing. So well in such cases QA (tinderbox maintainer, automated testing) than has to somehow work together with development to look at where the problem really is. This all could also have happened without the enhanced visibility in EIS, of course. Well what´s wrong with writing an issue and adding that to the CWS so options b and c are IMHO fine, aren´t they. My personal opinion is that if it looks like that developers-X changes on a CWS might eventually break the build on any other established platform we shouldn´t integrate the CWS but seek for help from developer-Y being expert on that platform. Developer-X would likely generate work for Porters (developer-Y + developer-Z) on that other platform anyway but waiting with integration gives them at least a chance to have a look at the potential problem when they have time to do so on the CWS and let´s Developer-Z also working on that platform continue with other important work on the MasterWorkspace. But hey well I am only maintaining EIS and mostly likely neither in the developer-X or developer-Y or developer-Z group so my personal opinion is not of much weight here. IMHO, none of these options are suitable for practical life. The only real solution (which needs to scale well) I scan see is, to provide access e.g. to Macs, to allow a developer to fix the issue him-/herself. *hmm* my understanding is that access to macs is at least partial available via buildbots provided by the community, but that´s probably not what you meant, of course. By the way, it would be nice, to offer a buttom to retrigger tinderbox builds, I have also heard that feature wish already and I think too that this would be a nice idea. But as far as I know that´s currently not possible with how tinderboxes currently work. If it becomes possible to trigger tinderbox builds somehow i would surely offer to provide a button for that in EIS also. and certainly a buildbot would be nice as well. Speaking about buildbots: TERMITE is now also visible in EIS you can find that at the menu at MISC / Termit Main Page. There are Wiki entries for Termite and Tinderbox on OOoWiki. And, as the tinderbox stuff seems to be important, I would have
[dev] [Fwd: Re: accented characters in Writer]
Forwarded Message
From: austin DuBrulle [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: accented characters in Writer
Date: Fri, 02 Mar 2007 00:33:27 -0800
Thank you for the pointer. I should find in the documentation a imple way
to solve my problem (macros assigned to shortcut keys would be a candidate).
Keep up the good work
Regards'
Austin
From: G. Roderick Singleton [EMAIL PROTECTED]
To: austin DuBrulle [EMAIL PROTECTED]
CC: discuss@openoffice.org
Subject: Re: accented characters in Writer
Date: Thu, 01 Mar 2007 14:57:30 -0500
On Mon, 2007-02-26 at 11:24 -0800, austin DuBrulle wrote:
I use Windows OpenOffice Writer 2.1 for letters to foreign contries. It
seems that my only way to create accented characters is to copy them
from
the Character Map. This is a bit awkward.
How about using the same device as in MS Word, that is, creating an
accent
with typing Ctrl+{accent}
before typing the character?
Otherwise, OO is a nice piece of software. In particular, including a
PDF
converter in the Writer is a good idea.
Have you tried any of the methods described in the HOW TO section at the
doc project? I use the method outlined for UNIX quite successfully and
Windows user say method for this OS works well.
See
http://documentation.openoffice.org/HOW_TO/various_topics/Howto_special_char.pdf
--
G. Roderick Singleton [EMAIL PROTECTED]
OpenOffice.org
smime.p7s
_
Win a Zunemake MSN your homepage for your chance to win!
http://homepage.msn.com/zune?icid=hmetagline
--
G. Roderick Singleton [EMAIL PROTECTED]
OpenOffice.org
smime.p7s
Description: S/MIME cryptographic signature
[dev] [Fwd: Re: Vorschlag zur Versserung in der Handhabung des OO]
-- Mit freundlichen Grüßen Ralf Krüger Dr.-Karl-Senft-Str. 7 93142 Maxhütte-Haidhof [EMAIL PROTECTED] ---BeginMessage--- Hallo Ralf, Am Freitag, 22. September 2006 22:30 schrieben Sie: Hallo Andreas, ich weiß nicht, ob ich bei Dir an der richtigen Adresse für meinen Verbesserungsvorschlag für die Handhabung des OO bin. Bitte leite ihn dann an die entsprechenden Stellen weiter, oder gib mir Bescheid, an wen ich mich mit meinem Vorschlag wenden kann. um einen Verbesserungsvorschlag für OOo einzubringen, mußt Du diesen in dem Issue Tracker eingeben. Dort wird er dann von den Entwicklern gelesen. Für das Bedienen dieses Projekttools ist es erforderlich, dass Du Dich kostenlos bei OOo registrierst, da über die Mailadresse, die mit dem Namen generiert wird (Weiterleitungsadresse), die Bearbeiter des Issue (auch die Entwickler) bei Dir nachfragen können. Eine Einführung in das Tool findest Du z.B. hier: http://de.openoffice.org/dev/issuezilla_einfuehrung.html Ich arbeite seit rund 14 Jahren mit der LotusSmartSuite als Office-Programm am Desktop (Textverarbeitung, Datenbank, Tabellenkalkulation, Präsentation, Organizer, Web-Designer), und habe auch einige Anwendungen in der integrierten Script-Sprache realisiert... Und deren, übrigens für alle oben aufgeführten Programmteile verfügbare, Info-Box ist (für mein Empfinden) ein einfach geniales Formatierungswerkzeug: Alt+Eingabe drücken, und schon hat man die für das im jeweiligen Programm benötigten Formatierungswerkzeuge zur Hand, unabhängig, ob es sich um Tabellen,Grafiken, Rahmen,Texte, Datenbanken undsoweiter handelt( siehe Anlage: Beispiel aus der Textverabeitung mit markiertem Rahmen). Das habe ich bisher noch bei keinem anderen Office-Programm gesehen, und ist nach einer kurzen Eingewöhnungszeit wirklich äußerst praktisch, wenn auch für klickwütige MS-Office-User sehr gewöhnungsbedürfig (nun genug der Häme). Leider hat sich dieses Feature nicht im Office-Bereich durchgesetzt (Excel wurde ja auch nur auf den Markt gebracht, damit MS beweisen konnte, die eigentliche PC-Killerapplikation Lotus 1-2-3 aus den 80ern zu toppen). Wäre eine Funktion analog der Info-Box in OO einzubauen? Da ich kein Entwickler bin, kann ich dazu nichts sagen. Die Entwickler lesen eher auf der englisch-sprachigen Liste dev@openoffice.org mit. Evtl. müßtest Du Dich dort einschreiben und Deine Idee äußern (und auf Feedback warten). p.s. Ich hätte große Lust, an der Dokumentaion des Open Office mitzuwirken, bin aber momentan zeitlich ziemlich begrenzt, um dessen Features zu testen, und sie beurteilen und beschreiben (dokumentieren) zu können. Es gibt bereits Teile von Dokumentationen (und natürlich die umfangreiche programmeigene Hilfe). Wenn Du übersetzen willst, findest Du Dokumente auf den Seiten von OOoauthors.org. Ansonsten schau einfach mal auf http://de.openoffice.org/doc/index.html, ob dort etwas fehlt, was Du beschreiben kannst und möchtest. Falls Du noch weitere Fragen zu Dokumentation hast, schreib' mich einfach noch einmal kurz an und hake nach. Schönes Wochenende Andreas -- ## Content Developer OpenOffice.org: lang/DE ## Freie Office-Suite für Linux, Mac, Windows, Solaris ## http://de.openoffice.org ## Meine Seite http://www.amantke.de --- avast! Antivirus: Eingehende Nachricht sauber. Virus-Datenbank (VPS): 0638-1, 22.09.2006 Getestet um: 23.09.2006 09:44:43 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com ---End Message--- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Contributions to the default icon set used by OO.o/StarOffice]
Hi, Michael Meeks wrote: The traditional way to solve this is to have a responsive maintainer that approves (and/or rejects - with suitable comments) changes to the icon set. Yes. That would be the idea Martin posted. It's also normal in such a situation for some received wisdom such as choice of palette, constraints etc. to get communicated clearly. Obviously having a guiding vision behind a coherent set of icons is great, but having lots of people working on a set is good too ;-) so far, there has been no useful collaboration / communication whatever from the outside with the Sun art team [1], fixing that situation is clearly vital. Yes. But we have to differentiate between working on new concepts for displaying icons (such as svg, different sizes, different palettes, etc.) and the daily work on the current set. IMHO if the use of this web tool causes pain, and is unusable by others, Sun should shoulder the burden here; and ultimately [ AFAIR ] good icons take ~3 hours each to draw ; [ in 2 sizes ], and as such it's unlikely that inserting 4 or 5 per day in some web tool is going to cause much grief :-) Correct. Still the tool should be open and viewable for everybody. We are working on that. Can you make sure this is clearly defined in the wiki ? also - when sts goes on vacation etc. is there somewhere else they can be CC'd (which will usefully preserve timestamps etc.) I guess the standard procedures should be used, if a maintainer is not available. Cheers, Tom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Contributions to the default icon set used by OO.o/StarOffice]
Hi, Tom Verbeek schrieb: IMHO if the use of this web tool causes pain, and is unusable by others, Sun should shoulder the burden here; and ultimately [ AFAIR ] good icons take ~3 hours each to draw ; [ in 2 sizes ], and as such it's unlikely that inserting 4 or 5 per day in some web tool is going to cause much grief :-) Correct. Still the tool should be open and viewable for everybody. We are working on that. The Icon-Tool offers a simple web-based access to to all the icons which we have in the product. IMO the availability of this tool for Sun-external use is not the limiting factor. Instead we are rather talking about processes in this topic. Having the Icon-Tool on eis.services.openoffice.org is IMHO more a nice-to-have feature. Nevertheless we are evaluating whether it could easily be made available for external usage. Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Rene Engelhard wrote: Hi, Am Mittwoch, 7. Juni 2006 17:08 schrieb Jürgen Schmidt: it can't work. The bootstrap mechanism searches for an soffice in the path, links are resolved and when a executable is found (binary or script) the mechanism expects that the executable is found in a office program directory and the known directory structure is interpreted in some way to bootstrap. A link soffice to ooffice won't help because the ooffice script is in usr/bin and the bootstrap mechanism will fail. In this case you have to use the UNP_PATH environment variable. Thanks for the explanation. I guess I really have to add a soffice link into /usr/bin pointing to /usr/lib/openoffice/program/soffice, then... Will be in the next packages' revision (i.e. 2.0.3-1 with current plans) What exactly is the contents of the /usr/bin/ooffice script, then? That is, when you add a link from /usr/bin/soffice to /usr/lib/openoffice/program/soffice through which OOo can be started, why not also make /usr/bin/ooffice a link to /usr/lib/openoffice/program/soffice (or to the new /usr/bin/soffice)? -Stephan Regards, Rene - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Tobias Krais wrote: Hi Stephan, [..] What makes the soffice execuable so specific that the Debian ooffice executable does not work? Please help us answering this question to solve this Bug in Debian. Is it the case that on Debian there is an executable named ooffice in $PATH but not an executable named soffice? Yes. Well, the OOo Java simple bootstrap mechanism needs to find an OOo installation, and one of the things it tries out is to search for a file named soffice in $PATH (other things are looking at an explicitly set $UNO_PATH, for example). OK, this means that would mean that a simple link to ooffice called soffice should work, but it does not. Hard to tell why it does not work without any further information... Both files, the /usr/lib/openoffice/program/soffice and the /usr/bin/ooffice call the /usr/lib/openoffice/program/soffice.bin and do some other things. And these other things make the difference. What is there so special? You mean the Debian ooffice script looks substantially different from the standard soffice script? -Stephan Greetings, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Tobias Krais wrote: Hi Stephan, [..] What makes the soffice execuable so specific that the Debian ooffice executable does not work? Please help us answering this question to solve this Bug in Debian. Is it the case that on Debian there is an executable named ooffice in $PATH but not an executable named soffice? Yes. Well, the OOo Java simple bootstrap mechanism needs to find an OOo installation, and one of the things it tries out is to search for a file named soffice in $PATH (other things are looking at an explicitly set $UNO_PATH, for example). OK, this means that would mean that a simple link to ooffice called soffice should work, but it does not. it can't work. The bootstrap mechanism searches for an soffice in the path, links are resolved and when a executable is found (binary or script) the mechanism expects that the executable is found in a office program directory and the known directory structure is interpreted in some way to bootstrap. A link soffice to ooffice won't help because the ooffice script is in usr/bin and the bootstrap mechanism will fail. In this case you have to use the UNP_PATH environment variable. Juergen Both files, the /usr/lib/openoffice/program/soffice and the /usr/bin/ooffice call the /usr/lib/openoffice/program/soffice.bin and do some other things. And these other things make the difference. What is there so special? Greetings, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Hi, Am Mittwoch, 7. Juni 2006 17:08 schrieb Jürgen Schmidt: it can't work. The bootstrap mechanism searches for an soffice in the path, links are resolved and when a executable is found (binary or script) the mechanism expects that the executable is found in a office program directory and the known directory structure is interpreted in some way to bootstrap. A link soffice to ooffice won't help because the ooffice script is in usr/bin and the bootstrap mechanism will fail. In this case you have to use the UNP_PATH environment variable. Thanks for the explanation. I guess I really have to add a soffice link into /usr/bin pointing to /usr/lib/openoffice/program/soffice, then... Will be in the next packages' revision (i.e. 2.0.3-1 with current plans) Regards, Rene - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Hi together, I submitted a bug against the Debian OpenOffice package and we need your help to solve it. Problem description: In my Java application I use the OO bootstrap mechanism with the classloader classes as described here: http://codesnippets.services.openoffice.org/Office/Office.BootstrapOpenOffice.snip In case there is no soffice executable in my PATH the bootstrap classes won't find the OO installation. Solutions: - add a link /usr/bin/soffice to /usr/lib/openoffice/program/soffice What makes the soffice execuable so specific that the Debian ooffice executable does not work? Please help us answering this question to solve this Bug in Debian. Greeting, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Tobias Krais wrote: Hi together, I submitted a bug against the Debian OpenOffice package and we need your help to solve it. Problem description: In my Java application I use the OO bootstrap mechanism with the classloader classes as described here: http://codesnippets.services.openoffice.org/Office/Office.BootstrapOpenOffice.snip In case there is no soffice executable in my PATH the bootstrap classes won't find the OO installation. Solutions: - add a link /usr/bin/soffice to /usr/lib/openoffice/program/soffice What makes the soffice execuable so specific that the Debian ooffice executable does not work? Please help us answering this question to solve this Bug in Debian. Is it the case that on Debian there is an executable named ooffice in $PATH but not an executable named soffice? Well, the OOo Java simple bootstrap mechanism needs to find an OOo installation, and one of the things it tries out is to search for a file named soffice in $PATH (other things are looking at an explicitly set $UNO_PATH, for example). -Stephan Greeting, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Hi Stephan, [..] What makes the soffice execuable so specific that the Debian ooffice executable does not work? Please help us answering this question to solve this Bug in Debian. Is it the case that on Debian there is an executable named ooffice in $PATH but not an executable named soffice? Yes. Well, the OOo Java simple bootstrap mechanism needs to find an OOo installation, and one of the things it tries out is to search for a file named soffice in $PATH (other things are looking at an explicitly set $UNO_PATH, for example). OK, this means that would mean that a simple link to ooffice called soffice should work, but it does not. Both files, the /usr/lib/openoffice/program/soffice and the /usr/bin/ooffice call the /usr/lib/openoffice/program/soffice.bin and do some other things. And these other things make the difference. What is there so special? Greetings, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [Fwd: Re: Bug#369924: soffice in PATH missing - automatic soffice starting from jar not possible]
Hi Tobias, On Tue, Jun 06, 2006 at 03:40:08PM +0200, Tobias Krais wrote: I submitted a bug against the Debian OpenOffice package and we need your help to solve it. Problem description: In my Java application I use the OO bootstrap mechanism with the classloader classes as described here: http://codesnippets.services.openoffice.org/Office/Office.BootstrapOpenOffice.snip In case there is no soffice executable in my PATH the bootstrap classes won't find the OO installation. Solutions: - add a link /usr/bin/soffice to /usr/lib/openoffice/program/soffice What makes the soffice execuable so specific that the Debian ooffice executable does not work? Please help us answering this question to solve this Bug in Debian. Nothing I guess... It seems that debian just did not calls it soffice and is simply not found. Not being able to find the installation without that startup-link is nothing special either - since vanilla OOo is not spread across the filesystem, but everything resides in one single prefix. file /usr/bin/soffice /usr/bin/soffice: symbolic link to /etc/openoffice.org-2.0/program/soffice And /etc/openoffice.org-2.0 is in turn a symlink to /opt/openoffice.org2.0 file /opt/openoffice.org2.0/program/soffice /opt/openoffice.org2.0/program/soffice: Bourne shell script text executable And there you have it. A simple shell-cribt that sets up some environment variable and then calls itself.bin (→ soffice.bin) The link in /usr/bin, as well as the symlink in /etc is setup by the desktop-integration packages. ciao Christian -- NP: Korn - Bonus (hidden track) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] FwD: Re:
ok ok ok, here is it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
