| Author |
 Topic  |
|
GauravBhabu
Advanced Member
4288 Posts |
 Posted - 11 November 2001 : 03:23:46
|
Here is a Small function, which is all that needed for displaying the Dates, MonthNames and Weekday Names in the selected language
function LangName(sType,iNum,iFormat,iFirstDay)
dim NewLocale,CurrentLocale
on error resume next
CurrentLocale = GetLocale
NewLocale = SetLocale(strLangLCID)
if Err.number = 447 then
Err.Clear
NewLocale = SetLocale(CurrentLocale)
end if
Select Case sType
case "W"
LangName = WeekDayName(iNum,iFormat,iFirstDay)
Case "M"
LangName = MonthName(iNum,iFormat)
Case "D"
LangName = FormatDateTime(dInPut,iFormat)
end select
NewLocale = SetLocale(CurrentLocale)
end function
This function should be called as below:
For Weekday name Translations
LangName("W",WEEKDAY,FORMAT,FIRSTDAYOFWEEK)
W = Week
WEEKDAY = A number between 1 to 7
Format = 0 for Full and 1 for Abbreviated
FirstDayOFWeek = 1 for Sunday, 2 for Monday...
For MonthName Translations
LangName("M",Month,FORMAT,FIRSTDAYOFMONTH)
M = Month
MONTH = A number between 1 to 12
Format = 0 for Full and 1 for Abbreviated
FirstDayOFWeek = ""
For date Translations
LangName("D",DATE,FORMAT,FIRSTDAYOFMONTH)
D = Date
DATE = A valid Date
Format = vbLongDate or vbShortdate or vbGeneralDate
FirstDayOFWeek = ""
I have implemented it at my site . Works Okay. However Not all LCID's are supported. In that case the function will default Translation to the Server language. For me if I choose Turkish, it defaults to English, because of error trapping. Some one may check it.
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.
Edited by - GauravBhabu on 11 November 2001 06:24:32< |
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 11 November 2001 : 03:58:49
|
Translating Weekday names
Example Translation in swedish
<%
currentLocale = GetLocale
original = SetLocale("sv-se")
testdate = cDate(Date)
testday = WeekDayName(Weekday(testdate),0)
Response.Write testday
original = SetLocale(currentLocale)
%>
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.< |
 |
