Changing Mixed Case (Title) headings to Lower Case...

Hi,
I am converting several word documents into InDesign CS3 documents in order to create a book. Certain paragraph headings use mixed case (Title Case) and I wish to change each of these into lower case and then apply a character style using an expert font. This seems to be a great task for GREP. However, I have not had much success with creating the correct expression. Any tips or tricks for doing this sort of thing? Also, do you know if there is a shortcut assigned to (Title Case)? It may be the case I will have to use the shortcut key to apply Title Case.
Thanks in advance for your assistance.
Kind regards,
Greg

Hi Greg,<br /><br />Glad it helped. I was actually referring to the simple all-purpose one <br />which will use whatever grep settings you have. Just save the following <br />script as GrepToLowercase.jsx (or whatever you want), and after setting <br />your grep settings in the dialog, just run the script.<br /><br />finds = app.documents[0].findGrep();<br />for(i=0;i<finds.length;i++){<br />    finds[i].contents=finds[i].contents.toLowerCase();<br />    }<br /><br />-- <br />Harbs<br />http://www.in-tools.com<br />"Automated Publishing for the Rest of Us!"

Similar Messages

  • Small caps in running heads - mixed case problem

    My running head is set to be small caps, and it picks up mixed-case text from the document. I want the head to be all 'lower case' small caps (or 'upper case', unless that really means ordinary caps) but can see no way to achieve this. Instead I get 'mixed case' small caps, if that makes any sense. If I select the head on the master page and then Type | Change Case, this has no effect on the appearance either on the master or the generated heads. How do I achieve uniform small caps where the source text for the running head is mixed-case? If small .indd attachments were allowed I would have attached one, but it got rejected despite not being llisted as a forbidden type.

    A few ways to do this:
    a script: http://jsid.blogspot.com/2005/09/script-of-day-changing-case-again.html
    or in your paragraph styles use OT small caps (assuming you're using an OT font)
    I also set up a keyboard shortcut, to Type > Change Case > lowercase
    you could probably do it with GREP too...

  • BUG: Export DDL and Data fails for mixed case table/column names

    Hi there,
    I have found a bug in SQL Developer. See details below.
    Description:
    When "Export DDL and Data) function is used on a table/columns not named in UPPERCASE, sql generated by SQL Developer is invalid.
    Steps to reproduce:
    - open SQL Developer, connect to DB
    - make a table named "lowerCase" (in double quotes, so it won't be automatically changed to capital letters)
    - you may also add some columns, for example "lowerCol1", "UpCol2", ALLUPCOL3
    - add some data rows to the table
    - choose Tools -> Export DDL and Data
    - check exporting of tables and data, on "filter" tabs choose your "lowerCase" table
    - press "Apply"
    Error:
    Generated SQL contains invalid INSERTs: mixed-case table and columns are referenced without obligatory double quotes, which yields an error when generated script is executed (see below, relevant line is underlined)
    -- DDL for Table lowerCase
    CREATE TABLE "DBO_HT"."lowerCase"
    (     "lowerCol1" VARCHAR2(100),
         "UpCol2" VARCHAR2(100),
         "ALLUPCOL3" VARCHAR2(100)
    -- DATA FOR TABLE lowerCase
    -- FILTER = none used
    -- INSERTING into lowerCase
    Insert into lowerCase (lowerCol1,UpCol2,ALLUPCOL3) values ('lc','uc','auc');
    -- END DATA FOR TABLE lowerCase
    Remarks
    SQL Developer: version 1.2.1, build MAIN-32.13
    Oracle DBs: 9.2 & Express
    OS: Windows 2000 Professional
    If you need any more details/testing, let me know. I'd really appreciate a quick patch for this issue...
    Alternatively, do you know of any other simple way of copying a single database (it's called a schema in Oracle, right?) from one computer to another? Possibly something so simple like detaching->copying->reattaching mdf (data) files in SQL Server... I thought that this "Export DDL&Data" function will do, but as you can see I couldn't use it.
    I just need a simple solution that works - one operation on source to stuff, get the resulting files to other computer and one operation to have it running there... I think that such scenario is very basic, yet I just can't achieve it and I am simply not allowed to spend more time on it (read: our test project fails, my company rejects my "lobbying" and stays with MSSQL :/ )
    Thanks a lot & bye

    Thanks for your reply.
    ad. 1)
    You're right. I just wanted to give some very short feedback on my experiences with SQL Developer, so I didn't think starting new threads would be necessary, but as I was writing it became much bigger than I initially planned - sorry about that. I will make proper threads as soon as possible. Having "Edit post" button on this forum would also be useful.
    ad. 2)
    Generally, you're right - in most cases it's true that "switching DBMS is a major commitment" and "you will produce terrible code" if you don't learn the new one.
    However, I think that you miss one part of market here - the market that I think Express is also targeted on. I'd call it a "fire&forget databases" market; MySQL comes to mind as possibly most common solution here. It's the rather small systems, possibly web-accessed, whose data-throughput requirements are rather modest; the point is to store data at all, and not necesarily in fastest way, because given the amount of data that is used, even on low-end hardware it will work well enough. What's important here is its general ease of use - how easy is to set up such system, connect and access data, develop a software using it, how much maintenance is needed, how easy this maintenance is, how easy are the most common development tasks as creating a DB, moving a DB from test to production server etc. There, "how easy" directly translates to "how much time we need to set it up", which translates to "how much will the development will cost".
    Considering the current technology, switching the DBMS in such systems is not necesarily a major commitment and believe me that you will not produce terrible code. In many cases it's as simple as changing a switch in your ORM toolkit: hibernate.dialect = Hibernate.Dialect.OracleDialect vs MySQLDialect vs MsSql2005Dialect
    Therefore, in some part of market it's easy to switch DBMS, even on project-by-project basis. The reason to switch will appear when other DBMS makes life easier => development faster. From that point of view, I can understand my colleagues giving me an embarassing look and saying "come on, I won't read all these docs just to have db copied to test server". And it doesn't mean "they are not willing to learn anything new", it's just that they feel such basic task should have self-explaining solution that doesn't require mastering any special knowledge. And if they get such simple solutions somewhere else, it costs them nothing to change the hibernate dialect.
    I think Oracle did the great job with introducing the Express to this "fire&forget" market. The installation is a snap, it just works out of the box, nothing serious to configure, opposite to what I remember from installing and working on Oracle 9 a few years ago. In some places it's still "you need to start SQL*Plus and enter this script", but it's definitely less than before. I also find the SQL Developer a great tool, it can do most of what we need to do with the DB, it's also much better and pleasant to use over Oracle 9 tools. Still, a few basic things still require too much hassle, and I'd say taking your schema to another machine is one of them. So I think that, if you do it well, the "schema copy wizard" you mentioned might be very helpful. If I was to give any general advice for Express line of DB/tools, I'd say "make things simple" - make it "a DB you can't see".
    That's, IMHO, the way to attract more Express users.

  • Mixed -Case Passwords?

    Is it possible to create users with mixed-case passwords? For example, CREATE USER "User01" IDENTIFIED BY "SaMpLePaSsWoRd";
    The documentation for Oracle 9.2 says this is possible and recommended but running the command above via SQL*Plus does not seem to work because I am able to login to the database no matter if I type it exactly as above or all UPPER CASE or lower case.
    If there is no way to do this then my application cannot comply with our security standards and I need to choose a database other than Oracle

    Oracle does not actually store the password anywhere. The value you see in the password field in DBA_USERS is a hash based on the user name, the password suplpied and some "magic salt". When a user logs in , the username and password supplied plus the salt are hashed then compared to the value in the password field. A basic test shows:
    SQL> CREATE FUNCTION verifier (userid_parameter IN VARCHAR,
      2                                       password_parameter IN VARCHAR,
      3                                       old_password_parameter IN VARCHAR)
      4  RETURN BOOLEAN IS
      5
      6  BEGIN
      7     IF UPPER(password_parameter) = password_parameter OR
      8        LOWER(password_parameter) = password_parameter THEN
      9        RETURN FALSE;
    10     END IF;
    11     RETURN TRUE;
    12  END;
    13  /
    Function created.
    SQL> CREATE PROFILE pwtest LIMIT PASSWORD_VERIFY_FUNCTION verifier;
    Profile created.
    SQL> CREATE USER jtest IDENTIFIED BY MyTest
      2  PROFILE pwtest;
    CREATE USER jtest IDENTIFIED BY MyTest
    ERROR at line 1:
    ORA-28003: password verification for the specified password failed
    ORA-28003: password verification for the specified password failedSo, the function sort of works, but obviously, Oracle is changing the password to all one case (I would bet UPPER) since
    SQL> CREATE USER jtest IDENTIFIED BY "MyTest"
      2  PROFILE pwtest;
    User created.passes validation. Oracle will never change the case of anything within double quotes. However, it appears that the profile only enforces the rules at password creation time, not at login since:
    SQL> GRANT CONNECT TO jtest;
    Grant succeeded.
    SQL> CONNECT jtest/mytest;
    Connected.So, it would appear that you cannot really enforce mixed case passwords. You can however enforce almost anything else, such as minimun length, combinations of letters, numbers and some special characters, or almost anything else that does not depend on the case of the password.
    Given the many other security and auditing features available with Oracle, not to mention power of the product itself, I would hope that the lack of mixed case passwords would not cause you to choose a different vendor.
    TTFN
    John

  • Convert data in table to mix case

    Hi All,
    I have a table that contains data.
    This table has to columns, an id and description.
    I would like to update my table to convert data to mix case.
    As of now, all of my data in the table are lower case.
    What I mean by mix case is first letter for each word is uppercase and the rest are lower case.
    is there a function i can use ?
    example:
    Amended/Resentence, Type UnknownThanks

    You can use the INITCAP function.
    update table
    set description = INITCAP(description);Example:
    create table test (description varchar(50));
    Table created
    insert into test values ('amended/resentence, type unknown');
    1 row inserted
    select * from test;
    DESCRIPTION
    amended/resentence, type unknown
    update test set description = initcap(description);
    1 row updated
    select * from test;
    DESCRIPTION
    Amended/Resentence, Type Unknown

  • Issue with mix case

    Hi!
    Is there any way to prevent the data to be converted to upper-case without changing it's domain?
    I'm trying to insert mix case in a CHAR40 domain, but the text allways returns as upper-case.
    Regards,
    Andre

    AMadeira wrote:
    > It is possible to do that using code only?
    Please give more details: what you want to do programatically. ?
    If you check the domain of CHAR40 thru SE11 you can find :lowercase" check box not checked. so it convert to upper case
    a®

  • Generating mixed case for table and column names

    I trying to get table definition from Oracle 9i database into my toplink workbench
    (version 9.0.3), the column names and table names are capitilized by
    default, how do I change this to be mixed case? Thanks

    I'm not sure why you want them changed. The Oracle database by default is case insensitive, which in essence means it converts everything to upper case when a case is not specified (which can be done by wrapping it in quotes). Unfortunately, Java strings are case sensitive. This means that if you try searching resultsets for "TableName" when the database driver is returning "TABLENAME", you will run into problems. It is probably better to have your project match your database as closely as possible to avoid any issues later on.
    That said, I don't know of a way to automatically have the workbench use mixed case names - it uses the strings as they are returned from the database. I believe you will need to manually change the table names if you want them to be different than what you have imported.
    Best Regards,
    Chris

  • Fetching data from database in case of mixed case in SE37

    Hi,
    I have created a function module(in se37) where the input is Last name(PA0002-NACHN). My requirement is i have to fetch data from PA0002 based on last name. But the problem is if i give a name in mixed case(both upper and lower) sap converts the last name into Capital letter and starts searching the database.
                      But i tried in abap editor. here SAP accept the parameter(last name) as mixed case and starts searching. Why in function module the parameters are converted into upper case. How to restrict it.
                 If i will create a domain with LOWER CASE check box checked and try to call the dataelement in import part of function module then also it's converting it inot upper case. If i uncheck the lower case check box then also it's taking it as upper case.
                How to process the input parameter in function module(SE37) which should take the input as user enters,i.e if user enters small letter it should take it as small letter , if mixed letter it should take it as mixed letter and start searching.
    regards
    sandeep

    HI sandeep,
    <i>"If i will create a domain with LOWER CASE check box checked and try to call the dataelement in import part of function module then also it's converting it inot upper case. If i uncheck the lower case check box then also it's taking it as upper case."</i>
    I think the data is getting converted to upper case even before it is passed to this FM.
    Can yo ushow how are you testing this FM?
    If you are calling this FM in a abap program using a parameter, it will convert the text to upper case as and when you enter data the name in it.
    Regards,
    Ravi

  • Changing font case in Apple mail

    Cannot figure out how to change font case in apple Mail. For example if I accidentally typed my message in all CAPS how can I change my typed message to lower case ?
    Any ideas ?
    Thanks
    Ian

    Cannot figure out how to change font case in apple Mail. For example if I accidentally typed my message in all CAPS how can I change my typed message to lower case ?
    I think WordService might be able to do that:
    http://www.devon-technologies.com/products/freeware/services.html

  • Mixed case in column & table name

    Hi,
    How can tell SQL to use mixed case for column & table name?
    For example:
    create table PerNode (netId number, nodeId number);
    select netId, nodeId from PerNode;
    The above statements automatically made to upper case. But I wanted to retain the case sensitiveness in the column & table names.
    I know a way by including the names in double quote in the case will make this to retain the case.
    But I don't want to give all the time the column & table names within double quote.
    What I wanted to know is that is there any ALTER kind of statement will make the SQL to use the case I use in the name of the column & table.
    I greatly appreciate your advice.
    Thanks,
    --JK                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

    Oracle column names and table names are case insensitive unless you enclose them in quotes.
    Unless you want to have two tables, one called PerNode and one called pernode or some such, I'm not sure what benefit case sensitivity would have. One can certainly use mixed case SQL statements in stored procedures and ad-hoc SQL for readability-- only in the Oracle internals is everything changed to upper case.
    Justin
    Distributed Database Consulting, Inc.
    www.ddbcinc.com/askDDBC

  • Mixed case operation names in generated Web Service

    I am generating a PL/SQL Web Service with Oracle JDeveloper 10.1.3.1. The PL/SQL package contains functions with mixed-case names, like “getAllNames”. When I generate my Web Service, JDeveloper transforms the names into all lower case, like “getallnames”.
    Does anyone know how I can modify this behavior? I need the mixed case for my service operation names. I’ve checked through JDeveloper preference and project properties but don't see anything obvious.
    Thanks,
    Bill
    Message was edited by:
    user574327

    I think you mean the names of the Java methods or even more the operation names in the WSDL.
    As I have observed, JDeveloper generates uppercase letters only after underscores and it deletes the underscores. This way names like "my_proc", "my_Proc", "My_proc", "My_Proc" and "MY_PROC" all become "myProc"; and names like "Myproc", "myProc", "MyProc", "MYPROC" all become "myproc".
    I don't know a way to modify this behaviour, but you can edit the WSDL manually after it is generated.
    Patrik

  • Mixed case table/col names and JDeveloper?

    I am thinking of trying to use mixed case table/column names in my Oracle 8i database.
    My hope is to achieve table/column names consistent with Java conventions (which I am happy with).
    Would this work with Jdeveloper 3.1? 3.2?
    Will JDeveloper/BC4J then generate mixed case names?
    Will I cause my self lots of pain and suffering? (I don't consider having to enter a correct mixed case name a pain; I do consider always having to quote it and/or use TOUPPER, etc. a bit of pain)
    Thanks
    R.Parr
    Temporal Arts
    null

    I do consider always having to quote it and/or use TOUPPER, etc. a bit of pain)<<<JDEV isn't as much the issue. If you have simple applications and don't intend to change things over time, or create lots of interfaces, or support multiple development tools against the same database, mixed cases seem to work fine.
    To give yourself an idea of how cumbersome things will be, go in and
    create "myTable" ( "myField" varchar2(20) );
    now DESC ribe the table,
    select myField from it.
    Putting doublequotes around things all the time gets very irritating. Remember it is also for having special characters and embedded spaces... and I don't know of any PL/SQL SET ( other than the opposite: SQLCASE that forces just about everything to uppercase ).
    Oh, and then you get to encounter fun things like ODBC and JDBC drivers that may or may not like it. Or if you MOVE/EXPORT the data around, your target may or may not be happy.
    Working at several diversified, large organization with MANY database products/targets, I've become very disenchanted with making mixed case attributes and table names!
    All tools should support mixed case correctly. Reality has returned a mixed case of results. grin or not, as the case may be.
    null

  • How to change sentence Case in Pages for ios

    Hi,
    does anyone anyone know how to change sentence case in Pages for IPad.
    I Mean from UPPER CASE TO lower case.

    The IOS version of Pages has no Format > Font > Capitalization facility to transform uppercase text into other case forms. You need to use Pages v5.2.2 on OS X, or export to Word, and use most any other Word compatible word processor. If it is a couple of words, then retype them in the appropriate case.

  • Sending mixed case data

    Hi All,
    I need to pass a field with mixed case characters ( Example : JoeSmith) .
    If I dont  do a TOUPPER formula for this field in Transformation at the DSO stage, the load fails with that Hex conversion message.
    We don't want to convert to Uppercase for name fields.
    I have set ALL_CAPITAL in RSKC ( We are on BI 7.0 SP10 Unicode system)
    I tried by checking the Lower case flag for this field in the Datasource.
    I am aware of Lowercase checkbox in Infoobject maintainence - and I would rather not use that.
    Any ideas?
    HD

    I'd be looking at the input side of this. Is there a buffered stream that is not shared by the ObjectInputStream? If there is then the symptoms can be explained. A buffered stream will read in as much data as is available (up to some limit), regardless of whether that data is required. If you switch to the ObjectInputStream before the data has been consumed, then it has effectively been lost.
    The 200ms delay prevents the buffered stream from consuming the extra, and makes the program work.
    The solution is to ensure that the ObjectInputStream shares the buffered stream.
    Sylvia.

  • Converting to mixed case.

    I recall seeing a method that would convert all upper or all lower case to
    mixed case. Does this sound familiar to anyone?

    Try using this formula
    propercase(split(,"-")[2])
    Regards,
    Raghavendra

Maybe you are looking for