Skip to main content

More on generating pango strings...

This is not so easy a 'nut to crack'. I've noticed that the solution that I've come up with so far fails to implement nested markup, ie <b> <s> text </s></b>. Conversely, getting the <span> </span> block is an issue too! Clearly there is a need for this functionality, but there is no clear solution that I can find. The Gimp developers are working on something similar but I notice that they have problems with <span> too!

So, I've gone back to basics. Rather than relying the pango string parser, I'll put something together of my own. Today I've been working on some extra string funcs. Here's what I've produced so far:

/*
gcc -o first first.c
*/

#include <stdio.h>
#include <string.h>
 
/**
    search for first occurance of p in s, starting from i
    done
**/
int strnfrst(char *s, char *p, int i)
{
        char *f;
        int l;
       
        l = strlen(p);  /* length of search string */
        f = s+i;
 
        /* search through string till match found */
        while (*f != '\0') {
                if ( !strncmp(f, p, l) ) {
                    return f-s;
                }
                f++;
        }
        return -1;
}

/**
    extract a range of characters from string s starting from position a to position b
    done
**/
char *strrng (char *dest, const char *src, int a, int b) {
  unsigned i,j;
 
  j=0;
  for (i=a; i<b; i++)
  {
    dest[j++] = src[i];
  }
  dest[j] = '\0';
  return dest;

}

/*
char *strcpy(char *dest, const char *src)
{
  unsigned i;
  for (i=0; src[i] != '\0'; ++i)
    dest[i] = src[i];
  dest[i] = '\0';
  return dest;
}
*/

/**
    gettag
    get name of next tag in string, starting at position i
**/
int getTag (char *str, char *tag, int i) {

        int a,b;
       
        a = strnfrst(str,"</",i);
       
        if (a) {
            a = strnfrst(str,"<",i);
        }
       
        b = strnfrst(str,">",a+1);

        strrng(tag,str,a,b+1);
       
        return a;
}


/**
    test
**/
int main()
{

        // p in s, starting from i
        char str1[] = "abCdefC";
       
        int i = strnfrst(str1, "C", 0);
        int j = strnfrst(str1, "C", i+1);
        printf("locations %d %d in %s\n",i,j,str1);

        char buf[32];

        /* get the characters between the Cs */
        printf("'%s' lies between chars %d and %d\n",strrng (buf,str1, i+1,j),i+1,j);

        char str2[] = "<b>bold</b>   <i>italic</i>   <u>underline</u>   <s>strikethrough</s>";

        printf("text range 3 thro' 8 = '%s'\n", strrng (buf, str2, 3, 8));

        /* get the next tag in the string */
        i= getTag (str2, buf, 3);
        printf("next tag %s at pos %d\n", buf, i);
       
        i=getTag (str2, buf, i+1);
        printf("next tag %s at pos %d\n", buf, i);

        /* parse the whole string */
        // get the position of the first tag toggle
        i = getTag (str2, buf, 0);
        printf("%d %s\n",i,buf);
       
        // parse the remainder of the string
        while ( i < strlen(str2) ) {
            i=getTag (str2, buf, i+1);
            printf("%d %s\n",i,buf);
           
        }

        return 0;

}


Comments

Popular posts from this blog

gnocl::calendar

Given this module some attention today. Added some of the more package wide options to the module and created customised handler for setting the month. (For some odd reason months are are counted 0-11 whereas days are 1-31.) There's still a little more to do to this one including the addition of code to store diary details. Here's the working test script to show the range of options at work. The percentage substitution string item %e explores something that I've been toying with, the name of the signal/event that initiated the call. Ok, a script can keep its own internal trace but who knows, it might prove useful. #--------------- # calendarTest.tcl #--------------- # Author:   William J Giddings # Date:     07/05/09 #--------------- #!/bin/sh # the next line restarts using tclsh \ exec tclsh "$0" "$@" #--------------- package require Gnocl set cal [gnocl::calendar] $cal configure -day 8 -month 7 -year 1956 $cal configure -rowHeight 1 -colWidth 1 $ca

Simple Runtime Debugging Message Dialog

At times it's useful to see what values variables hold, or offer some pause point before the code goes elsewhere before causing havoc. Its possible to write output to the terminal but this can get lost in copious forms of other outputs, besides, there's no pausing the script execution either. The following proc creates a custom dialog which displays ad message along with the point in the calling script from which it was invoked. ## simple runtime debugging feedback dialog, alternative to console based gnocl::msg # @param msg message to display # @returns none # proc xxx::msg {txt} { set frame [info frame -1] append msg "Message:\n\n" append msg " $txt \n\n\n" append msg "Called from:\n\n" append msg "Proc:\t[lindex [info level -1] 0]\n" append msg "File:\t[file tail [dict get $frame file]]\n" append msg "Line:\t[dict get $frame line]\n" gnocl::dialog \ -type info \ -text $msg

Gnocl Dashboard

Over the past few programming sessions I've been working on producing a central point, a dashboard, around which it's possible to see the various Gnocl widgets and commands in operation. In many ways like the demo script which shipped with the earlier releases of Gnocl but offers much more. The introspection functionality provides details of the various options and sub-commands of each Gnocl procedure which are displayed under the associated tab. Sample scripts are included for each item which offers newcomers a clearer insight into how make the most of what's on offer.