Sponsored Content
Full Discussion: Change font
Top Forums UNIX for Dummies Questions & Answers Change font Post 302914946 by Makarand Dodmis on Friday 29th of August 2014 08:33:54 AM
Old 08-29-2014
try
Code:
printf "%s\n" "$(tput bold)employee$(tput rmso)="

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Hw to change the font of output in perl

Hw to change the font color and size of output in perl (2 Replies)
Discussion started by: trupti_rinku
2 Replies

2. Shell Programming and Scripting

How to change the font colour in unix ?

Could you pls tell me how to change the font colour in unix ? What is the syntax ? (3 Replies)
Discussion started by: sars
3 Replies

3. Shell Programming and Scripting

Font Color Change Using .profile

Does anyone know how can I change font color, background color etc for a particular user using .profile? Any help is appreciated. (0 Replies)
Discussion started by: fifo_vs_lifo23
0 Replies

4. UNIX for Dummies Questions & Answers

How to change the font or color of text

Hi Gurus, I have a small requirement where i want to change the color & font of some text in a file. i have a file error.txt which will be created in the script using egrep. After that iam adding these lines at head & tail to that file using the following code awk 'BEGIN{print"Please... (4 Replies)
Discussion started by: pssandeep
4 Replies

5. AIX

how to change the font size of shell in $ prompt

Can any help me to change the default font type and its size.. To clear more about my question.. Once i login to my unix domain... the font it displaying is of small size... all my shell commands i am executing in $ prompt also carries the same style(ls, date and echo...) i searched whole... (2 Replies)
Discussion started by: tsjpraveen
2 Replies

6. Shell Programming and Scripting

change the font size in bash

Hi, I would like to change the font size in bash. I know how do it in ksh: F_VDOBLE="\033#6" print "${F_VDOBLE}Esto es..." But in bash I don't know Could you help me please? Many thanks! (5 Replies)
Discussion started by: mierdatuti
5 Replies

7. Shell Programming and Scripting

how to change font in mailx

I am writing sql reports to an oracle database, spooling them to a file and emailing them with mailx. I use the syntax below. The reports do not format properly, unless I use the Courier New font. How do I set this with mailx? mailx -s "MY REPORT, `date +'%D %r` " -r "REPORTING SYSTEM"... (2 Replies)
Discussion started by: guessingo
2 Replies

8. Programming

Change font in Motif

Does anyone know how to change the font size into a larger one, in a basic Motif application? (1 Reply)
Discussion started by: JenniferKuiper
1 Replies

9. Ubuntu

How to change ffmpeg default font size?

Hello, I have a problem with Greek subtitle font size when I map a subtitle file into a video in ffmpeg. I ran below code: ffmpeg -i video.mp4 -sub_charenc CP1253 -i video_sub.srt -c:v copy -c:a copy \ -c:s mov_text -metadata:s:s:0 language=gr mapped_video.mp4 When I play it in VLC,... (2 Replies)
Discussion started by: baris35
2 Replies

10. UNIX for Beginners Questions & Answers

Send mail with font change

Hi All, I have a file that contains following entries. I want to highlight the line that has word as "FAILURE" while sending the email. File ------------------------------------------------------------ Job Name: ABC Start Time: 07/20/2019 07:32:39 End Time: 07/20/2019... (4 Replies)
Discussion started by: sdosanjh
4 Replies
XMLForm(3pm)						User Contributed Perl Documentation					      XMLForm(3pm)

