You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Reinhard K. <rei...@we...> - 2022-02-12 21:18:35
|
Xin chào! Does this list still work? Otherwise I'll remove the link to this list from the VnTeX documentation. Regards, Reinhard -- ------------------------------------------------------------------ Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ------------------------------------------------------------------ |
|
From: Nam N. <nam...@go...> - 2014-03-14 15:17:06
|
On Thu, Mar 13, 2014 at 6:47 PM, Reinhard Kotucha <rei...@we...>wrote: > On 2014-03-13 at 10:21:27 -0700, Nam Nguyen wrote: > > > > I doubt that I'm allowed to change licenses at will. Our > > > policy is to respect the licence of the supplier. > > > > I totally understand that. That's why I also sent to Han The Thanh > > whom I assume to be the author. Besides, I am not seeking for a > > total conversion of VnTeX package, just the fonts. > > Hi Nam, > Thành added Vietnamese glyphs to existing fonts from Bitstream and > URW, so he can't change the license either. > > > > I also don't see any reason to change licenses at all. > > > Everything provided by VnTeX can be used freely. It makes more > > > sense to ask Google to accept GPL and LPPL too. > > > > I am following up with Google Fonts on this too. At the same time, > > other font repositories seem to favor OFL the most. It makes sense > > to change one upstream source so that many downstream users can > > benefit from that. > > Good to hear, thanks. IMO it's better if other free licenses are > accepted as well. There are zillions of free fonts but only a few > font repositories. > > > Adopting OFL not only brings more exposure to the font but also can > > be done effortlessly by the authors. Adam Twardoch has analyzed the > > GFL (GUST Font License, as pertained to Latin Modern), LPPL and > > OFL. His conclusion is that the adoption of OFL satisfies both LPPL > > and GFL with only minimal text change. But it must be done by the > > copyright owners. > > There is no problem offering Latin Modern under OFL as well. It's > more difficult to put the TeX Gyre fonts under OFL because they are > based on the fonts released by URW under GPL. GUST got the permission > from URW to license TeX Gyre under GFL. IMO it's inappropriate to ask > URW again to accept OFL too. We should be glad that they offered the > font for free and we can't bother them again and again for no good > reason. GFL is appropriate for this purpose. > > I assume that Adam Twardoch is aware of these problems. He knows the > Latin Modern/TeX Gyre developers personally and unless something > unpredictable happens I'll meet them all at BachoTeX-2014 in May. > I could at least ask for a session where these things are discussed. > I'm quite interested in these things, especially because Adam Twardoch > said that if TeX fonts can be used on the Web, it has a direct impact > on the reputation of TeX. > > I doubt that the fonts provided by VnTeX are useful for anything > except 8-bit TeX engines. > > For HTML it's much better to use OpenType fonts. Type 1 based OTF can > be used directly and for TrueType based OTF (or TrueType fonts) it > makes sense to convert them WOFF. > > This means that instead of using the VnTeX URW fonts it's better to > use the TeX Gyre OTF fonts. Instead of VnTeX's Bitstream Charter, use > CharisSIL (which is under OFL, of course). > > Despite of the licence, did you try to use any of the fonts provided > by VnTeX as a Web font? I doubt that it works because metrics for > Vietnamese glyphs are only accessible by TeX. > > The advantage of TeX Gyre and Charis SIL is that they support many > languages. VnTeX supports only English and Vietnamese. > Reinhard, This has been a very helpful discussion. Thank you for your clarification and appropriate suggestions. It seems that pursuing those alternative fonts would yield a more comprehensive glyph coverage and less troublesome licensing workaround. Reinhard, it would be great if you could meet up with GUST people and Adam to hash this out at BachoTeX-2014. I can ping Dave from Google Fonts to see if he can make it there. I'm really excited about the prospect of having TeX fonts readily and pervasively available on the web. Thanks, Nam |
|
From: Reinhard K. <rei...@we...> - 2014-03-14 01:48:09
|
On 2014-03-13 at 10:21:27 -0700, Nam Nguyen wrote: > > I doubt that I'm allowed to change licenses at will. Our > > policy is to respect the licence of the supplier. > > I totally understand that. That's why I also sent to Han The Thanh > whom I assume to be the author. Besides, I am not seeking for a > total conversion of VnTeX package, just the fonts. Hi Nam, Thành added Vietnamese glyphs to existing fonts from Bitstream and URW, so he can't change the license either. > > I also don't see any reason to change licenses at all. > > Everything provided by VnTeX can be used freely. It makes more > > sense to ask Google to accept GPL and LPPL too. > > I am following up with Google Fonts on this too. At the same time, > other font repositories seem to favor OFL the most. It makes sense > to change one upstream source so that many downstream users can > benefit from that. Good to hear, thanks. IMO it's better if other free licenses are accepted as well. There are zillions of free fonts but only a few font repositories. > Adopting OFL not only brings more exposure to the font but also can > be done effortlessly by the authors. Adam Twardoch has analyzed the > GFL (GUST Font License, as pertained to Latin Modern), LPPL and > OFL. His conclusion is that the adoption of OFL satisfies both LPPL > and GFL with only minimal text change. But it must be done by the > copyright owners. There is no problem offering Latin Modern under OFL as well. It's more difficult to put the TeX Gyre fonts under OFL because they are based on the fonts released by URW under GPL. GUST got the permission from URW to license TeX Gyre under GFL. IMO it's inappropriate to ask URW again to accept OFL too. We should be glad that they offered the font for free and we can't bother them again and again for no good reason. GFL is appropriate for this purpose. I assume that Adam Twardoch is aware of these problems. He knows the Latin Modern/TeX Gyre developers personally and unless something unpredictable happens I'll meet them all at BachoTeX-2014 in May. I could at least ask for a session where these things are discussed. I'm quite interested in these things, especially because Adam Twardoch said that if TeX fonts can be used on the Web, it has a direct impact on the reputation of TeX. I doubt that the fonts provided by VnTeX are useful for anything except 8-bit TeX engines. For HTML it's much better to use OpenType fonts. Type 1 based OTF can be used directly and for TrueType based OTF (or TrueType fonts) it makes sense to convert them WOFF. This means that instead of using the VnTeX URW fonts it's better to use the TeX Gyre OTF fonts. Instead of VnTeX's Bitstream Charter, use CharisSIL (which is under OFL, of course). Despite of the licence, did you try to use any of the fonts provided by VnTeX as a Web font? I doubt that it works because metrics for Vietnamese glyphs are only accessible by TeX. The advantage of TeX Gyre and Charis SIL is that they support many languages. VnTeX supports only English and Vietnamese. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- |
|
From: Nam N. <nam...@go...> - 2014-03-13 17:21:35
|
On Wed, Mar 12, 2014 at 5:21 PM, Reinhard Kotucha <rei...@we...>wrote: > On 2014-03-12 at 16:01:46 -0700, Nam Nguyen wrote: > > > Google Fonts converts and hosts many free fonts for consumption on > > the web. > > > > Their requirement for inclusion in the directory is that the font > > must be licensed under the OFL or Apache 2.0 license. > > > > My question is if vntex fonts (URW, HungLan, etc) are easily > > convertible to OFL/Apache? Can that be done at all (i.e. all > > copyright owners approve of the adoption)? > > Dear Nam, > Hello Reinhard, > I doubt that I'm allowed to change licenses at will. Our > policy is to respect the licence of the supplier. > I totally understand that. That's why I also sent to Han The Thanh whom I assume to be the author. Besides, I am not seeking for a total conversion of VnTeX package, just the fonts. > > I also don't see any reason to change licenses at all. Everything > provided by VnTeX can be used freely. It makes more sense to ask > Google to accept GPL and LPPL too. > I am following up with Google Fonts on this too. At the same time, other font repositories seem to favor OFL the most. It makes sense to change one upstream source so that many downstream users can benefit from that. Adopting OFL not only brings more exposure to the font but also can be done effortlessly by the authors. Adam Twardoch has analyzed the GFL (GUST Font License, as pertained to Latin Modern), LPPL and OFL. His conclusion is that the adoption of OFL satisfies both LPPL and GFL with only minimal text change. But it must be done by the copyright owners. For example, in Adam's words: ========================= If the Copyright string for Latin Modern Roman says: Copyright 2003, 2006 B. Jackowski and J.M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font Source License -- see http://tug.org/fonts/licenses/GUST-FONT-SOURCE-LICENSE.txt for details. it would need to be changed to: Copyright 2003, 2006, 2014 B. Jackowski and J.M. Nowacki (on behalf of TeX users groups, with Reserved Font Names "Latin Modern" and "LMRoman". This work is simultaneously released under the GUST Font Source License (see http://tug.org/fonts/licenses/GUST-FONT-SOURCE-LICENSE.txt for details) and under the SIL Open Font License, Version 1.1 (see http://scripts.sil.org/OFLfor details). It would also be useful to put the following text into the License field of the font: This work is simultaneously released under the GUST Font Source License (see http://tug.org/fonts/licenses/GUST-FONT-SOURCE-LICENSE.txt for details) and under the SIL Open Font License, Version 1.1 (see http://scripts.sil.org/OFL for details). ======================== Thanks, Nam > > Regards, > Reinhard > > -- > > ---------------------------------------------------------------------------- > Reinhard Kotucha Phone: > +49-511-3373112 > Marschnerstr. 25 > D-30167 Hannover mailto: > rei...@we... > > ---------------------------------------------------------------------------- > Microsoft isn't the answer. Microsoft is the question, and the answer is > NO. > > ---------------------------------------------------------------------------- > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > vntex-users mailing list > vnt...@li... > http://lists.sourceforge.net/lists/listinfo/vntex-users > |
|
From: Reinhard K. <rei...@we...> - 2014-03-13 00:21:46
|
On 2014-03-12 at 16:01:46 -0700, Nam Nguyen wrote: > Google Fonts converts and hosts many free fonts for consumption on > the web. > > Their requirement for inclusion in the directory is that the font > must be licensed under the OFL or Apache 2.0 license. > > My question is if vntex fonts (URW, HungLan, etc) are easily > convertible to OFL/Apache? Can that be done at all (i.e. all > copyright owners approve of the adoption)? Dear Nam, I doubt that I'm allowed to change licenses at will. Our policy is to respect the licence of the supplier. I also don't see any reason to change licenses at all. Everything provided by VnTeX can be used freely. It makes more sense to ask Google to accept GPL and LPPL too. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- |
|
From: Nam N. <nam...@go...> - 2014-03-12 23:01:53
|
Hello list! Google Fonts converts and hosts many free fonts for consumption on the web. Their requirement for inclusion in the directory is that the font must be licensed under the OFL or Apache 2.0 license. My question is if vntex fonts (URW, HungLan, etc) are easily convertible to OFL/Apache? Can that be done at all (i.e. all copyright owners approve of the adoption)? Cheers, Nam |
|
From: Reinhard K. <rei...@we...> - 2010-09-30 00:28:29
|
On 29 September 2010 Fool wrote:
> On Tue, Sep 28, 2010 at 3:18 AM, Reinhard Kotucha
> <rei...@we...>wrote:
> > Another question is whether the first word should always be
> > capitalized. Currently \today expands to "Ngày 27 tháng 9 năm 2010".
> > But is it appropriate to capitalize the word "ngày" if one writes in a
> > letter, for instance, "Hà Nội, \today"? Do we need two macros, \today
> > and \Today?
> >
> if it's in the middle of sentence it's not capitalized, but if you
> want to stress a specific point, say "Friday the 13th" then it's
> "Thứ** Sáu ngày 13", in which case it's sort of a proper noun.
> I don't remember any rule of the vietnamese language that specify
> capitalization or noncapitalization of dates. It has very loose
> grammar/structure/rules. The only rule is beginning of sentence and
> proper nouns are capitalized.
>
> So yeah maybe two macros.
With \newdateformat this can be accomplished:
\newdateformat{lcdate}{ngày \THEDAY\ tháng \THEMONTH\ năm \THEYEAR}
\today\\
Hôm nay là \lcdate\today
gives:
Ngày 29 tháng 9 năm 2010
Hôm nay là ngày 29 tháng 9 năm 2010
> > And finally, I used the word "tư" for the number four, but I also
> > found "bốn". What's the difference and which one is preferred?
> >
> > "tư" is roughly equivalently to fourth and "bốn" is four.
> For dates it's always "thứ* *tư".
Thanks. I don't have a real dictionary, only a few traveller guides.
The German one seems to be better than the lonely planet Vietnamese
Phrasebook. The latter always uses "bốn" for dates. Ok, it's
American and many Americans don't distinguish between two, to, and too
either. ;)
> say if i do
> \newdateformat{mydate}{\THEYEAR-\twodigit\THEMONTH-\twodigit\THEDAY}
> \uselanguage{vietnamese}
> \today
> \mydate\today
> \uselanguage{english}
> \today
> \mydate\today
>
> then I would supposedly get
>
> Thứ** hai ngày 27 tháng 9 năm 2010
What do the asterisk denote?
> 2010-09-27
> Monday, 27th September 2010
> 2010-09-27
>
> right ?
Yes, you can do a lot with \newdateformat, at least if the components
of a date are numeric. I don't know how to deal with DoWs this way.
There is a table in dt-vietnamese.def which associates numbers with
strings, i.e.:
1 => Chủ nhật
2 => Thứ hai
3 => Thứ ba
4 => Thứ tư
5 => Thứ năm
6 => Thứ sáu
7 => Thứ bảy
I capitalized the words because in VnTeX's definition of \today, the
word "ngày" is capitalized too, so one gets similar results.
However, if you need the DoW lowercase, you actually need a second
table. There is no way to produce something like
Hôm nay là thứ hai ngày 27 tháng 9 năm 2010
at all ATM. The date itself is not a problem, you don't even need
datetime, you can entirely rely on TeX primitives:
\def\today{ngày \number\day\ tháng \number\month\ năm \number\year}
\def\Today{Ngày \number\day\ tháng \number\month\ năm \number\year}
The DoW is problematic because table lookups are required and at least
in Vietnamese, case matters.
> by the way, \twodigit\THEYEAR doesn't really exist does it ?
\twodigit does exactly what it's supposed to do. It expects a number
as an argument and if this number is smaller than 10, it prepends a
"0". This also works properly for \THEYEAR. :)
You probably have something like \def\twodigit#1#2#3#4{#3#4} in mind.
Well, I don't think that it's very difficult to implement this feature
for numbers > 999. But it's up to Nicola. IMO it's quite useful.
Regards, and thanks for the explanations,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover mailto:rei...@we...
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
|
|
From: Fool <fo...@gm...> - 2010-09-29 18:38:27
|
On Wed, Sep 29, 2010 at 1:35 PM, Fool <fo...@gm...> wrote:
>
>
> On Tue, Sep 28, 2010 at 3:18 AM, Reinhard Kotucha <rei...@we...
> > wrote:
>
>> On 25 September 2010 Reinhard Kotucha wrote:
>>
>> > On 25 September 2010 Fool wrote:
>>
>> Is Fool your real name?
>>
> Fortunately no lol. It's an alias handle that I grow accustomed to being
> called.
>
>
>> > > Hi everybody,
>> > > I have this problem with vntex and datetime.
>> > > Please see the attached .tex and .log.
>> > > I've updated all the packages (texlive 2010).
>> > > What should I do ?
>> >
>> > This is strange. It seems that whenever one switches to Vietnamese
>> > and than to any other language, captions and font encodings are set
>> > properly but dates are still typeset in Vietnamese. This leads to the
>> > error message "Command \abreve unavailable in encoding T1." it
>> > doesn't happen without datetime.
>> >
>> > I'll report it to Nicola.
>>
>> I did, and she told me that the reason is that datetime doesn't
>> support Vietnamese and thus falls back to babel.
>>
>> Today I added basic support for Vietnamese. The files are attached.
>>
>>
>>
>> Please do not distribute these files because it's an inofficial patch
>> and I'm not sure whether I did everything properly. It's best to copy
>> the files to the directory containing the TeX project you are working
>> on instead of installing them in a texmf tree.
>>
>> I also reported a problem which is not related to Vietnamese.
>> Whenever the "long" option is used, the year is in British format,
>> independent of the selected language.
>>
>> I need help now from people who actually speak Vietnamese. What I
>> have done so far is to provide the standard date format as already
>> provided by VnTeX, "Ngày 27 tháng 9 năm 2010". It works now as usual,
>> you get the same results with and without the datetime package and you
>> can switch between different languages.
>>
>> With datetime's "long" option you get "Thừ hai ngày 27 tháng 9, 2010".
>> The year isn't displayed properly, but as I said before, it isn't
>> displayed properly in any other language either.
>>
>> Do Vietnamese write a date like "Thừ hai ngày 27 tháng 9 năm 2010" at
>> all? The list of days of a week contains an entry "Thừ hai". But
>> since datetime doesn't only format dates but also calculates the DoW,
>> it also makes sense to support it without the rest of the date too.
>> But wouldn't one then write "ngày thừ hai"? This is difficult to
>> support currently, if at all. I could define DoW this way, but then
>> the complete date would be "ngày thừ hai ngày 27 tháng 9 năm 2010".
>> This looks strange, though I have no idea about proper Vietnamese.
>>
>> Yes we do say "*Thứ* hai ngày 27 tháng 9 năm 2010", for example
>
> Hôm nay là thứ** hai ngày 27 tháng 9 năm 2010.
>
> is equivalent to Today is monday the 27th of September, 2010.
>
> (
>
>
>
>> A very similar problem exists in German too. One would write
>> "Montag, 27. September 2010", but I don't see any way to insert the
>> comma after Montag in datetime.
>>
>> I think that the problem with datetime is that it tries to handle too
>> much itself instead of delegating things to the dt-<language>.def
>> files. Languages are too different.
>>
>> Another question is whether the first word should always be
>> capitalized. Currently \today expands to "Ngày 27 tháng 9 năm 2010".
>> But is it appropriate to capitalize the word "ngày" if one writes in a
>> letter, for instance, "Hà Nội, \today"? Do we need two macros, \today
>> and \Today?
>>
> if it's in the middle of sentence it's not capitalized, but if you want to
> stress a specific point, say "Friday the 13th" then it's "Thứ** Sáu ngày
> 13", in which case it's sort of a proper noun.
> I don't remember any rule of the vietnamese language that specify
> capitalization or noncapitalization of dates. It has very loose
> grammar/structure/rules. The only rule is beginning of sentence and proper
> nouns are capitalized.
>
> So yeah maybe two macros.
>
>
>
>>
>> Most languages don't have this problem because names of days and
>> months are always capitalized and in many languages the date begins
>> with a number, hence it doesn't matter whether it appears at the
>> beginning of a sentence or not.
>>
>> And finally, I used the word "tư" for the number four, but I also
>> found "bốn". What's the difference and which one is preferred?
>>
>> "tư" is roughly equivalently to fourth and "bốn" is four.
> For dates it's always "thứ* *tư".
>
>
>> I hope someone can tell me more about Vietnamese date formats. I'll
>> discuss it with Nicola then. But I fear that not everything can be
>> handled by datetime in its current state.
>>
>> say if i do
> \newdateformat{mydate}{\THEYEAR-\twodigit\THEMONTH-\twodigit\THEDAY}
> \uselanguage{vietnamese}
> \today
> \mydate\today
> \uselanguage{english}
> \today
> \mydate\today
>
> then I would supposedly get
>
> Thứ** hai ngày 27 tháng 9 năm 2010
> 2010-09-27
> Monday, 27th September 2010
> 2010-09-27
>
> right ?
>
> At which point is datetime kicking in and which point is vntex(babel) ?
>
> Thanks!
>
by the way, \twodigit\THEYEAR doesn't really exist does it ?
|
|
From: Fool <fo...@gm...> - 2010-09-29 18:35:13
|
On Tue, Sep 28, 2010 at 3:18 AM, Reinhard Kotucha
<rei...@we...>wrote:
> On 25 September 2010 Reinhard Kotucha wrote:
>
> > On 25 September 2010 Fool wrote:
>
> Is Fool your real name?
>
Fortunately no lol. It's an alias handle that I grow accustomed to being
called.
> > > Hi everybody,
> > > I have this problem with vntex and datetime.
> > > Please see the attached .tex and .log.
> > > I've updated all the packages (texlive 2010).
> > > What should I do ?
> >
> > This is strange. It seems that whenever one switches to Vietnamese
> > and than to any other language, captions and font encodings are set
> > properly but dates are still typeset in Vietnamese. This leads to the
> > error message "Command \abreve unavailable in encoding T1." it
> > doesn't happen without datetime.
> >
> > I'll report it to Nicola.
>
> I did, and she told me that the reason is that datetime doesn't
> support Vietnamese and thus falls back to babel.
>
> Today I added basic support for Vietnamese. The files are attached.
>
>
>
> Please do not distribute these files because it's an inofficial patch
> and I'm not sure whether I did everything properly. It's best to copy
> the files to the directory containing the TeX project you are working
> on instead of installing them in a texmf tree.
>
> I also reported a problem which is not related to Vietnamese.
> Whenever the "long" option is used, the year is in British format,
> independent of the selected language.
>
> I need help now from people who actually speak Vietnamese. What I
> have done so far is to provide the standard date format as already
> provided by VnTeX, "Ngày 27 tháng 9 năm 2010". It works now as usual,
> you get the same results with and without the datetime package and you
> can switch between different languages.
>
> With datetime's "long" option you get "Thừ hai ngày 27 tháng 9, 2010".
> The year isn't displayed properly, but as I said before, it isn't
> displayed properly in any other language either.
>
> Do Vietnamese write a date like "Thừ hai ngày 27 tháng 9 năm 2010" at
> all? The list of days of a week contains an entry "Thừ hai". But
> since datetime doesn't only format dates but also calculates the DoW,
> it also makes sense to support it without the rest of the date too.
> But wouldn't one then write "ngày thừ hai"? This is difficult to
> support currently, if at all. I could define DoW this way, but then
> the complete date would be "ngày thừ hai ngày 27 tháng 9 năm 2010".
> This looks strange, though I have no idea about proper Vietnamese.
>
> Yes we do say "*Thứ* hai ngày 27 tháng 9 năm 2010", for example
Hôm nay là thứ** hai ngày 27 tháng 9 năm 2010.
is equivalent to Today is monday the 27th of September, 2010.
(
> A very similar problem exists in German too. One would write
> "Montag, 27. September 2010", but I don't see any way to insert the
> comma after Montag in datetime.
>
> I think that the problem with datetime is that it tries to handle too
> much itself instead of delegating things to the dt-<language>.def
> files. Languages are too different.
>
> Another question is whether the first word should always be
> capitalized. Currently \today expands to "Ngày 27 tháng 9 năm 2010".
> But is it appropriate to capitalize the word "ngày" if one writes in a
> letter, for instance, "Hà Nội, \today"? Do we need two macros, \today
> and \Today?
>
if it's in the middle of sentence it's not capitalized, but if you want to
stress a specific point, say "Friday the 13th" then it's "Thứ** Sáu ngày
13", in which case it's sort of a proper noun.
I don't remember any rule of the vietnamese language that specify
capitalization or noncapitalization of dates. It has very loose
grammar/structure/rules. The only rule is beginning of sentence and proper
nouns are capitalized.
So yeah maybe two macros.
>
> Most languages don't have this problem because names of days and
> months are always capitalized and in many languages the date begins
> with a number, hence it doesn't matter whether it appears at the
> beginning of a sentence or not.
>
> And finally, I used the word "tư" for the number four, but I also
> found "bốn". What's the difference and which one is preferred?
>
> "tư" is roughly equivalently to fourth and "bốn" is four.
For dates it's always "thứ* *tư".
> I hope someone can tell me more about Vietnamese date formats. I'll
> discuss it with Nicola then. But I fear that not everything can be
> handled by datetime in its current state.
>
> say if i do
\newdateformat{mydate}{\THEYEAR-\twodigit\THEMONTH-\twodigit\THEDAY}
\uselanguage{vietnamese}
\today
\mydate\today
\uselanguage{english}
\today
\mydate\today
then I would supposedly get
Thứ** hai ngày 27 tháng 9 năm 2010
2010-09-27
Monday, 27th September 2010
2010-09-27
right ?
At which point is datetime kicking in and which point is vntex(babel) ?
Thanks!
|
|
From: Reinhard K. <rei...@we...> - 2010-09-28 08:19:01
|
On 25 September 2010 Reinhard Kotucha wrote: > On 25 September 2010 Fool wrote: Is Fool your real name? > > Hi everybody, > > I have this problem with vntex and datetime. > > Please see the attached .tex and .log. > > I've updated all the packages (texlive 2010). > > What should I do ? > > This is strange. It seems that whenever one switches to Vietnamese > and than to any other language, captions and font encodings are set > properly but dates are still typeset in Vietnamese. This leads to the > error message "Command \abreve unavailable in encoding T1." it > doesn't happen without datetime. > > I'll report it to Nicola. I did, and she told me that the reason is that datetime doesn't support Vietnamese and thus falls back to babel. Today I added basic support for Vietnamese. The files are attached. |
|
From: Reinhard K. <rei...@we...> - 2010-09-25 21:50:19
|
On 25 September 2010 Fool wrote: > Hi everybody, > I have this problem with vntex and datetime. > Please see the attached .tex and .log. > I've updated all the packages (texlive 2010). > What should I do ? This is strange. It seems that whenever one switches to Vietnamese and than to any other language, captions and font encodings are set properly but dates are still typeset in Vietnamese. This leads to the error message "Command \abreve unavailable in encoding T1." it doesn't happen without datetime. I'll report it to Nicola. Thanks for your report. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- |
|
From: Fool <fo...@gm...> - 2010-09-25 19:10:57
|
Hi everybody, I have this problem with vntex and datetime. Please see the attached .tex and .log. I've updated all the packages (texlive 2010). What should I do ? Thanks. |
|
From: Prabhu_Pushpanathan <Pra...@ma...> - 2009-11-09 10:35:49
|
Thanks for the prompt reply.
> I can't run your example because you are using fonts I don't have installed on my system. Are you using the Bitstream Cyberbit fonts?
Yes. I am using Cyberbit fonts.
My tex file consists of many language fonts. In my tex file I am using a command "SectionHeaderFont" to define the header font.
\newcommand{\SectionHeaderFont}{%
\fontsize{12}{12}\usefont{T1}{phv}{b}{n}}
Here as I use T1 enc, I am getting error for Vietnamese fonts (because Vietnamese support only T5 enc). I think replacing the T1 to T5 enc can solve the Vietnamese font problem but may produce weird results for other countries.
So I have removed "\usefont{T1}{phv}{b}{n}" and replaced with individual parameter (excluding the fontencoding) that is "\fontfamily{phv}\fontseries{b}\fontshape{n} \selectfont". This solves my enc problem.
Is the above solution looks good? Or is there any other best solution to solve this?
And
Using "\usepackage{babel}" for Vietnam throws below error.
"! Package babel Error: You haven't specified a language option."
And by replacing it with "\usepackage[vietnam]{babel}" solves the problem.
Can you tell me, "\usepackage[vietnam]{babel} includes only Vietnam language? And What "\usepackage{babel}" will do ?
Thanks.
DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
|
|
From: Reinhard K. <rei...@we...> - 2009-11-07 22:01:56
|
On 6 November 2009 Prabhu_Pushpanathan wrote:
> I am working in GNU/Linux operating system. Here I have attached
> the requested log file (vntex-example.log).
Hi,
I'm not sure whether it matters, but your TeX distribution is very
old. It's very hard to compare the log files:
| < Package: babel 2008/07/06 v3.8l The Babel package
| > Package: babel 2004/11/20 v3.8d The Babel package
| < File: babel.def 2008/07/06 v3.8l Babel common definitions
| > File: babel.def 2004/11/20 v3.8d Babel common definitions
> Also find the attachment myViet.zip which contains a myViet.tex and
> myViet.log file. In myViet.tex I have used CJK package to generate
> Vietnamese output. Please look at the output font.
It's probably wrong to typeset Vietnamese within a CJK environment. I
can't run your example because you are using fonts I don't have
installed on my system. Are you using the Bitstream Cyberbit fonts?
I get error messages like:
kpathsea: Running mktexmf cyberb1e
You don't need them for Vietnamese, all fonts you need for typesetting
Vietnamese are provided by VnTeX.
> I have also generated output without CJK package using T5
> fontenc. The both fonts look different.
>
> Your vntex-example.tex has T5 fontenc. Please let me know for
> producing Vietnamese output
>
> 1. We should use only T5 fontenc?
For Vietnamese, yes.
> 2. Can we use CJK package for Vietnam? (For Japanese I use CJK
> package with ipagp font and for Thai I use CJK package with
> default font)
You don't need the CJK package for Vietnamese. If you are using babel,
you can switch between languages using the command \selectlanguage.
But you shouldn't do this inside a CJK environment, but I must admit
that I don't know anything about CJK.
Maybe it's helpful to read the VnTeX documentation. Please try:
find /home/pushpanp/mytex -name vntex.pdf -exec acroread '{}' \;
Regards,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover mailto:rei...@we...
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
|
|
From: Prabhu_Pushpanathan <Pra...@ma...> - 2009-11-06 09:49:07
|
I am working in GNU/Linux operating system. Here I have attached the requested log file (vntex-example.log). Also find the attachment myViet.zip which contains a myViet.tex and myViet.log file. In myViet.tex I have used CJK package to generate Vietnamese output. Please look at the output font. I have also generated output without CJK package using T5 fontenc. The both fonts look different. Your vntex-example.tex has T5 fontenc. Please let me know for producing Vietnamese output 1. We should use only T5 fontenc? 2. Can we use CJK package for Vietnam? (For Japanese I use CJK package with ipagp font and for Thai I use CJK package with default font) Thanks. -----Original Message----- From: rei...@we... [mailto:rei...@we...] Sent: Friday, November 06, 2009 1:52 AM To: vnt...@li... Cc: Prabhu_Pushpanathan Subject: Re: [vntex-users] CJK Package Vietnamese font support On 5 November 2009 Prabhu_Pushpanathan wrote: > Hi, > I have installed CJK package in my system and I believe that CJK > provides Vietnamese support. > > With is I can able to produce Vietnamese output. But I am not > getting the appropriate Vietnamese fonts. I tried installing the > vntex-3.1.9 Package. Even then I get the same output. > > My installation steps for vntex-3.1.9 are unpacking the folder and > adding the map files to updmap.cfg file and running updmap, texhash > and mktexlsr. Hi, the installation steps look correct. However, VnTeX is already part of all major TeX distributions. TeX Live and MikTeX allow you to update your TeX system and you don't have to install anything yourself. In order to be more helpful, we need more information. Which TeX distribution and which operating system are are you using? updmap is implemented differently in TeX Live and MikTeX. Could you please extract the attached file and then run pdflatex vntex-example.tex and post the content of vntex-example.log to this list? I don't know whether the list server removes attachments. DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. |
|
From: Reinhard K. <rei...@we...> - 2009-11-05 20:22:52
|
On 5 November 2009 Prabhu_Pushpanathan wrote: > Hi, > I have installed CJK package in my system and I believe that CJK > provides Vietnamese support. > > With is I can able to produce Vietnamese output. But I am not > getting the appropriate Vietnamese fonts. I tried installing the > vntex-3.1.9 Package. Even then I get the same output. > > My installation steps for vntex-3.1.9 are unpacking the folder and > adding the map files to updmap.cfg file and running updmap, texhash > and mktexlsr. Hi, the installation steps look correct. However, VnTeX is already part of all major TeX distributions. TeX Live and MikTeX allow you to update your TeX system and you don't have to install anything yourself. In order to be more helpful, we need more information. Which TeX distribution and which operating system are are you using? updmap is implemented differently in TeX Live and MikTeX. Could you please extract the attached file and then run pdflatex vntex-example.tex and post the content of vntex-example.log to this list? I don't know whether the list server removes attachments. |
|
From: Prabhu_Pushpanathan <Pra...@ma...> - 2009-11-05 07:47:42
|
Hi, I have installed CJK package in my system and I believe that CJK provides Vietnamese support. With is I can able to produce Vietnamese output. But I am not getting the appropriate Vietnamese fonts. I tried installing the vntex-3.1.9 Package. Even then I get the same output. My installation steps for vntex-3.1.9 are unpacking the folder and adding the map files to updmap.cfg file and running updmap, texhash and mktexlsr. Please guide me in getting the right Vietnamese fonts. Thanks. ________________________________ DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. |
|
From: Reinhard K. <rei...@we...> - 2009-07-20 00:40:52
|
Hi, unfortunately there is a severe bug VnTeX 3.1.8. It's fixed now in version 3.1.9. You can download the latest version either as .zip or as .tar.bz2 from sourceforge.net. http://vntex.sourceforge.net/download/vntex/vntex-3.1.9.zip http://vntex.sourceforge.net/download/vntex/vntex-3.1.9.tar.bz2 It's also available from CTAN and a few hours ago it had been uploaded to the TeX Live repository. TeX Live users are not affected because the broken version 1.3.8 was published after the TeX Live package updater had been switched off. Thus, TL-2008 still provides 3.1.7 and TL-2009 will provide 3.1.9. MikTeX users are advised to check whether package updates are available. Only users who downloaded and installed VnTeX-3.1.8 manually has to upgrade to 3.1.9 (manually again). Please apologize for the inconvenience. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- |
|
From: Reinhard K. <rei...@we...> - 2009-05-13 20:39:45
|
Hi, I just prepared a new VnTeX release. It's already available from souceforge.net and CTAN. Download either the .zip or the .tar.bz file. http://vntex.sourceforge.net/download/vntex/vntex-3.1.8.zip http://vntex.sourceforge.net/download/vntex/vntex-3.1.8.tar.bz2 If you don't have the nonfree fonts installed already, you can optionally download: http://vntex.sourceforge.net/download/vntex/vntex-nonfree-3.1.8.zip http://vntex.sourceforge.net/download/vntex/vntex-nonfree-3.1.8.tar.bz2 Please note that there had been no changes since vntex-nonfree-3.1.3 and hence, there is no reason to update. TeX Live users can use the program getnonfreefonts in order to install them automaticallỵ New in VnTeX 3.1.8: * There is a new package vntex.sty, proposed by Huỳnh Kỳ Anh, which uses UTF-8 by default. It is preferred for new documents. Currently, the only difference between vietnam.sty and vntex.sty is the default input encoding. * Both, vietnam.sty and vntex.sty have a new option "cmap". It is it is recommended to use it whenever creating PDF. It makes PDF files searchable. * A minor bug had been fixed by Hàn Thế Thành in Vietnamese CM Bright and Concrete fonts. However, this bug never caused any problems. * The text file vntex.txt had been replaced by a PDF file "vntex.pdf". The reason is the new documentation browser in TeX Live. If you type "texdoc vntex" on the command line, vntex.pdf will be displayed in your favourite PDF browser. It contains hyperlinks to all the other PDF files which are part of VnTeX. * Many files had been moved from the doc/ direrectory to source/. This had been done for two reasons: 1. texdoc formerly found too many files which were not really documentation. 2. The TeX Live installer can be instructed not to install any sources. It's useful if you want to install a live system on a USB stick. In order to keep such a system small, everything which an end user doesn't need had been moved to the source directorỵ If you want to upgrade, follow the instructions given in the README and INSTALL files. If you have any questions, ask on this mailing list. However, there is no need to upgrade if you are not interested in the new features. Fortunately, there are no known bugs in older releases which make an upgrade necessarỵ Enjoy, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- |
|
From: Reinhard K. <rei...@we...> - 2008-12-22 21:29:55
|
Peter Prevos writes: > Hi all, > > I am an MBA student and am writing an essay about the Vietnamese > economy. I managed to install and use vntex and following the > instructions in "Minimal steps to typeset Vietnamese" works very well. > > But, there is no capital D with the little line through it (as in Doi > Moi). I now use \dj for the small version. How do I typeset the capital? Hi Peter, you are right, this is missing in the documentation. The capital version is \DJ, as defined in t5enc.def, line 306. The documentation will be fixed in the next release. Thanks for reporting the problem. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:rei...@we... ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- |
|
From: Peter P. <pe...@pr...> - 2008-12-22 19:34:50
|
Hi all, I am an MBA student and am writing an essay about the Vietnamese economy. I managed to install and use vntex and following the instructions in "Minimal steps to typeset Vietnamese" works very well. But, there is no capital D with the little line through it (as in Doi Moi). I now use \dj for the small version. How do I typeset the capital? Regards Peter |
|
From: Reinhard K. <rei...@we...> - 2007-05-28 08:25:06
|
>>>>> "sehar" == sehar tahir <seh...@ya...> writes:
> Hi All, I want to use TimesTen font with T5 encoding. My document
> has some vietnam characters. Can anybody help me about how to
> convert this font to support T5 encoding.. Please its urgent.
Hi,
I suppose that you mean Times Ten from Linotype. I just looked at
Linotype's home page and it seems that this font does not support
Vietnamese. If this is true you have to use a program which allows
you to modyfy the font, like FontForge. But I suppose the license of
the font does not allow any modification.
One way to create Vietnamese characters is to fake them on TeX macro
level. Here is one example which is supposed to be used with Palatino
(mathpazo.sty):
\def\Nguyen{\bgroup\setbox0=\hbox{\^e}Nguy\rlap
{\kern.5\wd0\raise.4ex\hbox to\z@{\hss\~{}\hss}}\box0n\egroup}
It doesn't make much fun. Maybe dblaccnt.sty is helpful.
However, it seems that Times Ten is a Times-like font and you can try
to switch to URW Times provided by the urwvn package temporarily in
order to typeset Vietnamese.
Regards,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover mailto:rei...@we...
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
|
|
From: sehar t. <seh...@ya...> - 2007-05-28 06:40:12
|
Hi All,
I want to use TimesTen font with T5 encoding. My
document has some vietnam characters. Can anybody help
me about how to convert this font to support T5
encoding.. Please its urgent.
Thanks
____________________________________________________________________________________Ready for the edge of your seat?
Check out tonight's top picks on Yahoo! TV.
http://tv.yahoo.com/
|
|
From: bogo l. <bog...@gm...> - 2006-04-17 04:06:08
|
Reinhard, thank you for your help; i sincerely appreciate it. sorry about the late response, i have been busy with the document ;]. yes, using lmodern does seem to be fine. thank you again. |
|
From: Reinhard K. <rei...@we...> - 2006-04-06 18:51:52
|
Hello,
>>>>> <bog...@gm...> writes:
> i am using vntex to typeset some documents; however, when i do a
> \tableofcontent or \bibliography.. the titles appear in vietnamese
> (instead of saying TABLE OF CONTENTS / BIBLIOGRAPHY /INDEX etc..);
> how do i revert back to the normal behavior?
\usepackage[vietnam,english]{babel}
The last language is the default language. You can switch between
languages:
\selectlanguage{vietnam}
...text in vietnamese...
\foreignlanguage{english}{a phrase in english}
...text in vietnamese...
\begin{otherlanguage}{english}
...text in english...
\end{otherlanguage}
...text in vietnamese...
> also, the font (vnr) seems to have some weird problem with
> characters like \d{m} (as in the sanskrit Sa\d{m}gha); the period
> appears too close to the bottom of the 'm', making it almost
> invisible. To resolve t his problem, i had to switch back to cmr
> when typing sanskrit/pali romanization. is there another
> workaround for this?
Thank you very much for reporting this. I think that the problem is
not in the font itself but in the metrics.
VNR is supposed to support Vietnamese only. For multilingual
documents it is better to use Latin Modern (\usepackage{lmodern})
which is a replacement for Knuth's Computer Modern fonts. Latin
Modern supports all Latin languages except some African ones. I don't
know whether there are all glyphs available people need for
transliterations, but composing glyphs like in CMR or VNR is still possible.
http://www.ctan.org/tex-archive/fonts/lm
If you are interested in Latin Modern, please make sure you have the
latest version and if you enconter similar problems as with VNR,
please contact Boguslaw <B_J...@gu...> soon.
Boguslaw announced that he will release version 1.0 within the next
few weeks (I suppose end of the month because I think he wants to make
an announcement at the GUST conference). It would be very nice if any
bugs you find can be fixed before.
There are certainly not many people who need \d{m} and most people do
not provide the feedback necessary for fixing such problems. Hence,
your feedback is highly appreciated.
I would be very glad if you try Latin Modern and report problems to
Boguslaw.
Thanh, can you put the \d{m} issue into your TODO list?
Regards,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover mailto:rei...@we...
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
|