Hi Jeffrey, guess I was not precise enough. It is not that there are messages missing, but what Messages.properties are used at a given moment. The overlay mechanism works for the webapplication, but it will not overlay the catalogue used in api.
sunny greetings Claudia Jürgen Jeffrey Trimble schrieb: > Hi Claudia, > > Yes, that does help. I think users are sometimes confused where to find > some types of > messages. That is, we (meaning the DSpace community of know hows) > inform them > in Messages.Properties for 90-95% of the time to find a message for the > jspui. But, some > text, as you said below, are hard coded in the java, jsp, or the config > files. > > I guess in the future documentation, we might want to codify with a > table where all the different > types of messages reside or attempt to move hard-coded messages still > around in the java or jsp's into the Messages.properties > file (ooh, ooh, I vote for modularization!). > > --Jeff > > Jeffrey Trimble > System LIbrarian > William F. Maag Library > Youngstown State University > 330.941.2483 (Office) > [email protected] > http://www.maag.ysu.edu > http://digital.maag.ysu.edu > "Mad, Bad and Dangerous to Know" > > > > On Jul 1, 2009, at 2:49 AM, Claudia Jürgen wrote: > >> Hi Jeffrey, >> >> there is one further issue >> [dspace-src]/dspace/modules/jspui/src/main/resources/Messages.properties >> will only affect the webapplication UI part. >> >> Non webapplication related texts will still be taken from the >> dspace-api, e.g. the cron jobs run like the sub daily. >> >> Hope that helps >> >> Claudia Jürgen >> >> >> Jeffrey A Trimble schrieb: >>> Thanks Stuart. All documentation will be adjusted accordingly. >>> And I learned something new about Messages.properties today. I've >>> not been correctly placing it in the right place. I'll bet I'm not >>> the only one. >>> --Jeff >>> On Wed, 1 Jul 2009, Stuart Lewis wrote: >>>> Hi Jeff, >>>> >>>> >>>> >>>> 1. >>>> [dspace-src]/dspace/modules/jspui/src/main/resources/Messages.properties >>>> >>>> is the correct location. >>>> >>>> >>>> >>>> 2. Yes - I think you are right about i18n and themes needing >>>> to be >>>> created by hand (upgrade or fresh installation). As this is the source, >>>> there isn't really any difference between fresh install or upgrade. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> >>>> >>>> >>>> >>>> Stuart Lewis >>>> >>>> Digital Services Programmer >>>> >>>> Te Tumu Herenga The University of Auckland Library >>>> >>>> Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand >>>> >>>> Ph: 64 9 373-7599 x81928 >>>> >>>> http://www.library.auckland.ac.nz >>>> <http://www.library.auckland.ac.nz/> / >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> From: Jeffrey Trimble [mailto:[email protected]] >>>> Sent: Wednesday, 1 July 2009 3:25 a.m. >>>> To: [email protected] >>>> Subject: [Dspace-devel] Documentation--confirmation of information >>>> >>>> >>>> >>>> As I begin to revise the documentation for the next release, I may >>>> asking for clarification >>>> >>>> from time to time from those of you who wrote parts of the code. >>>> >>>> >>>> >>>> Today, I should like to ask if someone will confirm my "hunch". I'm >>>> going to reference >>>> >>>> Section 7.2, pg. 115/116 (using the 1.5.2 pdf file). This has to do >>>> with the Source Directory Layout. >>>> >>>> >>>> >>>> 1. The current documentation has under the modules/ >>>> >>>> -- jspui >>>> >>>> --src/main/resources It suggests this is where >>>> Messages.properties file should reside for the >>>> >>>> local installation. >>>> >>>> >>>> >>>> Question/Comment. Please confirm that this is indeed true. >>>> Personal experience has me placing it in >>>> >>>> the >>>> [dspace-source]/dspace-api/target/classes/Messages.properties >>>> >>>> >>>> >>>> If true, I will also make adjustments under the upgrade and >>>> installation section to reference this. It was >>>> >>>> lacking and many users keep asking about the >>>> Messages.properties files. >>>> >>>> >>>> >>>> I will also make notations regarding the xmlui flavor of the >>>> file. >>>> >>>> >>>> >>>> 2. -- xmlui >>>> >>>> --src/main/webapp/ >>>> >>>> --i18n/ >>>> >>>> --themes/ >>>> >>>> >>>> >>>> The two directories 'i18n/' and 'themes/' need >>>> to be created manually. At least my installation, as an upgrade, did >>>> >>>> not install this. >>>> >>>> >>>> >>>> Question/Comment: Please confirm that (1) site who perform >>>> upgrade will need to create these manually; and, (2) what >>>> >>>> a new, fresh installation will present--that is, will the >>>> directories be created automatically or would the user need to create >>>> them. >>>> >>>> >>>> >>>> >>>> >>>> Final comment, I realize that all this will/may/probably change in >>>> DSpace 2.0, but many will be up to a year behind upgrades, as we >>>> >>>> all know happens with institutions. >>>> >>>> >>>> >>>> TIA, >>>> >>>> >>>> >>>> Jeff >>>> >>>> >>>> >>>> Jeffrey Trimble >>>> >>>> System LIbrarian >>>> >>>> William F. Maag Library >>>> >>>> Youngstown State University >>>> >>>> 330.941.2483 (Office) >>>> >>>> [email protected] >>>> >>>> http://www.maag.ysu.edu >>>> >>>> http://digital.maag.ysu.edu >>>> >>>> "Mad, Bad and Dangerous to Know" >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> ------------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> Dspace-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/dspace-devel > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Dspace-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------------ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