NAME
CGI::XMLForm - Extension of CGI.pm which reads/generates formated XML. NB: This is a subclass of CGI.pm, so can be used in it's place. SYNOPSIS
use CGI::XMLForm; my $cgi = new CGI::XMLForm; if ($cgi->param) { print $cgi->header, $cgi->pre($cgi->escapeHTML($cgi->toXML)); } else { open(FILE, "test.xml") or die "Can't open: $!"; my @queries = ('/a', '/a/b*', '/a/b/c*', /a/d'); print $cgi->header, $cgi->pre($cgi->escapeHTML( join " ", $cgi->readXML(*FILE, @queries))); } DESCRIPTION
This module can either create form field values from XML based on XQL/XSL style queries (full XQL is _not_ supported - this module is designed for speed), or it can create XML from form values. There are 2 key functions: toXML and readXML. toXML The module takes form fields given in a specialised format, and outputs them to XML based on that format. The idea is that you can create forms that define the resulting XML at the back end. The format for the form elements is: <input name="/body/p/ul/li"> which creates the following XML: <body> <p> <ul> <li>Entered Value</li> </ul> </p> </body> It's the user's responsibility to design appropriate forms to make use of this module. Details of how come below... Also supported are attribute form items, that allow creation of element attributes. The syntax for this is: <input name="/body/p[@id='mypara' and @onClick='someFunc()']/@class"> Which creates the following XML: <body> <p id="mypara" onClick="someFunc()" class="Entered Value"></p> </body> Also possible are relative paths. So the following form elements: <input type="hidden" name="/table/tr"> <input type="text" name="td"> <input type="text" name="td"> <input type="text" name="../tr/td"> Will create the following XML: <table> <tr> <td>value1</td> <td>value2</td> </tr> <tr> <td>value3</td> </tr> </table> SYNTAX
The following is a brief syntax guideline Full paths start with a "/" : "/table/tr/td" Relative paths start with either ".." or just a tag name. "../tr/td" "td" Relative paths go at the level above the previous path, unless the previous path was also a relative path, in which case it goes at the same level. This seems confusing at first (you might expect it to always go at the level above the previous element), but it makes your form easier to design. Take the following example: You have a timesheet (see the example supplied in the archive) that has monday,tues- day,etc. Our form can look like this: <input type="text" name="/timesheet/projects/project/@Name"> <input type="text" name="monday"> <input type="text" name="tuesday"> ... Rather than: <input type="text" name="/timesheet/projects/project/@Name"> <input type="text" name="monday"> <input type="text" name="../tuesday"> <input type="text" name="../wednesday"> ... If unsure I recommend using full paths, relative paths are great for repeating groups of data, but weak for heavily structured data. Pic- ture the following paths: /timesheet/employee/name/forename ../surname title ../department This actually creates the following XML: <timesheet> <employee> <name> <forename>val1</forname> <surname>val2</surname> <title>val3></title> </name> <department>val4</department> </employee> </timesheet> Confusing eh? Far better to say: /timesheet/employee/name/forename /timesheet/employee/name/surname /timesheet/employee/name/title /timesheet/employee/department Or alternatively, better still: /timesheet/employee/name (Make hidden and no value) forename surname title ../department Attributes go in square brackets. Attribute names are preceded with an "@", and attribute values follow an "=" sign and are enclosed in quotes. Multiple attributes are separated with " and ". /table[@bgcolor="blue" and @width="100%"]/tr/td If setting an attribute, it follows after the tag that it is associated with, after a "/" and it's name is preceded with an "@". /table/@bgcolor readXML readXML takes either a file handle or text as the first parameter and a list of queries following that. The XML is searched for the queries and it returns a list of tuples that are the query and the match. It's easier to demonstrate this with an example. Given the following XML: <a>Foo <b>Bar <c>Fred</c> <c>Blogs</c> </b> <b>Red <c>Barbara</c> <c>Cartland</c> </b> <d>Food</d> </a> And the following queries: /a /a/b* c* /a/d it returns the following result as a list: /a Foo /a/b Bar c Fred c Blogs /a/b Red c Barbara c Cartland /a/d Food (NB: This is slightly incorrect - for /a and /a/b it will return "Foo " and "Bar " respectively). The queries support relative paths like toXML (including parent paths), and they also support wildcards using ".*" or ".*?" (preferably ".*?" as it's probably a better match). If a wildcard is specified the results will have the actual value substituted with the wildcard. Wildcards are a bit experimental, so be careful ;-) Caveats There are a few caveats to using this module: AUTHOR
Matt Sergeant msergeant@ndirect.co.uk, sergeant@geocities.com Based on an original concept, and discussions with, Jonathan Eisenzopf. Thanks to the Perl-XML mailing list for suggesting the XSL syntax. Special thanks to Francois Belanger (francois@sitepak.com) for his mentoring and help with the syntax design. SEE ALSO
CGI(1), CGI::XML perl v5.8.8 2005-01-18 XMLForm(3pm)
All times are GMT -4. The time now is 06:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy