Sponsored Content
Special Forums UNIX and Linux Applications Preparing a datamodel for internationalisation / localisation Post 302736583 by figaro on Tuesday 27th of November 2012 02:41:12 PM
Old 11-27-2012
Thank you for your response. We thought it was going to go that way. It looks like the work load for both development and changes is not going to be affected by this all that much, even if expressions were allowed.
 

8 More Discussions You Might Find Interesting

1. Solaris

book for preparing exam ?

dear solaris group, whitch are the best book for study admin 1 + 2 on solaris 9 to prepare for the exam of admin 1 & 2 best regards Maurizio (2 Replies)
Discussion started by: mauric
2 Replies

2. UNIX for Advanced & Expert Users

preparing veritas exams using nextcertify.com ?

how good are nextcertify.com preps for veritas exams ? . i look forward to yoiur responses (1 Reply)
Discussion started by: rendu
1 Replies

3. Linux

Documentation for preparing RHCE certification

Hi all, Could someony give me a link to download a document for preparing linux RHCE certification? Regards, Tovo (0 Replies)
Discussion started by: tovohery
0 Replies

4. UNIX for Dummies Questions & Answers

Script for reading filelist and preparing param file.

Hi All, Not sure if this would be in a dummies sectiin or advanced. I'm looking for a script if someone has doen something like this. I have list of files - adc_earnedpoints.20070630.txt adc_earnedpoints.20070707.txt adc_earnedpoints.20070714.txt adc_earnedpoints.20070721.txt... (2 Replies)
Discussion started by: thebeginer
2 Replies

5. UNIX for Dummies Questions & Answers

Resources for preparing exam certification

I had install Sun Solaris 10 in my virtual machine. Anyhow I still very limitation knowledge how to operate it. Would like to search for help somemore could assist me how could I get the resources by free for me to learn and prepare myself for sitting the Sun cerfitication exam? Please help and... (3 Replies)
Discussion started by: jimmyysk
3 Replies

6. AIX

AIX Monitoring Tool - under preparing

Guy's AIX Monitoring Tool - under preparing ..... I'm working to make and prepare tool to monitor AIX system and my idea it's based on the following outputs I want command to give me shout outpous about the following ... CPU load Memory load Used load Number of... (5 Replies)
Discussion started by: Mr.AIX
5 Replies

7. Shell Programming and Scripting

Preparing a list of spawned processes

Hi All I'm currently trying to develop a script which will find the child processes of a process ID already passed to the script. I then need the script to look for spawned processes of these child processes and so on until it can't find any more. For example At the moment, I have to... (6 Replies)
Discussion started by: huskie69
6 Replies

8. Shell Programming and Scripting

Using localisation of a Perl package

I have a Perl package, which is widely used and tested, but recently a version in another language was added. The relevant po-files have been reviewed for this and are ready for testing. What are the steps to select the language by the user? From my understanding the language environment variable... (3 Replies)
Discussion started by: figaro
3 Replies
aecattr(5)							File Formats Manual							aecattr(5)

NAME
aecattr - aegis change attributes file DESCRIPTION
A change attributes file is used to describe the modifiable portion of a change. CONTENTS
A change attributes file contains the following fields: description = string; This field contains a detailed description of the change. brief_description = string; This field contains a brief description of the change. cause = ( ... ); This field describes the cause which motivated the change. external_bug The change was created in response to a bug report from outside the development team. This repairs existing functional- ity. external_enhancement The change was created in response to an enhancement request from outside the development team. This adds new functional- ity. external_improvement The change was created in response to an improvement request from outside the development team. This improves existing functionality. internal_bug The change was created in response to a bug report from inside the development team. This repairs existing functionality. internal_enhancement The change was created in response to an enhancement request from inside the development team. This adds new functional- ity. internal_improvement The change was created in response to an improvement request from inside the development team. This improves existing functionality. chain This cause is where you have a fix to fix a fix; tracking these is an interesting quality metric. test_exempt = boolean; This field is true if it is not necessary to test the change. It is, in general, desirable to test all changes, whether new func- tionality or a bug fix. This is, however, a project management issue. test_baseline_exempt = boolean; This field is true if it is not necessary to test the change against the baseline before it is changed. The test of the baseline is required to fail; this is to establish that the test has isolated the bug, and that the change has fixed that isolated bug. regression_test_exempt = boolean; This field is true if it is not necessary to perform a full regression test on the change. If absent, defaults to true for all causes except improvements. architecture = [ string ]; This field is a list of names of system and machine architectures on which the change must successfully build and test. copyright_years = [ integer ]; This field details the years in which the change was worked on. This field is present in trunk, branch and leaf nodes. As a change is edited, years in which the change was worked on accumulate in this field automatically. Branches accumulate years as integrations occur. You may need to manually edit this, though it should be rare. version_previous = string; This field records the "previous" version, mostly to simplify patch generation. It is only meaningful for trunks and branches. It is set automatically when a branch is started or integrated. attribute = [ { ... } ]; This is a list of (name,value) pairs, defining user specified attributes. name = string; The name of the attribute. By convention, names which start with an upper-case letter will appear in listings, and lower- case will not. Attribute names are case-insensitive. value = string; The value of the attribute. Arguably, most change attributes which may be altered by the user (and some that can't) should be of this form. Due to an acci- dent of history, this is not the case. SEE ALSO
aenc(1) create a new change aeca(1) modify the attributes of a change aegis(5) aegis file format syntax aecstate(5) change state file format aepattr(5) project attributes file format COPYRIGHT
aegis version 4.24.3.D001 Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Peter Miller The aegis program comes with ABSOLUTELY NO WARRANTY; for details use the 'aegis -VERSion License' command. This is free software and you are welcome to redistribute it under certain conditions; for details use the 'aegis -VERSion License' command. AUTHOR
Peter Miller E-Mail: millerp@canb.auug.org.au //* WWW: http://www.canb.auug.org.au/~millerp/ Reference Manual Aegis aecattr(5)
All times are GMT -4. The time now is 10:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy