Skip to main content

insert a character before and after evrey letter in a string



i want to insert a % character before after every letter in a string , but using StringBuilder to make it fast.





for example,





if a string is 'AA'







then it would be '%A%A%'







if it is 'XYZ'







then it would be '%X%Y%Z%'




Comments

  1. String foo = "VWXYZ";
    foo = "%" + foo.replaceAll("(.)","$1%");
    System.out.println(foo);


    Output:


    %V%W%X%Y%Z%


    You don't need a StringBuilder. The compiler will take care of that simple concatenation prior to the regex for you by using one.

    Edit in response to comment below:

    replaceAll() uses a Regular Expression (regex).

    The regex (.) says "match any character, and give me a reference to it" . is a wildcard for any character, the parenthesis create the backreference. The $1 in the second argument says "Use backreference #1 from the match".

    replaceAll() keeps running this expression over the whole string replacing each character with itself followed by a percent sign, building a new String which it then returns to you.

    ReplyDelete
  2. string str="AA";
    StringBuilder sb = new StringBuilder();
    for(int i = 0; i < str.length(); s++)
    {
    sb.append("%");
    sb.append(str.charAt(i));
    }
    sb.append("%");


    This is the simpliest way to do that.

    ReplyDelete
  3. Try something like this:

    String test = "ABC";
    StringBuilder builder = new StringBuilder("");
    builder.append("%");
    for (char achar : test.toCharArray()) {
    builder.append(achar);
    builder.append("%");
    }
    System.out.println(builder.toString());

    ReplyDelete
  4. public static String escape(String s) {
    StringBuilder buf = new StringBuilder();
    boolean wasLetter = false;
    for (char c: s.toCharArray()) {
    boolean isLetter = Character.isLetter(c);
    if (isLetter && !wasLetter) {
    buf.append('%');
    }
    buf.append(c);
    if (isLetter) {
    buf.append('%');
    }
    wasLetter = isLetter;
    }
    return buf.toString();
    }

    ReplyDelete
  5. StringBuilder sb = new StringBuilder("AAAAAAA");

    for(int i = sb.length(); i >= 0; i--)
    {
    sb.insert(i, '%');
    }

    ReplyDelete
  6. You may see this.

    String s="AAAA";
    StringBuilder builder = new StringBuilder();
    char[] ch=s.toCharArray();
    for(int i=0;i<ch.length;i++)
    {
    builder.append("%"+ch[i]);
    }
    builder.append("%");
    System.out.println(builder.toString());


    Output

    %A%A%A%A%

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex