New - information

Hello to all on this ML.
I am new here so I introduce myself: my name is Paolo
and I'm from Italy.

I want you to know that I am available for translating
Emilda in my native language (italian).
I need to know if i have only to fill in the file
emilda.pot with italian terms or if there is something
else that need to be translated.
Thank you!

Paolo Pozzan

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it

locales for debian package

Hi,

I would be grateful to accept translations for the installation and
configuration of the Debian package of Emilda in case anyone would be
interested.

I'm attaching the templates.pot file.

Thanks,
Dave.
-- 
Encrypted Mail Preferred:
    Key ID:  8527B9AF
    Key Fingerprint:  E1B6 40B6 B73F 695E 0D3B  644E 6427 DD74 8527 B9AF
    Information:  http://www.gnupg.org/

ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
    Information:  http://www.expita.com/nomime.html

#
#    Translators, if you are not familiar with the PO format, gettext
#    documentation is worth reading, especially sections dedicated to
#    this format, e.g. by running:
#         info -n '(gettext)PO Files'
#         info -n '(gettext)Header Entry'
#
#    Some information specific to po-debconf are available at

Emilda 1.2.3 Released

Emilda 1.2.3 has been released.

This release incorporates several minor bug fixes and a few security
fixes. It is recommended that all 1.2 users upgrade to this latest
stable version.

With this release out the door our main focus will be on Emilda 1.3
development. Only major or critical bugs will be fixed for 1.2.

--

-- 
Mattias Nordstrom
CTO
Realnode Oy

nordstrom <at> realnode.com
www.realnode.com

Emilda 1.2 Language Template

Dear all,

I have updated the emilda.pot language template in the 1.2 branch of the 
lang module. This file can be used as base for localization of the 1.2 
branch.

Usage:
cp emilda.pot [my_new_language].po
or
msgmerge -Uv [my_existing_language].po emilda.pot

More information on gettext translation:
http://www.gnu.org/software/gettext/manual/html_chapter/gettext_toc.html

To install a translated language, simply run bin/compile_languages.sh 
(In case of problems make sure you also have run bin/locales.sh and 
setup.php?action=locales)

Thanks to Finno school and Wolfgang for pointing out missing gettext 
conversions.

Regards,
--

-- 
Erik Berglund
Chairman of the Board
Oy Realnode Ab

berglund <at> realnode.com
www.realnode.com

Emilda 1.2 Released

Dear all,

Emilda 1.2 has been declared stable and released on all mirrors. Since
the 1.1 release the system has been heavily redesigned and improved.
Emilda 1.2 includes enhanced cataloguing using item types and subject
headings, LDAP authentication, a completely renewed configuration system
using Control Panels, automated setup and upgrading, a new database
backend including cached queries and support for older 3.x MySQL
servers, Gettext i18n, a new default template, a new table layout design
and backend, a new search backend, new reports, enhanced MARC
configuration, a new Terminal Management system for dedicated Emilda
terminals, improved support for multiple locations, a complete help
system redesign and many bugfixes. I.e. a whole year of development
including valuable contributions from the community. Enjoy!

ChangeLog:

1.2

  - Fixed some minor bugs, including 207, 210.

1.2-rc1

  - Emilda Help.
  - New LDAP subsystem.
  - Many feature and bug fixes, including bugs:
    77, 135, 179, 180, 181, 182, 189, 92, 114, 119,
    140, 175, 183, 184, 185, 191, 197, 198, 201, 203,
    161, 177, 190, 168

Re: Polish translation of 1.2rc1

> What (file) are you using as base for the translation? We have still not 
> built a script for language string extraction for the fields in the 
> database and in page_config. However simple xgettext for all files 
> (emilda.pot) contains most text and is a good way to start.

I've started with gettext and emilda.pot file, then switched to
gtranslator. Currently I don't have testing-environment so I can't tell
if it works or not. Moreover, I'm more familiar with emilda 1.1 then
1.2. I plan to install fresh system with the newest RC and do something
more about that translation. (and I'm looking forward to testing LDAP
support). 

January 2005 would be quite nice term for Emilda 1.2 stable release,
wouldn't it?

Regards,

--

-- 
Lukasz Wilke <wilke <at> i-lo.debica.edu.pl>

Polish translation of 1.2rc1

Polish translation of Emilda ver. 1.2rc1 is being prepared and will be
ready in couple of days. (Current progress 30%).