|
|
Deleted
deleted
4116 Posts |
Posted - 11 November 2001 : 07:54:16
|
Actually we neared to the solution before the server collapsed, but our digital brains are gone. Thank you starting the topic with a solution again.
A couple of questions:
1) Not all hosts have locale support.
2) Can this handle this case: The site is in Turkish, hosted in UK and most visitors are from Turkey, which will need to see it in Turkish style. These include not only the names of months and days, but also the style (dd.mm.yy, dd.mm.yyyy, dd/mm/yyyy, dd mmmm yyyy, etc). Also some countries use yyyy/mm/dd... If you switch the language the apperance will also change.
What we need is to have a more general set of routines. These will be the interface between the server, snitz database format, config table settings and desired output format for each LCID. I did not go into detail yet, but te mpst appropriate solution in my mind is:
1) To keep date-time related data in the language file (*all* those settings in Win systems)
a) Use them from there, and disregard the admin interface
b) Carry some of them to the admin interface for further customization (default language only). Those in the language files will be the defaults for that language.
2) Provide a library of routines for programmers (base code or MODs) with clear and easy to use interfaces.
3) Never use date-time format or similar routine related to the server - everything will be SW based and under our control.
What do you think?
Think Pink
Test Site not ready yet | Post v40b03 Patches< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 11 November 2001 : 12:20:17
|
quote:
1) Not all hosts have locale support.
Correct.
quote:
2) Can this handle this case: The site is in Turkish, hosted in UK and most visitors are from Turkey, which will need to see it in Turkish style. These include not only the names of months and days, but also the style (dd.mm.yy, dd.mm.yyyy, dd/mm/yyyy, dd mmmm yyyy, etc). Also some countries use yyyy/mm/dd... If you switch the language the apperance will also change.
I think yes. Because it takes LCID as selected from the drop down. below are the several ways, I have it in use on my site:
LangName("D",ChkDate(rs("Start_Date")),vbLongDate,"")
Returns a long date in locale specific language.
Ex
Returns lundi 11 novembre 2001 (when selected language is french)
left(LangName("W",1,1,intWeekStartDay),2)
Gets the left two chars of the weekday name in locale language
Returns a long weekday name
Ex.
Returns lun.(when seleced language is french) and the left function trims it to lu
LangName("W",1,0,intWeekStartDay)
Returns a long weekday name
Ex.
Returns lundi(when seleced language is french)
strMonthName = LangName("M",intThisMonth,0,1)
Returns the long Month Name
Ex.
intthisMonth = 11
Returns novembre (when French isselected)
quote:
What we need is to have a more general set of routines...
I had tried several options. Developed some routines. But the one using locale seems to be more effective. Though there is limitation of formats plus not all languages are supported with locale. But I think that can be achieved by customizing this function further on the lines of ChkDate and ChkTime Routines.
quote:
I did not go into detail yet, but te mpst appropriate solution in my mind is:
...
What do you think?
I have to do more experimenting and will share whatever results I achieve.
I have not had a chance of looking at the international version of Calendar yet. I do not know what changes have already been made.
However, I have several features for the Calendar currently in use
1)Select a weekday of choice as the starting day of the week.
2)A Calendar with no Relation with the events. Just Calendar.
3)Full Year Calendar
4)Full day Calendar
In my opinion, the Work on internationalization is Excellent and the development process is very organized. Cheers bozden!
Think Pink
Test Site not ready yet | Post v40b03 Patches
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.
Edited by - GauravBhabu on 11 November 2001 12:21:24< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 11 November 2001 : 13:51:34
|
Thank you for your kind words and support. There are four major things before a final release, which will take some effort:
1) Date-time related issues: We can solve it here
2) Setup & documentation related issues: I hope I can get some support from admins for the first as it must be error free, the second needs my time only
3) Collecting a good set (quantity and quality) of Language Packs: Main problem is the quality check.
4) Starting v4.0 compatible MODs: As the installations will need them desperately
And somewhere in the future (I hope not very far) both versions must be merged, and other admins and moderators must be capable to deal with v4.0.
Think Pink
Test Site not ready yet | Post v40b03 Patches< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 11 November 2001 : 14:41:09
|
Just one quicjk question on Dates. I think we might need to do away with admin choices for date format.
And basically have 3 or 4 different date formats as below
LongDate = November 11 2001
MediumDate = Nov 11 2001
ShortDate = 11/11/2001
And may be some more
ExtendedDate = Sunday, November 11 2001
DateTime = November 11 2001 02:18:00 PM
Format for each Language may be defined in the language files under select case statements.
I have also tried the below noted functions on my site. This works fine as long as we are not converting a date already converted into a language other then English back to a string. But I did develop a routine as a fix for that. I will test it and share the results with you and others.
function chkLangDate(fDate)
if fDate = "" then
exit function
end if
' if IsDate(fDate) then
select case strDateType
case "dmy"
chkLangDate = Mid(fDate,7,2) & "/" & _
Mid(fDate,5,2) & "/" & _
Mid(fDate,1,4)
case "mdy"
chkLangDate = Mid(fDate,5,2) & "/" & _
Mid(fDate,7,2) & "/" & _
Mid(fDate,1,4)
case "ymd"
chkLangDate = Mid(fDate,1,4) & "/" & _
Mid(fDate,5,2) & "/" & _
Mid(fDate,7,2)
case "ydm"
chkLangDate =Mid(fDate,1,4) & "/" & _
Mid(fDate,7,2) & "/" & _
Mid(fDate,5,2)
case "dmmy"
chkLangDate = Mid(fDate,7,2) & " " & _
LangMonthName(Mid(fDate,5,2),1) & " " & _
Mid(fDate,1,4)
case "mmdy"
chkLangDate = LangMonthName(Mid(fDate,5,2),1) & " " & _
Mid(fDate,7,2) & " " & _
Mid(fDate,1,4)
case "ymmd"
chkLangDate = Mid(fDate,1,4) & " " & _
LangMonthName(Mid(fDate,5,2),1) & " " & _
Mid(fDate,7,2)
case "ydmm"
chkLangDate = Mid(fDate,1,4) & " " & _
Mid(fDate,7,2) & " " & _
LangMonthName(Mid(fDate,5,2),1)
case "dmmmy"
chkLangDate = Mid(fDate,7,2) & " " & _
LangMonthName(Mid(fDate,5,2),0) & " " & _
Mid(fDate,1,4)
case "mmmdy"
chkLangDate = LangMonthName(Mid(fDate,5,2),0) & " " & _
Mid(fDate,7,2) & " " & _
Mid(fDate,1,4)
case "ymmmd"
chkLangDate = Mid(fDate,1,4) & " " & _
LangMonthName(Mid(fDate,5,2),0) & " " & _
Mid(fDate,7,2)
case "ydmmm"
chkLangDate = Mid(fDate,1,4) & " " & _
Mid(fDate,7,2) & " " & _
LangMonthName(Mid(fDate,5,2),0)
case else
chkLangDate = Mid(fDate,5,2) & "/" & _
Mid(fDate,7,2) & "/" & _
Mid(fDate,1,4)
End Select
' end if
end function
When there is no support for locale then we can call a function in the language file for the specific language. I have developed a function for that and will post it after I test it.
function LangWeekDayName(dInPut,iFormat,iFirstDay)
dim NewLocale,CurrentLocale
on error resume next
CurrentLocale = GetLocale
NewLocale = SetLocale(strLangLCID)
if Err.number = 447 then
Err.Clear
NewLocale = SetLocale(CurrentLocale)
end if
LangWeekDayName = WeekDayName(dInPut,iFormat,iFirstDay)
NewLocale = SetLocale(CurrentLocale)
end function
function LangMonthName(dInPut,iFormat)
dim NewLocale,CurrentLocale
on error resume next
CurrentLocale = GetLocale
NewLocale = SetLocale(strLangLCID)
if Err.number = 447 then
Err.Clear
NewLocale = SetLocale(CurrentLocale)
end if
LangMonthName = MonthName(dInPut,iFormat)
NewLocale = SetLocale(CurrentLocale)
end function
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.
Edited by - GauravBhabu on 11 November 2001 14:44:34< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 11 November 2001 : 16:07:42
|
quote:
Just one quicjk question on Dates. I think we might need to do away with admin choices for date format.
That is what I'm also thinking of. But for compatibility reasons we may like to keep them for default language.
quote:
And basically have 3 or 4 different date formats as below
LongDate = November 11 2001
MediumDate = Nov 11 2001
ShortDate = 11/11/2001
And may be some more
ExtendedDate = Sunday, November 11 2001
DateTime = November 11 2001 02:18:00 PM
I think there are more. In Turkey we use:
LongDate = 10 Kasım 2001
MediumDate = 10 Nov. 2001
ShortDate = 10/11/2001
Also we don't use AM/PM but 24 hour format usually.
I think its better to specify the format in LangNNNN.asp file and provide long and short alternatives. Such as:
LongDate = "dd mmmm yyyy dddd hh:mm:ss"
A solution for an interpretor was in this forum before the collapse.
quote:
Format for each Language may be defined in the language files under select case statements.
I think no. A library function must interprete these to output the string.
Library:
datetime2dbdatetime
dbdatetime2datetime
datetime2longdate
datetime2shortdate
etc
Think Pink
Test Site not ready yet | Post v40b03 Patches< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 11 November 2001 : 16:58:49
|
quote:
And basically have 3 or 4 different date formats as below
LongDate = November 11 2001
MediumDate = Nov 11 2001
ShortDate = 11/11/2001
And may be some more
quote:
I think there are more. In Turkey we use:
LongDate = 10 Kasım 2001
MediumDate = 10 Nov. 2001
ShortDate = 10/11/2001
quote:
A library function must interprete these to output the string.
Library:
datetime2dbdatetime
dbdatetime2datetime
datetime2longdate
datetime2shortdate
Correct, That is basically what I meant. By LongDate, MediumDate or Shortdate ExtendedDate, DateTime, I meant a format specific to each region.
select case strLangLCID
'################# TURKISH ####################
case "1055"
sLangLongMonths = "Ocak#Subat#Mart#Nisan#Mayis#Haziran#Temmuz#Augustos#"
sLangLongMonths = sLangLongMonths & "Eylül#Ekim#Kasim#Aralik"
sLangShortMonths = "Oca#Sub#Mar#Nis#May#Haz#Tem#Ağu#Eyl#Eki#Kas#Ara"
sLangLongDays = "nedelja#ponedeljek#torek#sreda#cetrtek#petek#sobota"
sLangShortDays = "Paz#Pts#Sa#Çar#Per#Cu#Cts"
'################# ENGLISH ####################
case "1033"
end select
Then I have this function in inc_functions.asp
'Input: iWhichMonth = 1 to 12;bAbbrv = 1 or 0
'sLangShortMonths and sLangLongMonths is defined in LangMODS
function fLangMonthName(iWhichMonth,bAbbrv)
if bAbbrv = 1 then
arrLangShortMonths = split(sLangShortMonths,"#",-1,1)
flangMonthName = arrlangShortMonths(iWhichMonth - 1)
end if
if bAbbrv = 0 then
arrLangLongMonths = split(sLangLongMonths,"#",-1,1)
fLangMonthName = arrLangLongMonths(iWhichMonth - 1)
end if
end function
'Input: iWeekday = 1 to 7;bAbbrv = 1 or 0
'sLangShortdays and sLangLongDays is defined in LangMODS
function fLangWeekDayName(iWeekday,bAbbrv)
if bAbbrv = 1 then
arrLangShortDays = split(sLangShortDays,"#",-1,1)
fLangWeekDayName = arrLangShortDays(iWeekday - 1)
end if
if bAbbrv = 0 then
arrLangLongDays = split(sLangLongDays,"#",-1,1)
fLangWeekDayName = arrLangLongdays(iWeekday - 1)
end if
end function
I call this from chkLangDate posted earlier or call from LangMonthName or LangWeekDayName when SetLocale is not available.
And There is scenario, when a datestring has been formatted specific to a particular region and that formatted date needs to be converted back to datestring for storing to the DB.
I think this can be achieved by referring to the same delimited string, which i used to get the name for the Month or the WeekDay. The strings specific to each language can be defined in a Library or a file or a function.
What is your opinion?
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.
Edited by - GauravBhabu on 11 November 2001 17:00:13< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 11 November 2001 : 18:25:15
|
Now I see the confusion about the select-case ! You only looked at LangMods*.asp structure. Please look in the distributed config.asp (bottom part), Lang1033.asp and Lang1055.asp. These is no select-case there. Depending on the "current user preferred language", only the instructions in one file are executed, although all are loaded by the server.
This is except the first part of each LangNNN.asp file, where the array of locale specific info is filled. This part can be used like "configuration" part, where we can set "first day of week", "AM/PM", 12/24 hour display, the date-time formats etc.
The actual month and day names for that language can go into the part after the if statement.
About the strings "Ocak#Şubat#...": Which one is better? Splitting over and over or just using an array in the language file to keep them. Then the function will retrieve them easily and also other MODs may use them as is just by looping. These arrays will be global!
I'm not sure I understood the last part. But I can remember of one more case: using a form input which must be interpreted (also error checking). If something like this goes in the library things will be easier for everybody.
Think Pink
Test Site not ready yet | Post v40b03 Patches< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 11 November 2001 : 21:45:57
|
quote:
This is except the first part of each LangNNN.asp file, where the array of locale specific info is filled. This part can be used like "configuration" part, where we can set "first day of week", "AM/PM", 12/24 hour display, the date-time formats etc.
That sounds good, I happen to see those files just before I read this post and was just thinking the same.
quote:
The actual month and day names for that language can go into the part after the if statement.
You mean Lang.NNNN file?
quote:
About the strings "Ocak#Şubat#...": Which one is better? Splitting over and over or just using an array in the language file to keep them. Then the function will retrieve them easily and also other MODs may use them as is just by looping. These arrays will be global!
It can be either way. Having an array will also be good and useful. Where do you want to define the arrays. It will require Four arrays, I think. Two for Month Names and two for Weekday Names.
quote:
I'm not sure I understood the last part. But I can remember of one more case: using a form input which must be interpreted (also error checking). If something like this goes in the library things will be easier for everybody.
For all date inputs, use numbers as values for months or Weekdays, so this will be same for all languages and error trapping routine will be same for each language, if this is what you meant. Just the display varies depending on the selected language.
Think Pink
Test Site not ready yet | Post v40b03 Patches
[/quote]
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 11 November 2001 : 23:08:03
|
arrLangMonthName(1,0) = "Ocak"
arrLangMonthName(1,1) = "Oca"
This is Same convention as
MonthName(1,0)= "January"
MonthName(1,1)= "Jan"
Dim arrLangMonthName(12,1)
Dim arrLangWeekDayName(7,1)
arrLangMonthName (0,0)= ""
arrLangMonthName (1,0)= "Ocak"
arrLangMonthName (2,0)= "Subat"
arrLangMonthName (3,0)= "Mart"
arrLangMonthName (4,0)= "Nisan"
arrLangMonthName (5,0)= "Mayis"
arrLangMonthName (6,0)= "Haziran"
arrLangMonthName (7,0)= "Temmuz"
arrLangMonthName (8,0)= "Augustos"
arrLangMonthName (9,0)= "Eylül"
arrLangMonthName (10,0)= "Ekim"
arrLangMonthName (11,0)= "Kasim"
arrLangMonthName (12,0)= "Aralik"
arrLangMonthName (0,1)= ""
arrLangMonthName (1,1)= "Oca"
arrLangMonthName (2,1)= "Sub"
arrLangMonthName (3,1)= "Mar"
arrLangMonthName (4,1)= "Nis"
arrLangMonthName (5,1)= "May"
arrLangMonthName (6,1)= "Haz"
arrLangMonthName (7,1)= "Tem"
arrLangMonthName (8,1)= "Ağu"
arrLangMonthName (9,1)= "Eyl"
arrLangMonthName (10,1)= "Eki"
arrLangMonthName (11,1)= "Kas"
arrLangMonthName (12,1)= "Ara"
arrLangWeekDayName (0,0)= ""
arrLangWeekDayName (1,0)= "nedelja"
arrLangWeekDayName (2,0)= "ponedeljek"
arrLangWeekDayName (3,0)= "torek"
arrLangWeekDayName (4,0)= "sreda"
arrLangWeekDayName (5,0)= "cetrtek"
arrLangWeekDayName (6,0)= "petek"
arrLangWeekDayName (7,0)= "sobota"
arrLangWeekDayName (0,0)= ""
arrLangWeekDayName (1,1)= "Paz"
arrLangWeekDayName (2,1)= "Pts"
arrLangWeekDayName (3,1)= "Sa"
arrLangWeekDayName (4,1)= "Çar"
arrLangWeekDayName (5,1)= "Per"
arrLangWeekDayName (6,1)= "Cu"
arrLangWeekDayName (7,1)= "Cts"
This also gives the flexibility to add the FirstDayOfWeek Dimension or other dimensions, keeping in with the convention. Same way I will construct the LangDates, ShortDates etc. What is your opinion?
I was just wondering what to do with
arrLangMonthName (0,0)= ""
arrLangMonthName (0,1)= ""
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.
Edited by - GauravBhabu on 12 November 2001 00:14:33< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 12 November 2001 : 02:25:17
|
The following function may be used for Displaying the dates in language specific format, when SetLacale is not available for a language.
This function is based on the following criteria
Snitz dates are stored as
YYYYMMDDhhmmss
For a Region with a date Format dd.mm.yyyy
I have defined a variable in the Lang file and populated as below:
fLangDateFormat = "725214"
72 Represents dd
52 represents mm
14 represents yyyy
Each digit in the fLangDateFormat is referred in sequence as highlighted below.
The first text in red = 7
The first text in blue = 2
Gets the date part from the string
The second text in red = 5
The second text in blue = 2
Gets the Month part from the string
The third text in red = 1
The third text in blue = 4
Gets the Year Part from the string
function ChkfLangDate(fDate)
Select Case sDateType
Case "fLangShort", "dmy","ymd","ydm","mdy"
chkfLangDate = Mid(fDate,Mid(fLangDateFormat,1,1),Mid(fLangDateFormat,2,1)) & "." & _
Mid(fDate,Mid(fLangDateFormat,3,1),Mid(fLangDateFormat,4,1)) & "." & _
Mid(fDate,Mid(fLangDateFormat,5,1),Mid(fLangDateFormat,6,1))
Case "fLangMedium","dmmy","ymmd","ydmm","mmdy"
chkfLangDate = Mid(fDate,Mid(fLangDateFormat,1,1),Mid(fLangDateFormat,2,1)) & " " & _
arLangMonthName(Mid(fDate,Mid(fLangDateFormat,3,1),Mid(fLangDateFormat,4,1)),1) & " " & _
Mid(fDate,Mid(fLangDateFormat,5,1),Mid(fLangDateFormat,6,1))
Case "fLangLong", "dmmmy","mmmdy","ydmmm","ymmmd"
chkfLangDate = Mid(fDate,Mid(fLangDateFormat,1,1),Mid(fLangDateFormat,2,1)) & " " & _
arrLangMonthName(Mid(fDate,Mid(fLangDateFormat,3,1),Mid(fLangDateFormat,4,1)),0) & " " & _
Mid(fDate,Mid(fLangDateFormat,5,1),Mid(fLangDateFormat,6,1))
Case "fLangDayDate"
'Not Defined Yet
Case else
chkfLangDate = Mid(fDate,Mid(fLangDateFormat,1,1),Mid(fLangDateFormat,2,1)) & "." & _
Mid(fDate,Mid(fLangDateFormat,3,1),Mid(fLangDateFormat,4,1)) & "." & _
Mid(fDate,Mid(fLangDateFormat,5,1),Mid(fLangDateFormat,6,1))
end Select
end function
This is basically same as function ChkDate.
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.
Edited by - GauravBhabu on 12 November 2001 02:39:04< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 12 November 2001 : 03:51:12
|
Tested the above concept and it works very nicely.
The Library if it be called consists of about
Eight small functions.
Two Arrays in the LangNNNN.asp file
1. arrLangMonthName
2. arrLangWeekdayName
Two New variables. May require Two More.
I will assemble these functions in a file and post a link for your review.
This so far takes care of displaying dates as defined in the LangNNNN.asp file. I hope to use the existig DateToStr function or a new function fLangDateToStr to change the Dates to strings for storing in the database.
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 12 November 2001 : 10:27:56
|
Great  .
Think Pink
Test Site not ready yet | Post v40b03 Patches< |
|
|
|
GauravBhabu
Advanced Member
4288 Posts |
Posted - 12 November 2001 : 11:29:14
|
Here
LangDatesLib
GauravBhabu
There is only one miracle...That is LIFE! | It is difficult to IMPROVE on Perfection, There is no harm in Keep Trying.< |
|
|
|
n/a
deleted
593 Posts |
Posted - 12 July 2002 : 16:14:27
|
Would like to see what this LangDateLib contains but cannot access a link....by any chance, do you have it - Bozden? And if you do, would you kindly share it for my reference....
Here is something I am trying to do, as mentioned elsewhere:
(1) To see whether an international date implementation can work with US format in 4 language environments - English_US, Japanese, and 2 flavors of Chinese...
(2) Set up Events Calender to handle these international date formats but also adjusted to output Far Eastern mid/long names and style.
This is really beyond what I perhaps can do but am getting a reasonable sense of what may be required for testing out... including some function codes mentioned here...
Thanks.
Taku
< |
|
|
|
Topic |
|
|
|
Forum Locked
