yeah i got it....

the solution to pyuno error, it is because of linking with cc and cxx. I found that OO use linker as ${CC}, on the bugs and issue tracker i found a issue numbered 37731 related to same problem and came to know that this pyuno problem can be rectified by changing link to ${CXX} AND this change in linker to cxx can be achieved by the following patch:

Index: config_office/set_soenv.in
===================================================================
RCS file: /cvs/tools/config_office/set_soenv.in,v
retrieving revision 1.31
diff -u -r1.31 set_soenv.in
--- config_office/set_soenv.in 5 Jan 2005 12:10:00 -0000 1.31
+++ config_office/set_soenv.in 9 Jan 2005 18:51:24 -0000
@@ -1684,9 +1684,6 @@
ToFile( "CC", $CC, "e" );
ToFile( "CXX", $CXX, "e" );
ToFile( "USE_SYSTEM_STL", "@USE_SYSTEM_STL@", "e" );
-if ( $COM ne "MSC" ) {
- ToFile( "LINK", $CC, "e" );
-}
ToFile( "ENABLE_SYMBOLS", "@ENABLE_SYMBOLS@", "e" );
ToFile( "ENABLE_CRASHDUMP", "@ENABLE_CRASHDUMP@", "e" );
ToFile( "ENABLE_CUPS", "@ENABLE_CUPS@", "e" );

But one has to build the complete source again after applying this patch this is what i have done and rectified the error.

PyUno Error while building OO-1.1.4

while building 00-1.1.4 i am getting error in pyuno module and the error is:



Building project pyuno
=============
/home/vijay/OOo_1.1.4_src/pyuno/unotypes
-------------
/home/vijay/OOo_1.1.4_src/pyuno/zipcore
/home/vijay/OOo_1.1.4_src/pyuno/source/module
-------------
/home/vijay/OOo_1.1.4_src/pyuno/source/loader
-------------
rm -f ../../unxlngi4.pro/lib/pyuno_services.rdb
../../unxlngi4.pro/lib/pyuno_services.tmp
../../unxlngi4.pro/lib/pyuno_services.rdb
cd ../../unxlngi4.pro/lib && regcomp -register -r pyuno_services.tmp -c
typeconverter.uno -c invocation.uno -c corereflection.uno -c
introspection.uno -c invocadapt.uno -c proxyfac.uno -c pythonloader.uno
register component 'typeconverter.uno' in registry 'pyuno_services.tmp'
succesful!
register component 'invocation.uno' in registry 'pyuno_services.tmp'
succesful!
Abort
dmake: Error code 134, while making
'../../unxlngi4.pro/lib/pyuno_services.rdb'
---* TG_SLO.MK *---

ERROR: Error 65280 occurred while making
/mnt/hda3/OOo_1.1.3_src/pyuno/source/loader
dmake: Error code 1, while making 'build_all'
---* TG_SLO.MK *---


I am fighting with this error and trying to resolve it. And it seems that my frustation is creating a new world of challenge for me to crack the nut.
yes, i will.

target march

before a couple of days i targeted for march first week for a complete set of Linux and windows 001.1.4 build for the current five languages(hindi, tamil, kannada, gujarati, marathi). For the purpose i am working hard as this time i am not going to fail with respect to deadlines.
But again this strange and some entirely new error while building OO frustates me.

pot file

pot file is a acronym for "Portable Object Template", every translator takes a pot file copy and begins translating messages(msgstr) to the language desired. This file becomes a po(portable object) file.

What is pot file in openoffice

# pot file is a file with ".pot" extensions.

# it is organized in similar fashion as compared to directory
hierarchy of original source.
suppose a file 'sw/source/ui/dialog/ascfdlg.src' is to be
merged with the target string then the pot file will look
like this 'sw/source/ui/dialog.pot', it means that all the
strings which is to be merged with the files of the dialog
directory is present in the 'dialog.pot' file.

# 'dialog.pot' file is having a "msgid" mapped to "msgstr"(target language)
and the name of the file to be merged with.
example:
#: regionsw.src#FL_PROPERTIES_TEXT.#define.text
#: abstract.src#DLG_INSERT_ABSTRACT.FL_1.fixedline.text
#: ascfldlg.src#DLG_ASCII_FILTER.FL_1.fixedline.text
msgid "Properties"
msgstr ""

# it is useful and helpful for translation purpose not for merging to the source.

# after translation the complete pot files are converted into ".po" file
which is actually compatible with openoffice format for merging.

ICU

The International Components for Unicode (ICU) libraries
provide robust and full-featured Unicode services on a
wide variety of platforms. ICU supports the most current
version of the Unicode standard, and they provide support
for supplementary Unicode characters.

As computing environments become more heterogeneous, software
portability becomes more important. ICU lets you produce the
same results across all the various platforms you support,
without sacrificing performance. It offers great flexibility
to extend and customize the supplied services, which include:

· Text: Unicode text handling, full character properties and
character set conversions (500+ codepages)

· Analysis: Unicode regular expressions; full Unicode sets;
character, word and line boundaries

· Comparison: Language sensitive collation and searching

· Transformations: normalization, upper/lowercase, script
transliterations (50+ pairs)

· Locales: Comprehensive locale data (230+) and resource
bundle architecture

· Complex Text Layout: Arabic, Hebrew, Indic and Thai

· Time: Multi-calendar and time zone

· Formatting and Parsing: dates, times, numbers, currencies,
messages and rule based

ICU is an open source development project sponsored, supported,
and used by IBM. It is dedicated to providing robust, full-featured,
commercial quality, freely available Unicode-based technologies.
The ICU library supports multi-threading environments, and is
available in C, C++ and Java (ICU4J).

openoffice Localization

I don't understand why this openoffice source is behaving very strangely. Everytime i tried to solve something, some new things get strangled up.
Some thing works fine and some still irritates me.

test please ignore

test please ignore