Polskie tłumaczenie do Emildy 1.2rc1 jest w trakcie opracowania i będzie
gotowe za parę dni.

Regards,

Łukasz Wilke

Emilda 1.2-rc1 Released

Emilda 1.2-rc1 has been released!

The first release candidate Emilda 1.2-rc1 for the upcoming Emilda 1.2 
stable release is now available for testing. We encourage all Emilda 
users with available testing resources to evaluate and stress-test this 
release, and report all anomalies to Emilda Developers or the Emilda Bug 
Database. For Emilda 1.1 users, this release brings tons of 
improvements, such as: new search capabilities, LDAP support, web-based 
setup, item types, subjects, etc. Translators are called upon to begin 
possible translations of Emilda as language by this release has been frozen.

For more information and downloads, please visit http://www.emilda.org/

ChangeLog:

- Emilda Help.
- New LDAP subsystem.
- Many feature and bug fixes, including bugs:
   77, 135, 179, 180, 181, 182, 189, 92, 114, 119,
   140, 175, 183, 184, 185, 191, 197, 198, 201, 203,
   161, 177, 190, 168

--

-- 
Mattias Nordstrom
CTO
Oy Realnode Ab

nordstrom <at> realnode.com
www.realnode.com

Polish translation ready

I have finished preliminary translation of Emilda 1.1.0 interface. It's
beta quality, and will be updated as soon as someone starts complain
about it. 

Skończyłem wstępne tłumaczenie interfejsu Emildy. Jest ono w wersji
beta, i zostanie uaktualnione, gdy tylko ktoś zacznie na nie narzekać, a
najlepiej zaproponuje lepsze tłumaczenie, pewnych wyrażeń.

Stąd http://www.alrc.epac.to/pol.xml można pobrać plik z tłumaczeniem,
który należy umieścić w katalogu "/lang/", a następnie ustawić w pliku
konfiguracyjnym "config" wartość "language = pol". 
Jeżeli po zalogowaniu, w miejsu polskich znaków diakrytycznych są
"krzaczki", należy ustawić prawidłowe kodowanie polskich znaków w
szablonach, tzn. jeżeli używasz domyślnego szablonu (default) to
powinieneś zmienić w pliku /templates/default/layout_header.inc wartość
zmiennej charset, na ISO-8859-2, tak jak poniżej:

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-2">

Pozdrawiam,

--

-- 
Lukasz Wilke <wilke <at> i-lo.debica.edu.pl>

Polish interface in Emilda 1.1.0

Hello,

Currently I'm finishing the polish translation of Emilda interface and
have some questions. On www.emilda.org it is mentioned that translations
shoud be made using gettex. Is it necessary to use gettex if XML does
the same work?
I created pol.xml file in /lang and set the proper charset (ISO-8859-2)
in my template, it works fine.
I've been thinking about moving to UTF-8 at some point in the future,
maybe that will solve charset/encoding problems.

I experience a problem at importing data from remote Z39.50, that serves
data in old windows-1250 encoding. Is it possible to recode records 'on
the fly' using some of Emilda's API ? If not how should I do it? (PHP
iconv, recode, extenal bash script) 

Sorry for my poor English.

Łukasz

--

-- 
Łukasz A. Wilke <wilke <at> i-lo.debica.edu.pl>

Emilda 1.2-alpha Released

Emilda 1.2-alpha has been released!

After six months of heavy development we bring you Emilda 1.2-alpha, the 
first preview release of the forthcoming Emilda 1.2 stable branch. This 
alpha brings you most of the new enchancements planned for Emilda 1.2, 
including better cataloguing using item types and subject headings, LDAP 
authentication, completely renewed configuration system using Control 
Panels, automated setup and upgrade, new database backend including 
cached queries and support for older 3.x MySQL servers, Gettext i18n and 
a new default template. This release brings lots of new features and is 
intended to be a preview release of upcoming features in 1.2, for the 
community. This is not a stable release for production environments. A 
list of planned features for 1.2 can be found at Emilda's Bugzilla 
database http://bugs.realnode.com/ (http://tinyurl.com/2sdcw).

For more information and downloads, please visit http://www.emilda.org/

ChangeLog:

  - New Search backend
  - Subjects
  - Item Types
  - Reports
  - Setup Page
  - Configuration within Emilda
  - MySQL Cache
  - Gettext
  - LDAP
  - New template: Pastill
  - Several minor feature enchancements and bug fixes.